Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Order in time what can be ordered #481

Closed
nevencaplar opened this issue Jan 31, 2025 · 2 comments
Closed

Order in time what can be ordered #481

nevencaplar opened this issue Jan 31, 2025 · 2 comments
Assignees
@camposandro

Comments

@nevencaplar
Copy link
Member

Order in time all Sources, DiaSources, ForcedSources per Object/DiaObject when possible. I.e., if we are working with nested data or ForcedSources where multiple sources have same healpix_29, order per time when the data was taken.
@nevencaplar nevencaplar moved this to Todo in HATS / LSDB Jan 31, 2025
@camposandro camposandro self-assigned this Feb 4, 2025
@camposandro camposandro moved this from Todo to In Progress in HATS / LSDB Feb 6, 2025
@camposandro
Copy link
Collaborator

camposandro commented Feb 6, 2025 •
edited
Loading

Sources/forced sources are currently ordered (for each object) by timestamp for nested "diaObject_lc" and "object_lc" catalogs. The sorting is performed in 05-Nesting.ipynb.

@camposandro
Copy link
Collaborator

Closing this issue as completed for the time being. For further source post-processing we should open new issues.

@github-project-automation github-project-automation bot moved this from In Progress to Done in HATS / LSDB Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@camposandro camposandro

Labels
None yet
Projects
HATS / LSDB
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nevencaplar @camposandro