LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  February 2013

QSERV-L February 2013

Subject:

Re: Proposition of discussion for our phone meeting

From:

"Daniel L. Wang" <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Thu, 7 Feb 2013 09:32:20 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (42 lines)

On 02/06/2013 05:13 PM, Douglas Smith wrote:
> #2: data loading - wait didn't we do the source partitioning and loading
> also
> yet?  Um, looking at the Source.sql in the pt11 is looks like what you need
> is: "--theta-column 6 --phi-column 9".  The rest of the options should work
> fine.  Actually I think I looked that before, and the other columns
> would also
> work, it seems that there are repeated ra and dec fields in the table,and
> looking at the data quickly the values appear to be the same.
>
We talked about this on the call, but let's put it in writing so we're 
less likely to forget.

Looking at Source.sql in pt11, column 6 and 9 are NOT what you want, 
although it may accidentally work for now. Remember that we are not 
partitioning tables in isolation. For LSST catalogs, there is always one 
single table that is "in charge," so to speak. For PT11 and 
production-targeted data, this table is "Object". Object is partitioned 
according to a particular ra and decl, and every other table that is 
partitioned must be partitioned using the same values of ra and decl 
from the Object table. In Source, these are raObject and declObject. 
This is done so that Source can be joined with Object using objectId. In 
theory, you could leave the (raObject and declObject) columns out, but 
you would need to join Source with Object on objectId in order to get 
the right coordinates for partitioning, which is just way too expensive. 
Thus the same code that creates source rows populates raObject and 
declObject along with objectId.

For Summer12 and Winter13 (so far), the data is not production-targeted. 
The schema is different, and there was no attempt (as far as I know) to 
use a production-like schema. In these cases, you need to be told which 
is the table "in charge," and which columns in the other tables are the 
appropriate ra and decl columns to use.

-Daniel

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use