Swift-EAGLE IMF variations #62
Draft
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.
In progress work towards supporting arbitrary stellar initial mass function parametrisations in the Swift-EAGLE model.
In order to support an arbitrary IMF the code must be updated so that the feedback, enrichment and star formation models use the same self consistent IMF assumptions.
Feedback and enrichment changes:
feedback/EAGLE/imf.h. These include Chabrier+03, Salpeter+55, Kroupa+05, and a custom broken power law. Defaults to Chabrier+03 to ensure backwards compatibility.examples/EAGLE_low_z/EAGLE_6/imf_example_6.ymlwith the new (optional) IMF configuration options.Star formation changes:
tools/,imf_ks_normalisation.py, which uses FSPS to find the new normalisation of the Kennicut-Schmidt relation used in the EAGLE star formation model.Questions / TODOs:
EAGLEStarFormation:KS_normalisationwhen users choose a new IMF? Should we tabulate some common values using the FSPS script, as well as a table for different broken power law choices that can be interpolated? Or should this be left to the user to update manually?