Changes between Version 1 and Version 2 of CodeCampV/Planning/WorkingGroups/Richard


Ignore:
Timestamp:
Oct 6, 2016 3:30:39 PM (5 years ago)
Author:
richardh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • CodeCampV/Planning/WorkingGroups/Richard

    v1 v2  
    33Novice users should not "need to know hidden features" 
    44 
    5 "fit pages" have compute & fit buttons, could also have "save fit" and "report" buttons.  
    6           "save fit" could put up a list of "fit, P(Q), S(Q), unsmeared, etc" to choose from. [FISH does this] 
     5"fit pages" have compute & fit buttons, could also have "save fit" and "report" buttons, even "save model".  
     6          "save fit" could put up a list of "fit, P(Q), S(Q), unsmeared, etc" to choose which to save. [FISH does this] 
    77 
    88It is very tedious at present to use the same model on a different data set. 
    99Either - get the "data source" drop down at top of fit page to work to change data 
    10 Or - change "send to" then "fitting" to have "current fit page" or "new fit page"  
     10Or - change "send to" then "fitting" to instead have "current fit page" or "new fit page"  
    1111 
    1212 
     
    2121called inside polydispersity integrations for say Rcore , which may not be possible here. [FISH does this] 
    2222 
     23The fitting methods that hide inside "fitting" / "fit options" menu should be much more obvious and have explanations 
     24e.g. DREAM (aka Bumps? )has no explanation. 
     25 
     26 
     27Adding custom models is good, but duplicate "tools" / "python shell/editor" inside the "fitting" / "Edit custom model" menu please. 
    2328 
    2429 
    2530 
     31 
     32