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

More clearly document what INPUT_FILE_PATH can be #666

Closed
jfrost-mo opened this issue May 31, 2024 · 1 comment
Closed

More clearly document what INPUT_FILE_PATH can be #666

jfrost-mo opened this issue May 31, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jfrost-mo
Copy link
Member

What problem does your feature request solve?

  • It is unclear from the documentation if this is a directory (as in the RES) or if this includes the files as well.
  • This is further complicated by the CSET_FILE_NAME_METADATA_PATTERN under CSET_INCREMENTAL_DATA_FETCH
  • This may be something that will become clearer when multiple dates can be added as I imagine it will use the naming conventions that people are used to when cycling over different forecast cycles.
  • Related: Having a directory in the INPUT_FILE_PATH breaks #549
@jfrost-mo jfrost-mo added documentation Improvements or additions to documentation enhancement New feature or request labels May 31, 2024
@jfrost-mo jfrost-mo added this to the 2024 Usability Review milestone May 31, 2024
@jfrost-mo
Copy link
Member Author

Fixed in #765.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant