Fixing out of date TAI UTC tables (missing information on leap seconds): Difference between revisions
No edit summary |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 2: | Line 2: | ||
<pre style="background-color: #fffacd;"> | <pre style="background-color: #fffacd;"> | ||
SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307Leap second table TAI_UTC seems out-of-date. | |||
SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307)+ Until table is updated (see aips++ manager) times and coordinates | |||
SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307)+ derived from UTC could be wrong by 1s or more. | |||
</ | </pre> | ||
Leap seconds are inserted when needed by the Bureau International de l'Heure (BIH) based on geodetic data. Usually missing info on this is benign as leap seconds are only sparsely added or subtracted from the time. Even if they do, your typical dataset would not be affected by much, remember that your typical averaging time of visibilities llikely exceeds that second (the impact can be more important for VLBI, high time resolution or extremely precise spectroscopic data). | Leap seconds are inserted when needed by the Bureau International de l'Heure (BIH) based on geodetic data. Usually missing info on this is benign as leap seconds are only sparsely added or subtracted from the time. Even if they do, your typical dataset would not be affected by much, remember that your typical averaging time of visibilities llikely exceeds that second (the impact can be more important for VLBI, high time resolution or extremely precise spectroscopic data). | ||
Line 11: | Line 11: | ||
You can update the latest leap second information into CASA by the following shell command. The [casa directory] is the place where you have CASA installed. | You can update the latest leap second information into CASA by the following shell command. The [casa directory] is the place where you have CASA installed. | ||
<source lang='bash'> | |||
# in a terminal | |||
cd [casa directory]/data | cd [casa directory]/data | ||
rsync -avz rsync.aoc.nrao.edu::casadata . | rsync -avz rsync.aoc.nrao.edu::casadata . | ||
</source> |
Revision as of 19:55, 24 November 2010
If your CASA installation is a bit older, it may happen that upon starting CASA the system complains about missing leap second information for TAI_UTC. Messages like:
SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307Leap second table TAI_UTC seems out-of-date. SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307)+ Until table is updated (see aips++ manager) times and coordinates SEVERE gaincal::MeasTable::dUTC(Double) (file measures/Measures/MeasTable.cc, line 6307)+ derived from UTC could be wrong by 1s or more.
Leap seconds are inserted when needed by the Bureau International de l'Heure (BIH) based on geodetic data. Usually missing info on this is benign as leap seconds are only sparsely added or subtracted from the time. Even if they do, your typical dataset would not be affected by much, remember that your typical averaging time of visibilities llikely exceeds that second (the impact can be more important for VLBI, high time resolution or extremely precise spectroscopic data).
You can update the latest leap second information into CASA by the following shell command. The [casa directory] is the place where you have CASA installed.
# in a terminal
cd [casa directory]/data
rsync -avz rsync.aoc.nrao.edu::casadata .