If using the M_200 - c coupled halo option, h is set to h=0.671 km/s/Mpc (line 999 in physical_system.py). However, in iniparam_f.f90, h is set to 73 km/s/Mpc (line 80), which means it is possible for two different cosmologies to be adopted simultaneously within the code. Also, the M_200-c coupled halo relation used is only valid for z = 0 (but there are redshift dependent relations given in Dutton & Maccio 2014), which I think should be clarified in the documentation. More broadly, the hard-coding of a H_0 value in iniparam_f.f90 is not flexible to pushing the use cases of dynamite to higher redshifts.
If using the M_200 - c coupled halo option, h is set to h=0.671 km/s/Mpc (line 999 in physical_system.py). However, in iniparam_f.f90, h is set to 73 km/s/Mpc (line 80), which means it is possible for two different cosmologies to be adopted simultaneously within the code. Also, the M_200-c coupled halo relation used is only valid for z = 0 (but there are redshift dependent relations given in Dutton & Maccio 2014), which I think should be clarified in the documentation. More broadly, the hard-coding of a H_0 value in iniparam_f.f90 is not flexible to pushing the use cases of dynamite to higher redshifts.