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

harvest data handling #105

Open
chporter opened this issue Sep 24, 2015 · 2 comments
Open

harvest data handling #105

chporter opened this issue Sep 24, 2015 · 2 comments
Assignees
Labels

Comments

@chporter
Copy link
Member

Problem: a dataset included "hacom" (harvest component). This was correctly put into a harvest event under management in the json. The DSSAT translator created a harvest event, but the model failed because there was no date associated with the event.

Solution: The translator should create a harvest event and give the date of the observed harvest. If there is no observed harvest date, then don't create the event.

@MengZhang
Copy link
Member

I think we should add another DOME function or use current DOME command to add this event date. User should mention which date or what kind of date rule should be applied to the harvest date. This is not the job for translator. If it is a observed value, we should use observed variable rather than a management variable. If there is no such variable in the observed variable list, could we add one for it?

@chporter
Copy link
Member Author

Meng;
This is a DSSAT translator failure, not a user input issue. Let’s discuss it when I get back.
Cheryl

From: MengZhang [mailto:notifications@github.com]
Sent: Thursday, September 24, 2015 8:54 PM
To: agmip/translator-dssat
Cc: Porter, Cheryl H
Subject: Re: [translator-dssat] harvest data handling (#105)

I think we should add another DOME function or use current DOME command to add this event date. User should mention which date or what kind of date rule should be applied to the harvest date. This is not the job for translator. If it is a observed value, we should use observed variable rather than a management variable. If there is no such variable in the observed variable list, could we add one for it?


Reply to this email directly or view it on GitHubhttps://github.com//issues/105#issuecomment-143093931.

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