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.

Sign up for GitHub

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

Jump to bottom

expected forecasts not generated correctly #9

Closed
wsavran opened this issue Jun 11, 2018 · 1 comment
Closed

expected forecasts not generated correctly #9

wsavran opened this issue Jun 11, 2018 · 1 comment
Assignees
@wsavran

Comments

@wsavran
Copy link
Owner

wsavran commented Jun 11, 2018 •
edited

Some models produce multiple forecasts or have inputs appended to the filename as metadata, but this information does not get reflected in the forecast group configuration file if the models have not run successfully. This causes the CSEP crawler to incorrectly identify expected forecasts when generating expected filenames programmatically with information contained in the forecast group configuration file.

example
in forecast group one-day-models-Md2-V12.10 contains the following models.
ETAS_HW
K3
ETAS_DROneDay
JANUSOneDay
SE2OneDay
ETAS_HW_K3_AVERAGE_Md2

the JANUSOneDay model produces the following forecasts
JANUSOneDay
JANUSOneDayEEPAS1F
JANUSOneDayPPE
JANUSOneDayTV

the K3 model produces the following forecast
K3Md2
@wsavran wsavran self-assigned this Jun 11, 2018
@wsavran
Copy link
Owner Author

wsavran commented Jun 13, 2018

fixed with pull request #11

@wsavran wsavran closed this as completed Jun 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsavran wsavran

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wsavran