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  March 2014

QSERV-L March 2014

Subject:

Re: Notes from Qserv mtg (Mar 20)

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 21 Mar 2014 09:13:44 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (68 lines)

K-T

>>   - Serge has Eigen "emulator"
>
> 	Hmm.  Is this worth the maintenance and potential portability
> issues?

I am starting to be convinced we need a meeting sooner
than later to discuss this. After next week?


>>   - non elegant solution: if Eigen changes infrequently,
>>     perhaps just copy the header file over to our repo?
>
> 	It's not just one header, is it?

I haven't looked at the actual code, someone at the meeting
(Serge maybe?) mentioned it was just the header and I assumed
it is super light and everything is inside (Eg inlined)

> This sounds reallybad for a number of reasons.

yup, we all acknowledged that at the meeting


>>   - decision: existing Eigen emulator probably covers what
>>     is needed for Qserv, so continue with it for now, if
>>     we discover more work is needed, reconsider and possibly
>>     switch to using Eigen, in which case the dependency issue
>>     wouldn't be a problem any more for Qserv. If we stick with
>>     Eigen emulator, discuss w/Mario/Robert/Jim/KT
>
> 	I don't understand why there's an "If" in the last sentence
> given the decision in the first sentence.

If we stick with Eigen emulator, Jim still wants to have Euclidean
geom in geom.git, so we need to discuss it because it required Eigen
(or maybe could use the emulator). If we don't stick with the
emulator, Qserv will need Eigen in which case there is no issue,
we just have the dependency on Eigen from geom.git and then Jim
can easily add the Euclidean code to geom.git

> 	You will need to set up a separate Qserv agile board, then, so
> you can have your own sprints.

I was going to

> 	I think this can be arranged with Iain and Mario, but my
> impression was that the main stumbling block was getting an actual
> machine to use as the official platform.

Ok, I didn't know that.

> 	I haven't noticed any problems, but then again I get text
> E-mails.

I didn't get any either (maybe admins don't?) but all others from
my group present at the meeting (AndyS, AndyH, Serge and Daniel)
did get an email for every update I made in jira (hundreds)

Jacek

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