JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for STARDEV Archives


STARDEV Archives

STARDEV Archives


STARDEV@JISCMAIL.AC.UK


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

STARDEV Home

STARDEV Home

STARDEV  2003

STARDEV 2003

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: e-Science bids

From:

Tim Jenness <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Wed, 28 May 2003 16:50:14 -1000

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (150 lines)

On Wed, 28 May 2003, Malcolm J. Currie wrote:

> > I take it that that the "web enabling" of Starlink apps is covered as part
>
> The E-SO bid doesn't make the point that ORAC-DR can already and cdoes
> access web-based information, such as catalogues.  Thus one aspect of
> e-science can be addressed before the Starlink applications are `web
> enabled'.

Good point. catalogue access is already in.

>
> >  - You have missed IRIS-2 from the list of ORAC-DR support instruments.
>
> Yes, and UIST is more than the IFU.  There is also a proof-of-concept
> NIRI (Gemini) implementation akin to the GMOS one.
>

I think the current draft AG-II may over emphasise the Gemini angle.

> >  - You probably should point out that this work is complementary to the
> > ESO pipelines since ESO are not supporting user pipelines, just pipelines
> > to monitor data quality.
>
> I thought it was, but it doesn't harm to repat the point phrased in a
> different fashion to drum it home.

Looking at the eclipse web page it seems to me that ECLIPSE could be
called from oracdr for certain operations if that would make it more ESO
friendly.

> On the Dalton point, we could say that in the consultation period that
> we are mindful not to duplicate "grid-enabled" packages being written
> for specific instruments.  I don't think that they're so complex that we
> can't manage.  ORAC-DIR may not be as efficient in cpu cycles because it
> may take a few steps of atomic applications rather than invoking a
> bespoke task to perform the algorithm in one go, but we can save
> programming time.  The modular nature also makes it more amenable to
> modification by astronomers. ORAC-DR does work on a variety of
> instruments, some of which have multiple modes, and we've coped already.
> We've adapted existing recipes to new instruments.  These facts
> demonstrate that we can develop ORAC-DR for complex instruments, if
> we need to.
>
> >  - including letters of support from UK users of ESO data would be helpful
> > I think but you might be running out of time.
>
> I did go through the couple of years UKIRT observer reports to find
> quotable comments about ORAC-DR.  If it's right ethically, as these
> confidential to JAC, we can mail these people asking for permission to
> quote them.  What do you reckon Tim?

Andy agrees that you can mail people who have given positive ORAC-DR
comments in the past.

>
> I have already suggested asking Mark Birkinshaw, Chairman of the AAO
> Board, given the favourable comments re. ORAC-DR introduction at the
> AAT.  John Davies can give a comparison of ORAC-DR versus his experience
> at the VLT.

Is there enough time for these people to respond?

>
> > One of the key benefits is
> > making life easy for UK users so that they can make the most out of our
> > ESO subscription. I think the benefits paragraph should be fleshed out
> > some more. Something about large demand from users, no support from ESO
> > etc etc.
>
> One of the main thrusts of the PPARC plan is to maximise the benefits of
> participation in ESO and Gemini.  So yes we should push this for all its
> worth.  Astronomers concentrating on science not software... etc.
>

I see no-one is asking for money to put Gemini fully into ORAC-DR.... :-)

> Our work may also benefit future instrument builders, who don't have to
> start from scratch, posibly leading to a saving in ESO's development
> budget.  (I don't know how new instruments are funded in ESO.)

Nor do I.

>
> >  - Have ESO expressed an interest in your ISAAC pipeline? Is it to be
> > publicised in the ESO newsletter?
>
> Not directly, but Derek told me that some people at ESO were impressed.
> I already decided we should have a piece in the "ESO Messenger" once the
> pipeline has been beta-tested.  Besides showing how wonderful ORAC-DR
> is, it can address some of the problems, which, for example, may lead to
> improvements to the headers as Tim suggests.
>
> I'm also going to ask for a link on the ISAAC reduction page.  The
> question of where isn't clear yet but it should have some overview,
> links to the Software Store to obtain ORAC-DR and to the various SUNs.
> BTW Tim the ORAC-DR home page is a little out of date.
>

Yes. Hmm. Well. Talk to Brad :-)

> >  - The one staff year sounds like the work required simply to generate a
> > wide range of recipes for ESO data. Actual supporting the Starlink
> > applications will be difficult for that person. Where is the money coming
> > from for that?
>
> Personally, I don't think one SY/y on the wide range of recipes is
> sufficient in the first year.  To make an impact on more than one
> multi-mode instrument instrument, even just considering what's already
> in the ESO Archive, let alone the new instruments coming.  We must have
> the main few instruments supported quickly to become the standard for UK
> reduction of ESO data.  Speaking personally, while it's fine for my
> Annual Report being a vital cog in the machinery, it's important to
> spread the expertise in ORAC-DR amongst the Starlink team.  This can
> also lead to further ideas and improvements for ORAC-DR.
>

If this is the only source of funding for starlink classic then at least 2
people should be funded from this since it sounds like there is no way for
one person to do all the ESO recipes *and* support the appplications and
add new state-of-the-art algorithms.

> The work plan should mention that we wish to improve the documentation
> for astronomers to adapt the recipes.  This includes the Programmer
> Manual.  Is xoracdr documented outside of itself?

Not as such. xoracdr is mentioned in passing but nothing more.

>
> >  - Are ESO amenable to tweaking their FITS headers (eg by putting in a DR
> > recipe or the dispersion) to make life easier for the pipeline?
>
> My contacts so far would suggest otherwise.  I've made a number of
> suggestions, and I get no feedback.  No even a "thank you for your
> comments, and we'll consider your suggestions".  I've not been impressed

Maybe you should arrange a face to face meeting. Surely it is useful for
Starlink programmers to at least meet with ESO programmers.

Spoke to Andy about Co-I status: he is happy to be put forward as a
supportive community member but the current slant of the proposal is such
that JAC as a CoI would seem bizarre (especially given that the current 1
man year is focussed entirely on ESO recipes without regard to algorithm
enhancements that may benefit the JAC).

--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
January 2023
December 2022
July 2022
June 2022
April 2022
March 2022
December 2021
October 2021
July 2021
April 2021
January 2021
October 2020
September 2020
August 2020
May 2020
November 2019
October 2019
July 2019
June 2019
February 2019
January 2019
December 2018
November 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
December 2017
October 2017
August 2017
July 2017
May 2017
April 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 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
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
2004
April 2003
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

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