Opened 16 years ago

Last modified 16 years ago

#156 closed bug

time_code overflow — at Initial Version

Reported by: kate Owned by: arango
Priority: minor Milestone: Release ROMS/TOMS 3.2
Component: Nonlinear Version: 3.2
Keywords: Cc:

Description

Looking at what happens in time_string, the first thing is int(time) returning 0x80000000 or MIN_INT, being some huge negative number. My time is the number of seconds since the time origin of 1900, with years ranging from the 1950's to the present. The upshot is that all my time_codes end up being t = * ::

Change History (1)

by kate, 16 years ago

Attachment: patch.get_date added

patch

Note: See TracTickets for help on using tickets.