question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Test failure in test_aa_high_precision()

See original GitHub issue

Description

This is in regards to issue #11527 and PR #11564. At first, I didn’t worry too much about the failure as the difference appeared to be small enough to be ascribed to the change in the handling of polar motion introduced in pyerfa 1.7.2. I calculate that differences due to this change should be less than 1 uas and the difference shown in issue #11547 is 8.63433769e-11 degrees or 0.31 uas, but then along came PR #11564 which is evidently showing the following differences:

Azimuth 19.62 uas
Elevation 0.85  uas
Distance 38.87 mm

These seemed excessively large to me, so I downloaded the latest version of SOFA and reran my test program. The results for the time used in the test are:

       Time            Azimuth         Elevation       Distance (m)    DUT1      Xp       Yp
2017-04-06 00:00:00 15.032673509956 50.303110133923 376252883.247239 0.4634343 0.009587 0.384603

Here I am including the EOP values to make sure that we are still on the same page in that regard. The differences between this and the previous version of SOFA that I used are:

Azimuth 0.252 uas
Elevation -0.018 uas
Distance  0.000 mm

Considering the apparent discrepancy, I think it would be worthwhile to revisit the entire 24 hour test. If someone could please run the following script and post the output here, I can take a look at this.

astropy_topo_test.py.txt

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:24 (20 by maintainers)

github_iconTop GitHub Comments

3reactions
saimncommented, May 5, 2021

Re-pkg_resources: we replaced it with importlib.metadata (#11091)

3reactions
brandon-rhodescommented, May 5, 2021

No problem, having the separate issue helps track the change. I’ve resolved it; __version__ should appear with the next release.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Testing Precision and Recall - LinkedIn
High precision tests yield consistent results and identify exactly what failed, but they are going to miss every failure they were not ...
Read more >
Cognitive Tests and Performance Validity Tests - NCBI
Certainly, PVT “failure” does not equate to malingering or lack of disability. However, clear PVT failures make the validity of the remainder of...
Read more >
Streamline Test Failure Analysis for Quality Engineering Teams
Test failure analysis zooms in on failed tests and automated test troubleshooting. Read on to see how Katalon makes root cause analysis insightful...
Read more >
Why did my test fail? - Testim overview
After running a test, you may find that the test fails and Testim displays an error message with some details about the failure....
Read more >
How Accurate Are At-Home Covid Tests? Here's a Quick Guide
Here's a Quick Guide. When used correctly, many rapid antigen tests are good at detecting people carrying high levels of the virus.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found