1/12/2017: CDF version V3.6.3.1 is
released. This release, with a minor change to the earlier release of V3.6.3.0,
includes a new leap second added for 1/1/2017. Please read the change
note that describes the changes made in
this release, as well as all previous releases.
We have received questions about users getting warnings of incorrect
CDF_TIME_TT2000 times in CDFs
written with an out-dated leap second table. Previous CDF versions, till
3.6.3.0, leave the CDF header for the
leap-second-last-updated field to the value inserted when the CDF was
created. It turns out that this is a problem when adding additional data or
when copying an empty (master) CDF for filling with data, since the resulting
CDF carries the initial, out-dated leap-second-last-updated header and will cause
warnings when opening the CDF by the newer CDF version with a newly added leap
second. We have addressed this issue in this version, which will automatically
update this header to the newest leap second date, if there is a new
leap second added, when writing/updating TT2000 data to the CDFs.
You can check the leap-second-last-updated header in your master file by running
cdfdump tool command and searching for LeapSecondLastUpdated
field:
cdfdump -dump metadata <CDF master>
In case you need to update this header to the latest leap second date,
cdfconvert tool command can do that: