Feature description
Allow to add actual soil parameters dynamically for a pipeline execution, instead of having them hardcoded in the APSIM template
Problem it solves
To easier support running the vercye pipeline on different regions, the soil parameters for these should be derived dynamically. Currently, the soil parameters are hardcoded in the provided apsimx template for each run.
Suggested solution
Add a step in the pipeline that extract the soil from a soil database (e;g APSoil database) for a given region. Make the update_apsimx_template in the snakefile use this value as an input and adapt the corresponding script to use this to update the template with the correct soil data.
Additional context
Possible considerations
- Is there always a soil value available?
- Does it make sense to composite surrounding soil values, instead of just using the closest value?
- etc.
Feature description
Allow to add actual soil parameters dynamically for a pipeline execution, instead of having them hardcoded in the APSIM template
Problem it solves
To easier support running the vercye pipeline on different regions, the soil parameters for these should be derived dynamically. Currently, the soil parameters are hardcoded in the provided apsimx template for each run.
Suggested solution
Add a step in the pipeline that extract the soil from a soil database (e;g APSoil database) for a given region. Make the
update_apsimx_templatein thesnakefileuse this value as an input and adapt the corresponding script to use this to update the template with the correct soil data.Additional context
Possible considerations