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

Timestamp:

Oct 9, 2016 12:36:33 PM (8 years ago)

Author:

smk78

Comment:

—

CodeCampV/Planning/WorkingGroups/Richard

@@ -8 +8 @@
 It is very tedious at present to use the same model on a different data set.
 Either - get the "data source" drop down at top of fit page to work to change data
-Or - change "send to" then "fitting" to instead have "current fit page" or "new fit page" 
+Or - change "send to" then "fitting" to instead have "current fit page" or "new fit page" - '''Now #747'''
 
 
 Could possibly save results of every fit so that "wind back" to previous results 
-is possible - but could get very messy for simultaneous fits etc.
+is possible - but could get very messy for simultaneous fits etc. - '''Now #745'''
 
 Need look at constraints & polydispersity again. 
@@ -19 +19 @@
 this requires constraint for Tshell = Rcore(C-1)  where C can be fitted.
 This would save having to write variant models, BUT constraints may need to be 
-called inside polydispersity integrations for say Rcore , which may not be possible here. [FISH does this]
+called inside polydispersity integrations for say Rcore , which may not be possible here. [FISH does this] - '''Now #746'''
 
 The fitting methods that hide inside "fitting" / "fit options" menu should be much more obvious and have explanations
-e.g. DREAM (aka Bumps? )has no explanation.
-
+e.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'''
 
 Adding custom models is good, but duplicate "tools" / "python shell/editor" inside the "fitting" / "Edit custom model" menu please.