search

ukaea / PROCESS

PROCESS is a systems code at UKAEA that calculates in a self-consistent manner the parameters of a fusion power plant with a specified performance, ensuring that its operating limits are not violated, and with the option to optimise to a given function of these parameters.
https://ukaea.github.io/PROCESS/
MIT License
30 stars 11 forks source link

Inconsistent recording of inputs and outputs in output files #3248

Open j-a-foster opened 1 month ago

j-a-foster commented 1 month ago

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.

mkovari commented 1 month ago

So at present the way to include an IP or OP tag is to fill in the relevant field in each individual output statement.

The ITV tags are added automatically.

Once we have a master file of all variables with their short descriptions, long descriptions etc, it will be a straightforward if lengthy job to add the IP and OP tags for those variables where these are fixed. Some variables can be input or output depending the values of the switches - tags for these variables will have to be added in the code.