Reviewed outstanding issues not addressed later this meeting. Taken as read and correct.
2. Science/Software
2.1 Check for new APSIM Major Improvements
Noted proposed new model - (New PMF New Pigeon Pea Model for APSIM Next Generation Model)[https://github.com/APSIMInitiative/ApsimX/issues/5105] - noted comments on the model were added to this new issue, aligned with the concept note process. No further questions or comments.
APSIMX vs APSIM Next Generation - sought direction from the RP on this question. Ideally, would be good to utilise one term only. ACTION: Agreed to seek feedback on implications on renaming (1) the repository from APSIMX to APSIMNG and the file extension to .apsimng. Agreed to only change if there weren't any detrimental consequences.
Maize Model P Response Not Working - @enliwang raised issue with P response in Maize Model - Simulations function in 7.9 but not in 7.10. @enliwang to provide simulations to @jbrider. @keith-pembleton to discuss work conducted by post doc - already worked on this issue. Link with @jbrider.
Rice Model - @HamishBrownPFR requested an update on the Rice Model. @keith-pembleton noted that @andomariot with the support of Don Gaydon were working on a new model. @enliwang said he should be able to source some datasets from CN collaborators. Generic systems aspects would be a valuable start for this development and could benefit for a group of people working on this. Maybe a possibility to raise with the AI SC for some seed funding. Also noted that general utility across asia will be hampered by the lack of a paddy /pond capability, though projected activities (USQ) are unaffected. @enliwang may have a potential PhD student. @keith-pembleton offered to look at the possibility of USQ providing a scholarship. Requested @enliwang to forward CV when ready.
Labels for APSIM Initiative Issues
noted that this issue should be renamed to include the 'teams' concept. Reqeuest for RP to attend to the action from last meeting. ACTION: @APSIMInitiative/reference-panel need to engage people into the discussion noting the potential benefit of engagement with others. @APSIMInitiative/reference-panel to send email to developers/users within their own organisations/project group.
New Action ACTION: @APSIMInitiative/reference-panel and others to tag and/or mention teams on new issues. Also, include Steering Committee members in GitHub conversations where required.
APSIM Classic - process for continuous release - Noted this is 99% was nearly complete. @peter-devoil provided a demonstration of the system. ACTION: @sarahcleary to work with @peter-devoil on 'news article' when finalised.
Noted that the APSIM Commercial Click Wrap Licence is available to 3rd parties for download.
APSIM Development Plan - https://github.com/APSIMInitiative/ReferencePanel/issues/36. Reviewed proposed GitHub Dev Plan - https://github.com/APSIMInitiative/ApsimX/projects/3
Positive feedback. @APSIMInitiative/ReferencePanel comfortable to utilise GitHub rather than spreadsheet. Positives - integrated; easily amended/accessed; no discrepancies between plans/actual work. Noted it doesn't currently capture aspirational work which is on the current Dev plan. Agreed that these should be 'issues' within GitHub. ACTION: @APSIMInitiative/reference-panel to send request/development to team to update development plan and/or at least engage in internal conversation around current and future work. @APSIMInitiative/ReferencePanel to assist with transferring aspirtaional work into GitHub. @sarahcleary to process the new format.
Discussion on the possibility of a special issue publication. Agreed this should be investigated. Noted that a special issue can be open for a long time. Goal is for an approx. 6 month submission period and to raise this with attendees at the Symposium.
ACTION: @APSIMInitiative/reference-panel to suggest potential journals. @sarahcleary and @kchenu to discuss next steps.
APSIM Week - discussed reviewing the date in early July. Anticipate that the Symposium and workshops will be able to be held in November although note that non AU, NZ attendees may not be able to enter AU.
Run sheets and workshops to be discussed in July RP meeting
Noted the new training videos from Matt Harrison and that the Agroforestry workshop participants have been contacted by Phil Smethurst to ensure all participants can run simulations in APSIM NG.
Date
Tuesday 5/5/20; 9:30 AEST
Members: Video/Teleconference:
@yashvirchauhan; @peter-devoil; @LouisAK; @sarchontoulis; @sarahcleary; @EnliWang; @HamishBrownPFR; @MarkLieffering; @jbrider; @JulianneLilley; @kchenu; @Keith-Pembleton;
Apologies/Not in attendance
@sno036
1.1 Welcome/Apologies
Welcome from @peter-devoil
1.2 Review Minutes
Review Minutes: 2020-04 Minutes
Reviewed outstanding issues not addressed later this meeting. Taken as read and correct.
2. Science/Software
2.1 Check for new APSIM Major Improvements
Noted proposed new model - (New PMF New Pigeon Pea Model for APSIM Next Generation Model)[https://github.com/APSIMInitiative/ApsimX/issues/5105] - noted comments on the model were added to this new issue, aligned with the concept note process. No further questions or comments.
2.2 Updates from RP on models and reviews
Sorghum model - no update provided.
New PMF Gliricidia Model - noted @ElvisElli had agreed to review the model. ACTION: @sarahcleary to follow up with @ElvisElli.
Soybean Model - @EnliWang and @yashvirchauhan have both commenced their review.
Models requiring review
None
Models/Updates in release since last RP meeting
Addition of Agroforestry Model Creation of New SoilNutrient Model
3 Software
APSIMX vs APSIM Next Generation - sought direction from the RP on this question. Ideally, would be good to utilise one term only. ACTION: Agreed to seek feedback on implications on renaming (1) the repository from APSIMX to APSIMNG and the file extension to .apsimng. Agreed to only change if there weren't any detrimental consequences.
Maize Model P Response Not Working - @enliwang raised issue with P response in Maize Model - Simulations function in 7.9 but not in 7.10. @enliwang to provide simulations to @jbrider. @keith-pembleton to discuss work conducted by post doc - already worked on this issue. Link with @jbrider.
Rice Model - @HamishBrownPFR requested an update on the Rice Model. @keith-pembleton noted that @andomariot with the support of Don Gaydon were working on a new model. @enliwang said he should be able to source some datasets from CN collaborators. Generic systems aspects would be a valuable start for this development and could benefit for a group of people working on this. Maybe a possibility to raise with the AI SC for some seed funding. Also noted that general utility across asia will be hampered by the lack of a paddy /pond capability, though projected activities (USQ) are unaffected. @enliwang may have a potential PhD student. @keith-pembleton offered to look at the possibility of USQ providing a scholarship. Requested @enliwang to forward CV when ready.
Labels for APSIM Initiative Issues noted that this issue should be renamed to include the 'teams' concept. Reqeuest for RP to attend to the action from last meeting. ACTION: @APSIMInitiative/reference-panel need to engage people into the discussion noting the potential benefit of engagement with others. @APSIMInitiative/reference-panel to send email to developers/users within their own organisations/project group.
New Action ACTION: @APSIMInitiative/reference-panel and others to tag and/or mention teams on new issues. Also, include Steering Committee members in GitHub conversations where required.
APSIM Classic - process for continuous release - Noted this is 99% was nearly complete. @peter-devoil provided a demonstration of the system. ACTION: @sarahcleary to work with @peter-devoil on 'news article' when finalised.
Noted that the APSIM Commercial Click Wrap Licence is available to 3rd parties for download.
4 Outstanding Actions
APSIM Development Plan - https://github.com/APSIMInitiative/ReferencePanel/issues/36. Reviewed proposed GitHub Dev Plan - https://github.com/APSIMInitiative/ApsimX/projects/3
Positive feedback. @APSIMInitiative/ReferencePanel comfortable to utilise GitHub rather than spreadsheet. Positives - integrated; easily amended/accessed; no discrepancies between plans/actual work. Noted it doesn't currently capture aspirational work which is on the current Dev plan. Agreed that these should be 'issues' within GitHub.
ACTION: @APSIMInitiative/reference-panel to send request/development to team to update development plan and/or at least engage in internal conversation around current and future work. @APSIMInitiative/ReferencePanel to assist with transferring aspirtaional work into GitHub. @sarahcleary to process the new format.
Concept note - https://github.com/APSIMInitiative/ReferencePanel/issues/57 Underway with key developers.
5 Training
@APSIMInitiative/Reference Panel - agreed to tag relevant people onto GitHub when required. @sarahcleary to tag where not picked up quickly.
https://github.com/APSIMInitiative/ApsimX/labels/question https://github.com/APSIMInitiative/APSIMClassic/labels/question
Discussion on the possibility of a special issue publication. Agreed this should be investigated. Noted that a special issue can be open for a long time. Goal is for an approx. 6 month submission period and to raise this with attendees at the Symposium.
ACTION: @APSIMInitiative/reference-panel to suggest potential journals. @sarahcleary and @kchenu to discuss next steps.
APSIM Week - discussed reviewing the date in early July. Anticipate that the Symposium and workshops will be able to be held in November although note that non AU, NZ attendees may not be able to enter AU.
Run sheets and workshops to be discussed in July RP meeting
Noted the new training videos from Matt Harrison and that the Agroforestry workshop participants have been contacted by Phil Smethurst to ensure all participants can run simulations in APSIM NG.
7 Science Chats
@jwhish provided an overview on Pest/Disease plant interface. No actions arising.
8 RP Strategy Day
RP Strategy Day - Agenda items
Sprints:
Agreement that sprints could be utilised more and an avenue to involve a broader team. Worked well with the latest NZ sprint.
Sprints work well for progressing core science and software issues. Other work generally progressed under project work.
Another area of collaborative work - documentation in Next Gen. Tidying up and Refactoring. Lots of people could contribute to this.
discuss upcoming collaborative papers & projects (led by @Keith-Pembleton)
ACTION: @peter-devoil and @sarahcleary to circulate Agenda for RP Strategy Session.
10 Other Business
None
11 Next Meeting
RP Strategy Session 2 June 2020; 9-12 AEST.