Refactor output.R

[simonkrogmann]

Purpose of this PR

• I replaced parts of the command line parsing with the standard solution optparse (already a dependency of remind) instead of a self-rolled script in remind. This avoids dumping all parameters into the global namespace which is error-prone. The help function and documentation is now more like to stay up-to-date. This produces some changes:
  • all parameters now need to be prefixed with --
  • the parameter outputdir is changed to outputdirs
• I split the script into functions and prepared a later refactoring where the whole script can be called as a normal function.
• I removed some backwards compatibility code that seem to not have been used for years. Is it ok to remove them.
  • supporting ,cfg instead of .Rdata run files
  • boolean flag comp

I have tested some scripts with some parameter configurations but an exhaustive test is infeasible for me.

Type of change

Indicate the items relevant for your PR by replacing ◻️ with ☑️.
Do not delete any lines. This makes it easier to understand which areas are affected by your changes and which are not.

Parts concerned

• ◻️ GAMS Code
• ☑️ R-scripts
• ☑️ Documentation (GAMS incode documentation, comments, tutorials)
• ◻️ Input data / CES parameters
• ◻️ Tests, CI/CD (continuous integration/deployment)
• ◻️ Configuration (switches in main.gms, default.cfg, and scenario_config*.csv files)
• ◻️ Other (please give a description)

Impact

• ◻️ Bug fix
• ☑️ Refactoring
• ◻️ New feature
• ◻️ Change of parameter values or input data (including CES parameters)
• ◻️ Minor change (default scenarios show only small differences)
• ◻️ Fundamental change of results of default scenarios

Checklist

Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge.

• I executed the automated model tests (make test) after my final commit and all tests pass (FAIL 0)
• I adjusted the reporting in remind2 if and where it was needed
• I adjusted the madrat packages (mrremind and other packages involved) for input data generation if and where it was needed
• My code follows the coding etiquette
• I explained my changes within the PR, particularly in hard-to-understand areas
• I checked that the in-code documentation is up-to-date
• I adjusted forbiddenColumnNames in readCheckScenarioConfig.R in case the PR leads to deprecated switches
• I updated the CHANGELOG.md correctly (added, changed, fixed, removed, input data/calibration)

Further information (optional)

I'm happy about feedback on the renv handling that this PR touches only tangentially.

[simonkrogmann]

This could be simplified further if loading optparse before the renv is a possible. I;m not sure whether this is possible.