Closed hopkins9942 closed 2 years ago
Thanks for the fixes! Just so I understand correctly:
Energy_err
(the v1
file)? This whole v1
issue passed me by somewhat, so we're still catching up with bugs introduced by it...download
functions are correct, but I don't think think we'd run into this issue, because as long as the main astroNN
file was downloaded first, all the astroNN
paths in DR>16 resolved to that one, so no additional downloads were triggered. And we generally use astroNN
through the allStar
interface, which first accesses the main astroNN
file. But good to fix!v0
file and confirmed it has Energy_Err
where v1
has Energy_err
.allStar
is first called with either use_astroNN_distances=True
or use_astroNN_ages=True
. In those cases the DR14 distance or age file would have been downloaded first and saved incorrectly as the main astroNN file for whatever DR is being used, preventing the correct file from being downloaded later on.
download.astroNNDistances
anddownload.astroNNAges
previously only downloaded DR14 distance and age files, regardless ofdr
argument, causing incorrect file to be saved as the combined astroNN file for DR16 and DR17. Now fixed sodownload.astroNN
is called for DR16 and DR17, downloading correct combined astroNN file.Judging by previous code in
read._add_astroNN_orbits
, the DR16 astroNN FITS file used to have a fieldEnergy_Err
, however in most up-to-date version (v1) this field has been changed toEnergy_err
to match DR17. Now fixed sofields_to_append
is the same for both DR16 and DR17. N.B. this bug only affects users withfitsio
installed, as withfitsio
FITS fields are case-sensitive whereas withastropy.io.fits
they are not.