Changes between Version 19 and Version 20 of CodeCampII


Ignore:
Timestamp:
Oct 29, 2017 7:50:05 AM (21 months ago)
Author:
butler
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • CodeCampII

    v19 v20  
    99The Camp ran from the morning of Monday 31 March until lunchtime on Sunday 6 April 2014  with a 'meet-and-greet' over dinner on the evening of Sunday 30 March. 
    1010 
    11 The local arrangements were kindly made by Steve King (ISIS) with details on the [wiki:CampIIProposal planning page] 
     11The local arrangements were kindly made by Steve King (ISIS) with details on the [wiki:CodeCampII/Proposal planning page] 
    1212 
    1313[[BR]] 
     
    1717The high level objectives of the Code Camp were: 
    1818 
    19  * To learn about the SasView development environment 
     19 * To learn about the !SasView development environment 
    2020 * To progress and complete tickets in an encouraging and nurturing expert environment 
    21  * To shape the future development of SasView 
     21 * To shape the future development of !SasView 
    2222 
    2323In addition, on the first day, a series of specific objectives were set: 
     
    5555'''!Progress/Outcomes''' 
    5656 
    57 There were over 100 commits to the SasView code repository, and over 50 tickets were addressed, created or updated during the week. 
     57There were over 100 commits to the !SasView code repository, and over 50 tickets were addressed, created or updated during the week. 
    5858 
    5959A survey of which versions of packages were being used was made (ticket #213) and a table of results is available [raw-attachment:sasview-dependencies-survey.pdf:ticket:213 in pdf]. Excellent progress was made on migrating to wx 3.0 (ticket #216) but was deemed too large a change to risk on a relase anticipated by the end of the month and so will be actually implemented once the release is made. Likewise, the change to the repository structure to remove the last vestiges of the name *sans* and make the code layout in the development environment more closely match that in the deployed environement (ticket #218) was ready to push but deemed to risky so close to a release.  It too will be done after this release.  Finally the project to replace the optimizer (ticket #214) is mostly complete but again is viewed as too risky to deploy for this release. 
     
    6363Importantly, several new developers (Torben Nielsen (ESS), Tobias Richter (Diamond) and Richard Heenan (ISIS)) were introduced to the code and have begun to make contributions. The existing developers made good use of the week to make progress on existing tasks and to address new ones. 
    6464 
    65 There was discussion of the direction that SasView should head in, with a presentation from Mathieu Doucet of his web-based data reduction using Mantid. He proposed a similar approach for SasView and it was agreed that he and Torben would work on some technology demonstrations using the existing SasView code as a backend in order to allow the larger group to make a decision later this year on the way forward. A number of the long-term changes planned for SasView (for example using Bumps as the fitting engine, re-working the data structures to include constraints information, and changing the way that models are interfaced) are also required to enable the development of a web-based system with access to a HPC backend. 
     65There was discussion of the direction that !SasView should head in, with a presentation from Mathieu Doucet of his web-based data reduction using Mantid. He proposed a similar approach for SasView and it was agreed that he and Torben would work on some technology demonstrations using the existing SasView code as a backend in order to allow the larger group to make a decision later this year on the way forward. A number of the long-term changes planned for !SasView (for example using Bumps as the fitting engine, re-working the data structures to include constraints information, and changing the way that models are interfaced) are also required to enable the development of a web-based system with access to a HPC backend. 
    6666 
    6767The general conclusion was that all participants had had a fruitful week and look forward to the next Code Camp. It has been suggested that we might increase the frequency to every 6 months, but we should at least plan to meet next spring.