Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling Model Specific Variables #7

Open
frostbytten opened this issue Feb 3, 2014 · 0 comments
Open

Handling Model Specific Variables #7

frostbytten opened this issue Feb 3, 2014 · 0 comments
Assignees
Labels

Comments

@frostbytten
Copy link
Member

When a variable is present in the DOME (or base data) in the format:

model____variable____path

It is not being put in the output. People are needed this to input fields that are missing (even if the translator doesn't support it).

e.g.

apsim__swcon__soil

SWCON should be addded to the soil (even outside the apsim translator?)

This should allow us to be more flexible when reading from a DOME. We might need to figure out if we need to have the model there or not.

IDEA Could we store the model specific variables in a map (for version 1.0) and then if the required model is being requested, insert it into the data. This might require more work than the above solution, but we have no control over the model translators. Unless we write a preprocessor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants