Noted that Creating of New Soil Nutrient Model - has been updated and discussed with @hut104 when phoned in. It was noted that the documentation was always there but there was no link on the website. @sno036 issue stemmed from AgPasture being used in her testing, which led to errors in the simulation. @hut104 understands that @sno036's issue has been overcome.
ACTION: @sno036 to rerun the test. If this is positive, then fully approved.
Sorghum model - @jbrider provided an update. Major merge this morning - and a few outstanding issues to fix from sprint and initial review. So, should be ready for further review shortly.
Addition of Agroforestry Model - noted that this was in release. Like the Soil Nutrient Model - documentation issues have been fixed. ACTION: @sno036 to revisit comments and advise whether the module is ready for release
Models requiring review
Soybean Model - @EnliWang and @yashvirchauhan agreed to review this model. ACTION: @sarahcleary to make note on issue
New PMF Gliricidia Model - @APSIMInitiative/reference-panel agreed with @hut104's suggestions. ACTION: @sarahcleary to follow up with suggested reviewers.
Labels for APSIM Initiative Issues
Agreed that it would be worthwhile asking developer/users to sign up and join the APSIM Initiative GitHub Organisation and therefore any relevant teams. First step would be for @APSIMInitiative/reference-panel to engage/send email to developers/users within their own organisations/project group. 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.
--APSIM Classic - process for continuous release - Noted this was nearly complete and that the continuous integration process makes incorporating new features much easier. Suggested that this message is broadly communicated.
ACTION: @sarahcleary to provide communication around this process noting it is much easier now to capture improvements - RG/GitHub/Email
@sarchontoulis - questioned whether there is benefit to include new equations/work into Classic or just into Next Gen. General consensus was that if it's a simple job/good user base - do it; if not/difficult/time consuming - then wait for NG model. Suggested to load the amendment up in GitHub for review by RP if unsure.
Important is to avoid custom versions of APSIM. If change is used in publication, then in general it should be part of the APSIM release.
@EnliWang to convey conversation with @zur003 re:new process
Discussion around the purpose of the APSIM Development Plan - communication tool - internal and/or external. Is it a project management? Agreed that it is useful for tool for RP Strategy Day/Reviews as a resource and tool that can be used to help progress future projects.
Could be superseded in the future depending on GitHub use/access, but not at the moment.
Has two purposes - capturing what is happening as well as what people would wish to happen. Agreed it would be difficult to separate these two items out.
Agreed it's a useful planning component and well as what we are doing and also useful as it creates communication
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.
Audit of APSIM papers containing models (and/or improvements) not in an APSIM release - @yashvirchauhan discussed issue of updating the model. General agreement that the only effective way of including science developments into model developments is through ensuring the model development is part of the project - and contract developers as part of the project.
ACTION: @yashvirchauhan - to encourage development of projects which include model development. Others to assist where required.
5 Training
@sarahcleary provided short update on APSIM Week.
ACTION: to circulate updated running sheets for APSIM Symposium and workshops for discussion in next RP Meeting
-- @yashvirchauhan to led discussion on "special issue" publication - postponed till next meeting
ACTION: put on agenda for next meeting
8 AI Steering Committee Meeting Actions and RP Strategy Day - Agenda items
RP Strategy Day - Agenda items
Discussion and actions/agreement on how to tackle these items - out of session, part of std RP meetings (potential to extend certain meetings by an hour, for example, sub committee etc...)
-- RP "principles of membership"ACTION: @sarahcleary to provide proposed steps to complete task. To be discussed in next RP meeting
-- APSIM Roadmap
-- Operations
ACTION: - These two items to be discussed in June RP meeting. In lieu of 'normal' RP Meeting conduct a strategy planning session. Run through development plan, list of priorities which feed into the AI SC Action of possible issues to be funded or supported in some way. Extend meeting by an hour allowing a 3 hour session.
ACTION: @sno036 to set up a Microsoft teams and send invite.
Noted the actions from the AI SC Meeting were as follows:
-- ACTION: RP to review the issue of being involved at the start of development discussions. Could this be done via seminars, sprints, forums, video chats, other mechanisms? ACTION: Further discussion in RP Strategy session
-- ACTION: RP to lead the addition of outline on development of each model/activity on the development plan -“concept note”. These to be provided as links on the ‘cut down’ development plan.
ACTION: Included as part of the 'email' request to developers/users. Suggested that these are included on each major issue and scope of description is added to the email request. This should include adding a few sentences on what the science scope - how it was derived, how it differs, new functionality. Explain to developers that this is aiming to to grow the GitHub audience and make it easier for new users to engage with GitHub and therefore APSIM.
--ACTION: New Standing Item – (name of this new item) - RP to provide 1 pagers around key issues requiring funding support
ACTION: Further discussion and identification of key issues as part of the RP Strategy session
Date
Tuesday 7/4/20; 9:30 AEST
Members: Video/Teleconference:
@yashvirchauhan; @peter-devoil; @LouisAK; @sarchontoulis; @sarahcleary; @sno036; @Keith-Pembleton; @EnliWang; @HamishBrownPFR; @MarkLieffering; @jbrider; @JulianneLilley
Apologies/Not in attendance
@kchenu
1.1 Welcome/Apologies
Welcome from @peter-devoil
1.2 Review Minutes
Review Minutes: 2020-03 Minutes Taken as read and correct
2. Science/Software
2.1 Check for new APSIM Major Improvements
Noted that the new model - (New PMF Gliricidia Model)[https://github.com/APSIMInitiative/ApsimX/issues/1227] is seeking reviewers - to be discussed below
2.2 Updates from RP on models and reviews
Noted that Creating of New Soil Nutrient Model - has been updated and discussed with @hut104 when phoned in. It was noted that the documentation was always there but there was no link on the website. @sno036 issue stemmed from AgPasture being used in her testing, which led to errors in the simulation. @hut104 understands that @sno036's issue has been overcome. ACTION: @sno036 to rerun the test. If this is positive, then fully approved.
Sorghum model - @jbrider provided an update. Major merge this morning - and a few outstanding issues to fix from sprint and initial review. So, should be ready for further review shortly.
Addition of Agroforestry Model - noted that this was in release. Like the Soil Nutrient Model - documentation issues have been fixed. ACTION: @sno036 to revisit comments and advise whether the module is ready for release
Models requiring review
Soybean Model - @EnliWang and @yashvirchauhan agreed to review this model. ACTION: @sarahcleary to make note on issue
New PMF Gliricidia Model - @APSIMInitiative/reference-panel agreed with @hut104's suggestions. ACTION: @sarahcleary to follow up with suggested reviewers.
Models/Updates in release since last RP meeting
Addition of Agroforestry Model
3 Software
Labels for APSIM Initiative Issues Agreed that it would be worthwhile asking developer/users to sign up and join the APSIM Initiative GitHub Organisation and therefore any relevant teams. First step would be for @APSIMInitiative/reference-panel to engage/send email to developers/users within their own organisations/project group.
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.
--APSIM Classic - process for continuous release - Noted this was nearly complete and that the continuous integration process makes incorporating new features much easier. Suggested that this message is broadly communicated.
ACTION: @sarahcleary to provide communication around this process noting it is much easier now to capture improvements - RG/GitHub/Email
@sarchontoulis - questioned whether there is benefit to include new equations/work into Classic or just into Next Gen. General consensus was that if it's a simple job/good user base - do it; if not/difficult/time consuming - then wait for NG model. Suggested to load the amendment up in GitHub for review by RP if unsure.
Important is to avoid custom versions of APSIM. If change is used in publication, then in general it should be part of the APSIM release.
@EnliWang to convey conversation with @zur003 re:new process
4 Outstanding Actions
Discussion around the purpose of the APSIM Development Plan - communication tool - internal and/or external. Is it a project management? Agreed that it is useful for tool for RP Strategy Day/Reviews as a resource and tool that can be used to help progress future projects.
Could be superseded in the future depending on GitHub use/access, but not at the moment.
Has two purposes - capturing what is happening as well as what people would wish to happen. Agreed it would be difficult to separate these two items out.
Agreed it's a useful planning component and well as what we are doing and also useful as it creates communication
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.
ACTION: @yashvirchauhan - to encourage development of projects which include model development. Others to assist where required.
5 Training
@sarahcleary provided short update on APSIM Week. ACTION: to circulate updated running sheets for APSIM Symposium and workshops for discussion in next RP Meeting
-- @yashvirchauhan to led discussion on "special issue" publication - postponed till next meeting ACTION: put on agenda for next meeting
7 Science Chats
@hut104 provide an overview on Creating of New Soil Nutrient Model. Discussion on scope and work that can now proceed from this update
8 AI Steering Committee Meeting Actions and RP Strategy Day - Agenda items
-- RP "principles of membership" ACTION: @sarahcleary to provide proposed steps to complete task. To be discussed in next RP meeting -- APSIM Roadmap -- Operations ACTION: - These two items to be discussed in June RP meeting. In lieu of 'normal' RP Meeting conduct a strategy planning session. Run through development plan, list of priorities which feed into the AI SC Action of possible issues to be funded or supported in some way. Extend meeting by an hour allowing a 3 hour session.
ACTION: @sno036 to set up a Microsoft teams and send invite.
Noted the actions from the AI SC Meeting were as follows: -- ACTION: RP to review the issue of being involved at the start of development discussions. Could this be done via seminars, sprints, forums, video chats, other mechanisms?
ACTION: Further discussion in RP Strategy session
-- ACTION: RP to lead the addition of outline on development of each model/activity on the development plan -“concept note”. These to be provided as links on the ‘cut down’ development plan. ACTION: Included as part of the 'email' request to developers/users. Suggested that these are included on each major issue and scope of description is added to the email request. This should include adding a few sentences on what the science scope - how it was derived, how it differs, new functionality. Explain to developers that this is aiming to to grow the GitHub audience and make it easier for new users to engage with GitHub and therefore APSIM.
--ACTION: New Standing Item – (name of this new item) - RP to provide 1 pagers around key issues requiring funding support ACTION: Further discussion and identification of key issues as part of the RP Strategy session
10 Other Business
None
11 Next Meeting
5 May 2020