arXiv:1503.05680v1 [astro-ph.IM] 19 Mar 2015 srnmsh ahihe,2 uut2021 August 29 Nachrichten, Astronomische im rzl S RS n cec rgam) emn and Germany to Programme), Correspondence Science A and of (RSSD contribution ESA the Brazil, with gium, CNES, by operated is and developed cie eeaentsrcl iie oCRTdt,btmay but on data, applied CoRoT be to limited also of strictly de- not reduction methods are The data here yet. scribed the published been for has ‘tool- dataset routines CoRoT complete the and no algorithms But of (2010). chromatic al. box’ in et jumps Mislis of by correction the lightcurves or b (2009) effects al. systematic et of Mazeh minimization the like problems tial data N2 CoRoT the gen- of available. no 2012, reduction is far product so al. data but for et 2012), description al. (Carone et eral e.g. Grziwa 2012, papers, al. various et detection Bonomo in transit found the be to can specific techniques reduction Data Introduction 1 srol otiscretosta a eddcdfo a from deduced be can that corrections contains end only the to user in- published the is which extract data-product, to This data-product formation. N2 given the beyond cessing (2009). al. et exten Aigrain of al. are by characteristics exo-channel et analysed noise sively the Its Auvergne product. on by data focuses CoRoT paper the mainly the paper in This found (2009). be char and can performance al. transit- satellites acteristics et the of of (Baglin description asteroseismology A detection 2006). and the planets extrasolar to ing devoted instrument tometric P upcoming ⋆ h oo pc iso,luce n20 eebr2,hsbe has 27, December 2006 on launched mission, space CoRoT The tepshv enmd nteps oda ihpar- with deal to past the in made been have Attempts eea cec-plctosrqiea diinlpro- additional an require science-applications Several pho- precision high advanced an is satellite CoRoT The LATO h ehd ecie eeaentsrcl iie oCoRoT to limited mission. strictly Plato not pe are squares here described least methods the The or us doma function frequency be autocorrelation the The might in noise. filters channels various i needs, color linear the CoRoT on by Depending the filled from be th derived can improving Magnitudes Gaps with algorithm. along drizzle data dimensional of must reduction datapoints The unflagged releas reconsidered. only d been Though N2 has correctly. dataset CoRoT CoRoT whole the from the for Since far planets. so extrasolar published techniques reduction Data words Key later online Published XXXX accepted 2021, August 29 Received Sternwart der An (AIP), f¨ur Astrophysik Leibniz-Institut Weingrill J. CoRoT [email protected] : . iso Rure l,2014). al., et (Rauer mission 2.0 Kepler ⋆ 1 ehius htmti ehd:dt analysis data methods: – photometric techniques: aaRdcinB Example By Reduction Data Brcie l,21)dt rthe or data 2010) al., et (Borucki sra Bel- ustria, Spain. en y - - - h oo-antd iga hudb sda reference a as in used position be the should diagram information, color-magnitude FITS-header the the in stars the of rough a for used be classification. can K- spectral and and stellar precise J- rather H-, other given are The with magnitudes correctness. compared for be catalogues should source and pr only information represent liminary temperature lu effective type, DENIS or spectral and class, given minosity 2005) The catalogue. al. 1999) (Skrutskie et al. 2MASS (Zacharias et (Vauglin the NOMAD 2006), using al. by et assembled FITS- the been in has information files auxiliary Most database. ExoDat 07 eei ta.20) ti ihyrcmeddto recommended highly Topcat is e.g. It like 2009). VOTools al. use et ExoDat Deleuil through 2007; accessed be can mation onoda h A aacentre data IAS the at download signal lightcurve. transit the where lute instance be for magneti to spots stellar stellar of noise as identification activity instrumental the to the contrast and in removed activity re which stellar signals the transit-like for quire search the prom is A in- example processing. nent by scientific different unfiltered for is allow data-product to be tention This to user. have the origin by random Other removed or 2009). systematic al., of et either (Auvergne variations jitter interference, and linearity, background electronic liers, for are applied co The tions orbit. satellite’s the e.g. like model deterministic 6 -48 osa,Germany Potsdam, D-14482 16, e 4 3 2 1 idga r prpit ehd oietf eidcsig periodic identify to methods appropriate are riodogram d pcfi loihsaerqie opoestelightcur the process to required are algorithms specific ed, huhtelmnst ls siaei ie o most for given is estimate class luminosity the Though aafo oo ushsbe aeaalbefor available made been has runs CoRoT from Data http://aladin.u-strasbg.fr/ http://www.star.bris.ac.uk/ http://cesam.oamp.fr/exodat/ http://idoc-corot.ias.u-psud.fr/ aabtmyas eapido elrdt rteupcoming the or data Kepler on applied be also may but data frequency high or background noise red the either remove in troae aawtothrigtefeunyspectrum. frequency the harming without data nterpolated inlt-os ai a eahee yapyn one a applying by achieved be can ratio signal-to-noise e ecoe o cetfi rcsig oeflg ih be might flags some processing, scientific for chosen be t rdc eetree rmrl ntedtcinof detection the on primarily targeted were product ata dt eieadtoa nomto bu h targets. the about information additional derive to ed oyih iewl epoie ytepublisher the by provided be will line Copyright oyih iewl epoie ytepublisher the by provided be will line Copyright 3 rAladin or 1 upeetr infor- Supplementary . ˜ mbt/topcat/ 2 4 Muire al. et (Meunier oacs the access to rrec- di- s nals. out- ves e- i- c - - 2 J. Weingrill: CoRoT Data Reduction By Example to roughly discriminate between the dwarf and giant popu- Table 1 List of CoRoT runs with their approximate run lation. Usually the information from ExoDat succeeds the length sorted by date of observation start. The run LRc09 information from the FITS-headers, requiring the user to was not public available at the date of publication. perform the update of relevant data by himself. An exam- run duration run duration ple of possible (mis-)identification of luminosity classes of code (days) code (days) stars in the run LRa01 (Carone et al., 2012) is shown in Fig- IRa01 57.75 SRa03 24.29 ure 1. For parameters resulting in astrophysical parameters SRc01 25.55 LRc05 87.26 LRc01 152.02 LRc06 77.41 LRa01 131.46 LRa04 77.58 SRa01 23.41 LRa05 90.49 11 LRc02 145.00 LRc07 81.21 SRc02 20.88 SRc03 3.46 12 SRa02 31.74 LRc08 83.56 LRa02 114.65 SRa04 52.25 13 LRc03 89.19 SRa05 38.68 LRc04 84.15 LRa06 76.62 14 LRa03 148.31 LRc09 – V [mag] V 15
16 identified by the combination of RUN ID, HLFCCD ID and WIN ID, which is also unique for each CoRoT tar- 17 get (Carone et al., 2012). To verify the existence of mul- 0.0 0.5 1.0 1.5 2.0 tiple observations for one target, the CoRoTIDs have to be B - V queried in the ExoDat database. The user has to download the whole run and concatenate the observations based on the Fig. 1 Color-magnitude diagram of stars from LRa01. time-stamp. A proper cross-identification of targets should Dwarf stars are represented as squares, giants as triangles. be done using their coordinates. Individual targets can be A possible criterion for the separation of luminosity classes downloaded on ExoDat as FITS files or by using VO-tools. is indicated by a dashed line. Except for the runs SRa01 (pipeline version 0.9 and N2-version 2.1) and SRa05 (pipeline ver.2.3, N2-ver.3.0) like e.g. B − V , one should use VizieR5 to get up-to-date which have erroneous coordinates in the FITS-headers, all measurements. other targets can be cross-matched using their coordinates, We are only discussing the reduction of the exoplanet- which originate from the USNO-B1 catalogue (Monet channel here since the requirements for the asteroseismol- et al. 2003) or PPMXL catalogue (R¨oser, Demleitner & ogy are very different to preserve the precious frequency in- Schilbach 2010). Errors in position of CoRoT targets should formation. However, most of the algorithms and filter tech- always be within one arcsecond. The user should keep in niques presented here could in principle also be applied on mind that the point-spread-function (PSF) is several arcsec- the asteroseismic-channel. More detailed information on the onds wide and that the variability might not originate from CoRoT’s seismology programme can be found in Michel et the CoRoT target, but a background star. A nice demonstra- al. (2006). tion of topic is given in the paper by Papar´oet al. (2011). The CoRoT observation started with the initial field The contamination factor from ExoDat or the FITS-header IRa01 (Carpano et al., 2009) in the galactic anti-center is a good proxy for the identification of diluting background direction towards the constellation Monoceros. The next targets in the PSF. Otherwise the WINDESCRIPTOR image pointing was a so-called short run SRc01 (Erikson et al., must be checked for other pointsources within the PSF. 2012) in the galactic center-direction between the constella- Details for some individual CoRoT runs can be found in tions Aquila and Ophiuchus. The two fields in the constel- Cabrera et al. (2009), Carone et al. (2012), Cavarroc et al, lations are called eyes of CoRoT and are necessary to avoid (2011) and Erikson et al. (2012). contamination by sunlight and the eclipse of the satellite by the earth (Baglin et al, 2000). Some areas within the field of view of CoRoT have been visited twice. The CoRoT obser- 2 The CoRoT N2 Data Product vation runs lasted between 20 days for the short ones up to 150 days for the long ones, which are listed in table 1. The The basis for this section is the technical description for detector E1 failed between the observation runs LRa02 and the N2 data product (Baudin et al., 2012). The lightcurves LRc03. (Moutou et al., 2013) for each run are provided as gzipped tar-archives contain- Each target is assigned a unique identification number, ing the FITS-files for each individual target. The archives the so-called CoRoTID. Additionally the targets can also are grouped by monochromatic-, chromatic-, asteroseismic- 5 http://vizier.u-strasbg.fr/viz-bin/VizieR and imagette-targets as well as their WINDESCRIPTOR-
Copyright line will be provided by the publisher AN header will be provided by the publisher 3
Table 2 Grid of different channels and modes The CoRoT colours are still reliable enough to identify mean values normal mode Imagette mode a blended binary (Carone et al., 2012) or a change in the LC MEAN WHITEFLUX WHITEFLUX IMAG stellar effective temperature, e.g. to differentiate between LC MEANR REDFLUX REDFLUX IMAG pulsation or rotation (Weingrill, 2011). The scientific use LC MEANG GREENFLUX GREENFLUX IMAG of CoRoT’s colors is still controversial (Borsa & Poretti, LC MEANB BLUEFLUX BLUEFLUX IMAG 2012; Auvergne et al., 2009). For each run the flux values in the three channels (REDFLUX, GREENFLUX, BBLUE- FLUX) can be transformed into CoRoT colors (RC, VC , files. The imagette-archives also contain their WINDE- BC ) using an idealised transformation matrix SCRIPTOR-files. The header keywords are subject to change in each new RC R0 r 0 0 − version of the N2-pipeline. The FITS-files generally follow VC = V0 2.512 log10 0 g 0 , (1) the standard described in Hanisch et al. (2001), but contain BC B0 0 0 b some non-standard values for the fields. Where some values where R, V , B are the respective magnitudes given in the are simply left empty like e.g. the VARCLAS cards, others FITS file, r, g, b are the mean flux values (LC MEANR, like unknown magnitudes are set with ’-99.0000’or set with LC MEANG and LC MEANB) and R0, V0, B0 are the non-standard values like ’null’ or ’NaN’ which are not al- magnitude zero points. This is of cause the ideal case, where ways understood by libraries used for reading the files. we assume that we have to deal with discrete filter bands. Since the color information is spread across the PSF, the 2.1 Epoch of measurements color channels are polluted. For the CoRoT run LRa01 as an example we obtain For high precision epoch determination the DATEHEL field in the FITS-file must be used. Each 512 second exposure RC 25.197 epoch must undergo a time-correction that is 224 seconds VC = 25.392 ′ − resulting from t = t + (256 32)/86400, where t is the BC 25.794 ′ original epoch in the file and t is the corrected epoch. For 0.984 −0.262 0.220 r alarm-mode candidates with mixed cadence, the 32 second − 2.512 log10 0.398 0.155 0.412 · g , cadence data must not be corrected, but the 512 second data 0.115 0.360 0.497 b must undergo this correction. Lightcurves only taken in 32 (2) seconds cadence mode are also exempt from this correction. DATEJD describes the CoRoT Julian day where day to get the CoRoT magnitudes RC , VC , BC. The transforma- zero is defined as 1 Jan 2000 12:00:00.0 equivalent to Ju- tion matrix in eqn. 2 demonstrates that most of the V flux is lian day 2451545.0 in the reference frame of the CoRoT distributed among the red and blue channels. The transfor- satellite (Auvergne et al., 2009). mation can be calculated for all runs, where the respective BVR-magnitudes are known. This excludes SRc02, SRa02 and LRc03 where the photometric data is incomplete. Other 2.2 Flux measurements runs like IRa01, SRc01, LRa04 and SRc03 give unrealistic CoRoT provides different products as shown in Table 2 de- results due to e.g. negative correlation between colors and pending on the target magnitude. Some bright stars have Johnson magnitudes. been observed in the so-called Imagette mode, which should For monochromatictargets the R magnitude matches the provide a high signal-to-noise ratio. In ‘CoRoT-terms’ the median flux value as shown in Figure 2. name Imagette also describes the aperture for the photom- The root-mean-square (rms) value given in the FITS- etry (Baudin et al., 2012; Drummond et al., 2006). Each header is a preliminary indicator for the variability of the aperture is divided in three sections for the blue, red and lightcurve and is mostly governedby photon noise. The rms green channel, representing the spectral output of the prism is not corrected for any instrumental trend in the lightcurve, mounted in front of the charge coupled devices (CCDs) so for example relativistic aberration amplifies the rms value (Rouan et al., 1999; Auvergne et al., 2009). There are artificially. Other sources that might affect this value are the 256 different templates for apertures in use since the PSF stellar activity, eclipse-signals and instrumental noise espe- varies along field of view (Barge et al., 2006). cially for faint objects. The typical noise characteristics can Usually the three colours should be at the same order of be seen in Figure 3, which compares the given rms of each magnitude. Spacecraft jitter and relativistic aberration might lightcurve(represented by a dot) between the first run IRa01 cause the flux to be shifted from one channelto another. The (Carpano et al., 2009) and LRa01 (Carone et al., 2012). flux distribution in the three different channels depends on The global rms value is different for each run and is af- the type of Imagette, position on the chip and the spectral fected by the ageing of the instrument (Moutou et al., 2013) type of the star (Auvergne et al., 2009). Several (SRa01, as well as other sources that affect the performance of the SRc01, SRa02 and SRc02) runs have rounded magnitudes CCDs, e.g. cosmic ray hits or changing detector temper- in their headers which badly correlate to the red flux. ature. The rms value given in Table 3 is governed by the
Copyright line will be provided by the publisher 4 J. Weingrill: CoRoT Data Reduction By Example
Table 3 This table shows the overall relative rms values taken from the N2 dataproduct for each run on each CCD. 16 The rms values were taken from monochromatictargets and averaged for each CCD and each run. The four runs LRc06, LRa04, SRc03 and LRc08 do not contain rms values in the 15 official dataproduct. start date run CCD rms 14 2007-02-03 13:05:53 IRa01 E1 0.0075 2007-02-06 13:35:47 IRa01 E2 0.0080 2007-04-13 18:00:30 SRc01 E1 0.0055 magnitude
C 13 2007-04-13 18:02:06 SRc01 E2 0.0053 R 2007-05-16 06:00:50 LRc01 E1 0.0126 2007-05-16 06:02:26 LRc01 E2 0.0133 12 2007-10-23 22:30:35 LRa01 E1 0.0152 2007-10-23 22:30:35 LRa01 E2 0.0196 2008-03-07 21:50:33 SRa01 E2 0.0079 11 2008-03-07 21:50:33 SRa01 E1 0.0111 11 12 13 14 15 16 2008-04-15 23:10:48 LRc02 E2 0.0204 R magnitude 2008-04-15 23:10:48 LRc02 E1 0.0186 2008-09-15 09:33:11 SRc02 E2 0.0415 2008-09-15 09:33:11 SRc02 E1 0.0063 Fig. 2 Each dot represents a chromatic target in the run 2008-10-11 14:30:35 SRa02 E2 0.0152 LRa01 with its given R magnitude versus CoRoT RC mag- 2008-10-11 14:30:35 SRa02 E1 0.0137 nitude. The linear correlation is evident. 2008-11-16 19:02:24 LRa02 E1 0.0126 2008-11-16 19:02:24 LRa02 E2 0.0132 2009-04-03 22:00:30 LRc03 E2 0.0175 0.02 2009-07-07 04:45:28 LRc04 E2 0.0099 2009-10-03 22:31:49 LRa03 E2 0.0172 2010-03-05 00:15:25 SRa03 E2 0.0074 2010-04-08 22:30:49 LRc05 E2 0.0098 2010-07-08 20:45:34 LRc06 E2 0.0114 2010-07-09 00:00:14 LRc06 E2 – 0.01 2010-09-29 14:00:53 LRa04 E2 – 2010-12-21 18:00:26 LRa05 E2 0.0154
rms [mag] rms 2011-04-08 14:15:49 LRc07 E2 0.0106 2011-07-01 18:30:50 SRc03 E2 – 2011-07-08 15:30:29 LRc08 E2 – 2011-07-08 15:38:29 LRc08 E2 0.0117 2011-10-07 00:10:47 SRa04 E2 0.0127 0.00 10 11 12 13 14 2011-12-01 18:15:27 SRa05 E2 0.0344 R [mag] 2012-01-12 18:30:55 LRa06 E2 0.0154
Fig. 3 Magnitude versus rms for each individual star in the initial run IRa01 (triangles) and the long run LRa01 sue then one might consider including flagged points where (squares). The photon noise limit is indicated by a dashed the lowest bit in the status flag is not set. This should in- line at the bottom. crease the numberof usable data to a maximumof 95% (see Figure 4). The usage of flagged data still might introduce spurious artefacts or frequencies. All non-zero status val- length of the run as well as by selection effects like the stel- ues indicate artificial changes of the flux mostly caused by lar population in the field, number of targets in the CCDs the satellite crossing the Southern Atlantic Anomaly (SAA). and the essential fraction of variable stars. Due to the orbit geometry of the CoRoT satellite this event To convert the rms flux to magnitude units one easily occurs quasi-periodic but is still obvious in the frequency calculates m = −2.512 log10(1 − r/f¯), where m is the analysis of most lightcurves as a period of 103 minutes variation in magnitudes, r is the rms of the flux and f¯is the (≃ 0.162 mHz or ≈ 13.98 cycles per day). mean flux. Usually the rms or the variation is calculated an Care must be taken for adjacent data points to marked basis of a given time-scale, like 5 hours. ones, since the flagging might not always be appropriate. All valid data points can be selected by taking the rows, In fact the flagging is only dependent on the longitude and where the STATUS flag is zero, which is usually more then latitude of the satellite regardless of the size of the SAA. 66% of the data. If the numberof data points is of critical is- Random electronic events that alter the flux on a region of
Copyright line will be provided by the publisher AN header will be provided by the publisher 5
CoRoTID 221629528 when fitting models to the lightcurve, since most of these 1.04 algorithms are based on matrix inversion techniques which then cause singular values. Depending on the further appli- 1.03 cation the data should be normalized by the median or the mean, which is also given in the FITS header as LC MEAN 1.02 or LC MEANR (see Table 2) for e.g. the red channel. 1.01 3.2 De-trending
norm. flux norm. 1.00 Almost all lightcurves suffer from a linear or polynomial 0.99 trend which is either a stellar phenomenon e.g. long term variability or caused by the relativistic aberration due to the 0.98 satellites orbit as it is co-moving with the earth around the 0.0 0.5 1.0 1.5 2.0 sun. The latter can be identified as it affects the color chan- time [days] nels differently and is usual evident in long runs as a sinu- Fig. 4 This exemplary lightcurve demonstrates the typical soid with a period of a sidereal year. On shorter runs this ef- distribution of data points with different flags. Valid data fect might not be visible or can be removedby the described points are shown with filled circles, flagged data with even polynomial. status (boxes) and odd ones (triangles). When applying a polynomial fit to the data for detrend- ing (e.g., De Medeiros et al., 2013 and references therein), the original measurement errors must not be taken into ac- the CCD or the whole CCD are not flagged and must be count. A better way would be fit with a smaller weight on detected and removed by the user (see Sec. 3.4 for details). outliers or an unweighted fit. This can be achieved in two The selection of valid data points can also be managed stages by fitting a polynomial with uniform measurement- by the user himself in principle. Taking into account, that all errors and afterwards taking the absolute difference between lightcurves are affected in the same way, the outliers can be the flux and the polynomial as weights for the second fit removed either by simple sigma clipping or by subtracting (Figure 5). a median trend (cf. Sec.3.2).