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
Currently the catalog representation copies the dask data frame lazy representation, which confuses users to thinking the data has been loaded, especially with the hipscat id column. Some other way of showing the table would be useful, and replacing the index column to show the HEALPix pixels instead of the hipscat id might be a good start for this.
The text was updated successfully, but these errors were encountered:
No, it is the same problem. I think we have decided to start first with removing hipscat id column values, and then evaluating based on the feedback if this is sufficient change.
Currently the catalog representation copies the dask data frame lazy representation, which confuses users to thinking the data has been loaded, especially with the hipscat id column. Some other way of showing the table would be useful, and replacing the index column to show the HEALPix pixels instead of the hipscat id might be a good start for this.
The text was updated successfully, but these errors were encountered: