Details
-
Type:
Story
-
Status: In Progress
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: DM Subsystem Science, Requirements Documents
-
Labels:
-
Epic Link:
-
Team:DM Science
Description
From a Robert Lupton comment in LDM-151:
We need to define what we'll do with objects that are too large to fit in a single patch, even with overlaps
The simplest proposal is that we simply won't try to process them as single objects, but I think this is a question whose answer belongs in the DPDD. If we need to process objects up to a certain scale, that either puts a requirement on our patch sizes or will require special code to process them.
Attachments
Issue Links
- relates to
-
DM-9375 Revisit the Qserv neighbor-query radius (overlap distance)
- To Do
I would be ready to argue that we shouldn't try to process objects larger than some
limit - assuming that we would somehow record this decision and thus enable easy
identification of such cases and specialized post-processing as part of Level 3.
What angular scale do you have in mind?