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

Update URL for MOA alerts in 2025 #218

Open
rachel3834 opened this issue Apr 2, 2025 · 3 comments
Open

Update URL for MOA alerts in 2025 #218

rachel3834 opened this issue Apr 2, 2025 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@rachel3834
Copy link
Contributor

MOA alerts for 2025 have moved URL to:
https://moaprime.massey.ac.nz/alerts/index/moa/2025
Update MOA broker accordingly

@rachel3834 rachel3834 added this to the MOP v6.0 milestone Apr 2, 2025
@rachel3834 rachel3834 self-assigned this Apr 2, 2025
@rachel3834 rachel3834 added the enhancement New feature or request label Apr 2, 2025
@rachel3834 rachel3834 moved this to Triage in MOP Development Apr 2, 2025
@rachel3834 rachel3834 moved this from Triage to Backlog in MOP Development Apr 2, 2025
@KKruszynska
Copy link
Collaborator

@rachel3834
Copy link
Contributor Author

The formatting of MOA's alert tables for 2025 have changed considerable. While I've written code to parse the new format of event index, it no longer contains the MOA internal ID for the event. This is needed in order to build the URL for the event's photometry file, e.g. for MOA-2025-BLG-0001:
https://moaprime.massey.ac.nz/alerts/datafile/MOA/gb1-R-3-34830/phot

The internal ID can be found on the event's detail page, but in the process of testing a harvester to this effect, I discovered that none of the URLs on the new server are accessible to programmatic requests.
Queries raise the error:
SSLError: HTTPSConnectionPool(host='moaprime.massey.ac.nz', port=443): Max retries exceeded with url: /alerts/index/moa/2025 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')))

Similar queries to the old MOA URLs (e.g. https://www.massey.ac.nz/~iabond/moa/alert2024/index.dat) still work, as do queries to other URLs.

The next step is to ask Ian Bond as the MOA developer about the SSL certificate for this site.

@rachel3834
Copy link
Contributor Author

rachel3834 commented Apr 7, 2025

@KKruszynska I noticed that your code queries the 2025 MOA pages using pandas, which is what I'm doing.
I found I needed to add the parameter "flavor ='html5lib'" to the read_html. However, I still get the SSL certification error using requests and pandas.read_html when I attempt to load the website
https://moaprime.massey.ac.nz/alerts/index/moa/2025

The same code works fine when I try to load LCO's own website, so its not my environment as far as I can tell.
I've even tried downloading the SSL certificate via the browser and this doesn't work either.

The issue may be related to my using a public wifi network, so it would be interesting to know whether I can continue to test this branch while I'm on this network. Can you use either requests or pandas to programmatically access the URL above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants