-
Notifications
You must be signed in to change notification settings - Fork 67
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
Properly address units in PintPulsar position #370
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #370 +/- ##
==========================================
- Coverage 88.44% 88.37% -0.07%
==========================================
Files 13 13
Lines 3037 3036 -1
==========================================
- Hits 2686 2683 -3
- Misses 351 353 +2
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Note that the lines not covered by tests were already not covered. I think it's actually worthwhile to include a NG 5yr dataset (say, B1855+09) in the test data (under tests/data/), so we can load a quick PINT pulsar with RAJ/DECJ parameters and also run those tests. PINT also includes that pulsar in its test data. Having a pulsar with RAJ/DECJ that is not 1713 is useful to have for other unit tests that still need to be implemented as wel. Right now we only have 1713.Sep.T2.par/tim |
Also note that the designmatrix and model parameter units are not addressed by this PR. That is a separate issue that should be addressed in a more comprehensive PR |
This one depends on #382 for the added test to pass. So @tcromartie, this last test I added was missing (uncovered lines). If it had been there from the start, your PR #382 would have never been happening. Other than that, this PR is ready |
This fixes #363
By using astropy.units to convert to units.rad, it doesn't matter what units PINT returns, the position is read in radians.