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

detect FORCE_DTSTEP based on MET_TAG (?) #284

Open
gmao-rreichle opened this issue Jul 29, 2020 · 1 comment
Open

detect FORCE_DTSTEP based on MET_TAG (?) #284

gmao-rreichle opened this issue Jul 29, 2020 · 1 comment
Assignees
Labels
0-diff consistency check check guarding against user error

Comments

@gmao-rreichle
Copy link
Contributor

FORCE_DTSTEP depends on the forcing data set and could be determined from MET_TAG.

Rather than having FORCE_DTSTEP be a separate input in the "exeinp" file, it could be determined from a look-up table that pairs MET_TAG with the appropriate FORCE_DTSTEP value.

a) This could probably be done during ldas_setup. In this case, ldas_setup would still write FORCE_DTSTEP into LDAS.rc.

b) Alternatively, FORCE_DTSTEP could be removed entirely from LDAS.rc. In this case, GEOSldas would have to read and process the look-up table during the initialization of the MetForce GridComp. This option is probably more involved.

Option a) seems easier.

@gmao-rreichle gmao-rreichle self-assigned this Jul 29, 2020
@gmao-rreichle
Copy link
Contributor Author

In the meantime, some language was added to the documentation (see pull request #286 )
@gmao-jkolassa

@gmao-rreichle gmao-rreichle added the consistency check check guarding against user error label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0-diff consistency check check guarding against user error
Projects
None yet
Development

No branches or pull requests

1 participant