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.
>From: Bernard Mendiburu <address@hidden> >Organization: UCLA >Keywords: 200311250001.hAP01xEH008098 IDV timestamp Hi Bernard- >Just a simple question, with no coding included ;-) Well, unfortunately, the answer is not so simple. >Is it possible to use miliseconds-accurate time steps ? Sort of. >vis5D timesteps are only second-accurate. It's my understanding that Vis5D times are in seconds since 1900-01-00. If you put in a decimal value, does it not work? >NetCDF file handles miliseconds, isn't it ? Yes. The problem in the IDV is that the time formatter is set to only print out time as HH:MM:SS by default. You can have times that are in milliseconds, but the string representation will not show that. There is a way that you can change the default format programatically, but there is no interface into the IDV to allow the user to do this. I'll think about this a bit more to see what we can come up with. I just tried a test and was able to set the formatting so you could see milliseconds. Now, I just have to figure out how to bubble that up to the user and what ramifications that would have. BTW, I like the 3D images on your examples page. How did you create those? Don Murray