Feature request: QCEFF tables for models
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 263
- Forks
- 182
- Avg merge
- 11d 12h
- Merged PRs (30d)
- 7
Description
Use case
Users looking to use the QCEFF have to build their own QCEFF table, which seems to be a barrier to entry.
Is your feature request related to a problem?
Ease of use,
- creating the table
- so many columns in the table
Describe your preferred solution
"Typical" qceff.csv for a model
not sure if this would be per-model, or per component, e.g. ocean models have "typical" qceff options, atm models have "typical" qceff options.
Is qceff a "set it and forget it" thing? bounded qty, bnrh?
Describe any alternatives you have considered
better interface for qceff, but this is unclear what is required. e.g. is it set and forget.
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 by clarifying how QCEFF tables are currently created and which columns users must provide. Resolve whether a typical qceff.csv should be per model or component, and whether settings such as bounded quantities and bnrh are persistent. Done should include an agreed table scope, interface, and model or component coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100