[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #9953] [octave forge] (mapping) angl2str
From: |
Philip Nienhuis |
Subject: |
[Octave-patch-tracker] [patch #9953] [octave forge] (mapping) angl2str |
Date: |
Thu, 16 Jul 2020 05:45:36 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #4, patch #9953 (project octave):
@Ricardo:
Now that I have temporary access to a real computer instead of a cell phone
(I'm away from home) I could have a better look.
Well, an impressive piece of work. I wish I had known earlier, could have
saved me quite some time :-)
You supplied a large amount of BIST tests as well, that's very much
appreciated.
The version currently in mapping returns cell arrays (with a reason BTW),
while Matlab returns char arrays (I think a sort of legacy issue there, it's a
very old function). Your version conforms to Matlab, which is preferable but
does not match what I needed angl2str for. But that's an easy fix.
Matlab also doesn't wrap degree values into the 0-360 (or -180 - 180 NS) range
(similarly for radians); a bit surprising IMO. ML help says "The purpose ...
suitable for map display" but I have never seen maps with degree values
outside those intervals (I'm a hydrogeologist and have seen quite a few maps
in my almost 40 years career).
These things + the Latex output could be catched using extra Octave-specific
options (along the lines of "compat" or even "traditional" or "braindead").
Let's discuss in early August how to proceed further.
Did you also start work on a str2angle.m version? (I mixed up the two in my
previous comment.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/patch/?9953>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/