I aim to vary cosmological parameters for inference, such as Omega_m, but when doing so I have come to the realization that the output fields are not obtained in the requested redshift range (zmin,zmax) for extreme omega_m.
Example:
z min: 3.6519546435033474 z max: 6.115043211898531 Omega m = 0.21
z min: 4.413734994173905 z max: 8.190620077801478 Omega m = 0.27
z min: 4.276968023137314 z max: 7.795646887915723 Omega m = 0.26
z min: 4.015662168524921 z max: 7.0687066375098295 Omega m = 0.24
z min: 3.8908066698121253 z max: 6.733851929344507 Omega m = 0.23
z min: 3.5376842962431434 z max: 5.828864570704496 Omega m = 0.2
z min: 3.7696175535864285 z max: 6.416350594784393 Omega m = 0.22
z min: 4.144331163376727 z max: 7.422178440708719 Omega m = 0.25
These printed redshifts are now min and max from lightcone.lightcone_redshifts and the inputed zmin,zmax is (5.0,10.0).
Why is that? Is it possible to strictly get light cones in the range I want?
I also have another, related, question. I have also found some realizations that that has the lightcone_redshifts in the wanted range, but below some threshold value, seed dependent, have the output fields never been filled but just goes to 0...
Example:
halo_sfr
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
halo_mass
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
brightness_temp
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
neutral_fraction
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
this is with the following set-up: {'M_TURN': 9.585523679998476, 'F_ESC10': -2.8209379003515362, 'F_STAR10': -2.1009746734330954, 'ALPHA_ESC': -0.6802421636474193, 'ALPHA_STAR': 0.05482920328295837, 'OMm': 0.21446160450707033}
Why would this have happened? Is there some parameter combination that triggers some type of "early stopping" in the field population process so they are initialized to be 0 but never populated below some redshift threshold?...
I aim to vary cosmological parameters for inference, such as Omega_m, but when doing so I have come to the realization that the output fields are not obtained in the requested redshift range (zmin,zmax) for extreme omega_m.
Example:
z min: 3.6519546435033474 z max: 6.115043211898531 Omega m = 0.21
z min: 4.413734994173905 z max: 8.190620077801478 Omega m = 0.27
z min: 4.276968023137314 z max: 7.795646887915723 Omega m = 0.26
z min: 4.015662168524921 z max: 7.0687066375098295 Omega m = 0.24
z min: 3.8908066698121253 z max: 6.733851929344507 Omega m = 0.23
z min: 3.5376842962431434 z max: 5.828864570704496 Omega m = 0.2
z min: 3.7696175535864285 z max: 6.416350594784393 Omega m = 0.22
z min: 4.144331163376727 z max: 7.422178440708719 Omega m = 0.25
These printed redshifts are now min and max from lightcone.lightcone_redshifts and the inputed zmin,zmax is (5.0,10.0).
Why is that? Is it possible to strictly get light cones in the range I want?
I also have another, related, question. I have also found some realizations that that has the lightcone_redshifts in the wanted range, but below some threshold value, seed dependent, have the output fields never been filled but just goes to 0...
Example:
halo_sfr
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
halo_mass
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
brightness_temp
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
neutral_fraction
z min/max in file: 5.0 12.001959
first nonzero z: 7.384826
last nonzero z : 12.001959
this is with the following set-up: {'M_TURN': 9.585523679998476, 'F_ESC10': -2.8209379003515362, 'F_STAR10': -2.1009746734330954, 'ALPHA_ESC': -0.6802421636474193, 'ALPHA_STAR': 0.05482920328295837, 'OMm': 0.21446160450707033}
Why would this have happened? Is there some parameter combination that triggers some type of "early stopping" in the field population process so they are initialized to be 0 but never populated below some redshift threshold?...