| 42 | | The week began with an introduction by Paul Butler outlining the goals for the week. A [wiki:CodeCampIIIScheduleAndWork schedule and series of work packages] were formulated to guide the work. |
| | 42 | The code camp gathered 10 developers working full time for over a week on the sasview code base. Further, the team was joined in the latter half of the camp by 2 new developers (Wim Bouwman and Jurriaan Bakker from TUD) interested in adding support for SESANS data to the SasView package. Several major advances were made |
| | 43 | |
| | 44 | The camp began with an introduction by Paul Butler outlining the goals for the week. A [wiki:CodeCampIIIScheduleAndWork schedule and series of work packages] were formulated to guide the work. |
| | 45 | |
| | 46 | The first task was to migrate the SasView code repository from SourceForge, which has been problematic of late, to Github. This was successfully accomplished. Migration included redirecting host names, editing trac and web pages, moving web pages hosting from UTK to github as well as updating all the developer machines. In the process the final phase of renaming and reorganizing the folders in the SasView tree was completed. The official build servers and Jenkins site were moved to the DMSC servers and the development finally moved from using the old wx 2.8 to using wx 3.0. |
| | 47 | |
| | 48 | With the move to wx 3.0 the documentation re-write started at code camp II at ISIS was completed with a porting of all the non-model documentation to RST files that can be built by sphinx. The new documentation was integrated into the gui simplifying the code in the process. Most of the non-model documentation was also carefully edited and updated. |
| | 49 | |
| | 50 | 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. |
| | 51 | |
