Skip to content

Merged input yaml records seed used - #130

Merged
lrobion merged 5 commits into
MIT-LAE:mainfrom
lrobion:merged-yaml-record
Aug 21, 2026
Merged

Merged input yaml records seed used#130
lrobion merged 5 commits into
MIT-LAE:mainfrom
lrobion:merged-yaml-record

Conversation

@lrobion

@lrobion lrobion commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Closes #120.
The merged-input.yaml generated in the output directory now records the seed that was used for a simulation even if Forced Seed was set to false in the original input.
Re-running a simulation with merged-input.yaml now reproduces (bitwise) the results of the original simulation. It is now an exact reproducibility artefact rather than an exact record of the user inputs (same logic as resolving the relative paths in inputs files to absolute paths before recording them).

E.g:
With this in the input.yaml passed to APCEMM:

  RANDOM NUMBER GENERATION SUBMENU:
    Force seed value (T/F): F
    Seed value (positive int): 0

The merged-input.yaml will be:

  RANDOM NUMBER GENERATION SUBMENU:
    Force seed value (T/F): T
    Seed value (positive int): =Actual value of the seed used by the simulation=

@lrobion
lrobion merged commit b746494 into MIT-LAE:main Aug 21, 2026
2 checks passed
@lrobion
lrobion deleted the merged-yaml-record branch August 21, 2026 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

merged-input.yaml choice: track exact inputs or allow for exact reproducibility?

1 participant