the qso project: specifications and design of the phase ii

Canada - France - Hawaii Telescope Corporation Société du Télescope Canada - France - Hawaii P.O. Box 1597 Kamuela, Hawaii 96743 USA Telephone (808) 885-7944 FAX (808) 885-7288

The QSO Project:Specifications and Design of the Phase II Database

Prepared by: Renaud Savalle & Pierre MartinQSO-007/06-13-2000/Version 1.0/Draft

1. Document Scope2. Phase II Database: Purpose3. Phase II Database: Specifications, Architecture, Tables and Entry Fields4. Test and Release--------------------------------------------------------------------------------------------------------------------------------------

1. Document Scope

This document presents the specifications and design of the Phase II database for the Queued Service Observations (QSO) Project. It also briefly describes the resources necessary (software and hardware) as well as the interaction with NEO. The documentinserted has been produced through Power Designer, an application tool for designing and implementing Sybase relationaldatabase, and includes the details of the conceptual model (CDM) and physical model (PDM) of the QSO database.

2. The Phase II Database: Purpose

The Phase II database is the “brain” of the entire QSO operational mode (see QSO Scope document QSO-001). It plays a majorrole during the proposal submission phase and the execution of the observations. It might also be used as a reference during theanalysis and distribution of the data. The global interaction with the other different software components of the QSO and theELIXIR and DAD Projects is illustrated in Figure 1.

Figure 1. Interaction between the Phase II Database and other software components

Phase II Database

Phase II Tool

Phase I Database

Q Scheduler

Electronic LogbookDBMS

Elixir

Observation Tool

DAD

Data Information

2

The Phase II database has these specific functions:

a) Phase I database entry fields and records: Relevant data from the Phase I database, obtained from the Phase I submissionproposal through the Phase I tool, must be parsed to the Phase II database prior to the Phase II submission proposal deadline.

b) Phase II Tool: The Phase II submission is a key step for the QSO mode. The Phase II database must include all the detailsfor the execution of the observations, including the specific constraints for a given science program. The Phase II databaseis populated with the Phase II tool, a Web-based interface (see QSO-006 and QSO-008). The Phase II database design mustprovide data integrity throughout the submission process.

c) DataBase Management Software (DBMS): The Phase II database must be manageable (e.g. to modify entry fields) from adatabase management software.

d) Electronic Logbook: Some entry fields of the database must be editable from the electronic logbook, available for the QSOobservers.

e) Q Scheduler: The Phase II database tables must be parsed by the Q scheduler software in order to produce a prioritized listof programs for a given observing night.

f) Observation Tool: The observation parses all the relevant parameters necessary for the execution of one observation (or asequence of observations), contained in the Phase II database.

g) Data: An important function of the Phase II database is to tabulate the relevant information for the images produced throughNEO. Most relevant information is parsed from the fits headers. Some tables in the database are operational, that is, theircontent will change frequently during a QSO run.

h) Elixir and DAD: The Phase II database stores the information for all the observing programs, including the identification ofthe exposures. This information would be useful for Elixir and DAD. Moreover, for DAD, the relevant information (e.g. PIaddress) for the distribution of the data will be available.

3. Phase II Database: Specifications, Architecture, Tables and Entry Fields

The Phase II relational database is constituted of a complex network of tables linked through specific relationships. These tables(or entities) contain a series of entry fields (or attributes) which are defined during the Phase II proposal submission or duringthe observations. These fields have a value of a specific format that might be mandatory or not. These fields also might be foundwithin a specific domain of values or might take any value. Relevant fields are parsed to the executable observing scripts residingin NEO for the execution of the observation blocks. Some characteristics of the Phase II Database:

1. The database must be in the second normal form to avoid unwanted loss of information and ensure data integrity.

2. The database and database server must be designed to ensure reliability. Redundancy provided by mirrored and replicatedserver is absolutely necessary. (see document QSO-008).

3. The database must be backed up regularly and the QSO Coordinator entirely and exclusively ensures management.

3

The design of the database must first be done through a Conceptual Database Model (CDM) in which the entities, attributes,domains and business rules are defined. This CDM is presented here in the document attached. The Physical Database Model(PDM) can then be generated from the CDM.

4. Test and Release

The database is an essential part of the implementation of the Phase II tool, the Q scheduler and all the other observing tools relatedto queued observations. It is then very important to have a database fully operational for the development and testing phases ofthese tools. Hence, the database should be available just before starting the Phase II Tool implemented.

The database has to be fully operational for the Phase II submission phase for the semester 2001A, which will start on Dec 1st,2000. The relevant information from the Phase I database (Poopsy) should have been fully parsed by November 1st, 2000,allowing one full month of testing and preparing the Phase II tool for the submission of the observation blocks for the scienceprograms to be executed in 2001A.

4

Standard CDM report

5

Table of ContentsCDM Graphs .............................................................................................................................................................. 7

Global model Graph ................................................................................................................................................ 7Lists of objects.......................................................................................................................................................... 10

Business Rule List ................................................................................................................................................. 10Domain List .......................................................................................................................................................... 10Data Item List ....................................................................................................................................................... 11Entity List ............................................................................................................................................................. 16Relationship List ................................................................................................................................................... 17

Entity Information..................................................................................................................................................... 19Entity Airmass....................................................................................................................................................... 19Entity Binning ....................................................................................................................................................... 20Entity Binning Assignement................................................................................................................................... 22Entity CoI Assignment .......................................................................................................................................... 23Entity Constraint ................................................................................................................................................... 23Entity Ephemeris................................................................................................................................................... 25Entity Events......................................................................................................................................................... 27Entity Exposures ................................................................................................................................................... 29Entity Filter ........................................................................................................................................................... 50Entity Filter Assignment ........................................................................................................................................ 52Entity IC Sequence................................................................................................................................................ 52Entity Image Quality ............................................................................................................................................. 53Entity Instrument .................................................................................................................................................. 55Entity Instrument Configuration ............................................................................................................................ 59Entity OB.............................................................................................................................................................. 62Entity OB Priority ................................................................................................................................................. 67Entity Observation ................................................................................................................................................ 68Entity Observation Conditions............................................................................................................................... 70Entity Offset.......................................................................................................................................................... 75Entity Pattern ........................................................................................................................................................ 77Entity Pointing ...................................................................................................................................................... 79Entity Program...................................................................................................................................................... 81Entity Site ............................................................................................................................................................. 90Entity Sky Background ......................................................................................................................................... 92Entity Target......................................................................................................................................................... 94Entity Target defined By Ephemeris ...................................................................................................................... 97Entity Target defined by OE.................................................................................................................................. 98Entity Target defined by RA and DEC................................................................................................................. 102Entity Tracking ................................................................................................................................................... 104Entity User.......................................................................................................................................................... 105

Relationships Information........................................................................................................................................ 109Relationship Binning Is Avail On Instr................................................................................................................. 109Relationship Constraint Features Airmass ............................................................................................................ 109

6

Relationship Constraint Features IQ .................................................................................................................... 110Relationship Constraint Features Sky Bg ............................................................................................................. 110Relationship Event Is Related To Prg .................................................................................................................. 111Relationship Event Was Recorded By.................................................................................................................. 111Relationship Filter Is Avail On Instr..................................................................................................................... 112Relationship IC Occurs In IC Sequence ............................................................................................................... 112Relationship IC Uses Binning .............................................................................................................................. 113Relationship IC Uses Filter .................................................................................................................................. 113Relationship Instr Features Binning ..................................................................................................................... 114Relationship Instr Features Filter ......................................................................................................................... 114Relationship Is Obsed With Priority..................................................................................................................... 115Relationship Ob Is Obsed Using ICs In................................................................................................................ 116Relationship OB Is Obsed Using Tracking........................................................................................................... 116Relationship OB Is Observable Under Const........................................................................................................ 117Relationship OB Is Observed In Exp ................................................................................................................... 117Relationship OB Is Observed Under Condition .................................................................................................... 118Relationship Observation Is Defined In OB.......................................................................................................... 118Relationship Pattern Is Defined By Offset............................................................................................................ 119Relationship Pattern Is Used By IC...................................................................................................................... 119Relationship Prg Is Made Of Observations........................................................................................................... 120Relationship Prg Observes Target........................................................................................................................ 120Relationship Program Has CoIs........................................................................................................................... 121Relationship Program Owns Constraints.............................................................................................................. 121Relationship Program Owns ICs.......................................................................................................................... 122Relationship Program Owns OBs ........................................................................................................................ 122Relationship Program Uses Instr.......................................................................................................................... 123Relationship Target Ephem Must Have Ephemeris Defined By ............................................................................ 124Relationship Target Is Obsed In OB .................................................................................................................... 124Relationship Target Is Pted By Pointing .............................................................................................................. 125Relationship Target OE May Have Ephemeris Defined By................................................................................... 125Relationship User Co Investigates ....................................................................................................................... 126Relationship User Is PI........................................................................................................................................ 126Relationship User Own Poiting............................................................................................................................ 127Relationship User Owns Pattern .......................................................................................................................... 127

7

CDM Graphs

Global model Graph

8

[0,n]

[1,1]

Is Obsed With Priority

[0,n] [1,1]OB Is Obsed Using Tracking

[0,n]

[1,1]

Event Is Related To Prg

[0,n]

[0,1]Event Was Recorded By

[0,n]

[1,1]

Constraint Features Airmass

[0,n]

[1,1]

Constraint Features Sky Bg

[0,n]

[1,1]Constraint Features IQ

[1,n][1,1]Instr Features Binning

[1,n]

[1,1]

Binning Is Avail On Instr

[0,n]

[1,1]IC Uses Binning

[0,n]

[1,1]IC Uses Filter

[1,n][1,1]Instr Features Filter

[1,n]

[1,1]Filter Is Avail On Instr

[0,n]

[1,1]

Program Uses Instr

[1,n]

[1,1]

OB Is Observed In Exp

[0,n]

[0,1]

User Own Poiting

[0,n]

[0,1]

User Owns Pattern

[0,n]

[1,1]

OB Is Observed Under Condition

[0,n]

[1,1]

Target OE May Have Ephemeris Defined By

[1,n]

[1,1]

Target Ephem Must Have Ephemeris Defined By

[0,n]

[1,1]

Program Has CoIs

[0,n]

[1,1]

User Co Investigates

[0,n]

[1,1]

User Is PI

[0,n]

[1,1]Target Is Pted By Pointing

[0,n]

[1,1]

Pattern Is Defined By Offset

[1,n]

[0,1]

Observation Is Defined In OB

[0,n]

[1,1]Prg Is Made Of Observations

[1,n]

[1,1]

Program Owns Constraints

[0,n]

[1,1]Program Owns ICs

[1,1]

[0,1]

Ob Is Obsed Using ICs In

[0,1]

[1,1]

IC Occurs In IC Sequence

[0,n]

[1,1]Pattern Is Used By IC

Special Target Inherites Target GP GC id

[1,1]

[0,1]

OB Is Observable Under Const

[0,n]

[1,1]

Target Is Obsed In OB

[1,n]

[1,1]Program Owns OBs

[1,n]

[1,1]

Prg Observes Target

User

Id NO11 Mand.First Name VA40 Mand.Last Name VA40 Mand.Institute VA100 Mand.Address1 VA100Address2 VA100Address3 VA100State VA40Zip Code VA10City VA20Country VA20 Mand.Work Phone VA20 Mand.Work Email VA40 Mand.Work Fax VA20User ID VA20Ph1 User ID VA20Password VA40Ph1 Password VA40Status VA20 Mand.

Conceptual Data Model

Project : Phase II Database Design

Model : Ph2DB

Author : Renaud Savalle and Pierre Martin Version 2.8 06/13/2000

Program

Id NO11 Mand.Run id VA10 Mand.Agency VA10 Mand.Title VA200 Mand.Abstract TXT1000 Mand.Tech_Feas TXT1000 Mand.PhaseII Comment TXT1000TAC Rank A1 Mand.TAC Grade N3,1 Mand.Allocated I_Time N8,1 Mand.Calculated I_Time N8,1Used I_Time N8,1 Mand.Photometric Flag BL Mand.Monitor Flag BL Mand.Moving Fields Flag BL Mand.Need Quick Data Access BL Mand.Status VA20 Mand.Type VA20 Mand.

Target

Id NO11 Mand.Label N3 Mand.Name VA20Magnitude N3,1Checked by PI BL Mand.Ph2 Comment VA40Apparent RA VA11Apparent DEC VA11Currently Observable BL Mand.

