Skip to content

Commit 6181a55

Browse files
committed
✅ Fix test_pi_men
1 parent b5c3576 commit 6181a55

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

tests/test_locate.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,6 @@
1414
from tess_locator import locate, SECTORS
1515

1616

17-
@pytest.mark.xfail # TessCut currently claims Pi Men was in Sector 35 (whereas it was just off edge)
1817
def test_pi_men():
1918
"""Tests `locate()` against `astroquery.mast.Tesscut.get_sectors()`"""
2019
# Query using Tesscut
@@ -25,6 +24,9 @@ def test_pi_men():
2524
# Do the sector, camera, and ccd numbers all match?
2625
our_result_df = our_result.to_pandas().reset_index()[["sector", "camera", "ccd"]]
2726
mast_result_df = mast_result.to_pandas().reset_index()[["sector", "camera", "ccd"]]
27+
# Hack: MAST incorrectly returns Pi Men as having been observed in Sector 35, while in
28+
# reality it is just off the science area of the CCD, so we ignore the row for Sector 35.
29+
mast_result_df = mast_result_df.query("sector != 35").reset_index(drop=True)
2830
# Note: MAST may have less results because it only reports archived data
2931
assert our_result_df.iloc[0 : len(mast_result_df)].equals(mast_result_df)
3032
# Can we search by passing a string instead of the coordinates?

0 commit comments

Comments
 (0)