On Tue, 27 May 2003, Giaretta, DL (David) wrote:
> Dear all
>
> I have significantly changed and put more details in the AstroGrid 2 bid -
> see section 4.2 and its sub-sections in
> http://wiki.astrogrid.org/bin/view/AG2/AgVirObInf I believe that it now fits
> in better with the rest of the AstroGrid bid and clarifies and reduces
> apparent overlap with other areas.
I take it that that the "web enabling" of Starlink apps is covered as part
of the AG-II bid. Is there some idea of whether Starlink will get a
guaranteed person or will Starlink fall off the bottom of the AstroGrid
bid if they don't get everyone they ask for?
>
> I have also added to the ESO bid - see
> http://wiki.starlink.ac.uk/twiki/bin/view/Starlink/ESODataProcessing
>
- You have missed IRIS-2 from the list of ORAC-DR support instruments.
- 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.
- including letters of support from UK users of ESO data would be helpful
I think but you might be running out of time. 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.
- Have ESO expressed an interest in your ISAAC pipeline? Is it to be
publicised in the ESO newsletter?
- The link to ORAC-DR at the bottom of the document does not work.
- I'm not sure about whether JAC should be a CoI or whether we can help
in that way. You should discuss that with Andy Adamson.
- I note that this bid is essentially supporting JAC's use of the
pipeline by saying that we need to support ESO. Supporting JAC clearly
does not get you money :-) [but see later my worries concerning manpower]
- You should point out the synergy between the "web enabling of
ORAC-DR/Starlink" and the processing of ESO data and how this fits into a
GRID-enabled future. Saying you are working towards grid-enabled pipeline
reduction of ESO data might sound good.
- 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?
- 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?
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|