documentation for filter_nml
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 263
- Forks
- 182
- Avg merge
- 11d 12h
- Merged PRs (30d)
- 7
Description
-
Difficult to find, does not show up in search (needs search term adding)
-
https://docs.dart.ucar.edu/en/latest/assimilation_code/modules/assimilation/filter_mod.html#namelist
Is this true? (No?) That a list of files is not supported. The option is in the code
| input_state_files | character(len=256), dimension(MAXFILES) | A list of the NetCDF files to open to read the state vectors. Models using multiple domains must put the domain and ensemble numbers in the file names. The order and format of those is to be determined. NOT SUPPORTED as of March, 2017. |
|---|
"The order and format of those is to be determined." 🙃
Same table for output_state_files:
| output_state_files | character(len=256), dimension(MAXFILES) | A list of the netCDF files to open for writing updated state vectors. Not supported when using multiple domains. |
|---|
The first search result for filter_nml is "diffs from lanai" which has a subset of namelist options, talks about list of files for small models.
https://docs.dart.ucar.edu/en/latest/guide/Manhattan_diffs_from_Lanai.html#filter-nml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked filter_mod namelist documentation and the Manhattan_diffs_from_Lanai.html filter_nml page. Compare their input_state_files and output_state_files descriptions with the current filter_nml implementation, then update the search term and tables so supported file-list behavior and naming limitations are accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100