Open hover2pi opened 6 years ago
I think you should report this to RedCat. They use JIRA. Maybe @rizeladiaz can advise. Thanks, Rossy!
@rizeladiaz Hi Rossy! Any leads on this issue? Should I talk to someone specific on the RedCat Team about it? We're still not sure how many of the models are wrong or if this is an isolated incident but it is definitely problematic.
Also, is the code that generates this accessible, i.e. is there a RedCat repo I should move this issue to?
Also, this may be related to #74. Thanks!
@hover2pi If you haven't already, please open a ticket in the Jira RedCAT project about this.
Some exoplanet folks noticed that the
Phoenix
model atmospheres retrieved by theIcat
class were strange so I looked into it. It appears that some of the models are incorrect and don't match the flux density of the rawPhoenix
models.In particular,
pysynphot.Icat('phoenix', 6000, 0, 5)
is an extreme example butpysynphot.Icat('phoenix', 6000, 0, 4)
is also too cool by about 400K. I compared theIcat
results to the files they are pulled from at/grp/hst/cdbs/grid/phoenix/
and they appear to be identical so the fault isn't withpysynphot
. Instead, whatever script was used to process the rawPhoenix
models and generate the FITS files on the ST servers appears to have made some errors. Perhaps, when interpolating to align the wavelength arrays?I'm not sure if this problem extends beyond Teff=6000 but I would strongly suspect it. Just wanted to leave a note here so it can be looked into.
I made a Jupyter notebook to do this analysis if you want to have a look. Thanks!