Well, the crux of the problem as I see it is that Object in the sense of
an Object Table in the schema is not the same animal as an Astronomical
Object. Quite. So it gets a bit confusing. Especially since that
mapping changes as knowledge changes. Astronomical Object is a
perfectly appropriate thing to call a Thing, but then we have to
constantly re-determine if an Astronomical Object and and Object are the
same thing (Thing) or not. Its nomenclature, but I've watched it get
tripped over several times.
Jeffrey P Kantor wrote:
I think our UML model calls a Thing an Astronomical Object...see the Domain
Model:Catalogs:Astronomical Object classes...
From: Deborah Levine <[EMAIL PROTECTED]>
Organization: IPAC/SSC
Reply-To: [EMAIL PROTECTED], LSST Data Management
<[email protected]>
Date: Thu, 30 Nov 2006 13:57:35 -0800
To: LSST Data Management <[email protected]>
Subject: Re: [LSST-data] Notes from Database telecon Wed Nov 29
Actually, to me, "detection" sounds like a single data point in one band
on one night.... If I were starting from
scratch, I'd try to find a nomenclature that has separate and not easily
confused words for each of these things:
A single extractable flux from one filter at one observational epoch; a
single data point; a detection
All the extractable fluxes in all filters for one position for one
observational epoch; a visit
All the extractable fluxes in all filters which are believed to belong
to the same physical celestial entity; an "object"?
The actual physical celestial entity; a star, galaxy, solar system
object, etc. which is what I called Thing. Starting from scratch I
might call this an "object" or a "source"
Kem Cook wrote:
I think we should use detection for Deborah's Thing.
Kem
Hi All,
--> Deborah will try to summarize what info related to
confused/resolved objects will be readily needed
from database from a scientist point of view
Deborah has so attempted, the result is attached!
--
---------------------------------------------------------------------
Deborah Levine, Ph.D. (626)395-8567 (Office)
Operations Scientist (626)590-7500 (Mobile)
Spitzer Space Telescope Science Center (626)432-7484 (FAX)
Mail Code 314-6, Caltech [EMAIL PROTECTED]
Pasadena, CA 91125
"Make everything as simple as possible, but not simpler."
Albert Einstein
_______________________________________________
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
--
---------------------------------------------------------------------
Deborah Levine, Ph.D. (626)395-8567 (Office)
Operations Scientist (626)590-7500 (Mobile)
Spitzer Space Telescope Science Center (626)432-7484 (FAX)
Mail Code 314-6, Caltech [EMAIL PROTECTED]
Pasadena, CA 91125
"Make everything as simple as possible, but not simpler."
Albert Einstein
_______________________________________________
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
--
---------------------------------------------------------------------
Deborah Levine, Ph.D. (626)395-8567 (Office)
Operations Scientist (626)590-7500 (Mobile)
Spitzer Space Telescope Science Center (626)432-7484 (FAX)
Mail Code 314-6, Caltech [EMAIL PROTECTED]
Pasadena, CA 91125
"Make everything as simple as possible, but not simpler."
Albert Einstein
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
