Changes between Version 21 and Version 22 of CodeCampV
- Timestamp:
- Oct 12, 2016 3:58:51 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CodeCampV
v21 v22 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 ... ISIS indicated 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. ILL .... SNS .... 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, ESS47 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. 48 48 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. 50 51 Of note is the ESS's SINE2020 grant which represents the first new specific funding since the UTK NSF grant ended in 2011 and is a sign of the maturation of the project, is the GUI refactoring that was started prior to the Delft Code Camp and continuing. 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. 52 50 53 51 To focus the work for the code camp, the management team made proposed we target late 2016 for a v4.1 release of the features discussed and agreed. In order to achieve this, the development team was placed in [wiki:CodeCampVWorkingGroups groups] focusing on: … … 59 57 * Developer Infrastructure 60 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 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 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. 62 63 Some infrastructure enhancements were made: some of the build servers were upgraded to deploy with scipy 0.18 (which proved to be more difficult than anticipated); a test build server for a 64bit windows build was set up and it was agreed that 4.1 will be the last 32bit Windows release; the Trac server was properly integrated with Github so that code browsing works and commit messages can add comments to and close Trac tickets. The developers all became comfortable with a branch-work-merge/pull request workflow, rather than committing all changes to master. This approach will hopefully allow us to make more frequent releases as we can choose to not include code in master that is not yet stable enough. 64 65 Overall, good progress was made towards the 4.1 release goals. 61 66 62 67 === Code Stats === … … 69 74 == Next Steps == 70 75 76 All the developers will continue to work on the tickets that are assigned to them. The aim is for anything that is going to make it into 4.1 to be ready for merging with master by the end of October or mid-November at latest. 77 71 78 == Photos == 72 79 73 80 [https://flic.kr/s/aHskJrKEMo All photos from the code camp on Flickr] 81 82 [[Image(https://flic.kr/p/MZ3gwr][img]https://c2.staticflickr.com/6/5751/30181537281_3311fbae09_k.jpg)]] 74 83 75 84 … … 77 86 78 87 79 80 88 === Tickets Closed === 81 89 [[TicketQuery(changetime=2016-10-03..2016-10-11&status=closed,group=milestone,desc=1,format=table,col=resolution|summary|owner|reporter)]]