Constraint

Id NO11 Mand.Label N2 Mand.Name VA20

Observation Conditions

Id NO11 Mand.Date of insertion (local) DTJulian Date N14,7 Mand.Date LST DT Mand.Date UT DT Mand.Air Temperature N3,1Wind Speed N4,1Wind Direction N4,1Relative Humidity N4,1IQ Observed N3,2 Mand.Sky Background FEvaluation A1

Instrument Configuration

Id NO11 Mand.Label N2 Mand.Name VA20Raster VA20 Mand.Exp Time N6,1 Mand.Pattern Radius F Mand.

OB

Id NO11 Mand.Label N3 Mand.Q Run Id VA10I Time N6,1 Mand.Status VA20 Mand.Comment VA100Is Monitoring OB ? BL Mand.Mon Period (h) N6,1Mon Min number of iter SIMon Number of iter SI

Pointing

Id NO11 Mand.Name VA5 Mand.RA Pointing Offset VA8 Mand.DEC Pointing Offset VA8 Mand.Is User BL Mand.Available for PH2 ? BL Mand.

Target defined by OE

Longitude F Mand.Semi_Major Axis F Mand.Excentricity F Mand.Inclination F Mand.Ascending Node Long F Mand.Perihelion Long F Mand.Equinox for orbital elts F Mand.Minimal Elongation F Mand.Maximal Elongation F Mand.

Target defined by RA and DEC

Requested RA VA11Requested DEC VA11Requested PM RA F Mand.Requested PM DEC F Mand.Requested Equinox N5,1 Mand.

Pattern

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.Description VA200 Mand.Is User BL Mand.Available for PH2 ? BL Mand.

Ephemeris

Id NO11 Mand.RA VA11 Mand.DEC VA11 Mand.Date and Time UT DT Mand.Type VA10 Mand.

IC Sequence

Id NO11 Mand.Number SI Mand.

LEGEND:How to read the relationships:Cf PD Manual pp 135-136

EXAMPLE1) When displaying roles on the relationship USER <---[0,n] owns-------[1,1] belongs to---> PROGRAMMEANS1) one (instance of entity User/row of table usr) USER: owns: [0 to n] (row of table) PROGRAMS 2) one (instance of entity User/row of table usr) PROGRAM: belongs to: [1 and only 1] (row of table) USER

EXAMPLE2) When displaying names on the relationshipUSER <--- [0,n]-- User is a PI --[1,1]--> PROGRAMMEANS1) User is a PI for 0..n programs2) A program has [1 and only 1 PI]

NB: | = mandatoryo = optional

Observation

Id NO11 Mand.Type VA10 Mand.Label N2 Mand.Number SI Mand.

Offset

Id NO11 Mand.Exp Number SI Mand.RA Offset VA8 Mand.DEC Offset VA8 Mand.

CoI Assignment

Target defined By Ephemeris

WARNINGS:Do not use domain for Id (serial will propagate to foreign keys in the PDM !)Do not overwrite checks of items by defining new check on domains and propagating the checks !

MANDATORY AND DEFAULTSBoolean attributes must be mandatoryNo default for string values: NULL serves as a default value thenAllow more NULL in tables modified by PH2 (targets etc)

Explain the meaning of NULL for all non mandatory columns in ANNOTATION

Exposures

id NO11 Mand.Local Date and time of insert DT Mand.Local Date and time of observation DT Mand.Julian Date at exp start N14,7 Mand.[FITS] Instrument VA20 Mand.[FITS] Q Run Id VA10 Mand.[FITS] Run Id VA20 Mand.[FITS] Label of OB VA10 Mand.[FITS] Exposure Type VA10 Mand.[FITS] Exposure Id N7 Mand.[FITS] Filename VA10 Mand.[FITS] Filter used VA10 Mand.[FITS] Exposure Time N6,2 Mand.[FITS] Object VA40 Mand.[FITS] Observer VA40 Mand.[FITS] Name of PI VA40 Mand.[FITS] [TCS] Date UTC at exp start VA10 Mand.[FITS] [TCS] Time UTC at exp start VA11 Mand.[FITS] [TCS] LST at exp start VA11 Mand.[FITS] [TCS] MJD at exp start N14,7 Mand.[FITS] [TCS] Pointed RA VA11 Mand.[FITS] [TCS] Pointed DEC VA11 Mand.[FITS] [TCS] Equinox of obs N5,1 Mand.[FITS] [TCS] Airmass F Mand.[FITS] Raster used VA20 Mand.[FITS] Binning factor X N2 Mand.[FITS] Binning factor Y N2 Mand.[FITS] Temperature of CCD N4,1 Mand.[FITS] Duration of shutter open N6,2 Mand.[FITS] Duration of shutter close N6,2 Mand.[FITS] Date of file creation VA19 Mand.

Site

Id NO10 Mand.Is Current BL Mand.Observatory Id N4 Mand.Name VA20 Mand.Timezone VA10 Mand.Time difference from UTC N2 Mand.Longitude N7,4 Mand.Lattitude N7,5 Mand.Elevation N4 Mand.

Instrument

Id NO11 Mand.Name VA10 Mand.Mosaic Total Width N6 Mand.Mosaic Total Height N6 Mand.Number of Chips wide N2 Mand.Number of Chips high N2 Mand.Pixel Size N3,1 Mand.Pixel Scale N5,4 Mand.Chip Width N5 Mand.Chip Height N5 Mand.

Filter

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.Description VA100 Mand.Available for PH2 ? BL Mand.

Filter Assignment

Binning

Id NO11 Mand.Name VA20 Mand.Value N1 Mand.Available for PH2 ? BL Mand.

Binning Assignement

Image Quality

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.Description VA100Available for PH2 ? BL Mand.

Sky Background

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.Description VA100Available for PH2 ? BL Mand.

Airmass

Id NO11 Mand.Name VA20 Mand.Value N1 Mand.Description VA100Available for PH2 ? BL Mand.

Events

Id NO11 Mand.Date DT Mand.Module VA20 Mand.Event VA20 Mand.Parameters VA200 Mand.

Tracking

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.

OB Priority

Id NO11 Mand.Name VA20 Mand.Value VA20 Mand.

10

Lists of objects

Business Rule List

Name Code Type Expr

U

Calc of OB calc_of_ob Definition

No No

Calc of OB I_Time calc_itime_ob Formula No NoCalc of Observation I_Time calc_itime_obs Formula No NoCalc of Program I_Time calc_itime_prg Formula No NoMax I_Time of an OB ob_max_itime Validatio

nNo No

Max iter_min for a mon OB mon_ob_max_iter_min Validation

Yes Yes

Min I_Time of a prg prg_min_itime Validation

No No

Domain List

Name Code TypeBig Integration Time in seconds int_time_s_big N8,1Date and Time UT datetime DTEmail Address email VA40Float coordinate offset coord_offset_float FFloat coordinates coord_float FFloat Equinox equinox_accurate FIntegration Time in seconds int_time_s N6,1Julian Date with second accuracy julian_date N14,7Label with 1 digit label1 N1Label with 2 digits label2 N2Label with 3 digits label3 N3Large Text text_l VA100Magnitude magnitude N3,1Medium Text text_m VA40Oribital Element oribital_element FPassword password VA40Period between OBs period N6,1Phone Number phone VA20Simple Equinox equinox_simple N5,1Small Text text_s VA20Small Text2 text_s2 VA20String coordinate offset coord_offset_string VA8String coordinates coord_string VA11

11

Name Code TypeUser Id user_id VA20Very Large Text text_xl VA200Very Small Text text_xs VA10Very very large text text_xxl TXT1000Zip Code zip_code VA10

Data Item List

Name Code Type[FITS] [TCS] Airmass _airmass F[FITS] [TCS] Date UTC at expstart

_date#obs VA10

[FITS] [TCS] Equinox of obs _equinox N5,1[FITS] [TCS] LST at exp start _lst#obs VA11[FITS] [TCS] MJD at exp start _mjd#obs N14,7[FITS] [TCS] Pointed DEC _dec VA11[FITS] [TCS] Pointed RA _ra VA11[FITS] [TCS] TCS Status _telstat VA40[FITS] [TCS] Time UTC at expstart

_utc#obs VA11

[FITS] Binning factor X _ccdbin1 N2[FITS] Binning factor Y _ccdbin2 N2[FITS] Bonnette X Probe (TCS) _xprobe N6,3[FITS] Bonnette Y Probe (TCS) _yprobe N6,3[FITS] Bonnette Z Probe (TCS) _zprobe N6,3[FITS] Dark Time _darktime N6,2[FITS] Date and Time HST filesaved

_hsttime VA28

[FITS] Date of file creation _date VA19[FITS] Detector Temp Status _detstat VA40[FITS] Detector used _detector VA10[FITS] Duration of shutter close _shutclos N6,2[FITS] Duration of shutter open _shutopen N6,2[FITS] Exposure Id _obsid N7[FITS] Exposure Time _exptime N6,2[FITS] Exposure Type _obstype VA10[FITS] Filename _filename VA10[FITS] Filter Id _filterid N1[FITS] Filter used _filter VA10[FITS] Instrument _instrume VA20[FITS] Label of OB _qob VA10[FITS] Maxlin param _maxlin N5[FITS] Name of CCD _ccd VA30

12

Name Code Type[FITS] Name of PI _pi_name VA40[FITS] Number of amps used _namps N2[FITS] Number of CCDs used _nccds N2[FITS] Object _object VA40[FITS] Observer _observer VA40[FITS] Overscan area of frame _biassec VA40[FITS] Pixel scale X _pixscal1 N5,4[FITS] Pixel scale Y _pixscal2 N5,4[FITS] Pixel Size X _pixsize1 N3,1[FITS] Pixel Size Y _pixsize2 N3,1[FITS] Q Run Id _qrunid VA10[FITS] Raster used _raster VA20[FITS] Rotation Angle _rotangle N6,3[FITS] Run Id _runid VA20[FITS] Saturate param _saturate N5[FITS] Size of detector _detsize VA40[FITS] Soft version of controler _conswv VA40[FITS] Software version of CCDcontroler

_imageswv VA40

[FITS] Tel Focus _telfocus N4[FITS] Telescope Focus _telconf VA20[FITS] Temperature of CCD _dettem N4,1[FITS] Time System _timesys VA3Abstract abstract TXT1000Address1 address1 VA100Address2 address2 VA100Address3 address3 VA100Agency agency VA10Air Temperature air_temp N3,1Allocated I_Time itime_alloc N8,1Apparent DEC app_dec VA11Apparent DEC in degrees app_dec_deg FApparent RA app_ra VA11Apparent RA in degrees app_ra_deg FAscending Node Long ascnode_long FAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLAvailable for PH2 ? is_avail_ph2 BLCalculated I_Time itime_calc N8,1

13

Name Code TypeChecked by PI is_pi_checked BLChip Height chip_h N5Chip Width chip_w N5City city VA20Comment comment VA100Country country VA20Currently Observable is_observable BLDate date_insert DTDate and Time UT date_ut DTDate LST date_lst DTDate of insertion (local) date_insert DTDate UT date_ut DTDEC dec VA11DEC in degrees dec_deg FDEC Offset dec VA8DEC Pointing Offset dec_offset VA8DEC Pointing Offset in degrees dec_offset_deg FDescription description VA100Description description VA100Description description VA100Description description VA100Description description VA200Elevation elevation N4Equinox for orbital elts oe_equinox FEvaluation evaluation A1Event event VA20Excentricity excentricity FExp Number expnum SIExp Time exptime N6,1First Name fname VA40Home Email home_email VA40Home Fax home_fax VA20Home Phone home_phone VA20I Time itime N6,1Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11

14

Name Code TypeId id NO10Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Id id NO11Inclination inclination FInstitute institute VA100IQ Observed iq N3,2Is Current is_current BLIs Monitoring OB ? is_monitor BLIs User is_user BLIs User is_user BLJulian Date jdate N14,7Julian Date at exp start jdate_obs N14,7Label label N2Label label N2Label label N2Label label N3Label label N3Last Name lname VA40Lattitude latitude N7,5Local Date and time of insert date_insert DTLocal Date and time ofobservation

date_obs DT

Longitude longitude FLongitude longitude N7,4Magnitude magv N3,1Maximal Elongation elong_max FMinimal Elongation elong_min FMobile Phone mobile_phone VA20Module module VA20Mon Min number of iter mon_niter_min SIMon Number of iter mon_niter SI

