Presentation of oidb:

• Oifits explorer
• Oifits validation: L2/L3 portal, submission, L0 VEGA.
• Remarks: cases where the 1 year embargo is too short: students, long-term program. So adjustable embargo (up to 18 months ?) should be enable for L2 (and L1 in the future).
• we could imagine to get quick look feature for L1 data : a general calibration pipeline

Discussion about CHARA L0 metadata:

• Runs have a program number (eg., CLASSIC 10) that are not written in the oifits header for the moment. This program ID is linked to the PI name since 2005 (beggining of scheduling) on the schedule (pdf) : a student (Chris) is looking at this manually. In some months, we will have the run ID linked with the PI name. However, the schedule can be not representative of reality because of opportunity programs (ex: nova explosion).

• Default PI contact name : Theo. Otherwise: DataPI name

• On top of this, there are additionnal log files for each night : r0 and t0 values, messages such as lost fringes, acquisition stopped, etc….

• On the oidb instrument pages put link of weather and observations pages on the chara website
• Climb uses 2 calibrators

Roadmap:

L1 data:

• clearly encouraged to be on the database but we need to work on:
• the link Calibration/ SCI + manage the calibration grades : GRADING scheme to standardize with the community(IAU54).
• flag system (eg., 1 to 5) for calibration purpose: rms of the calibrator visiblities, order of the polynom that fit the calibrator points, numbers of calibration point, etc...

L0 is the priority:

• We are waiting for the access to the CHARA server : one directory with L0 information per night.
• Check if these files have all the L0 metadata we need from CLASSIC and CLIMB.
• Theo will contact John and Mike (MIRC, PAVO) through Gail Schaeffer to ask about sharing MIRC and PAVO L0 with the JMMC oidb.

NSF CHARA application results will be know by the end of August 2014.