While setting my first own calibration, i was confused by the several steps involved; this PR makes one of them automatic.
Namely, after using ./collect_calibration, one has to copy paste the commit hash into a config file. This is now done automatically, upon user confirmation.
Do you think user confirmation is necessary? Does it happen that we don't want to copy the hash, or to copy it to a different file?
Here is the new terminal output:
Type of change
[x] Minor change (default scenarios show only small differences)
Purpose of this PR
While setting my first own calibration, i was confused by the several steps involved; this PR makes one of them automatic. Namely, after using
./collect_calibration
, one has to copy paste the commit hash into a config file. This is now done automatically, upon user confirmation.Do you think user confirmation is necessary? Does it happen that we don't want to copy the hash, or to copy it to a different file?
Here is the new terminal output:![image](https://github.com/remindmodel/remind/assets/1883023/54397de6-5f80-4cf7-afad-175538808a67)
Type of change
Checklist:
remind2
where it was neededforbiddenColumnNames
in readCheckScenarioConfig.R in case the PR leads to deprecated switchesFAIL 0
in the output ofmake test
)CHANGELOG.md
has been updated correctlyFurther information (optional):