Changes between Version 24 and Version 25 of CodeCampV
- Timestamp:
- Oct 12, 2016 10:40:26 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CodeCampV
v24 v25 8 8 == Initial Goals == 9 9 10 The management team met on Monday afternoon just prior to the Code Camp to work on a proposed set of goals for the Camp based , as alwayson the [https://github.com/SasView/documents/blob/master/SasView%20Roadmap%202015-11-24.md published roadmap] but informed by the many developments and activities that have taken place since the last official update. For example the ESS contribution through its SINE2020 funding to work on refactoring the GUI, an activity targeted for 2019 in the roadmap, makes moot some of the smaller GUI enhancements envisaged earlier. Further, the final release of !SasView version 4.0, completing the work from the [wiki:CodeCampIV previous Code Camp in Delft], was released just prior to the code camp. The plan was presented to the developers and after a brief disscussion the primary goals for the code camp, which will be translated to the next update to the [https://github.com/SasView/documents/blob/master/SasView%20Roadmap.md roadmap], were agreed:10 The management team met on Monday afternoon just prior to the Code Camp to work on a proposed set of goals for the Camp based on the [https://github.com/SasView/documents/blob/master/SasView%20Roadmap%202015-11-24.md published roadmap] but informed by the many developments and activities that have taken place since the last official update. For example the ESS contribution through its SINE2020 funding to work on refactoring the GUI, an activity targeted for 2019 in the roadmap, makes moot some of the smaller GUI enhancements envisaged earlier. Further, the final release of !SasView version 4.0, completing the work from the [wiki:CodeCampIV previous Code Camp in Delft], was released just prior to the code camp. The plan was presented to the developers and after a brief disscussion the primary goals for the code camp, which will be translated to the next update to the [https://github.com/SasView/documents/blob/master/SasView%20Roadmap.md roadmap], were agreed: 11 11 12 12 * TBA from list of tickets … … 45 45 This code camp brought 13 developers together to work for 7 days on the [http://github.com/sasview/sasview SasView] and [http://github.com/sasview/sasmodels sasmodels] code, documentation, and development infrastructure. One new developer, Dirk Honecker from ILL, joined the project. 46 46 47 As usual the camp began with introductions and updates from all the partner labs. NIST indicated that !SasView has now surpassed the use of its old IGOR analysis package among both its users and staff and that with release 4.0 plans are being made for some local tutorials. Further with their effort at the code camps and in between from 3 staff members the feeling is that they now have a sufficient handle on the code base to not dependent on others for any critical needs. ANSTO have been focussed on delivering data reduction for two new beam lines - Kookaburra and Bilby - but they want to be able to support their users who analyse their data using !SasView. ISIS were happy to report that they had somehow managed to hire a summer undergrad to work on the code this summer who was extraordinarily productive providing many fixes and new features to the project. Several people asked about the possibility of hiring him again and it was suggested that was not out of the realm of possibility. From the ILL, Dirk Honecker introduced himself and said that his primary interest was in getting magnetic and oriented models working properly. SNS has users who use !SasView and the primary interest from the facility is in incorporating sasmodels into their web-based data work flow, requiring some work on the sasmodels API. Delft has done some work on the SESANS project but mostly not progressed too much on the code since last code camp. Their hope is that they can get something into the GUI at this code camp. Finally, ESS have continued the work laid out in the SINE2020 project - the first new specific funding for !SasView since the UTK NSF grant ended in 2011 - focussing on GUI redesign for !SasView, !SasFit integration work and performance enhancement of sasmodels.47 As usual the camp began with introductions and updates from all the partner labs. NIST indicated that !SasView usage has grown significantly among its users and staff, a trend that should only continue with the new features available in release of 4.0. This collaborative community approach to analysis software development is key to NIST’s ability to provide maximum data analysis support for the long term and the hope is to expand the number of staff able to contribute beyond the current 3 developers as time goes on. ANSTO have been focused on delivering data reduction for two new beam lines - Kookaburra and Bilby - but they want to be able to support their users who analyse their data using !SasView. ISIS were happy to report that they had somehow managed to hire a summer undergrad to work on the code this summer who was extraordinarily productive providing many fixes and new features to the project. Several people asked about the possibility of hiring him again and it was suggested that was not out of the realm of possibility. From the ILL, Dirk Honecker introduced himself and said that his primary interest was in getting magnetic and oriented models working properly. SNS has users who use !SasView and the primary interest from the facility is in incorporating sasmodels into their web-based data work flow, requiring some work on the sasmodels API. Delft has done some work on the SESANS project but not progressed as much as it would have liked on the code since last code camp. Their hope is that they can get an initial access to modelling SESANS data from within the !SasView GUI at this code camp. Finally, ESS have continued the work laid out in the SINE2020 project - the first new specific funding for !SasView since the UTK NSF grant ended mid 2012 - focusing on GUI redesign for !SasView, !SasFit integration work and performance enhancement of sasmodels. 48 48 49 49 While not slated for deployment in the next release, the work on GUI refactoring and SASfit model integration, tasks receiving the attention of the full time !SasView developers at ESS, continued at this code camp in preparation for release 5.0. As part of that effort, some review discussions were undertaken and a few other developers began to help with those tasks both to speed up the development to meet our target release but more importantly to start learning the new code base for a smooth transition as the time approaches. … … 57 57 * Developer Infrastructure 58 58 59 By the end of the code camp, several of the main goals had been achieved. SESANS functionality was working in the GUI - both transforming SANS models automatically and calculating SESANS function directly. The save project functionality had been improved and repaired. The models from S asFit that do not currently overlap with sasmodels had been identified and work started on shipping them to the sasmodels marketplace for users to download. Refactoring of oriented cylinder-type models had begun to improve the behaviour when using orientation distributions. The documentation was broadly reviewed, then corrected and enhanced as needed. As can be seen from the list of tickets that were closed or worked on during the code camp, there was a lot of work on stability improvements and bug fixing.59 By the end of the code camp, several of the main goals had been achieved. SESANS functionality was working in the GUI - both transforming SANS models automatically and calculating SESANS function directly. The save project functionality had been improved and repaired. The models from SASFit that do not currently overlap with sasmodels had been identified and work started on shipping them to the sasmodels marketplace for users to download. Refactoring of oriented cylinder-type models had begun to improve the behaviour when using orientation distributions. The documentation was broadly reviewed, then corrected and enhanced as needed. As can be seen from the list of tickets that were closed or worked on during the code camp, there was a lot of work on stability improvements and bug fixing. 60 60 61 61 The work that had been done by Lewis O'Driscoll at ISIS over the summer was integrated into the main code base, adding a Correlation Function perspective, and a data converter for file formats that put Q and I in separate files. In addition, the sasmodels marketplace that Lewis wrote was now live and some models were uploaded.