Re: [Visualpython-users] gcurve issue in VPython 3.2.11

[P H B. <P.H...@bh...>]

You do not say what units you are using.

When doing problems of this sort it is sometimes helpful to use "normalised"
units, so as to keep the numbers manageable, and not to have too many powers
of 10 floating around.

For example, when dealing with the motion of planets in the solar system, I
use astronomical units for distance and years for time and the solar mass as
the unit of mass rather than SI units.

Regards

Peter



In message <47B...@ma...>
          Matthew Kohlmyer <mko...@ma...> wrote:

> Is it the case that gcurve in VPython 3.2.11 cannot deal with a number 
> greater than approximately 3e38?  I was writing a program that plots the 
> kinetic and potential energies of a binary star system and found that 
> the energy plots on the graph blew up when they reached this value. 
> I've tried it on two different computers and saw the same thing, so I 
> don't think it's a graphics driver issue.  I did not have this problem 
> on a computer running 4.beta26.
> 
> One of our TAs pointed out that this might have something to do with 
> handling 128 bit numbers--in fact, 2^128 = 3.4e38.  Is there a connection?
> 
> If this is the case, why does gvbars have no problems with such large 
> numbers?
> 
> Sorry if I'm rehashing a previously discussed issue.
> 
> Matt
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users


-- 

Peter Borcherds		|<mailto:P.H...@bh...>
			|phone 	0044 (0)121 475 3029