15

Name Code TypeMon Period (h) mon_period N6,1Monitor Flag is_monitor BLMosaic Total Height mos_full_h N6Mosaic Total Width mos_full_w N6Moving Fields Flag is_moving_fields BLName name VA20Name name VA20Name name VA20Name name VA20Name name VA5Name name VA10Name name VA20Name name VA20Name name VA20Name name VA20Name name VA20Name name VA20Name name VA20Name name VA20Need Quick Data Access is_quick_data_access BLNumber num SINumber num SINumber of Chips high mos_chips_h N2Number of Chips wide mos_chips_w N2Observatory Id obsid N4Parameters params VA200Password pw VA40Pattern Radius pradius FPerihelion Long peri_long FPh1 Password ph1_pw VA40Ph1 User ID ph1_userid VA20Ph2 Comment ph2_comment VA40PhaseII Comment ph2_comment TXT1000Photometric Flag is_photometric BLPixel Scale pix_scale N5,4Pixel Size pix_size N3,1Q Run Id qrunid VA10RA ra VA11RA in degrees ra_deg FRA Offset ra VA8RA Pointing Offset ra_offset VA8RA Pointing Offset in degrees ra_offset_deg FRaster raster VA20

16

Name Code TypeRelative Humidity hum_rel N4,1Requested DEC req_dec VA11Requested DEC in degrees req_dec_deg FRequested Equinox req_equinox N5,1Requested PM DEC req_pm_dec FRequested PM RA req_pm_ra FRequested RA req_ra VA11Requested RA in degrees req_ra_deg FRun id runid VA10Semi_Major Axis smajor_axis FSky Background sky_bg FState state VA40Status status VA20Status status VA20Status status VA20TAC Grade tac_grade N3,1TAC Rank tac_rank A1Tech_Feas tech_feas TXT1000Time difference from UTC timediff_utc_hh N2Timezone timezone VA10Title title VA200Type type VA10Type type VA20Type type VA10Used I_Time itime_used N8,1User ID userid VA20Value value N1Value value VA20Value value N1Value value VA20Value value VA20Value value VA20Value value VA20Value value VA20Wind Direction wind_direction N4,1Wind Speed wind_speed N4,1Work Email work_email VA40Work Fax work_fax VA20Work Phone work_phone VA20Zip Code zip VA10

Entity List

17

Name CodeAirmass airmassBinning binningBinning Assignement binning_aCoI Assignment coi_aConstraint consEphemeris ephemerisEvents eventsExposures expFilter filterFilter Assignment filter_aIC Sequence icseqImage Quality iqInstrument instrInstrument Configuration iconfigOB obOB Priority obpriorityObservation obsObservation Conditions ocndOffset offsetPattern patternPointing pointingProgram prgSite siteSky Background skybgTarget targetTarget defined By Ephemeris target_ephTarget defined by OE target_oeTarget defined by RA and DEC target_fixTracking trackingUser usr

Relationship List

Name CodeBinning Is Avail On Instr binning_is_avail_on_instrConstraint Features Airmass constraint_features_airmassConstraint Features IQ constraint_features_iqConstraint Features Sky Bg constraint_features_sky_bgEvent Is Related To Prg event_is_related_to_prgEvent Was Recorded By event_was_recorded_byFilter Is Avail On Instr filter_is_avail_on_instrIC Occurs In IC Sequence ic_occurs_in_ic_sequenceIC Uses Binning ic_uses_binning

18

Name CodeIC Uses Filter ic_uses_filterInstr Features Binning instr_features_binningInstr Features Filter instr_features_filterIs Obsed With Priority is_obsed_with_priorityOb Is Obsed Using ICs In ob_is_obsed_using_ics_inOB Is Obsed Using Tracking ob_is_obsed_using_trackingOB Is Observable Under Const ob_is_observable_under_constOB Is Observed In Exp ob_is_observed_in_expOB Is Observed Under Condition ob_is_observed_under_condObservation Is Defined In OB observation_is_defined_in_obPattern Is Defined By Offset pat_is_def_by_offsetPattern Is Used By IC pattern_is_used_by_icPrg Is Made Of Observations prg_is_made_of_observationsPrg Observes Target prg_observes_targetProgram Has CoIs prg_has_coisProgram Owns Constraints prg_owns_constraintsProgram Owns ICs prg_owns_icsProgram Owns OBs prg_owns_obsProgram Uses Instr program_uses_instrTarget Ephem Must Have EphemerisDefined By

tae_has_ephem_def_by

Target Is Obsed In OB target_is_obsed_in_obTarget Is Pted By Pointing target_is_pted_by_pointingTarget OE May Have Ephemeris DefinedBy

tao_may_have_ephem_def_by

User Co Investigates user_co_investigatesUser Is PI user_is_piUser Own Poiting user_own_poitingUser Owns Pattern user_owns_pattern

19

Entity Information

Entity Airmass

Name: AirmassCode: airmassLabel:Number: Generate Table: Yes

Attribute List

Name Code Type I MId id NO11 Yes YesName name VA20 No YesValue value N1 No YesDescription description VA10

0No No

Available for PH2 ? is_avail_ph2 BL No Yes

Data Item Id

Data Item Name

Description

Name of upper limits on Airmass

- less than 1.2- less than 1.5- Any

Data Item Value

Description

Possible values for Upper limit on Airmass

Check

Low Value:High Value:

20

Default Value:Unit:Format: 2Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Description

Description

Description of Airmass upper value

Annotation

Special value: NULL= not avail.

Data Item Available for PH2 ?

Description

Flag T if this this row is available for selection in the PH2 interface.

Check

Low Value:High Value:Default Value: 1Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Reference List

Entity Card Dep.

Relationship

Constraint(cons) 0,n No Constraint FeaturesAirmass(constraint_features_airmass)

Entity Binning

Name: Binning

21

Code: binningLabel:Number: Generate Table: Yes

Description

Available binnings for all instruments

NB: It is not planned to allow other values than 1 in PH2.

Attribute List

Name Code Type I MId id NO11 Yes YesName name VA20 No YesValue value N1 No YesAvailable for PH2 ? is_avail_ph2 BL No Yes

Data Item Id

Data Item Name

Description

Possible names for binning. Names are for display in the interface.Example: 1x1,2x2,4x4

Check

Low Value:High Value:Default Value:Unit:Format: 2x2Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Value

Description

Possible values for binning. Same as in acq softwareExamples: 1, 2, 4 or NO, BIN2, BIN4 (TBD)

22

Check

Low Value:High Value:Default Value:Unit:Format: 2Uppercase: No Lowercase: No Can't modify: NoList of Values:


Description

Flag true if this value of binning is available in PH2 Tool

Check


Reference List

Entity Card Dep.

Relationship

Binning Assignement(binning_a) 1,n Yes Binning Is Avail OnInstr(binning_is_avail_on_instr)

Instrument Configuration(iconfig) 0,n No IC UsesBinning(ic_uses_binning)

Entity Binning Assignement

Name: Binning AssignementCode: binning_aLabel:Number: Generate Table: Yes

23

Description

This table is used to store the assignment of binning factors to instruments

Annotation

This is a many-to-many relationship instancied into the intersection entity

Reference List

Entity Card Dep.

Relationship

Binning(binning) 1,1 Yes Binning Is Avail OnInstr(binning_is_avail_on_instr)

Instrument(instr) 1,1 Yes Instr FeaturesBinning(instr_features_binning)

Entity CoI Assignment

Name: CoI AssignmentCode: coi_aLabel:Number: Generate Table: Yes

Description

This table is used to store the assignment of co-investigators to programs

Annotation


Reference List

Entity Card Dep.

Relationship

Program(prg) 1,1 Yes Program Has CoIs(prg_has_cois)User(usr) 1,1 Yes User Co

Investigates(user_co_investigates)

Entity Constraint

Name: ConstraintCode: cons

24

Label:Number: Generate Table: Yes

Description

A constraint is a set of 3 {upper limits or bins} of sky-related parameters (Image Quality, Sky Background, andAirmass) that define in which condition an OB can be best observed.

Annotation

The table is named cons because constraint is a Sybase reserved word

Attribute List

Name Code Type I MId id NO11 Yes YesLabel label N2 No YesName name VA20 No No

Data Item Id

Data Item Label

Description

The label is used for easy identification and classification of this row by the userMust be prefixed with the letter 'C' in the interface.

Example: C1 = first constraint defined by PI

Annotation

NB: The label is unique in all the constraints of a given program.

Check

Low Value: 1High Value: 99Default Value:Unit:Format: 1Uppercase: No Lowercase: No Can't modify: NoList of Values:

25

Data Item Name

Reference List

Entity Card Dep.

Relationship

Airmass(airmass) 1,1 No Constraint FeaturesAirmass(constraint_features_airmass)

Image Quality(iq) 1,1 No Constraint FeaturesIQ(constraint_features_iq)

Sky Background(skybg) 1,1 No Constraint Features SkyBg(constraint_features_sky_bg)

OB(ob) 0,1 No OB Is Observable UnderConst(ob_is_observable_under_const)

Program(prg) 1,1 No Program OwnsConstraints(prg_owns_constraints)

Entity Ephemeris

Name: EphemerisCode: ephemerisLabel:Number: Generate Table: Yes

Description

The table ephemeris holds all the timed positions for moving objects.The positions can be supplied by the users or computed at CFTH from the OE supplied by the users (see item Type)

Attribute List

Name Code Type I MId id NO11 Yes YesRA ra VA11 No YesRA in degrees ra_deg F No YesDEC dec VA11 No YesDEC in degrees dec_deg F No YesDate and Time UT date_ut DT No YesType type VA10 No Yes

26

Data Item Id

Data Item RA

Description

RA of target at the date and time specified

Check

Low Value:High Value:Default Value:Unit:Format: -12:34:56.7Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item RA in degrees

Data Item DEC

Description

DEC of target at the date and time specified

Data Item DEC in degrees

Data Item Date and Time UT

Check

Low Value:High Value:Default Value:Unit: UTFormat: 2001/01/28 12:30:11Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Type

27

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: USER Ephemeris supplied by user with PH2

GEN Ephemeris generated from OE

Reference List

Entity Card Dep.

Relationship

Target defined ByEphemeris(target_eph)

1,1 No Target Ephem Must HaveEphemeris DefinedBy(tae_has_ephem_def_by)

Target defined by OE(target_oe) 1,1 No Target OE May Have EphemerisDefinedBy(tao_may_have_ephem_def_by)

Entity Events

Name: EventsCode: eventsLabel:Number: Generate Table: Yes

Description

This table is a logging facility where important dated events of QSO are recorded.

Each event is assigned the user responsible for it as well as the program it is related to when this applies.

Annotation

Useful to follow Phase 2 progress and for the Observing Log during operations of QSO

Attribute List

Name Code Type I MId id NO11 Yes Yes

28

Name Code Type I MDate date_insert DT No YesModule module VA20 No YesEvent event VA20 No YesParameters params VA20

0No Yes

Data Item Id

Data Item Date

Description

Date of event

Check

Low Value:High Value:Default Value: getdate()Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Module

Description

Module where the action happenedExample: PH2

Data Item Event

Description

Description of what happened

Data Item Parameters

Description

Parameters: details of the event

29

Reference List

Entity Card Dep.

Relationship

Program(prg) 1,1 No Event Is Related ToPrg(event_is_related_to_prg)

User(usr) 0,1 No Event Was RecordedBy(event_was_recorded_by)

Entity Exposures

Name: ExposuresCode: expLabel:Number: Generate Table: Yes

Description

This table holds the parameters of the exposures taken with the camera in Q modeThese parameters are mainly used for Quality Control

NB:Items read from FITS header are prefixed with [FITS]In addition the FITS headers coming from TCS are prefixed with [TCS]

Annotation

This table could be used by other projects (Elixir, DAD)

Attribute List

Name Code Type I Mid id NO11 Yes YesLocal Date and time of insert date_insert DT No YesLocal Date and time ofobservation

date_obs DT No Yes

Julian Date at exp start jdate_obs N14,7 No Yes[FITS] Instrument _instrume VA20 No Yes[FITS] Q Run Id _qrunid VA10 No Yes[FITS] Run Id _runid VA20 No Yes[FITS] Label of OB _qob VA10 No Yes[FITS] Exposure Type _obstype VA10 No Yes[FITS] Exposure Id _obsid N7 No Yes[FITS] Filename _filename VA10 No Yes

30

Name Code Type I M[FITS] Date and Time HST filesaved

_hsttime VA28 No Yes

[FITS] Filter used _filter VA10 No Yes[FITS] Exposure Time _exptime N6,2 No Yes[FITS] Object _object VA40 No Yes[FITS] Observer _observer VA40 No Yes[FITS] Name of PI _pi_name VA40 No Yes[FITS] Filter Id _filterid N1 No Yes[FITS] [TCS] Date UTC at expstart

_date#obs VA10 No Yes

[FITS] [TCS] Time UTC at expstart

_utc#obs VA11 No Yes

[FITS] [TCS] LST at exp start _lst#obs VA11 No Yes[FITS] [TCS] MJD at exp start _mjd#obs N14,7 No Yes[FITS] [TCS] Pointed RA _ra VA11 No Yes[FITS] [TCS] Pointed DEC _dec VA11 No Yes[FITS] [TCS] Equinox of obs _equinox N5,1 No Yes[FITS] [TCS] Airmass _airmass F No Yes[FITS] Raster used _raster VA20 No Yes[FITS] Binning factor X _ccdbin1 N2 No Yes[FITS] Binning factor Y _ccdbin2 N2 No Yes[FITS] Pixel Size X _pixsize1 N3,1 No No[FITS] Pixel Size Y _pixsize2 N3,1 No No[FITS] Tel Focus _telfocus N4 No No[FITS] Number of CCDs used _nccds N2 No No[FITS] Number of amps used _namps N2 No No[FITS] Rotation Angle _rotangle N6,3 No No[FITS] Temperature of CCD _dettem N4,1 No Yes[FITS] Maxlin param _maxlin N5 No No[FITS] Saturate param _saturate N5 No No[FITS] Bonnette X Probe (TCS) _xprobe N6,3 No No[FITS] Bonnette Y Probe (TCS) _yprobe N6,3 No No[FITS] Bonnette Z Probe (TCS) _zprobe N6,3 No No[FITS] Pixel scale X _pixscal1 N5,4 No No[FITS] Pixel scale Y _pixscal2 N5,4 No No[FITS] Duration of shutter open _shutopen N6,2 No Yes[FITS] Duration of shutter close _shutclos N6,2 No Yes[FITS] Dark Time _darktime N6,2 No No[FITS] Date of file creation _date VA19 No Yes[FITS] Software version of CCDcontroler

_imageswv VA40 No No

[FITS] Name of CCD _ccd VA30 No No[FITS] [TCS] TCS Status _telstat VA40 No No

31

Name Code Type I M[FITS] Telescope Focus _telconf VA20 No Yes[FITS] Detector used _detector VA10 No Yes[FITS] Size of detector _detsize VA40 No No[FITS] Soft version of controler _conswv VA40 No No[FITS] Detector Temp Status _detstat VA40 No No[FITS] Overscan area of frame _biassec VA40 No No[FITS] Time System _timesys VA3 No Yes

Data Item id

Data Item Local Date and time of insert

Description

Date and Time HST of insertion

Check

Low Value:High Value:Default Value: getdate()Unit: loc timeFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Local Date and time of observation

Description

Date and Time UT of observation

Check

Low Value:High Value:Default Value:Unit: loc timeFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

32

Data Item Julian Date at exp start

Description

Julian date at start of exposure

Annotation

Computed by trigger: add 2400000.5 to _mjd#obs

Check

Low Value:High Value:Default Value:Unit: jul. dayFormat: 2415020.1234567Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Instrument

Description

Instrument used for exposure - from FITS PHU card INSTRUME

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: CFH12K

MEGACAM

Data Item [FITS] Q Run Id

Description

Q Run Id - from FITS PHU card QRUNID

Check

33

Low Value:High Value:Default Value:Unit:Format: 01AQ02Uppercase: Yes Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Run Id

Description

Run Id - from FITS PHU card RUNID

Check

Low Value:High Value:Default Value:Unit:Format: 01AC12QUppercase: Yes Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Label of OB

Description

OB Label - from FITS PHU QOB

Annotation

The OB label is the # of the OB in the program identified by _runid

Check


34

Data Item [FITS] Exposure Type

Description

Observation Type - from FITS PHU

Annotation

Cannot enforce fixed values because camera software may change them

Check

Low Value:High Value:Default Value:Unit:Format: OBJECTUppercase: Yes Lowercase: No Can't modify: NoList of Values: OBJECT

DARKBIASFLAT

Data Item [FITS] Exposure Id

Description

Exposure Id - from FITS HDU card OBSID

Check


Data Item [FITS] Filename

Description

35

File name - from FITS PHU card FILENAME

Check

Low Value:High Value:Default Value:Unit:Format: 535130b.fitsUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Date and Time HST file saved

Description

Date and Time file was saved - from FITS PHU card HSTTIME

Format: Sat Jan 01 01:39:32 HST 2000

Annotation

Format is too long to fit in Check Format, put in Description

Data Item [FITS] Filter used

Description

Filter used for exposure - from FITS HDU card FILTER

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: B

VRIZTiO2HAlpha

36

HAlphaOFF

Data Item [FITS] Exposure Time

Description

Duration of exposure - from FITS HDU card EXPTIME

Check

Low Value: 0.2High Value: 10800.0Default Value:Unit: secondsFormat: 480.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Object

Description

Object observed - from FITS HDU card OBJECT

Annotation

This attribute has the same value as the field Name of entity Target,for the target belonging to the OB where the Exposure belong

Example SELECT to check that:

SELECT exp._runid, exp._qob, exp._object, ob.label, target.nameFROM exp, ob, prg, targetWHERE exp._runid = prg._runidAND exp._qob = ob.labelAND (ob.tar_id = target.id OR ob.tar2_id = target.id OR ob.tar3_id = target.id)

Check

Low Value:High Value:Default Value:Unit:Format: M51

37

Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Observer

Description

The Q observer who took the exposure - from FITS HDU card OBSERVER

Data Item [FITS] Name of PI

Description

Name of PI - from FITS HDU card PI_NAME

Passed to director in observation scripts

Data Item [FITS] Filter Id

Data Item [FITS] [TCS] Date UTC at exp start

Description

UT Date at start of exposure - from FITS HDU card DATE-OBS

Check

Low Value:High Value:Default Value:Unit:Format: 2000-01-01Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] [TCS] Time UTC at exp start

Description

UT Time at start of exposure - from FITS HDU card UTC-OBS

Check

Low Value:

38

High Value:Default Value:Unit:Format: 11:32:25.00Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] [TCS] LST at exp start

Description

Local Sideral Time at start of exposure - from FITS HDU card LST-OBS

Data Item [FITS] [TCS] MJD at exp start

Description

Modified Julian Date at start of exposure - from FITS HDU card MJD-OBS

Data Item [FITS] [TCS] Pointed RA

Description

RA of TCS main beam at start of exposure - from FITS HDU card RA

Check

Low Value:High Value:Default Value:Unit:Format: -12:34:56.7Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] [TCS] Pointed DEC

Description

DEC of TCS main beam at start of exposure - from FITS HDU card DEC

Check

Low Value:

39

High Value:Default Value:Unit:Format: -12:34:56.7Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] [TCS] Equinox of obs

Description

Equinox for RA and DEC - from FITS HDU card EQUINOX

Data Item [FITS] [TCS] Airmass

Description

Airmass computed by TCS - from FITS HDU card AIRMASS

Data Item [FITS] Raster used

Description

Raster used for all chips in exposure - from FITS HDU card RASTER

Check

Low Value:High Value:Default Value:Unit:Format: FULLUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Binning factor X

Description

Binning factor in X direction - from FITS HDU card CCDBIN1

Check

Low Value: 1

40

High Value: 4Default Value:Unit:Format: 1Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Binning factor Y

Description

Binning factor in Y direction - from FITS HDU card CCDBIN2

Check


Data Item [FITS] Pixel Size X

Description

Pixel size in X direction - from FITS PHU card PIXSIZE1

Check

Low Value:High Value:Default Value:Unit: micronsFormat: 15.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Pixel Size Y

41

Description

Pixel size in Y direction - from FITS PHU card PIXSIZE2

Check


Data Item [FITS] Tel Focus

Description

Telescope Focus position used for exposure - from FITS PDU card TELFOCUS

Check

Low Value:High Value:Default Value:Unit: mmFormat: 6114Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Number of CCDs used

Description

Nb of CCD used - from FITS PDU card NCCDS

Data Item [FITS] Number of amps used

Description

Number of CCD amplifiers used - from FITS PDU card NAMPS

Data Item [FITS] Rotation Angle

42

Description

Telescope Bonnette Rotation angle - from FITS PDU card ROTANGLE

Check

Low Value: 0.0High Value: 360.0Default Value:Unit: degreesFormat: 89.820Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Temperature of CCD

Description

CCD Temperature - from FITS PDU card DETTEM

Check

Low Value:High Value:Default Value:Unit:Format: -88.9Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Maxlin param

Description

Parameter MAXLIN - from FITS PDU card MAXLIN

Check

Low Value:High Value:Default Value:Unit:Format: 65535Uppercase: No Lowercase: No Can't modify: No

43

List of Values:

Data Item [FITS] Saturate param

Description

Parameter SATURATE - from FITS PDU card SATURATE

Check


Data Item [FITS] Bonnette X Probe (TCS)

Description

Telescope Bonnete xyprobe X-pos - from FITS PHU card XPROBE

Check

Low Value:High Value:Default Value:Unit: mmFormat: 32.870Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Bonnette Y Probe (TCS)

Description

Telescope Bonnete xyprobe X-pos - from FITS PHU card XPROBE

Check

Low Value:

44

High Value:Default Value:Unit: mmFormat: 151.89Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Bonnette Z Probe (TCS)

Data Item [FITS] Pixel scale X

Description

Pixel scale for axis X - from FITS PHU card PIXSCAL1

Check

Low Value:High Value:Default Value:Unit: arcs/pixFormat: 0.2060Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Pixel scale Y

Description

Pixel scale for axis Y - from FITS PHU card PIXSCAL2

Check

Low Value:High Value:Default Value:Unit: arcs/pixFormat: 0.2060Uppercase: No Lowercase: No Can't modify: NoList of Values:

45

Data Item [FITS] Duration of shutter open

Description

Shutter blade opening time - from FITS PHU card SHUTOPEN

Check

Low Value:High Value:Default Value:Unit: msecFormat: 200.00Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Duration of shutter close

Description

Shutter blade closing time - from FITS PHU card SHUTCLOS

Check

Low Value:High Value:Default Value:Unit: msecFormat: 200.00Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Dark Time

Description

Dark current time - from FITS PHU card DARKTIME

Check

Low Value:High Value:Default Value:Unit: seconds

46

Format: 480.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Date of file creation

Description

UTC date and time of file creation - from FITS PHU card DATE

Check

Low Value:High Value:Default Value:Unit:Format: 2000-01-01T11:39:32Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Software version of CCD controler

Description

Image creation software version - from FITS PHU card IMAGESW

Format:CFHT 12kcom v2.6 (Dec 01 1999)

Annotation

Format is too long to fit in check format - see description

Check

Low Value:High Value:Default Value:Unit:Format: see descriptionUppercase: No Lowercase: No Can't modify: NoList of Values:

47

Data Item [FITS] Name of CCD

Description

Name of CCD - from FITS PHU card CCD

Check

Low Value:High Value:Default Value:Unit:Format: MIT/LL 2K x 4K CCDUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] [TCS] TCS Status

Description

TCS status - from FITS PHU card TELSTAT

Check

Low Value:High Value:Default Value:Unit:Format: okUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Telescope Focus

Description

Telescope focus - from FITS PHU card TELCONF

Check

Low Value:High Value:Default Value:Unit:

48

Format: primeUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Detector used

Description

Detector used - from FITS PHU card DETECTOR

Check

Low Value:High Value:Default Value:Unit:Format: CFH12KUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Size of detector

Description

Total data pixels in full mosaic - from FITS PHU card DETSIZE

Check

Low Value:High Value:Default Value:Unit: pixelsFormat: [1:12450,1:8230]Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Soft version of controler

Description

CCD Control Software DSPID and SERNO versions- from FITS PHU card CONSWV

49

Format:CTM=203,CUM=201,CTS=193,CUS=52

Annotation

Format too long to fit in check format, see description

Check

Low Value:High Value:Default Value:Unit:Format: see descriptionUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Detector Temp Status

Description

Detector temperature range (-91..85) - from FITS PHU card DETSTAT

Check

