-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some skysim5000 hdf5 files have an inconsistent schema which prevent their conversion to parquet #426
Comments
@patricialarsen @yymao The fact that this inconsistency is occurring in just a few healpixels is mysterious. Can you provide a list of the healpixels which have a problem so that we can investigate further? The first 2 variables are copied from the input files used for the production pipeline, so it is possible that those input files have an issue. The last variable is copied from UniverseMachine inputs. What exactly is the problem with baseDC2/source_halo_mvir? None of the above variables are actually produced by the production code and have been included in the catalog for completeness and provenance. Once we have tracked down the cause, it would be possible to regenerate the subset of affected healpixels. |
@evevkovacs Here is the list of problematic healpixels: Regarding baseDC2/source_halo_mvir, this is also a dtype mismatch in the files corresponding to the 3 redshift intervals |
A small fraction of the skysim5000 healpixels (52 out of 1568) in hdf5 format have an inconsistent schema for some native quantities which prevent their conversion to parquet format.
The following fields have been identified as possibly problematic:
lightcone_replication: int64
lightcone_rotation: int64
baseDC2/source_halo_mvir
The inconsistency is between the files corresponding to the 3 redshift intervals.
While it would be better to fix this problem upstream, it is also possible to hack the conversion script as in https://github.com/LSSTDESC/DC2-production/tree/u/boutigny/fix_schema_parquet_skysim
The text was updated successfully, but these errors were encountered: