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.
Dave, I'm working on it. Unfortunately, I've been sidetracked by a need to revamp the UDUNITS continuous- integration pipeline. > The following problem in utCalendar was reported for Udunits versions > 2.1.19 and 2.1.20. The function outputs 59 minutes, 60.000 seconds, etc. > when I expect an even hour result at 0 minutes 0 seconds. Udunits-1 gave > the expected results. > > See attached short test program. Note that I am using the Udunits-1 API so > that the identical program may be tested with either Udunits-1 or Udunits-2. > > Can you please fix this problem so that Udunits-2 will always round off to > keep seconds in the 0-59.999 range? Thank you. > > linux64:~/udunits/ctest 278> gcc -g test3.udunits.c -ludunits -lm > linux64:~/udunits/ctest 279> ./a.out > Input time value: 876595 (double) > Input unit string: hours since 1901-01-01 00:00:00 > Decoded date and time: 2000-12-31 19:00:0 UTC > > linux64:~/udunits/ctest 280> gcc -g test3.udunits.c -ludunits2 > linux64:~/udunits/ctest 281> ./a.out > Input time value: 876595 (double) > Input unit string: hours since 1901-01-01 00:00:00 > Decoded date and time: 2000-12-31 18:59:60 UTC Regards, Steve Emmerson Ticket Details =================== Ticket ID: AGR-867317 Department: Support UDUNITS Priority: Critical 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.