LP_214M26 (spirou_offline_udem)

This page was last modified: 2026-02-12 20:50:48.043481 (UTC)

Back to the object table

Contents

Target info

This section gives some details of the APERO astrometric database used when processing this target (e.g. for BERV calculation). Any observation with a object name in the alias list will be associated with this “APERO target” i.e. DRSOBJN=LP_214M26

Target Information

RA

166.0651984 [deg] (Gaia DR2)

Dec

40.00421267 [deg] (Gaia DR2)

Finder chart

[FINDER CHART]

Teff

4000.0 [K] (HEADER[CFHT])

Spectral Type

K5V (1986AJ…..92..139S)

Proper Motion (RA)

-200.2672583 [mas/yr] (Gaia DR2)

Proper Motion (Dec)

-104.0980864 [mas/yr] (Gaia DR2)

Parallax

32.91811735 [mas/yr] (Gaia DR2)

Radial Velocity

28.74 [mas/yr] (2018yCat.1345….0G)

Aliases

2MASS J11041590+4000165, ASCC 407561, GJ 3640, GSC 03010-01216, Gaia DR1 777005625896147072, Gaia DR2 777005625896147072, HAT 183-00175, HIC 54105, HIP 54105, LP 214-26, LSPM J1104+4000, NLTT 26156, PM J11042+4000, StKM 2-696, TIC 353970454, TYC 3010-1216-1, UCAC2 45825243, UCAC4 651-050998, USNO-B1.0 1300-00210749, WISEA J110415.71+400015.8, [RHG95] 1720, ASCC 407561, GJ 3640, HIC 54105, HIP 54105, LP 214-26, LP214-26, LP_214M26, UCAC2 45825243, [RHG95] 1720, 2MASSJ11041590+4000165, ASCC407561, GJ3640, GSC03010-01216, GaiaDR1777005625896147072, GaiaDR2777005625896147072, HAT183-00175, HIC54105, HIP54105, LP214-26, LSPMJ1104+4000, NLTT26156, PMJ11042+4000, StKM2-696, TIC353970454, TYC3010-1216-1, UCAC245825243, UCAC4651-050998, USNO-B1.01300-00210749, WISEAJ110415.71+400015.8, [RHG95]1720, ASCC407561, GJ3640, HIC54105, HIP54105, LP214-26, LP214-26, LP214M26, UCAC245825243, [RHG95]1720

OBJECT name(s) in headers

LP 214-26

PI name(s) in headers

Ryan Cloutier

Project/Run name(s) in headers

20AC25

Spectrum

This section presents the observation after extraction,with and without telluric correction.

LBL

No LBL reduction found

CCF

This section presents the APERO CCF results for this object.

../../../_images/ccf_plot_LP_214M26_spirou_offline_udem.png

CCF stats

Mask used

GL846_neg.fits

CCF systemic velocity

29019.88 \(\pm\) 30.16 m/s

CCF FWHM

7395.97 \(\pm\) 118.13 m/s

Number of CCF files Total

9

Number of CCF passed QC

9

Number CCF files failed QC

0

First ccf file [Mid exposure]

2020-02-18 09:13:45.343

Last ccf file [Mid exposure]

2020-06-10 06:51:37.967

Last processed [ccf]

2025-02-23 20:11:37.339

Version [ccf]

0.7.292

Request

CCF files

CCF Downloads

File URL

Uploaded

CCF Table

ccf_LP_214M26_spirou_offline_udem_file_list.txt

2026-02-12 20:50:50.866

Time series

This section deals with providing the time series information for this object

Debug

This section has various debug plots from APERO products

Telluric map

../../../_images/debug_tcorr_map_plot_LP_214M26_spirou_offline_udem.png

Telluric map of e2dsff_tcorr_A files.Files are low-passed and corrected for the stars motion. The QC is displayed to the right of the image - in purple are the files that passed, in orange the files that failed.

Maximum Saturation level plot

../../../_images/debug_extsmax_plot_LP_214M26_spirou_offline_udem.png

Maximum saturation level measured at time of extraction

Measured effective readout noise before extraction

../../../_images/debug_effron_plot_LP_214M26_spirou_offline_udem.png

Measured effective readout noise before extraction

APERO Processing Debug Plot

../../../_images/debug_version_plot_LP_214M26_spirou_offline_udem.png

Plotting the version and processed date from the header from APERO. Note that offline reductions should lead to a straight line, while online reductions should be roughly a one-to-one with the Date axis.

APERO Calibration times plot

../../../_images/debug_mjd_cdt_plot_LP_214M26_spirou_offline_udem.png

Computed time between observation and calibration used. Some calibrations arereference calibrations (in purple) and thus diverge from the reference night, others should always be from the same night (orange) unless no calibration was taken that night in which case the closest calirbation in time should have been used.