You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have parquet files produced by LSDB which contain nested column "lc" with four fields: mjd, mag, magerr, band. I successfully hats-imported those files. However I have a weird problem in margin pipeline which tells me that struct-fields are in a wrong order (truncated):
Failed REDUCING stage for pixel: 0_9
worker address: tcp://127.0.0.1:38957
struct fields don't match or are in the wrong order: Input fields: struct<band: list<element: string>, mag: list<element: float>, magerr: list<element: uint16>, mjd: list<element: double>> output fields: struct<mjd: list<element: double>, mag: list<element: float>, magerr: list<element: uint16>, band: list<element: string>>
Example input catalog on PSC Bridges2: /ocean/projects/phy210048p/malanche/zubercal-filtering/hats/zubercal_vrrlyr. Tar file on Google Drive.
Before submitting
Please check the following:
I have described the situation in which the bug arose, including what code was executed, information about my environment, and any applicable data others will need to reproduce the problem.
I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a description of what I expected instead.
If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.
The text was updated successfully, but these errors were encountered:
Bug report
I have parquet files produced by LSDB which contain nested column "lc" with four fields: mjd, mag, magerr, band. I successfully hats-imported those files. However I have a weird problem in margin pipeline which tells me that struct-fields are in a wrong order (truncated):
Example input catalog on PSC Bridges2:
/ocean/projects/phy210048p/malanche/zubercal-filtering/hats/zubercal_vrrlyr
. Tar file on Google Drive.Before submitting
Please check the following:
The text was updated successfully, but these errors were encountered: