source: sasview/park_integration/docs/requirements.txt @ 4c2c93f

ESS_GUIESS_GUI_DocsESS_GUI_batch_fittingESS_GUI_bumps_abstractionESS_GUI_iss1116ESS_GUI_iss879ESS_GUI_iss959ESS_GUI_openclESS_GUI_orderingESS_GUI_sync_sascalccostrafo411magnetic_scattrelease-4.1.1release-4.1.2release-4.2.2release_4.0.1ticket-1009ticket-1094-headlessticket-1242-2d-resolutionticket-1243ticket-1249ticket885unittest-saveload
Last change on this file since 4c2c93f was 4a0536a, checked in by Gervaise Alina <gervyh@…>, 17 years ago

some work done.only our fit is working.thing about hoe to make the engine_fit method…learning about the other fit

  • Property mode set to 100644
File size: 658 bytes
Line 
1Functional Requirements:
2
3 - Client should be able to set models
4 - Client should be able to set data sets
5 - Client should be able to enter constraints
6 - Client should be able to start a fit
7 - Client should be able to access the results of a fit
8 
9 Non-Functional Requirements:
10 - Models and Data belong in their own class
11 - Data loader should be external to the module
12 - The Models should be compatible with SANS models
13 
14 
15 Risks:
16 - Can we run Park standalone without a server?
17 - Can we define an interface to Park that is as simple as scipy.optimizer?
18 
19 [ALINA] Am I on the right track?
20 please take a look at the uml diagram...
Note: See TracBrowser for help on using the repository browser.