Closed hombit closed 3 years ago
I found that PS1 dataset contains NaN redshift values, and NaN being casted to a long integer (here) is some weird number. Probably some type of the input data validation is needed?
Thanks for reporting this. parsnip
currently requires the redshift to be known, and lcdata
doesn't do any input data validation. Instead of using lcdata.read_hdf5('data/ps1.h5')
, use parsnip.load_dataset('data/ps1.h5')
instead. That will reject all of the light curves with NaN redshift values. I realize that this isn't documented anywhere right now. I'll update that, and add a more informative error message.
I released a new version of ParSNIP (v1.1.0) that should handle the situation that you ran into much more gracefully. Now if you try to run ParSNIP on a dataset that contains light curves without redshifts, it will prune those light curves from the dataset and output a warning suggesting that you use parsnip.load_dataset
instead. This should resolve this issue.
Some weird error happened when I run a sample script to predict
parsnip
encoding for PS1 datapip freeze