Run_TAP breaks down during evaluating targets for interferometry

[KKruszynska]

Run TAP breaks down during interferometry evaluation, and priorities are not being stored.

[KKruszynska]

This message is present in the log. It seems that it's related to the GSC catalogue:

INTERFERO: Stored neighbouring star data in MOP
INTERFERO: Querying GSC catalog around event OGLE-2025-BLG-0001
runTAP: Cannot perform TAP for target OGLE-2025-BLG-0001
Exception: TypeError('expected str, bytes or os.PathLike object, not NoneType')

[KKruszynska]

Oddly enough, I don't get this bug on MOP local. I will check with the MOP dev.

[KKruszynska]

Okay, I think I understand. In Vizier, the utils cache is set to 'None', which I think is causing the issue. However, we have to find a good solution because the cache was set to None for a reason. For now, I added exception handling for interferometry evaluation.

@rachel3834 Let's have a look at this once we have a chat.

[rachel3834]

Ah, I had to fix this one for the MOA broker updates. The issue is that the Vizier query tool by default expects to use a cache on local disk. I've not found a way to make that work in the cloud so I had to switch it off. The syntax for doing so changed during a recent version update to astroquery tool. The fix to this issue is to comment out the Vizier.cache_location = None line and instead add an optional parameter to the query call - have a look at the MOA broker for examples of this.

…

On Sat, Apr 5, 2025, 8:00 AM Katarzyna Kruszynska ***@***.***> wrote: Okay, I think I understand. In Vizier, the utils cache is set to 'None', which I think is causing the issue. However, we have to find a good solution because the cache was set to None for a reason. For now, I added exception handling for interferometry evaluation. @rachel3834 <https://github.com/rachel3834> Let's have a look at this once we have a chat. — Reply to this email directly, view it on GitHub <#225 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPJA3H435VI4QPOMO4QYTL2X4FILAVCNFSM6AAAAAB2PTDH3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZHA3TGOBQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: KKruszynska]*KKruszynska* left a comment (LCOGT/mop#225) <#225 (comment)> Okay, I think I understand. In Vizier, the utils cache is set to 'None', which I think is causing the issue. However, we have to find a good solution because the cache was set to None for a reason. For now, I added exception handling for interferometry evaluation. @rachel3834 <https://github.com/rachel3834> Let's have a look at this once we have a chat. — Reply to this email directly, view it on GitHub <#225 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPJA3H435VI4QPOMO4QYTL2X4FILAVCNFSM6AAAAAB2PTDH3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZHA3TGOBQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>