-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
See MOA or KMTNet brokers here: https://github.com/KKruszynska/fit_all_gsa/blob/main/module_gaia_xmatch.py#L67 |
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: 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. 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. |
@KKruszynska I noticed that your code queries the 2025 MOA pages using pandas, which is what I'm doing. 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. 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? |
MOA alerts for 2025 have moved URL to:
https://moaprime.massey.ac.nz/alerts/index/moa/2025
Update MOA broker accordingly
The text was updated successfully, but these errors were encountered: