octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59444] [octave forge] (mapping) missing refer


From: anonymous
Subject: [Octave-bug-tracker] [bug #59444] [octave forge] (mapping) missing referenceSphere function
Date: Sat, 14 Nov 2020 17:39:32 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #10, bug #59444 (project octave):

My thought referenceSphere uses the equal volume radius, as JWE noted there is
nothing stating this in the docs. Equal volume makes more sense in this case
than equal surface area.

I think the value does not have a lot of precision and they have not been
updated.
Something like this
https://nssdc.gsfc.nasa.gov/planetary/factsheet/jupiterfact.html
Where the value is in km, this would explain all numbers having three zeros
for meter units.

To look at the age https://en.wikipedia.org/wiki/Pluto#Mass_and_size

Philip notes 

Pluto 1151000


Would indicate the value came from somewhere between 1994-2010 (Maybe a
book?)
Since 2011 the radii size increased. The value for Octave's Pluto radius is
from the results after the New Horizon mission. 
It could be difficult to check against the values provided by matlab.
 

Since you are not worried about the class def part.
I could update the values supplied by JWE to use the equal volume radius from
my (not approved) rsphere code. 

Philip your thoughts?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59444>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]