Low Value:High Value:Default Value:Unit:Format: okUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Overscan area of frame

Description

Overscan area of frame - from FITS PHU card BIASSEC

Check

Low Value:High Value:Default Value:

50

Unit:Format: [2050:2080,2:4128]Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item [FITS] Time System

Description

Time system for DATExxxx keywords - from FITS PHU card TIMESYS

Check

Low Value:High Value:Default Value:Unit:Format: UTCUppercase: Yes Lowercase: No Can't modify: NoList of Values: UTC

Reference List

Entity Card Dep.

Relationship

OB(ob) 1,1 No OB Is Observed InExp(ob_is_observed_in_exp)

Entity Filter

Name: FilterCode: filterLabel:Number: Generate Table: Yes

Description

Available filters for all instruments

Attribute List

Name Code Type I MId id NO11 Yes Yes

51

Name Code Type I MName name VA20 No YesValue value VA20 No YesDescription description VA10

0No Yes


Data Item Id

Data Item Name

Description

Possible names for filters. Names are for display in PH2 and other interfacesExamples: B,V,R,I,Z,Halpha,HalphaOFF,TiO2

Check

Low Value:High Value:Default Value:Unit:Format: BUppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Value

Description

Possible values for filters. Same codes as in acq interface.Examples: B,V,R,I,Z,Halpha,HalphaOFF,TiO2



Description

Flag is T if this filter is to show on the PH2 tool

Check

52


Reference List

Entity Card Dep.

Relationship

Filter Assignment(filter_a) 1,n Yes Filter Is Avail OnInstr(filter_is_avail_on_instr)

Instrument Configuration(iconfig) 0,n No IC Uses Filter(ic_uses_filter)

Entity Filter Assignment

Name: Filter AssignmentCode: filter_aLabel:Number: Generate Table: Yes

Description

This table is used to store the assignment of binning factors to instruments

Annotation


Reference List

Entity Card Dep.

Relationship

Filter(filter) 1,1 Yes Filter Is Avail OnInstr(filter_is_avail_on_instr)

Instrument(instr) 1,1 Yes Instr FeaturesFilter(instr_features_filter)

Entity IC Sequence

Name: IC Sequence

53

Code: icseqLabel:Number: Generate Table: Yes

Description

An IC (Instrument Configuration) Sequence is an ordered list of Instrument Configurations to be performed within anObserving Block for a particular target.

Attribute List

Name Code Type I MId id NO11 Yes YesNumber num SI No Yes

Data Item Id

Data Item Number

Description

The sequence # is used to sort the sequence of IC by time.

Reference List

Entity Card Dep.

Relationship

Instrument Configuration(iconfig) 1,1 No IC Occurs In ICSequence(ic_occurs_in_ic_sequence)

OB(ob) 0,1 No Ob Is Obsed Using ICsIn(ob_is_obsed_using_ics_in)

Entity Image Quality

Name: Image QualityCode: iqLabel:Number: Generate Table: Yes

Attribute List

Name Code Type I M

54

Name Code Type I MId id NO11 Yes YesName name VA20 No YesValue value VA20 No YesDescription description VA10

0No No


Data Item Id

Data Item Name

Description

Available names for the ranges of Image Quality:

- less than 0.55 arcsec- 0.55 to 0.65 arcsec- 0.65 to 0.80 arcsec- 0.80 to 1.0 arcsec- 1.0 to 1.2 arcsec- greater than 1.2 arcsec

Data Item Value

Description

Available values for the ranges of Image Quality:

- less than 0.55 arcsec- 0.55 to 0.65 arcsec- 0.65 to 0.80 arcsec- 0.80 to 1.0 arcsec- 1.0 to 1.2 arcsec- greater than 1.2 arcsec


Description

Description of IQ range

Annotation

55



Description

Flag T if this row is available for selection in the PH2 interface.

Check


Reference List

Entity Card Dep.

Relationship

Constraint(cons) 0,n No Constraint FeaturesIQ(constraint_features_iq)

Entity Instrument

Name: InstrumentCode: instrLabel:Number: 3 Generate Table: Yes

Description

This table contains the instrument+detector parameters

Attribute List

Name Code Type I MId id NO11 Yes YesName name VA10 No YesMosaic Total Width mos_full_w N6 No YesMosaic Total Height mos_full_h N6 No YesNumber of Chips wide mos_chips_w N2 No Yes

56

Name Code Type I MNumber of Chips high mos_chips_h N2 No YesPixel Size pix_size N3,1 No YesPixel Scale pix_scale N5,4 No YesChip Width chip_w N5 No YesChip Height chip_h N5 No Yes

Data Item Id

Data Item Name

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: Yes Lowercase: No Can't modify: NoList of Values:

Data Item Mosaic Total Width

Description

Total width of mosaic in pixels including gaps

Check

Low Value:High Value:Default Value:Unit: pixelsFormat: 12540Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Mosaic Total Height

Description

Total height of mosaic in pixels including gaps

57

Check


Data Item Number of Chips wide

Description

Number of chips in width

Check

Low Value:High Value:Default Value:Unit: chipsFormat: 6Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Number of Chips high

Description

Number of chips in height

Check

Low Value:High Value:Default Value:Unit: chipsFormat: 2Uppercase: No Lowercase: No Can't modify: NoList of Values:

58

Data Item Pixel Size

Description

Pixel size in microns

Check


Data Item Pixel Scale

Description

Pixel scale in arcsec/pixel

Check

Low Value:High Value:Default Value:Unit: asec/pixFormat: 0.2060Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Chip Width

Description

Width of each individual chip in pixels

Check

Low Value:High Value:Default Value:Unit: pixels

59

Format: 2048Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Chip Height

Description

Height of each individual chip in pixels

Check


Reference List

Entity Card Dep.

Relationship

Binning Assignement(binning_a) 1,n Yes Instr FeaturesBinning(instr_features_binning)

Filter Assignment(filter_a) 1,n Yes Instr FeaturesFilter(instr_features_filter)

Program(prg) 0,n No Program UsesInstr(program_uses_instr)

Entity Instrument Configuration

Name: Instrument ConfigurationCode: iconfigLabel:Number: Generate Table: Yes

Description

The instrument configuration holds a configuration of the camera used to produce one single exposures or severalexposures grouped in a pattern (Ex: Dithering Pattern)

60

Attribute List

Name Code Type I MId id NO11 Yes YesLabel label N2 No YesName name VA20 No NoRaster raster VA20 No YesExp Time exptime N6,1 No YesPattern Radius pradius F No Yes

Data Item Id

Data Item Label

Description

The label is used for identification and classification of this row by the PIMust be prefixed with the letter 'I' in the interfaceEx: I1 = first instrument configuration defined

Check

Low Value: 1High Value: 99Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Name

Description

Name of Instrument Config to be defined by the PIExample: "Filter V, 3 sec exp"

Data Item Raster

Description

Raster to use for the exposures defined by this IC.

Example values (same values as in director)

61

- FULL Full raster- CENTER 100 100 Raster centered on chip, size 100x100- 200 200 64 64 Raster centered on (200,200), size 64x64

NB: It is not planned to allow other values than FULL is PH2

Data Item Exp Time

Description

Exposure time to use for the exposures defined by this IC.

Minimum value due to shutter limit: 0.2 secondsMaximum value is the maximum duration of a block: 3h or 10800 seconds

Check

Low Value: 0.2High Value: 10800.0Default Value:Unit: secondsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Pattern Radius

Description

Pattern radius: radius in which all the offsets of a dithering pattern are contained

Annotation

Alternate solution is to use a scaling factor:

Factor to rescale the pattern in use for this IC.Example: All the offsets for pattern DP2 stands in a 15 arcsecs disc. To observe with the same pattern but within a 30arcsecs disc, the scale factor will be 2.0

Check

Low Value: 10High Value: 150Default Value: 15

62

Unit: arcsecsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Reference List

Entity Card Dep.

Relationship

IC Sequence(icseq) 0,1 No IC Occurs In ICSequence(ic_occurs_in_ic_sequence)

Binning(binning) 1,1 No IC UsesBinning(ic_uses_binning)

Filter(filter) 1,1 No IC Uses Filter(ic_uses_filter)Pattern(pattern) 1,1 No Pattern Is Used By

IC(pattern_is_used_by_ic)Program(prg) 1,1 No Program Owns

ICs(prg_owns_ics)

Entity OB

Name: OBCode: obLabel:Number: Generate Table: Yes

Description

Observing Blocks are individual units of observations including one target and not lasting more than 3 hours.

An OB is either completly observed or completly failed. If failed, the I-Time of the OB is not accounted to the PI andthe OB has to be observed again.

Attribute List

Name Code Type I MId id NO11 Yes YesLabel label N3 No YesQ Run Id qrunid VA10 No NoI Time itime N6,1 No YesStatus status VA20 No Yes

63

Name Code Type I MComment comment VA10

0No No

Is Monitoring OB ? is_monitor BL No YesMon Period (h) mon_period N6,1 No NoMon Min number of iter mon_niter_min SI No NoMon Number of iter mon_niter SI No No

Data Item Id

Data Item Label

Description

The label is used for identification and classification of this row by the PIMust be prefixed with the string 'OB' in the interfaceEx: OB1 = first observing block defined

Check


Data Item Q Run Id

Description

Queue Run Id

This string represent the Q Run Id, an identifier of the Q Run (run in Q mode) when the OB is observed. This attributewill only be filled when OB is actually observed

Example: 00AQ0200A 1st semester of 2000Q This is a Q run id02 Sequence number of this Q run in the semester (first Q run = 01)

Annotation

64

Special value: NULL = OB not observed yet

Data Item I Time

Description

Integration time of the OBSum of the I-Time of all the IC in the IC Sequence for the OB

Example:OB defined by IC1+IC2=> I-Time(OB)= Exp.Time(IC1)+Exp.Time(IC2)

Limit:Minimum integration time is minimum exp time for an exposure: 0.2 secondsMaximum integration time for an OB is 3h or 10800 seconds

Check

Low Value: 0.2High Value: 10800.0Default Value:Unit: secondsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Status

Description

Status of the OB

Statuses follow a Markov chainNB: (STATE) means: there exists a reflexive relationship on STATE

IDLE <---> (QUEUED) ---> COMPLETED

IDLE ---> QUEUED: OB is queued for tentative observation when the programcontaining the OB is queued.

QUEUED ---> QUEUED: The OB has been observed but QC has rejected it

65

QUEUED ---> IDLE: The OB is unqueued (eg if could not be observed repeatively)

QUEUED ---> COMPLETED: The OB has been observed successfully

Check

Low Value:High Value:Default Value: IDLEUnit:Format:Uppercase: Yes Lowercase: No Can't modify: NoList of Values: IDLE OB is waiting to be queued

QUEUED OB is queuedCOMPLETED OB is completed

Data Item Comment

Description

This comment is used by the PI to annotate the OB

Annotation

Special value: NULL = no comment entered

Data Item Is Monitoring OB ?

Description

True if this OB is a monitoring OB

Check


Data Item Mon Period (h)

66

Description

Period of execution of the OB in HOURS

Limits:Minimum period is readout time of CCD: 1 minute or 0.0167 hourMaximum period is the semester (6 months) 6 months or 648000 hours

Annotation

Special value: NULL = OB is not a monitoring OB

Check

Low Value: 0.0167High Value: 648000Default Value:Unit: hoursFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Mon Min number of iter

Rule List

Name Code Type Expr

Max iter_min for a mon OB mon_ob_max_iter_min Validation

Yes

Description

Minimum number of iterations of the OB needed to reach the science goal

Annotation


Data Item Mon Number of iter

Description

Requested number of iterations of the OB

67

Annotation


Reference List

Entity Card Dep.

Relationship

OB Priority(obpriority) 1,1 No Is Obsed WithPriority(is_obsed_with_priority)

IC Sequence(icseq) 1,1 No Ob Is Obsed Using ICsIn(ob_is_obsed_using_ics_in)

Tracking(tracking) 1,1 No OB Is Obsed UsingTracking(ob_is_obsed_using_tracking)

Constraint(cons) 1,1 No OB Is Observable UnderConst(ob_is_observable_under_const)

Exposures(exp) 1,n No OB Is Observed InExp(ob_is_observed_in_exp)

Observation Conditions(ocnd) 1,1 No OB Is Observed UnderCondition(ob_is_observed_under_cond)

Observation(obs) 0,1 No Observation Is Defined InOB(observation_is_defined_in_ob)

