comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Error in function js2ymds (JHU/APL/S1R IDL Lib)?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Error in function js2ymds (JHU/APL/S1R IDL Lib)? [message #26717 is a reply to message #26584] Fri, 14 September 2001 00:34 Go to previous messageGo to previous message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
Harald Giese wrote:
>
> Olaf Stetzer wrote:
>> ...
>> It seems that in the MS-year 1900 has 1 more day
>> compared to the one calculated by js2ymds!! I don't
>> know if the fault is in Microsoft Excel or in the
>> function js2ymds but maybe in 1900 there was an
>> extra switching day (german: Schalttag) which is
>> not calculated in the function?
>
> Hi Olaf,
>
> MS-Excel has indeed two peculiarities (at least):
>
> 1. it counts the 01.01.1900 00:00 as Julian day 1.0 (where most of us
> would expect 0.0)
> 2. it has a "29.02.1900" - though 1900 was definitely not a leap year
>
> Happy coding!
>
> Regards,
> Harald


I have seen this problems by storing data with labview too. It seems to
me
that it comes from the Microft Windows.

I haven't tried to program a fix around this, because our exchange
format
from Labview to IDL is an ASCII file format named ENZ.

In this file format we are able to set a start date then only seconds of
day
have to be stored. Later on the read_enz() routine translates the date
seconds
information correctly in julian seconds. Result is the ICG data
structure.

Some more words about ENZ.
Normally data is a bit more as only values.
You like to know the units, the long name (for printouts), the missing
value,
the short name of the data probably a scaling factor or an offset
as well as who did the experiment and why and where
and which resources are used and some more.
Our data is always described in the data files.
This information is defined as GLOBAL comments and PARAMETER comments.
HDF, netCDF handles this informtion the same way.
ENZ is specially for vector data and we are using it for Experiments if
we like or need ASCII data for exchange.



regards

Reimar

--
Reimar Bauer

Institut fuer Stratosphaerische Chemie (ICG-1)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
http://www.fz-juelich.de/icg/icg1/
============================================================ ======
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml

http://www.fz-juelich.de/zb/text/publikation/juel3786.html
============================================================ ======

read something about linux / windows
http://www.suse.de/de/news/hotnews/MS.html
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Multi-threaded IDL
Next Topic: phase unwrapping

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 00:53:56 PDT 2025

Total time taken to generate the page: 1.01071 seconds