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


Ignore:
Timestamp:
Oct 9, 2016 10:36:33 AM (7 years ago)
Author:
smk78
Comment:

Legend:

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

    v2 v3  
    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 instead have "current fit page" or "new fit page"  
     10Or - change "send to" then "fitting" to instead have "current fit page" or "new fit page" - '''Now #747''' 
    1111 
    1212 
    1313Could possibly save results of every fit so that "wind back" to previous results  
    14 is possible - but could get very messy for simultaneous fits etc. 
     14is possible - but could get very messy for simultaneous fits etc. - '''Now #745''' 
    1515 
    1616Need look at constraints & polydispersity again.  
     
    1919this requires constraint for Tshell = Rcore(C-1)  where C can be fitted. 
    2020This would save having to write variant models, BUT constraints may need to be  
    21 called inside polydispersity integrations for say Rcore , which may not be possible here. [FISH does this] 
     21called inside polydispersity integrations for say Rcore , which may not be possible here. [FISH does this] - '''Now #746''' 
    2222 
    2323The fitting methods that hide inside "fitting" / "fit options" menu should be much more obvious and have explanations 
    24 e.g. DREAM (aka Bumps? )has no explanation. 
    25  
     24e.g. DREAM (aka Bumps? )has no explanation. - '''SELECTING AN OPTIMISER IN FIT OPTIONS AND CLICKING THE HELP BUTTON BRINGS UP THE DOCUMENTATION FOR THAT OPTIMISER''' 
    2625 
    2726Adding custom models is good, but duplicate "tools" / "python shell/editor" inside the "fitting" / "Edit custom model" menu please.