Program(prg) 1,1 No Program OwnsOBs(prg_owns_obs)

Target(target) 1,1 No Target Is Obsed InOB(target_is_obsed_in_ob)

Entity OB Priority

Name: OB PriorityCode: obpriorityLabel:Number: Generate Table: Yes

Description

Available OB prioritiesExample: High, Medium, Low

Attribute List

68

Name Code Type I MId id NO11 Yes YesName name VA20 No YesValue value VA20 No Yes

Data Item Id

Data Item Name

Description

Name of priorityExample: High

Data Item Value

Description

Value of priorityExample: H

Reference List

Entity Card Dep.

Relationship

OB(ob) 0,n No Is Obsed WithPriority(is_obsed_with_priority)

Entity Observation

Name: ObservationCode: obsLabel:Number: Generate Table: Yes

Description

Table to hold the planned observations

Observations can be of the following types:

- Type=NOB: Normal OB to be observed once- Type=SOB: Sequence of OBs to be observed contiguously

69

- Type=MOB: Repetition of Monitoring OB to be observed repetitively

Annotation

* Parameter I_Time is not necessary:

Would be a copy of the integration time of the OB which is linked to this row.

WARNING: Usage of thiswould allow easier view of the observations for a prg but is REDUNDANT !

THe following select should be used to get the I_Time for an observation:Select OBS.ID, OB.ITIME from OBS, OB where OBS.OB_ID=OB.ID

* Parameter Period if not necessary

Old definition:Period of observation:NULL: no period: single OB or last of sequence of monitoring0: after this observation it is mandatory to perform the next one with order=order+1n: the next observation of this monitoring program should occur in <n> hours

Attribute List

Name Code Type I MId id NO11 Yes YesType type VA10 No YesLabel label N2 No YesNumber num SI No Yes

Data Item Id

Data Item Type

Description

Type of observation

Check

Low Value:High Value:Default Value:Unit:Format: NOB

70

Uppercase: Yes Lowercase: No Can't modify: NoList of Values: NOB Single (Normal) OB

SOB Contiguous sequence of OBsMOB Repeated OB with period

Data Item Label

Description

LabelType+Label uniquely identify an observationEx: NOB1, SOB1, MON1

Check


Data Item Number

Description

The order is used to sort the sequence of Observations by time.

Reference List

Entity Card Dep.

Relationship

OB(ob) 1,n No Observation Is Defined InOB(observation_is_defined_in_ob)

Program(prg) 1,1 No Prg Is Made OfObservations(prg_is_made_of_observations)

Entity Observation Conditions

Name: Observation Conditions

71

Code: ocndLabel:Number: Generate Table: Yes

Description

This table is used to log observation conditions during the observations for Quality Control

Annotation

The table is populated with the datalogger or with the results of the Elixir real-time partNULL values are used when the data is not available

Attribute List

Name Code Type I MId id NO11 Yes YesDate of insertion (local) date_insert DT No NoJulian Date jdate N14,7 No YesDate LST date_lst DT No YesDate UT date_ut DT No YesAir Temperature air_temp N3,1 No NoWind Speed wind_speed N4,1 No NoWind Direction wind_direction N4,1 No NoRelative Humidity hum_rel N4,1 No NoIQ Observed iq N3,2 No YesSky Background sky_bg F No NoEvaluation evaluation A1 No No

Data Item Id

Data Item Date of insertion (local)

Description

Date of insertion of the row in the DB

Check

Low Value:High Value:Default Value:Unit: loc timeFormat:

72


Data Item Julian Date

Description

Julian date for the row

Check

Low Value:High Value:Default Value:Unit: jul dayFormat: 2400000.1234567Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Date LST

Description

Local Sideral Time for the row

Data Item Date UT

Description

UT for the row

Data Item Air Temperature

Description

Air temperature measured

Check

Low Value:High Value:Default Value:Unit: deg CFormat:

73


Data Item Wind Speed

Description

Speed of wind measured

Check

Low Value:High Value:Default Value:Unit: knotsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Wind Direction

Description

Direction of wind measured

Check

Low Value: 0.0High Value: 360.0Default Value:Unit: degreesFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Relative Humidity

Description

Relative humidity measured

Check

74

Low Value: 0.0High Value: 100.0Default Value:Unit: %Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item IQ Observed

Description

Image quality observed

Annotation

Value to get from Elixir ?

Check

Low Value: 0.0High Value:Default Value:Unit: arcsecsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Sky Background

Description

Sky background measured

Annotation

Value to get from Elixir ?

Data Item Evaluation

Description

Quality ranking of the conditions

75

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: A

BC

Reference List

Entity Card Dep.

Relationship

OB(ob) 0,n No OB Is Observed UnderCondition(ob_is_observed_under_cond)

Entity Offset

Name: OffsetCode: offsetLabel:Number: Generate Table: Yes

Description

This table holds the offsets which define all the patterns

Annotation

Example: the following rows define the offsets for DP2 (for which we assume id=1 in table pattern)

id pat_id exp ra_off dec_off1 1 1 00:00 00:002 1 2 -00:11 -00:11

Query to show the offset of a particular named pattern:

SELECT pattern.name,offset.exposure,offset.ra,offset.dec_offsetFROM pattern,offset

76

WHERE offset.pat_id=pattern.id

Attribute List

Name Code Type I MId id NO11 Yes YesExp Number expnum SI No YesRA Offset ra VA8 No YesDEC Offset dec VA8 No Yes

Data Item Id

Data Item Exp Number

Description

The exposure number in the Pattern

Annotation

Assuming the pattern as a spiral structure like the current DPn patterns:

exposure=1 for the 1st exposure at target coordinatesexposure=2 for the following exposure with small offset from 1stetc...

Data Item RA Offset

Description

Offset in RA for Exposure # exposure of Pattern

Annotation

Example for DP2 [Ref] [11 arcsecs E]:Exposure 1: RA Offset= 00:00.0Exposure 2: RA Offset=-00:11.0

Data Item DEC Offset

Description

Offset in DEC for Exposure # exposure of Pattern

77

Annotation

Example for DP2 [Ref] [11 arcsecs E]Exposure 1: DEC Offset= 00:00.0Exposure 2: DEC Offset=-00:11.0

Reference List

Entity Card Dep.

Relationship

Pattern(pattern) 1,1 No Pattern Is Defined ByOffset(pat_is_def_by_offset)

Entity Pattern

Name: PatternCode: patternLabel:Number: Generate Table: Yes

Description

A Pattern is a scheme to observe a target with several offset exposures.

The succession of offsets to perform between exposures are stored in the table Offsets

Examples of patterns:

SINGLE a single exposureDP1 to DP8 Dithering patterns of CFH12KUserN User pattern defined with PH2 Web Tool (cf table User Pattern)

Attribute List


0No Yes

Is User is_user BL No YesAvailable for PH2 ? is_avail_ph2 BL No Yes

Data Item Id

78

Data Item Name

Description

Name of patternExamples: SINGLE,DP2,User1

Data Item Value

Description

Implementation of this patternName or arguments of obs. script to call... TBD


Description

Description of patternFor regular pattern, provides a description for the PIFor user pattern, PI may provide a description of his pattern

Data Item Is User

Description

If true, the pattern is defined by User

Check



Description

Flag T if this pattern is available for selection in the PH2 interface.

Check

79


Reference List

Entity Card Dep.

Relationship

Offset(offset) 0,n No Pattern Is Defined ByOffset(pat_is_def_by_offset)

Instrument Configuration(iconfig) 0,n No Pattern Is Used ByIC(pattern_is_used_by_ic)

User(usr) 0,1 No User OwnsPattern(user_owns_pattern)

Entity Pointing

Name: PointingCode: pointingLabel:Number: Generate Table: Yes

Description

The Pointing entity stores the parameters necessary to precisely position the object on the camera mosaic.

The offsets in RA and DEC measure the difference between the target coordinates and the requested center of themosaic.

Ex:To put target at std position 0: ra_offset=00:00, dec_offset=00:00To put target at position 5: ra_offset~+03:00 dec_offset~-03:30

Annotation

NB: If object at center of mosaic, both offsets are 0 (standard position 1)

Attribute List

80

Name Code Type I MId id NO11 Yes YesRA Pointing Offset in degrees ra_offset_deg F No NoDEC Pointing Offset in degrees dec_offset_deg F No NoName name VA5 No YesRA Pointing Offset ra_offset VA8 No YesDEC Pointing Offset dec_offset VA8 No YesIs User is_user BL No YesAvailable for PH2 ? is_avail_ph2 BL No Yes

Data Item Id

Data Item RA Pointing Offset in degrees

Data Item DEC Pointing Offset in degrees

Data Item Name

Description

The label is used for identification and classification of this row

Typical values:For regular pointings: values 1..6 identify std positions of target on chip.For user-defined pointings: User1 etc. identify user-created positions of target on chip.

Data Item RA Pointing Offset

Description

Offset in RA between target and center of mosaic.+/- mm:ss.s (arcmin, arcsecs)

Annotation

This offset is entered by PI by hand or using the FOV tool.

Data Item DEC Pointing Offset

Description

Offset in DEC between target and center of mosaic.+/- mm:ss.s (arcmin, arcsecs)

81

Annotation

This offset is entered by PI by hand or using the FOV tool.

Data Item Is User

Check



Description

Flag true if this value of binning is available in PH2 Tool

Check


Reference List

Entity Card Dep.

Relationship

Target(target) 0,n No Target Is Pted ByPointing(target_is_pted_by_pointing)

User(usr) 0,1 No User OwnPoiting(user_own_poiting)

Entity Program

82

Name: ProgramCode: prgLabel:Number: 20 Generate Table: Yes

Description

A science or calibration program, accepted and ranked by the Telescope Allocation ComitteeNB: The fraction completed is defined by Used I_Time/Allocated I_Time

Attribute List

Name Code Type I MId id NO11 Yes YesRun id runid VA10 No YesAgency agency VA10 No YesTitle title VA20

0No Yes

Abstract abstract TXT1000

No Yes

Tech_Feas tech_feas TXT1000

No Yes

PhaseII Comment ph2_comment TXT1000

No No

TAC Rank tac_rank A1 No YesTAC Grade tac_grade N3,1 No YesAllocated I_Time itime_alloc N8,1 No YesCalculated I_Time itime_calc N8,1 No NoUsed I_Time itime_used N8,1 No YesPhotometric Flag is_photometric BL No YesMonitor Flag is_monitor BL No YesMoving Fields Flag is_moving_fields BL No YesNeed Quick Data Access is_quick_data_access BL No YesStatus status VA20 No YesType type VA20 No Yes

Data Item Id

Data Item Run id

Description

83

Run Id of the program.

In Q mode, it is rather a Program Id, since Programs may be observed during different runs

Format:Year on 2 digits + semester A|B + agency C|F|H|E|D|Q + sequence number on 2 digits + Q

Meaning of 'agency' letters:C=Canada F=France H=Hawaii (E=Engineering, D=Discretionary)Q=specific Q program (program belonging to a calibration plan at CFHT)

Examples of Run-Ids:00AC12Q Science program from Canada to be observed in Q mode during 2000A00AQ01Q Q program (calibration) program from CFHT to be observed in Q mode during 2000A

Check

Low Value:High Value:Default Value:Unit:Format: 00AC12QUppercase: Yes Lowercase: No Can't modify: NoList of Values:

Data Item Agency

Description

Agency responsible for the program

Check

Low Value:High Value:Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: Canada

FranceHawaiiCFHT For Q programs

84

Data Item Title

Description

Title of the programImported from Poopsy DBEditable by PI in PH2

Data Item Abstract

Description

Abstract of the programImported from Poopsy DBEditable by PI in PH2

Data Item Tech_Feas

Description

Technical Feasability of the programImported from Poopsy DB

Data Item PhaseII Comment

Description

Optional comment entered by the PI during PH2Describes the program to QSO Team.

Special value: NULL = no comment entered

Check

Low Value:High Value:Default Value: NULLUnit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item TAC Rank

85

Description

Absolute Rank affected by TAC

Check

Low Value:High Value:Default Value:Unit:Format: AUppercase: Yes Lowercase: No Can't modify: NoList of Values: A must-do

B priorityC best effortD snapshot

Data Item TAC Grade

Description

Grade affected by TAC for programs with Rank=B or CPrograms with Rank=A have Grade=1.00

Check

Low Value: 1.00High Value: 3.00Default Value:Unit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Allocated I_Time

Description

