Inconsistent recording of inputs and outputs in output files
Open
@timothy-nunn is already working on this.
Since May 6, 2026.
Input/Output Files
Triaged
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
Description
There is an inconsistency in how variables are reported in the OUT.DAT and MFILE.DAT output files. Some variables are identified as iteration variables (ITV), inputs (IP), or outputs (OP). However, a lot of variables are not identified by any of these, some are inputs and some are outputs. It would be good if all variables in the output files are identified by what type of these variables they are.
I appreciate this might not be feasible as some variables might be inputs in one case, and outputs in another, but it would provide more clarity to what is actually being calculated in a PROCESS run.
Contributor guide
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.