Port the maize model from Apsim 7.10 into Next Gen - @jbrider provided an update. The two APSIM Classic maize models are being combined into a single one for Next Gen. Aim to progress this work in NZ at the APSIM Developer's workshop
@hol353 has created both labels and teams.
Some @APSIMInitiative/reference-panel and others have joined/requested to join relevant teams.
Need these to be used. ACTION: @APSIMInitiative/reference-panel to start some conversations within these teams as well as label new issues, as appropriate.
--APSIM Classic - process for continuous release - continued discussion on the GitHub issue. RP agreed that the best option is to provide download links on the website, but only accessible if a valid/current email address is provided as an input. Email address requires to be the same one used within the last 3 years when downloading APSIM and agreeing to the T&Cs.
Request to simplify the current versioning. Ensure that there is consistent numbering. @peter-devoil, @jbrider and @sarahcleary to work with @hol430.
--Apsim development sprint in Lincoln - update provided @jbrider - will be going ahead in Lincoln in early March. Working on finalising Sorghum model; progressing new maize model as well as a number of other outstanding tasks.
@sarahcleary noted that there were a number of outstanding actions that have been around for close to a year. @APSIMInitiative/reference-panel agreed to either comment or close issues.
19/20 APSIM Development Plan - https://github.com/APSIMInitiative/ReferencePanel/issues/36ACTION: @sarahcleary to send new link for updating prior to the RP Strategy Session. @APSIMInitiative/reference-panel to update by end of February for both AI SC March meeting and for use in the RP Strategy meeting.
@sno036 provided an update on the Stock Model and the issues around the out of date code that was ported from the original AusFarm model into NextGen. Not suitable for release as a model in Next Gen. Team has assessed that it would take around 2-3months full time for the code translation. Further discussion on the science occurred.
5 Training
APSIM online training topics - noted that another two videos have been uploaded. @APSIMInitiative/reference-panel requested to think about additional topics and if they could/would record additional training videos.
Update on APSIM Week
@sarahcleary to provided a short update
--Symposium Running Sheet
available on the web
--Papers/presenters
all have been notified
--Workshops - numbers - filling fast and a number are full.
--Workshops - facilitators - can be found on the website. If you can provide additional support, please let @sarahcleary know.
@Keith-Pembleton to email GRDC contact and request circulation of APSIM week info. @sarahcleary to do the same for CRDC.
@sarahcleary to discuss Agroforestry workshop with Phil. @APSIMInitiative/reference-panel would like it to go ahead but final call will be Phil's.
@sarahcleary to contact suggestions from https://github.com/APSIMInitiative/ReferencePanel/issues/26 - for April meeting, but allow sufficient time for review of APSIM week. So, May meeting would be fine to commence these 'chats' again.
8 AI Steering Committee Meeting
Actions requiring work/completion prior to 23 March AI SC meeting
Additional Actions from AI SC meeting:
-- As part of the uJV review, ask the RP to develop a ‘principles of membership’ similar to that of the AI. @sarahcleary provided background and will circulate current role of RP
-- Steering Committee would like guidance from RP with regard to the Software Engineering role. What resourcing is required long term. What additional tasks could/should be done. Looking at not just fixing bugs, but e.g. new features. - include as part of RP strategy discussion
-- Stock Model update - update provided above
9 Discussion on RP Strategy Day - 24 March 2020
ACTION: @APSIMInitiative/reference-panel to forward input to @peter-devoil and @sarahcleary. @peter-devoil and @sarahcleary to provide a draft agenda for input.
@Keith-Pembleton would like publication plan to be included as part of this discussion. How to bring together 'larger' APSIM applications into this.
10 Other Business
Noted that UQ is chairing the RP this year. @peter-devoil and @kchenu as co-chairs. -
Date
Thursday 4/2/20; 9:30 AEST
Members: Video/Teleconference:
@yashvirchauhan; @peter-devoil; @MarkLieffering; @LouisAK; @jbrider; @sarahcleary; @sno036; @Keith-Pembleton; @EnliWang;
Apologies/Not in attendance
@sarchontoulis;; @HamishBrownPFR; @kchenu; @JulianneLilley
1.1 Welcome/Apologies
Welcome from @peter-devoil
1.2 Review Minutes
Review Minutes: 2019-12 Minutes Taken as read and correct
2. Science/Software
2.1 Check for new APSIM Major Improvements
Noted that there were a few MAJOR science issues since last meeting.
New Cotton Model - @Keith-Pembleton said David Johnston was helping to pull together some data.
G-Range in ApsimX - will need review by RP when ready
Port the maize model from Apsim 7.10 into Next Gen - @jbrider provided an update. The two APSIM Classic maize models are being combined into a single one for Next Gen. Aim to progress this work in NZ at the APSIM Developer's workshop
No discussion on New Science issues.
2.2 Updates from RP on models and reviews
Noted that Creating of New Soil Nutrient Model is still awaiting @hut104 to progress
Sorghum model - @hut104 and @HamishBrownPFR to be review in NZ in early March
Addition of Agroforestry Model - awaiting @sno036 to provide final signoff
Models requiring review
None
Models/Updates in release since last RP meeting
None
3 Software
Labels for APSIM Initiative Issues
@hol353 has created both labels and teams. Some @APSIMInitiative/reference-panel and others have joined/requested to join relevant teams.
Need these to be used.
ACTION: @APSIMInitiative/reference-panel to start some conversations within these teams as well as label new issues, as appropriate.
--APSIM Classic - process for continuous release - continued discussion on the GitHub issue. RP agreed that the best option is to provide download links on the website, but only accessible if a valid/current email address is provided as an input. Email address requires to be the same one used within the last 3 years when downloading APSIM and agreeing to the T&Cs. Request to simplify the current versioning. Ensure that there is consistent numbering. @peter-devoil, @jbrider and @sarahcleary to work with @hol430.
--Apsim development sprint in Lincoln - update provided @jbrider - will be going ahead in Lincoln in early March. Working on finalising Sorghum model; progressing new maize model as well as a number of other outstanding tasks.
4 Outstanding Actions
@sarahcleary noted that there were a number of outstanding actions that have been around for close to a year. @APSIMInitiative/reference-panel agreed to either comment or close issues.
19/20 APSIM Development Plan - https://github.com/APSIMInitiative/ReferencePanel/issues/36 ACTION: @sarahcleary to send new link for updating prior to the RP Strategy Session. @APSIMInitiative/reference-panel to update by end of February for both AI SC March meeting and for use in the RP Strategy meeting.
@sno036 provided an update on the Stock Model and the issues around the out of date code that was ported from the original AusFarm model into NextGen. Not suitable for release as a model in Next Gen. Team has assessed that it would take around 2-3months full time for the code translation. Further discussion on the science occurred.
5 Training
APSIM online training topics - noted that another two videos have been uploaded. @APSIMInitiative/reference-panel requested to think about additional topics and if they could/would record additional training videos.
Update on APSIM Week
@sarahcleary to provided a short update --Symposium Running Sheet available on the web --Papers/presenters all have been notified --Workshops - numbers - filling fast and a number are full.
--Workshops - facilitators - can be found on the website. If you can provide additional support, please let @sarahcleary know.
@Keith-Pembleton to email GRDC contact and request circulation of APSIM week info. @sarahcleary to do the same for CRDC.
@sarahcleary to discuss Agroforestry workshop with Phil. @APSIMInitiative/reference-panel would like it to go ahead but final call will be Phil's.
6 Website/Communications
-- Require new information (updated references) - https://www.apsim.info/apsim-model/models-in-release/ - nearly complete. Still awaiting a few references.
7 Science Chats
@sarahcleary to contact suggestions from https://github.com/APSIMInitiative/ReferencePanel/issues/26 - for April meeting, but allow sufficient time for review of APSIM week. So, May meeting would be fine to commence these 'chats' again.
8 AI Steering Committee Meeting
Actions requiring work/completion prior to 23 March AI SC meeting
-- Paper on GitHub process and RP meeting structure and changes - agree to be a verbal update. @APSIMInitiative/reference-panel to provide @peter-devoil with comments/input -- AI SC Report - AI funded software position - @sno036 demonstrated a visualisations of GitHub commits - good demonstration of work being undertaken -- Improving Next Gen Documentation to include summary page - @HamishBrownPFR to update/complete -- Discussion on leveraging resources between members - require input from @HamishBrownPFR
Additional Actions from AI SC meeting: -- As part of the uJV review, ask the RP to develop a ‘principles of membership’ similar to that of the AI. @sarahcleary provided background and will circulate current role of RP -- Steering Committee would like guidance from RP with regard to the Software Engineering role. What resourcing is required long term. What additional tasks could/should be done. Looking at not just fixing bugs, but e.g. new features. - include as part of RP strategy discussion -- Stock Model update - update provided above
9 Discussion on RP Strategy Day - 24 March 2020
ACTION: @APSIMInitiative/reference-panel to forward input to @peter-devoil and @sarahcleary. @peter-devoil and @sarahcleary to provide a draft agenda for input.
@Keith-Pembleton would like publication plan to be included as part of this discussion. How to bring together 'larger' APSIM applications into this.
10 Other Business
Noted that UQ is chairing the RP this year. @peter-devoil and @kchenu as co-chairs. -
11 Next Meeting
3 March 2020