Issue |
A&A
Volume 597, January 2017
|
|
---|---|---|
Article Number | C2 | |
Number of page(s) | 1 | |
Section | Numerical methods and codes | |
DOI | https://doi.org/10.1051/0004-6361/201220860e | |
Published online | 05 January 2017 |
Optimizing the search for transiting planets in long time series (Corrigendum)
Institut für Astrophysik, Georg-August-Universität, Friedrich-Hund-Platz 1, 37077 Göttingen, Germany
e-mail: avivofir@astro.physik.uni-goettingen.de
Key words: methods: data analysis / planets and satellites: detection / planetary systems / errata, addenda
1. Processing groups of stars
In the computer code accompanying the paper Ofir (2014), a single line of code was erroneously omitted, allowing the mixing of the first star’s result with the other stars’ results. By adding the following line as the penultimate line of the main loop:
ind=sub2ind(size(mtr),ind,1:numel(ind));
the code is made correct for groups of stars as well, as indeed discussed in the paper. We note that the paper itself does not need any corrections regarding this matter, and that already the old code behaved correctly when applied to one light curve at a time.
2. Counting configurations
Section 4.2 described the optimal search grid in terms of MinBin and NumBins, which are defined to be the number of bins
resolving the smallest and largest expected transits. The formula for NumBins (Eq. (11)) is thus missing a MinBin factor and should be replaced with:(11)correcting Eq. (11) does not change the speedup factor or any other equation or conclusion in the paper other than Eq. (11).
Acknowledgments
I wish to thank the careful reader, who declined to be named, and Geert Jan Talens for identifying the above errors.
References
- Ofir, A. 2014, A&A, 561, A138 [NASA ADS] [CrossRef] [EDP Sciences] [Google Scholar]
© ESO, 2017
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.