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

Home » Public Forums » archive » Strange floating-point precision behavior
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: Strange floating-point precision behavior [message #33993 is a reply to message #33926] Tue, 11 February 2003 09:49 Go to previous messageGo to previous message
tim is currently offline  tim
Messages: 9
Registered: July 1994
Junior Member
On Mon, 10 Feb 2003, James Kuyper wrote:

> Tim Lloyd wrote:
>>
>> I have written a routine that converts Earth-Centered Inertial
>> coordinates in x/y/z to geodetic latitude/longitude/altitude using the
>> WGS84 standard. I have one issue, however, that I believe is
>> affecting my calculations of altitude so that they are accurate only
>> to 1-meter resolution. I am defining the ECI coordinates as
>> double-precision:
>>
>> IDL> boulder={x:-1283388.8693d0, $
>> y:-4713016.9053d0, $
>> z:4090191.0471d0} ;Boulder, CO, GPS station
>
> Are you sure those are ECI coordinates? Interpreted as ECR
> (Earth-Centered Rotating) coordinates, they correspond pretty closely to
> Boulder CO. Interpreted as ECI coordinates, you'd need a fourth value,
> the precise time at which the conversion from ECI to ECR should occur.
> ECI and ECR coordinates match only once each day, so it would be quite a
> coincidence if those ECI coordinates happened to match the ECR
> coordinates for Boulder.

My bad, those are actually ECR. Guess I use too many TLA's to keep them
all straight.

>> and yet IDL seems to be storing the data incorrectly:
>>
>> IDL> print,boulder,format='(3f20.10)'
>> -1283388.8692999999 -4713016.9052999998 4090191.0471000001
> ...
>> What am I doing wrong? I am fairly certain that this behavior is
>> responsible for my calculations yielding 1674.6658 m as the altitude
>> of the Boulder GPS station, and not 1674.7428 m (the actual altitude).
>
> No, that isn't the cause of your problem. Floating point roundoff has
> introduced errors of only about 10^-10 meters into your calculations;
> that can't be the cause of a 0.123 meter error in the altitude. I have
> access to a C routine which performs this same conversion, and it
> produces the same result as your routine. Is it possible that it's not
> the routine that's at fault, but the data?

That's helpful, actually. Looks like I got a false positive on my
debugging. Time to dive back in...

Thanks,

Tim Lloyd, lloyd@lasp.colorado.edu
SNOE Mission Operations Lead Flight Controller
Laboratory for Atmospheric and Space Physics
"The eyes of the world now look into space, to the moon and to the
planets beyond, and we have vowed that we shall not see it governed
by a hostile flag of conquest, but by a banner of freedom and peace."
-- John F. Kennedy
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: drawing a single point in 3-D
Next Topic: License options when starting IDL

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

Current Time: Sun Oct 12 08:49:06 PDT 2025

Total time taken to generate the page: 1.36045 seconds