Changes between Version 50 and Version 51 of CodeCampIII

Timestamp:

Feb 26, 2015 10:40:07 PM (10 years ago)

Author:

butler

Comment:

fixed CamelCase autolinkings

CodeCampIII

@@ -50 +50 @@
 With respect to that second theme, getting a developer environment properly installed has historically been a huge barrier, both for “amateur” developers lacking experience in installing the plethora of required packages and getting them running together, and for more professional programmers who may have a number of the wrong versions of required packages already installed.  To address both issues as well as others, such as ensuring that new required packages get propagated easily to developers and build machines, the Anaconda scientific python distribution was explored. This looks like a promising solution and significant progress was made in implementing it. 
 
-In order to address the third theme, a very large effort to completely restructure the models interface, move models into an independent package and support GPU computing was begun and while not finished progressed far enough that a code branch integrating the new sasmodels package into sasview was created. Approximately a quarter of the existing models were moved to the new package during the code camp. The next steps are to move the remaining models, integrate magnetic models, ensure full test coverage and generate a build with the new package for beta testing. This work was more ambitious than originally envisaged, but it provides major advantages and it was determined that it was better done as one integrated effort rather than piece by piece.  When complete, the learning curve for developers adding a new model should drop from many days to a few hours while implementing a new model should also drop from a day or more to a few hours at most.  User supplied models will have full access to the SasView infrastructure (in particular the polydispersity) and will be able to be supplied in C as well as python. As an added bonus, SasView will gain transparent access to multiprocessing and GPUs on many computers.
+In order to address the third theme, a very large effort to completely restructure the models interface, move models into an independent package and support GPU computing was begun and while not finished progressed far enough that a code branch integrating the new sasmodels package into !SasView was created. Approximately a quarter of the existing models were moved to the new package during the code camp. The next steps are to move the remaining models, integrate magnetic models, ensure full test coverage and generate a build with the new package for beta testing. This work was more ambitious than originally envisaged, but it provides major advantages and it was determined that it was better done as one integrated effort rather than piece by piece.  When complete, the learning curve for developers adding a new model should drop from many days to a few hours while implementing a new model should also drop from a day or more to a few hours at most.  User supplied models will have full access to the !SasView infrastructure (in particular the polydispersity) and will be able to be supplied in C as well as python. As an added bonus, !SasView will gain transparent access to multiprocessing and GPUs on many computers.
 
-The SESANS project, a completely new feature, championed by the delft group, progressed remarkably rapidly partly aided by the new models interface.  The data is now recognized by and can be loaded into SasView.  Further, the current sasmodels can be used (by running through a Henkel transform routine), in conjunction with BUMPS optimization engine, to fit the data. Thus SESANS data can now be analyzed with SASVIEW using the command line using any models which have been ported to the new structure.  Adding support for analytical SESANS models and Fully integrating with the GUI will be the next steps. 
+The SESANS project, a completely new feature, championed by the delft group, progressed remarkably rapidly partly aided by the new models interface.  The data is now recognized by and can be loaded into !SasView.  Further, the current sasmodels can be used (by running through a Henkel transform routine), in conjunction with BUMPS optimization engine, to fit the data. Thus SESANS data can now be analyzed with !SasView using the command line using any models which have been ported to the new structure.  Adding support for analytical SESANS models and Fully integrating with the GUI will be the next steps. 
 
-Finally, the group spent a half day discussing the long term needs, desires and dreams for the future of SasView.  Questions discussed ranged from technologies to use and where they are currently headed,  to immediate requests from instrument scientists at facilities, key new features, and to visions for pipelining, web applications and  submission of large calculations to clusters.  Priorities were also touched upon. The goal is to use that discussion to develop the first roadmap document for the project, an exercise currently underway.
+Finally, the group spent a half day discussing the long term needs, desires and dreams for the future of !SasView.  Questions discussed ranged from technologies to use and where they are currently headed,  to immediate requests from instrument scientists at facilities, to key new features, and to visions for pipelining, web applications and  submission of large calculations to clusters.  Priorities were also touched upon. The goal is to use that discussion to develop the first roadmap document for the project, an exercise currently underway.