Data Flow for the SINGS SIRTF Data

Daniela Calzetti (STSci)

SINGS Team MeetingBaltimore, November 22nd, 2002

The Ideal World

SSC

SSC(IRS)

FTP?

STScI(team archive)

FTP

Arizona(MIPS)

STScI(IRAC)

SINGS TeamWeb

FTP?

The Real World

Step 1: from SSC to data-reduction teams: We requested `push-ftp’. However, AZ (and possibly STScI) will not allow it. `Active’ ftp retrieval by each of the three data-reduction institution? During both pre- and post-archive, SSC-to-PI communication expected when data are available: weekly e-mail? Other? Will SSC-to-PI communication contain instrument-relevant infos? Path for sorting BCD data between the three data-reduction institutions unclear; will individual teams receive e-mails? From PI (or designated person)? From SSC directly?

Step 2: from data-reduction teams to team archive: Weekly deliveries, on pre-defined day, from data-reduction teams to stsci anonymous ftp account. Delivery will need to contain products and readme file with explanation of individual files.

Designated person (DA with DC supervision) will take out the data from ftp site and position them in appropriate directory/ies for Web access. Data-quality team(s) are informed via e-mail. Feedback from them within (3 days? 1 week?). Who are the data-quality team(s)? Upon OK from data-quality team(s), entire Team will be informed of new available data via e-mail. Web table(s) updated. Self-discipline will be important to avoid out-of-schedule deliveries.

Step 3: Delivery of data products to SSC (IRSA?): Image/header delivery test performed by placement of image in stsci anonymous ftp account, and retrieval by SSC person (method may not be supportable by SSC). Option: periodic (weekly?) placement of data products on anonymous site for ftp access by SSC.

The Real World (2)

Image/Header delivery tests

Overlap of USNOA-2 sources on SINGS optical image using header’s world coordinates information. Performed on Nov 1st, 2002.