"Extra" historical names in metadata commented out
@ehariton is already working on this.
Since Feb 11, 2026.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Aviary variable metadata has a large number of "alternate" names for historical variables that trace where those values can be found inside the legacy codes, but not the same as names used to define an input file. These variables needed to be commented out to avoid conflicts with the converter utility, but retaining them may be useful for traceability and debugging.
A plan for these commented out variables is needed. Should they be added to a new key in the metadata to keep the F2A converter clean? Or perhaps documentation via comments is acceptable, and just re-formatting the commented out information is all that is needed.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response
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.
Assessment
This issue has not been assessed yet.