Total I-Time allocated for the program

NB: Estimation of total I-Time allocated for all programs:

1) Total I-Time for one semester, all programs all instruments = 2000 hours2) Part CFH12K = 40 %

86

3) Part of CFH12K which is observed with Q = 95%4) Part which is substracted for overhead : 0% of overhead is accounted by user during PH2

=> Total I-Time allocated for all programs 2000 * 40/100 * 95/100= 760 hours or 2 736 000 seconds for all Q programs on CFH12K

Check

Low Value: 18000High Value:Default Value:Unit: secondsFormat: 36000Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Calculated I_Time

Description

I-Time calculated by formula looking at OBs

Annotation

Special value: NULL = no itime calculated yet (program not started)

Check

Low Value:High Value:Default Value:Unit: secondsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Used I_Time

Description

I-Time used by the program so far

Annotation

87

Programs are created with Used I-Time=0.0 sec

Check

Low Value:High Value:Default Value: 0.0Unit: secondsFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Photometric Flag

Description

Specifies if the program requires photometric conditions

Check


Data Item Monitor Flag

Description

Specifies if the program requires monitoring and therefore defines Monitoring OBs

Check


88

Data Item Moving Fields Flag

Description

Specifies if the program has moving fields and therefore requires targets defined by Orbital Elements of Ephemeris

Check


Data Item Need Quick Data Access

Check


Data Item Status

Description

Current status of the program

Statuses follow a Markov chain:

IDLE <---> QUEUED ---> STARTED ---> COMPLETED

IDLE ---> QUEUED: Program is inserted in the Programs queue for tentative observation

QUEUED ---> IDLE: A program that can't be started can come back to IDLE

89

QUEUED ---> STARTED: At least one OB has been observed, program remains in the Programs queue and has an higher priority to be finished.

STARTED ---> COMPLETED: All the OBs have been observed (or other criterium for Snapshot Programs). Program is removed from the queue

Check

Low Value:High Value:Default Value: IDLEUnit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: IDLE Program is idle

STARTED Program is startedQUEUED Program is in queueCOMPLETED Program is completed

Data Item Type

Description

Type of program, related to the observation strategy

Check

Low Value:High Value:Default Value: REGULARUnit:Format: REGULARUppercase: No Lowercase: No Can't modify: NoList of Values: REGULAR Regular prg

TOO Target of Opportunity programSNAPSHOT Snapshot prg

Reference List

Entity Card Dep.

Relationship

Events(events) 0,n No Event Is Related ToPrg(event_is_related_to_prg)

90

Entity Card Dep.

Relationship

Observation(obs) 0,n No Prg Is Made OfObservations(prg_is_made_of_observations)

Target(target) 1,n No Prg ObservesTarget(prg_observes_target)

CoI Assignment(coi_a) 0,n Yes Program Has CoIs(prg_has_cois)Constraint(cons) 1,n No Program Owns

Constraints(prg_owns_constraints)

Instrument Configuration(iconfig) 0,n No Program OwnsICs(prg_owns_ics)

OB(ob) 1,n No Program OwnsOBs(prg_owns_obs)

Instrument(instr) 1,1 No Program UsesInstr(program_uses_instr)

User(usr) 1,1 No User Is PI(user_is_pi)

Entity Site

Name: SiteCode: siteLabel:Number: 1 Generate Table: Yes

Description

The Sites table is used to compute local time from UT and for ephemeris generation

Attribute List

Name Code Type I MId id NO10 Yes YesIs Current is_current BL No YesObservatory Id obsid N4 No YesName name VA20 No YesTimezone timezone VA10 No YesTime difference from UTC timediff_utc_hh N2 No YesLongitude longitude N7,4 No YesLattitude latitude N7,5 No YesElevation elevation N4 No Yes

91

Data Item Id

Data Item Is Current

Check


Data Item Observatory Id

Description

UAI Observatory Id

Data Item Name

Data Item Timezone

Data Item Time difference from UTC

Check

Low Value:High Value:Default Value:Unit: hoursFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Longitude

Check

Low Value:High Value:

92

Default Value:Unit: degreesFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Lattitude

Check

Low Value:High Value:Default Value:Unit: degreesFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Elevation

Check

Low Value:High Value:Default Value:Unit: metersFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Entity Sky Background

Name: Sky BackgroundCode: skybgLabel:Number: Generate Table: Yes

Attribute List

Name Code Type I M

93


0No No


Data Item Id

Data Item Name

Description

Name of upper limits on Sky Background

- dark Tmp value, final TBD- less than 20% moon Tmp value, final TBD- less than 50% moon Tmp value, final TBD

Data Item Value

Description

Value of upper limits on Sky BackgroundUnit: photons/arcsec^2/seconds

Values TBD


Description

Description of this sky bg value

Annotation



Description

94

Flag true if this row is available in PH2 Tool

Check


Reference List

Entity Card Dep.

Relationship

Constraint(cons) 0,n No Constraint Features SkyBg(constraint_features_sky_bg)

Entity Target

Name: TargetCode: targetLabel:Number: 200 Generate Table: Yes

Description

Targets are astronomical targets defined by Fixed coordinates, Orbital Elements, or a list of ephemeris (time, position)

Attribute List

Name Code Type I MId id NO11 Yes YesLabel label N3 No YesName name VA20 No NoMagnitude magv N3,1 No NoChecked by PI is_pi_checked BL No YesPh2 Comment ph2_comment VA40 No NoApparent RA app_ra VA11 No NoApparent RA in degrees app_ra_deg F No NoApparent DEC app_dec VA11 No NoApparent DEC in degrees app_dec_deg F No No

95

Name Code Type I MCurrently Observable is_observable BL No Yes

Data Item Id

Data Item Label

Description

The label is used for identification and classification of this row by the PIMust be prefixed in the interfaces with the strings

T for a fix targetMTC for a moving target defined by coordinates/ephemerisMTO for moving target defined by orbital elements

Example: T1 = first fix target defined

Check


Data Item Name

Description

Name of target to be defined by the PIExample: M33

Data Item Magnitude

Description

Estimate of magnitude of Target in V band, defined by PI

Data Item Checked by PI

96

Description

True if the target has been checked by the PI using the FOV toolThis flag is used mainly by PI in PH2 for remembering what was checked.

Check include:- coordinate checked- no bright star on CCD

Check


Data Item Ph2 Comment

Description

Comment associated with target by PI during Ph2

Annotation

Not mentionned in PH2 design. Needed ?Special value: NULL = no comment entered

Data Item Apparent RA

Description

Current RA, for the apparent epoch.

This field is automatically updated by the DB on a daily basis for moving targets.

Annotation

Special value: NULL = unknonw (not computed)

Data Item Apparent RA in degrees

Data Item Apparent DEC

97

Description

Current DEC, for the apparent epoch

This field is automatically updated by the DB on a daily basis for moving targets

Annotation

Special value: NULL = unknonw (not computed)

Data Item Apparent DEC in degrees

Data Item Currently Observable

Description

True if target is observable.This flag is updated on a hourly basis for all targets by the DB.

Check


Reference List

Entity Card Dep.

Relationship

Program(prg) 1,1 No Prg ObservesTarget(prg_observes_target)

OB(ob) 0,n No Target Is Obsed InOB(target_is_obsed_in_ob)

Pointing(pointing) 1,1 No Target Is Pted ByPointing(target_is_pted_by_pointing)

Entity Target defined By Ephemeris

Name: Target defined By EphemerisCode: target_eph

98

Label:Number: Generate Table: Yes

Description

A target defined by a table of coordinates stored in the Ephemeris tableInterpolation is used to compute the position of the target at observation time.

Reference List

Entity Card Dep.

Relationship

Ephemeris(ephemeris) 1,n No Target Ephem Must HaveEphemeris DefinedBy(tae_has_ephem_def_by)

Entity Target defined by OE

Name: Target defined by OECode: target_oeLabel:Number: Generate Table: Yes

Description

A target defined by its orbital elementsThe QSO ephemeris engine may compute ephemeris to be stored in the Ephemeris table.

Attribute List

Name Code Type I MLongitude longitude F No YesSemi_Major Axis smajor_axis F No YesExcentricity excentricity F No YesInclination inclination F No YesAscending Node Long ascnode_long F No YesPerihelion Long peri_long F No YesEquinox for orbital elts oe_equinox F No YesMinimal Elongation elong_min F No YesMaximal Elongation elong_max F No Yes

Data Item Longitude

99

Description

1st orbital element: Longitude of the object

Check


Data Item Semi_Major Axis

Description

2nd orbital element: Semimajor axis of the orbit

Check


Data Item Excentricity

Description

3rd orbital element: Excentricity of the orbit

Check

Low Value:High Value:Default Value:Unit: degreesFormat:Uppercase: No Lowercase: No Can't modify: No

100

List of Values:

Data Item Inclination

Description

4th orbital element: Inclination of the orbit on the plane of the ecliptic

Check


Data Item Ascending Node Long

Description

5th orbital element: Longitude of the ascending node.

Check


Data Item Perihelion Long

Description

6th orbital element: Longitude of the perihelion

Check

Low Value:

101

High Value:Default Value:Unit: degreesFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Equinox for orbital elts

Data Item Minimal Elongation

Description

Minimum Elongation Constraint

Check

Low Value:High Value:Default Value:Unit: degreesFormat: 170.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Maximal Elongation

Description

Maximum Elongation Constraint

Check

Low Value:High Value:Default Value:Unit: degreesFormat: 190.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

102

Reference List

Entity Card Dep.

Relationship

Ephemeris(ephemeris) 0,n No Target OE May Have EphemerisDefinedBy(tao_may_have_ephem_def_by)

Entity Target defined by RA and DEC

Name: Target defined by RA and DECCode: target_fixLabel:Number: Generate Table: Yes

Description

A target which is fix in the skyIt is defined by RA,DEC and equinox and may have a small proper motion (maximum: a few sec/years in RA, a fewarcsecs/years in DEC)

Attribute List

Name Code Type I MRequested RA req_ra VA11 No NoRequested RA in degrees req_ra_deg F No NoRequested DEC req_dec VA11 No NoRequested DEC in degrees req_dec_deg F No NoRequested PM RA req_pm_ra F No YesRequested PM DEC req_pm_dec F No YesRequested Equinox req_equinox N5,1 No Yes

Data Item Requested RA

Description

RA of target requested by PIFormat: hh:mm:ss.ss

Data Item Requested RA in degrees

Data Item Requested DEC

103

Description

DEC of target requested by PIFormat: +/- dd:mm:ss.s

Data Item Requested DEC in degrees

Data Item Requested PM RA

Description

in sec of RA/years (TCS)

Check

Low Value:High Value:Default Value: 0.0Unit: sec/yearFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Requested PM DEC

Description

Proper Motion of Targetin arcsec/year (TCS)

Check

Low Value:High Value:Default Value: 0.0Unit: as/yearFormat:Uppercase: No Lowercase: No Can't modify: NoList of Values:

Data Item Requested Equinox

Description

104

Equinox for requested coordinates

Check

Low Value:High Value:Default Value: 2000.0Unit:Format: 2000.0Uppercase: No Lowercase: No Can't modify: NoList of Values:

Entity Tracking

Name: TrackingCode: trackingLabel:Number: Generate Table: Yes

Description

Types of trackings availableSIDERALNON-SIDERAL=follow target

Attribute List

Name Code Type I MId id NO11 Yes YesName name VA20 No YesValue value VA20 No Yes

Data Item Id

Data Item Name

Description

Name of trackingExample: Sid, NonSid

Data Item Value

105

Description

Value for trackingExample: SIDERAL

Reference List

Entity Card Dep.

Relationship

OB(ob) 0,n No OB Is Obsed UsingTracking(ob_is_obsed_using_tracking)

Entity User

Name: UserCode: usrLabel:Number: 50 Generate Table: Yes

Description

This table holds all QSO users

Annotation

Table name=usr since user is a Sybase reserved word

Attribute List

Name Code Type I MId id NO11 Yes YesFirst Name fname VA40 No YesLast Name lname VA40 No YesInstitute institute VA10

0No Yes

Address1 address1 VA100

No No


No No


No No

State state VA40 No NoZip Code zip VA10 No NoCity city VA20 No No

106

