updated default value listed in --maximum-evolution-time #1448
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

there is a minor type in the documentation and YAML file for --maximum-evolution-time
the default YAML file says "maximum-evolution-time: 14021.28" (https://github.com/TeamCOMPAS/COMPAS/blob/dev/compas_python_utils/preprocessing/compasConfigDefault.yaml ) but the online documentation says:
--maximum-evolution-time
Maximum time to evolve binaries (Myr). Evolution of the binary will stop if this number is reached. Default = 13700.0
The correct value is 14031, which is the value that one obtains when you take the HUBBLE_TIME value from src/constants.h (and use the default definition from src/Options.cpp which defines maximum-evolution-time as:
m_MaxEvolutionTime > HUBBLE_TIME / SECONDS_IN_MYR, which leads to 14031 Myr as the default (The 14021.28 Myr value comes from doing the same calculations but rounding values early on). More precisely, the calculation is: 1/ (67.8 * 1000.0 / (3.0* 10^(22))) seconds to Myr = 14031 Myr , with 67.8 from WMAP from the constant.h defaults.Again, not a big deal, just a rounding of the value/typo. So a very minor fix