Input data

Introduction

Please read all bullet points carefully before running LBL.

• Below we list suggested file inputs. Note these are just a guide with files we have tested. 

• The calib, science and template directories are located in the {DATA_DIR} parameter from the warp files.

• Science files should be copied into a directory per target i.e. {DATA_DIR}/science/{OBJECT_NAME}

• We recommend running telluric correction (wrap file parameter RUN_LBL_TELLUCLEAN) on any science data that is not telluric corrected.

• You must run template construction if not providing a templates. You do not need to provide templates if you have the science data. Copy any templates in the the {DATA_DIR}/template directory.

• Note variables are denoted by the {}  i.e. {OBJECT_NAME} means put your object name here.

• The exact name of the files are not important for LBL unless they are calibration files being taken from the header (i.e. wave or blaze files).

  • wrap file parameter BLAZE_FILE will force the blaze file - otherwise the blaze file will probably be taken from the header (if possible)

    • This blaze file (either forced or from the header) must be copied into the calibration directory

  • You can override globally which template file will be used (but still need to provide the parameter OBJECT_TEMPLATE)

    • Do do this add parameter TEMPLATE_FILE to your wrap file - this will force a single template file for all observations and thus must copied manually into the template directory

  • Currently you cannot force a wave solution - it will loaded by the instrument+mode either from an extension or a header key

    • If a wavelength solution is listed in the calibration directory below please provide it, otherwise you can assume it is supplied in the science data.

• If you are missing calibration data or science data please contact staff responsible for those instruments.

SPIROU

DATA SOURCE: APERO

• calib directory:

  • • wavelength solution: 

      • {HASH}_pp_e2dsff_AB_wave_night_AB.fits

      • {HASH}_pp_e2dsff_AB_wave_night_A.fits

      • {HASH}_pp_e2dsff_AB_wave_night_B.fits

      • {HASH}_pp_e2dsff_AB_wave_night_C.fits

    • Blaze file:

      • {HASH}_pp_blaze_AB.fits

• science directory:

  • • {OBJECT_NAME}/{odocode}_pp_e2dsff_tcorr_AB.fits

• template directory:

  • • Template_s1dv_{OBJECT_NAME}_sc1d_v_file_AB.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• By default we use non-blaze corrected files. 

• By default we use telluric corrected files supplied from APERO thus RUN_LBL_TELLUCLEAN is False by default

• By default we use templates supplied from APERO thus RUN_LBL_TEMPLATE is False by default

DATA SOURCE: CADC

• calib directory:

  • • None

• science directory:

  • • {OBJECT_NAME}/{odocode}t.fits

• template directory:

  • • Template_s1dv_{OBJECT_NAME}_sc1d_v_file_AB.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• By default we use non-blaze corrected files. 

• By default we use telluric corrected files supplied from APERO thus RUN_LBL_TELLUCLEAN is False by default

• By default we use templates supplied from APERO thus RUN_LBL_TEMPLATE is False by default, however these are not currently available on CADC so you may want to generate templates via LBL.

CARMENES

DATA SOURCE: CARMENES-vis

• calib directory:

  • • None

• science directory:

  • • {OBJECT_NAME}/car-{YYYYMMDD}T{HH}h{MM}m{SS}s-sci-gtoc-vis_A.fits

• template directory:

  • • Template_{OBJECT_NAME}_CARMENES.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• By default we use blaze corrected files. 

HARPS

DATA_SOURCE: ESO

• calib directory:

  • • Blaze file: None

• science directory:

  • • {OBJECT_NAME}/r.HARPS.{yyyy-mm-dd}T{HH-MM-SS.SSS}_S2D_A.fits

• template directory:

  • • Template_{OBJECT_NAME}_HARPS_ESO.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• By default we use blaze corrected files. 

DATA_SOURCE: ORIG

• calib directory:

  • • Blaze file: 

      • • HARPS.{yyyy-mm-dd}T{HH_MM_SS.SSS}_blaze_A.fits

• science directory:

  • • {OBJECT_NAME}/HARPS.{yyyy-mm-dd}T{HH-MM-SS.SSS}_e2ds_A.fits

• template directory:

  • • Template_{OBJECT_NAME}_HARPS_ORIG.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• By default we use non-blaze corrected files. 

MAROONX

DATA_SOURCE: MAROONX_b

• calib directory:

  • • master flat: 

      • • {yyyymmdd}T{HH}_masterflat_backgroundsubtracted_FFFFF_x_0000.hd5

• science directory:

  • • {OBJECT_NAME}/{yyyymmdd}T{HHMMSSZ}_SOOOe_x_{NNNN}.hd5}

    • {OBJECT_NAME}/{yyyymmdd}T{HHMMSSZ}_SOOOe_b_{NNNN}.hd5}

• template directory:

  • • Template_{OBJECT_NAME}_MAROONX_BLUE.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• Do not mix _x_ and _b_ science files, use a full set of one or the other.

• By default we get the blaze from the science file

DATA_SOURCE: MAROONX_r

• calib directory:

  • • master flat: {yyyymmdd}T{HH}_masterflat_backgroundsubtracted_FFFFF_x_0000.hd5

• science directory:

  • • {OBJECT_NAME}/{yyyymmdd}T{HHMMSSZ}_SOOOe_x_{NNNN}.hd5}

    • {OBJECT_NAME}/{yyyymmdd}T{HHMMSSZ}_SOOOe_r_{NNNN}.hd5}

• template directory:

  • • Template_{OBJECT_NAME}_MAROONX_RED.fits     [Only supply templates if you don't want to generated them in lbl]

Notes:

• Do not mix _x_ and _r_ science files, use a full set of one or the other.

• By default we get the blaze from the science file