Skip to content

Releases: geospace-code/matmap3d

*ECI* functions: higher accuracy

06 Jul 20:55
14e4f0c
Compare
Choose a tag to compare

Enabled much better accuracy for ECI functions by using Vallado and other methods accounting for nutation etc.

Interfaces for eci2ecef() and ecef2eci() are similar to Matlab now. Other functions interfaces are unchanged.

correct ecef2ned: Add missing namespace

26 Jun 18:15
3a2a485
Compare
Choose a tag to compare

Thanks @MartinKoch123

also various lint, CI fixes over time.

deduplicate validations

26 Oct 20:21
795ee58
Compare
Choose a tag to compare

add lint test

21 Oct 09:45
8960007
Compare
Choose a tag to compare
v3.0.3

add lint test

CI: use function-based tests

12 Oct 04:56
985480c
Compare
Choose a tag to compare

improve flexibility and control of tests by using function-based tests instead of script-based

CI: add Matlab Travis-CI

07 Oct 01:27
2b10df5
Compare
Choose a tag to compare

Use the new Focal (Ubuntu 20.04) Travis-CI image with Matlab on Travis-CI

use R2019b argument validation

02 Sep 22:29
9b94342
Compare
Choose a tag to compare

Help ensure better correctness and error feedback by using Matlab R2019b argument validation

Use datetime() for robustness

27 Aug 03:10
addbf28
Compare
Choose a tag to compare

Use datetime class for robustness. GNU Octave users can use Tablicious for datetime.

use as package to control scope

14 Aug 15:30
d669d06
Compare
Choose a tag to compare

Since the function names overlap with Matlab Mapping Toolbox and other user-created functions, using matmap3d as a package helps ensure you're in the desired namespace.
The top-level matmap3d/ must be on Matlab path, and then:

import matmap3d.*

and/or

matlab.geodetic2ecef(..)

bugfix: eci2ecef, ecef2eci non-scalar

29 Jul 16:40
3510ebd
Compare
Choose a tag to compare

Thanks @brethvoice for pointing out that ecef2eci and eci2ecef didn't work for non-scalar inputs.