Closed mtakahiro closed 3 years ago
When using set_tabular_sfh
the units of Z
are 'absolute', not Z/Z_sun
or log(Z/Z_sun)
. So with sps.libraries == ('mist', 'miles')
you would set Z=np.ones_like(sfr) * 0.014
(for padova Z_sun is 0.019). Perhaps the docstring for set_tabular_sfh
could be worded more clearly. I've verified this produces spectra that are consistent within a few % (max difference around 2000AA) and the remaining difference likely due to the linear approximation used when SFH=3.
also, when zcontinuous=0
, logzsol
is ignored and the metallicity is set by the integer zmet
to one of the pre-computed SSP metallicity values (i.e., Z=sps.zlegend[sps.params["zmet"]]
). I believe the default is zmet=1
, which is the second lowest metallicity and therefore quite different from the default for zcontinuous=1
. Sorry for the changing behavior with different zcontinuous
values, it is inherited from fsps and we haven't made the effort to homogenize in the python interface.
You are right! I was providing Z in the units of Z_sun. Now switched to absolute values, the resulting SEDs look identical. And thanks for the note on the case with zcontinuous=0. I was a bit confused with an unchanged outcome despite different metallicity inputs. Your comment here makes sense.
I will close this issue. Thanks a lot!
Hi, I was checking the consistency between SEDs generated by a tabular SFH and functional one (here delayed tau model), somewhat similar to what was addressed previously (https://github.com/dfm/python-fsps/issues/91)
I found that resulting SEDs are different when metallicity was provided to the tabular SFHs, though the value was fixed to the solar, to match with the functional one (attached). When the metallicity was not provided, this does not happen.
The code I used was as following, and the version of fsps is 0.3.0. Could you advise me what makes the difference? When zcontinuous=0 for the functional SFH, the output SED changes but still differs from what I get from the tabular SFH.