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  January 2016

QSERV-L January 2016

Subject:

Re: webserv and butler issue

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 22 Jan 2016 08:37:43 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (61 lines)

When I point to my new STRIPE82L/v2, I am getting

AttributeError: 'HscMapper' object has no attribute 'map_fpC'


Nate, do you have time today? I'd like to sit with you and
sort these issues

Jacek



On 01/21/2016 06:29 PM, Kian-Tat Lim wrote:
> Jacek,
>
>> I noticed one more thing... imgserv is using by default this path
>>
>> /lsst7/releaseW13EP/
>
> 	That's the repository it was configured for.  You should be able
> to point that to your new STRIPE82L/v2 repository.  If the path was
> hard-coded in the prototype, you'll need to change it.
>
>> and that is another 194GB. At this point I am totally lost.
>>
>> I generated some catalog based on a subset of
>>
>> /raid/lauren/rerun/LSST/STRIPE82L/v2
>>
>> when producing the catalog I used something from _parent,
>
> 	We don't currently expect repositories to be moved or copied, in
> whole or in part.  We don't have tooling for doing that.  But you can do
> it manually.  You need to move the parts that contain the data you want
> (which you did) as well as the parts that define the repository
> structure itself (currently _mapper).  For certain dataset types, you
> also need the registry (registry.sqlite3).  You don't need to copy the
> _parent symlink; that's just a way of dividing the "effective"
> repository into physical pieces.  You also don't need to copy datasets
> that you're not using (like CALIB -- unless you want to access
> calibrations or reconstitute calexps from raw images).
>
>> That feels so convoluted I have no clue which subset I should
>> be copying over. K-T, do you know? Should I ask Laurie or Paul?
>
> 	Lauren, not Laurie.  I think you're almost there.  You may also
> need to modify the imgserv code/configuration to retrieve the proper
> dataset type (deepCoadd_calexp for /raid/lauren/... vs. deepCoadd for
> /lsst7/releaseW13EP).
>
>> Should I just give up and run the whole thing on lsst-dev?
>
> 	No, you shouldn't need to.
>

########################################################################
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