Closed drd13 closed 4 years ago
Hi,
I think I understand why this happens: unlike MOOG, Turbospectrum does not use the atmosphere's abundances as the base of its model, so every abundance needs to be specified. While [a/Fe] needs to be separately passed to Turbospectrum, carbon is not, and if carbon was not specified as an abundance to be varied, its value was not passed to the line that takes into account the atmosphere's carbon content. I'm surprised that I made this mistake, because I was aware of this Turbospectrum feature when I wrote it, butI guess I never noticed.
I committed a fix that I think should address the issue, but I haven't tested it. Could you test it and let me know?
Hi,
There were some issues related to tuples being immutable. After modifying
if not 6 in [elem[0] for elem in args]:
args= args+([6,0.])
to
if not 6 in [elem[0] for elem in args]:
args= args+([6,0.],)
the output is what I would expect.
I'll let you do the commit. Thank you for maintaining the package and the quick response!
Oops, messed that up, thanks for checking! (I had even tested the line, but forgot the final comma in editing the actual code...). And thanks for a very well described issue, makes it much easier to fix the code!
Hi,
I'm using turbospectrum and Atlas9 to generate synthetic spectra and I've noticed what might be a bug. The parameter
cm
does not seem to modify the carbon in the spectra. This can, for example, be seen by using FERRE to retrieve synthetically generated spectra.Here is a figure showing retrieved
cm
againstcm
input parameter. I've also attached the code required to reproduce it below.Here is the same thing for
am
which shows the behavior I would have expected.I am using the atlas9 synthetic spectra as obtained from http://research.iac.es/proyecto/ATLAS-APOGEE//. I imagine that this could maybe be due to a difference between whether the apogee colaborator atlas grid is used.
Code for reproducing cm figure
Code for reproducing am figure