Use default values in data input requirements for "Field" components when using CLI. #309
Replies: 3 comments
-
|
Hi Aaron, Yes, I could meet next week if you like - not sure how you want to set that up. We would like to generate farms with field component CSVs programmatically and execute them with the CLI, but we just wish to use the application defaults for inputs that we do not have (e.g., "Biomass Coefficient Product" or "Climate Factor"). Unfortunately, the input files are not accepted when these attributes are not entered, so I'm trying to decide how to proceed. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Friday morning wouldn't work for me. I could do afternoon if you wanted to stick with Friday. Maybe 1PM MST? |
Beta Was this translation helpful? Give feedback.
-
|
Unclassified / Non classifié
That works for me. Can you send me your email address aaron [dot] mcpherson [at] agr [dot] gc [dot] ca>) and I’ll send out the Team link
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Given a farm location and management details, I would like to generate farm settings and field components with default values to reduce the input requirements for CLI execution.
Creating farms via the GUI and exporting them as proposed in #57 would not scale for our use case, and the alternative seems to be reimplementing
H.Corefunctionality in our application to populate these attributes.Is there any way to do this with the CLI? If not, is this something I could implement with some C# code around the
H.Corepackage?Thanks for your consideration!
Beta Was this translation helpful? Give feedback.
All reactions