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

"Server Error 500" from Similarity Search #20

Open
GNiklasch opened this issue Jan 3, 2020 · 2 comments
Open

"Server Error 500" from Similarity Search #20

GNiklasch opened this issue Jan 3, 2020 · 2 comments

Comments

@GNiklasch
Copy link

After some trial and error, I believe I've identified a scenario which reproducibly causes the Similarity Search tool to respond with a "Server Error 500". This particular failure mode appears to happen only when the subject of interest has identical duplicates.

For example, Gravity Spy Subjects 37105179, 37107088, 37109656, 37111837 are four identical copies of one and the same glitch event. In the search form at https://gravityspytools.ciera.northwestern.edu/search/ , enter the following:
Database: Multiview Model (default)
How many similar... return? 1
This is the Zooniverse... 37109656
The gravityspy uniqueid ... (blank)
Ifo: H1
Era: ALL (default)
Then Execute Similarity Search; the error will appear after a few seconds.

This example also fails in the same way when you ask the tool to return 2 images.
It works fine when you ask it to return 3 or 4 or more images (which provides a workaround).

Background: I fairly often use this tool asking for a small number of results just because, when it works, it is the quickest way to extract a peak frequency, or to get an idea of the UTC timestamp of the event - quicker than creating a short-lived single-subject ad hoc collection and using the Display Your Collection With Metadata Info tool.

Cheers, Gerhard (ZngabitanT)

@GNiklasch
Copy link
Author

This appears to have been fixed (thanks!) - I can no longer reproduce this failure mode.

@GNiklasch
Copy link
Author

Eating my words: There are still cases where asking for 1 results results in a 500 response status when the subject is one of a pair of identical duplicates; while asking for more than 1 result succeeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant