Swift-EAGLE IMF variations - #62
Conversation
|
Hi Chris, Thanks for contributing this. We should probably do this via the gitlab server since the github here is just a mirror updated every night. From a quick look at the changes, it seems everything is sensible. I would recommend running the example |
|
Are you still looking at using these changes? |
|
At some point yes. Should I move to gitlab now? |
|
That would be easier, yes. |
|
@christopherlovell could you move this to the gitlab if you want it integrated? |
|
I tried to get access to the Gitlab a while ago with Alastair's help, but no success. I'll look into it again |
|
You are a registered developer of the project there already. |
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?