Yes, I think the fast moving objects will be kept in a separate
catalog (called Orbit Catalog I think), and the issue I am raising
is for slow moving objects. So the question is whether slowly moving
object can move more than one chunk per night?
thanks,
Jacek
Serge Monkewitz wrote:
Kem - I just assumed there was a seperate table for moving objects so
this is good to hear, but ... what about really slow movers? Will the
MOP be able to detect and track an object that crosses a chunk over the
course of 6 months? 1yr? Put another way, do we need to assume some kind
of small but still significant (over the course of a release cycle)
velocity for objects in the main object table (especially leading up to
DR1 since the deep/moving pipelines won't have had very much time to
discover/tell eachother about such objects)?
Thanks,
Serge
On Tue, 21 Nov 2006 16:43:06 -0800, Kem Cook <[EMAIL PROTECTED]> wrote:
Hi Jacek,
Your partitioning makes perfect sense, but there will be a few objects
which move more than quite a bit more than 1 chunk per night. But, I
think we were going to be keeping the moving obectsd in a separate table,
for this, as well as other, reasons.
cheers,
Kem
Keywords: DataAccWG
Hello,
Here is a brand new suggestion how to partition Object table
for the nightly processing use case:
http://www.slac.stanford.edu/~becla/tmp/objectTablePartitioningAtBase.doc
Hope we will have time to talk about it during the telecon tomorrow.
Jacek
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
