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

[Philip Nienhuis]

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

@Anonymous:
referenceSphere.m is about complete. It's here in the bug tracker because it
started as a feature request from someone. The patch tracker isn't meant for
that.

The radius values come from the output of Matlab itself, r2014 and r2020b, w/o
special formatting.
I'm not the one to decide on why some particular radius value is best; it all
depends on what it's needed for. All I know is that we have always been
striving, and succeeded, to mimic Matlab's output as much as possible,
supposedly because that seems to be one of the critical success factors for
accepting Octave.
As a spherical shape is a simplification for most celestial bodies anyway I
don't think these rounded values will do much harm. When using
referenceEllipsoid.m with an inverse flattening of Inf one gets radii that are
probably betterin the sense of "more natural". Even then there is (at least
for Earth) a choice of some dozens of reference radii all depending on the
chosen reference ellipsoid :-)

BTW classdef would be nice, but we would need to rewrite almost all mapping
functions for classdef which might be a lot of work. As I wrote in comment #3
there's another obstacle (classdef I/O). So for the foreseeable time we'll
make do with "classic" objects.

Good to hear you're working on rsphere. Please put your implementation up on
the patch tracker when it's ready :-)
Thanks


    _______________________________________________________

Reply to this item at:

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

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