Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENH: Add Coordinate transformations from pysat #6

Merged
merged 60 commits into from
Aug 17, 2020
Merged

ENH: Add Coordinate transformations from pysat #6

merged 60 commits into from
Aug 17, 2020

Conversation

jklenzing
Copy link
Member

@jklenzing jklenzing commented Jul 3, 2020

Addresses #7

Adds coordinate routines related to JRO from pysat. Includes pysat history for contribution credit.

Also adds a changelog

Copy link
Member

@aburrell aburrell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style comments for cleaning up and parametrizing unit tests.

pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
aburrell and others added 3 commits July 13, 2020 10:54
Fixed downstream use of `coords` to use local coordinate routine.  Also fixed
import order.
@jklenzing
Copy link
Member Author

Pushed proposed structural changes for the geodetic to geocentric tests. If we are fully embracing parametrize, then the setup teardown class structure isn't needed.

@jklenzing jklenzing marked this pull request as draft July 23, 2020 16:02
@jklenzing
Copy link
Member Author

Marking as draft until group discussion on test styles for path forward

@jklenzing
Copy link
Member Author

Notes for moving forward:

  • Use hybrid approach for class / parametrize
  • always include setup and teardown, even if blank
  • test default options first, then kwargs in parametrize

@jklenzing jklenzing linked an issue Aug 15, 2020 that may be closed by this pull request
@jklenzing
Copy link
Member Author

failures due to changing pysat standards. Fixed in #15

@jklenzing
Copy link
Member Author

Rewrite based on 8/12 discussion ready for review

@jklenzing jklenzing marked this pull request as ready for review August 15, 2020 23:48
Copy link
Member

@aburrell aburrell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestions applied to unit tests can be used in other unit test classes in the same file, reducing the number of lines.

import numpy as np

from pysatMadrigal.instruments.methods import madrigal as mad_meth
from pysat.instruments.methods import general as mm_gen
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
from pysat.instruments.methods import general as mm_gen
from pysat.instruments.methods import general as ps_gen

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With appropriate changes made below.

pysatMadrigal/tests/test_utils_coords.py Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
pysatMadrigal/tests/test_utils_coords.py Outdated Show resolved Hide resolved
jklenzing and others added 3 commits August 17, 2020 09:30
@jklenzing
Copy link
Member Author

Thanks for the suggestions! It's a lot cleaner now.

Copy link
Member

@aburrell aburrell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! It's a lot easier for me to read now.

@jklenzing jklenzing merged commit e250c86 into develop Aug 17, 2020
@jklenzing jklenzing deleted the coords branch August 17, 2020 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Geographic and Geodetic Coordinates
3 participants