Name Code Type I MCountry country VA20 No YesWork Phone work_phone VA20 No YesWork Email work_email VA40 No YesWork Fax work_fax VA20 No NoHome Phone home_phone VA20 No NoHome Email home_email VA40 No NoHome Fax home_fax VA20 No NoMobile Phone mobile_phone VA20 No NoUser ID userid VA20 No NoPh1 User ID ph1_userid VA20 No NoPassword pw VA40 No NoPh1 Password ph1_pw VA40 No NoStatus status VA20 No Yes

Data Item Id

Data Item First Name

Data Item Last Name

Data Item Institute

Data Item Address1

Data Item Address2

Data Item Address3

Data Item State

Description

State or Province

Data Item Zip Code

Data Item City

Data Item Country

107

Data Item Work Phone

Data Item Work Email

Data Item Work Fax

Data Item Home Phone

Data Item Home Email

Data Item Home Fax

Data Item Mobile Phone

Data Item User ID

Description

User Id used to log to PH2

Data Item Ph1 User ID

Description

User Id inherited from Poopsy Database, for reference if User Id changes

Data Item Password

Description

Password necessary to log in PH2

Data Item Ph1 Password

Description

Password inherited from Poopsy, for reference in case the Password changes

Data Item Status

Description

Status of user for permission purpose on PH2

108

Annotation

Users are created with default status = LOCKEDOnce user is created, allow him to login by changing his status

Check

Low Value:High Value:Default Value: LOCKEDUnit:Format:Uppercase: No Lowercase: No Can't modify: NoList of Values: ACTIVE User can log in PH2

LOCKED User cannot log in PH2

Reference List

Entity Card Dep.

Relationship

Events(events) 0,n No Event Was RecordedBy(event_was_recorded_by)

CoI Assignment(coi_a) 0,n Yes User CoInvestigates(user_co_investigates)

Program(prg) 0,n No User Is PI(user_is_pi)Pointing(pointing) 0,n No User Own

Poiting(user_own_poiting)Pattern(pattern) 0,n No User Owns

Pattern(user_owns_pattern)

109

Relationships Information

Relationship Binning Is Avail On Instr

Name: Binning Is Avail On InstrCode: binning_is_avail_on_instrLabel:Entity 1: BinningEntity 2: Binning AssignementCardinality: One to ManyEntity 2 dependent of Entity 1: Yes

Entity 1 --> Entity 2:Role:Mandatory: YesDominant: NoMin, Max: 1, n

Entity 2 --> Entity 1:Role:Mandatory: YesDominant: NoMin, Max: 1, 1

Relationship Constraint Features Airmass

Name: Constraint Features AirmassCode: constraint_features_airmassLabel:Entity 1: AirmassEntity 2: ConstraintCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: belongsMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: features

110

Mandatory: YesDominant: NoMin, Max: 1, 1

Relationship Constraint Features IQ

Name: Constraint Features IQCode: constraint_features_iqLabel:Entity 1: Image QualityEntity 2: ConstraintCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: belongs toMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: hasMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Constraint Features Sky Bg

Name: Constraint Features Sky BgCode: constraint_features_sky_bgLabel:Entity 1: Sky BackgroundEntity 2: ConstraintCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: belongs toMandatory: NoDominant: NoMin, Max: 0, n

111

Entity 2 --> Entity 1:Role: featuresMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Event Is Related To Prg

Name: Event Is Related To PrgCode: event_is_related_to_prgLabel:Entity 1: ProgramEntity 2: EventsCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: was used inMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: is related toMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Event Was Recorded By

Name: Event Was Recorded ByCode: event_was_recorded_byLabel:Entity 1: UserEntity 2: EventsCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: has recorded

112

Mandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: was recorded byMandatory: NoDominant: NoMin, Max: 0, 1

Relationship Filter Is Avail On Instr

Name: Filter Is Avail On InstrCode: filter_is_avail_on_instrLabel:Entity 1: FilterEntity 2: Filter AssignmentCardinality: One to ManyEntity 2 dependent of Entity 1: Yes



Relationship IC Occurs In IC Sequence

Name: IC Occurs In IC SequenceCode: ic_occurs_in_ic_sequenceLabel:Entity 1: Instrument ConfigurationEntity 2: IC SequenceCardinality: One to OneEntity 2 dependent of Entity 1: No

113

Entity 1 --> Entity 2:Role: occurs inMandatory: NoDominant: NoMin, Max: 0, 1

Entity 2 --> Entity 1:Role: is an occurence ofMandatory: YesDominant: NoMin, Max: 1, 1

Relationship IC Uses Binning

Name: IC Uses BinningCode: ic_uses_binningLabel:Entity 1: BinningEntity 2: Instrument ConfigurationCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is used byMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: usesMandatory: YesDominant: NoMin, Max: 1, 1

Relationship IC Uses Filter

Name: IC Uses FilterCode: ic_uses_filterLabel:Entity 1: Filter

114

Entity 2: Instrument ConfigurationCardinality: One to ManyEntity 2 dependent of Entity 1: No



Relationship Instr Features Binning

Name: Instr Features BinningCode: instr_features_binningLabel:Entity 1: InstrumentEntity 2: Binning AssignementCardinality: One to ManyEntity 2 dependent of Entity 1: Yes



Relationship Instr Features Filter

Name: Instr Features Filter

115

Code: instr_features_filterLabel:Entity 1: InstrumentEntity 2: Filter AssignmentCardinality: One to ManyEntity 2 dependent of Entity 1: Yes



Relationship Is Obsed With Priority

Name: Is Obsed With PriorityCode: is_obsed_with_priorityLabel:Entity 1: OB PriorityEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No


Entity 2 --> Entity 1:Role: is obsed withMandatory: YesDominant: NoMin, Max: 1, 1

116

Relationship Ob Is Obsed Using ICs In

Name: Ob Is Obsed Using ICs InCode: ob_is_obsed_using_ics_inLabel:Entity 1: OBEntity 2: IC SequenceCardinality: One to OneEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is observed by using ICs inMandatory: YesDominant: NoMin, Max: 1, 1

Entity 2 --> Entity 1:Role: belongs toMandatory: NoDominant: NoMin, Max: 0, 1

Relationship OB Is Obsed Using Tracking

Name: OB Is Obsed Using TrackingCode: ob_is_obsed_using_trackingLabel:Entity 1: TrackingEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No


Entity 2 --> Entity 1:Role: is observed usingMandatory: YesDominant: No

117

Min, Max: 1, 1

Relationship OB Is Observable Under Const

Name: OB Is Observable Under ConstCode: ob_is_observable_under_constLabel:Entity 1: OBEntity 2: ConstraintCardinality: One to OneEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is observable underMandatory: YesDominant: NoMin, Max: 1, 1

Entity 2 --> Entity 1:Role: applies toMandatory: NoDominant: NoMin, Max: 0, 1

Relationship OB Is Observed In Exp

Name: OB Is Observed In ExpCode: ob_is_observed_in_expLabel:Entity 1: OBEntity 2: ExposuresCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is observed inMandatory: YesDominant: NoMin, Max: 1, n

Entity 2 --> Entity 1:

118

Role: belongs toMandatory: YesDominant: NoMin, Max: 1, 1

Relationship OB Is Observed Under Condition

Name: OB Is Observed Under ConditionCode: ob_is_observed_under_condLabel:Entity 1: Observation ConditionsEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: conditions apply toMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: OB is observed underMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Observation Is Defined In OB

Name: Observation Is Defined In OBCode: observation_is_defined_in_obLabel:Entity 1: ObservationEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: requiresMandatory: YesDominant: No

119

Min, Max: 1, n

Entity 2 --> Entity 1:Role: is observed byMandatory: NoDominant: NoMin, Max: 0, 1

Relationship Pattern Is Defined By Offset

Name: Pattern Is Defined By OffsetCode: pat_is_def_by_offsetLabel:Entity 1: PatternEntity 2: OffsetCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is defined byMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: defineMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Pattern Is Used By IC

Name: Pattern Is Used By ICCode: pattern_is_used_by_icLabel:Entity 1: PatternEntity 2: Instrument ConfigurationCardinality: One to ManyEntity 2 dependent of Entity 1: No


120

Role: is used byMandatory: NoDominant: NoMin, Max: 0, n


Relationship Prg Is Made Of Observations

Name: Prg Is Made Of ObservationsCode: prg_is_made_of_observationsLabel:Entity 1: ProgramEntity 2: ObservationCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is made ofMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: belongs toMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Prg Observes Target

Name: Prg Observes TargetCode: prg_observes_targetLabel:Entity 1: ProgramEntity 2: TargetCardinality: One to Many

121

Entity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: ownsMandatory: YesDominant: NoMin, Max: 1, n


Relationship Program Has CoIs

Name: Program Has CoIsCode: prg_has_coisLabel:Entity 1: ProgramEntity 2: CoI AssignmentCardinality: One to ManyEntity 2 dependent of Entity 1: Yes

Entity 1 --> Entity 2:Role:Mandatory: NoDominant: NoMin, Max: 0, n


Relationship Program Owns Constraints

Name: Program Owns ConstraintsCode: prg_owns_constraintsLabel:

122

Entity 1: ProgramEntity 2: ConstraintCardinality: One to ManyEntity 2 dependent of Entity 1: No



Relationship Program Owns ICs

Name: Program Owns ICsCode: prg_owns_icsLabel:Entity 1: ProgramEntity 2: Instrument ConfigurationCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: ownsMandatory: NoDominant: NoMin, Max: 0, n


Relationship Program Owns OBs

123

Name: Program Owns OBsCode: prg_owns_obsLabel:Entity 1: ProgramEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No



Relationship Program Uses Instr

Name: Program Uses InstrCode: program_uses_instrLabel:Entity 1: InstrumentEntity 2: ProgramCardinality: One to ManyEntity 2 dependent of Entity 1: No



124

Relationship Target Ephem Must Have Ephemeris Defined By

Name: Target Ephem Must Have Ephemeris Defined ByCode: tae_has_ephem_def_byLabel:Entity 1: Target defined By EphemerisEntity 2: EphemerisCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: has ephemeris defined byMandatory: YesDominant: NoMin, Max: 1, n

Entity 2 --> Entity 1:Role: defines the targetMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Target Is Obsed In OB

Name: Target Is Obsed In OBCode: target_is_obsed_in_obLabel:Entity 1: TargetEntity 2: OBCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: is observed inMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: has targetMandatory: YesDominant: No

125

Min, Max: 1, 1

Relationship Target Is Pted By Pointing

Name: Target Is Pted By PointingCode: target_is_pted_by_pointingLabel:Entity 1: PointingEntity 2: TargetCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: applies toMandatory: NoDominant: NoMin, Max: 0, n

Entity 2 --> Entity 1:Role: is pointing byMandatory: YesDominant: NoMin, Max: 1, 1

Relationship Target OE May Have Ephemeris Defined By

Name: Target OE May Have Ephemeris Defined ByCode: tao_may_have_ephem_def_byLabel:Entity 1: Target defined by OEEntity 2: EphemerisCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role: may have ephemeris defined byMandatory: NoDominant: NoMin, Max: 0, n


126

Role: define targetMandatory: YesDominant: NoMin, Max: 1, 1

Relationship User Co Investigates

Name: User Co InvestigatesCode: user_co_investigatesLabel:Entity 1: UserEntity 2: CoI AssignmentCardinality: One to ManyEntity 2 dependent of Entity 1: Yes



Relationship User Is PI

Name: User Is PICode: user_is_piLabel:Entity 1: UserEntity 2: ProgramCardinality: One to ManyEntity 2 dependent of Entity 1: No

Entity 1 --> Entity 2:Role:Mandatory: NoDominant: No

127

Min, Max: 0, n


Relationship User Own Poiting

Name: User Own PoitingCode: user_own_poitingLabel:Entity 1: UserEntity 2: PointingCardinality: One to ManyEntity 2 dependent of Entity 1: No


Entity 2 --> Entity 1:Role:Mandatory: NoDominant: NoMin, Max: 0, 1

Description

User may own Pointing

Annotation

WARNING: Do not use inheritance here because PD will generate a bad foreign key definition (with too manycolumns) !

Relationship User Owns Pattern

Name: User Owns PatternCode: user_owns_pattern

128

Label:Entity 1: UserEntity 2: PatternCardinality: One to ManyEntity 2 dependent of Entity 1: No


Entity 2 --> Entity 1:Role:Mandatory: NoDominant: NoMin, Max: 0, 1

Description

A pattern can belong to a User

Annotation

WARNING: Do not use inheritance here because PD will generate a bad foreign key definition (with too manycolumns) !

the qso project: specifications and design of the phase ii

Documents