[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[UDUNITS #FQG-435699]: Problem with ut_decode_time

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [UDUNITS #FQG-435699]: Problem with ut_decode_time
  • Date: Tue, 09 May 2017 14:40:14 -0600
Molly,

> I have a problem with ut_decode_time returning 60 seconds instead of 0
> seconds and Minutes+1.
> 
> I see on the github change log that this was fixed in version 2.2.24,
...

The problem with ut_decode_time() returning 60 seconds should have been
fixed in version 2.1.24 (rather than 2.2.24). Version 2.2.24 has a fix for
ut_calendar() (rather than ud_decode_time()).

What version are you using?

Is the problem with ut_decode_time() or ut_calendar()?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FQG-435699
Department: Support UDUNITS
Priority: Urgent
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.