Hi, I am trying to set up a watchlist for Milky Way globular clusters, however, when I hit ‘Rerun watchlist’, I get ’ 504 Gateway Time-out’ error. I investigated the issue a little bit - it seems like it works all right with a very few number of objects in the list (~5), but as I add more sources, the error starts to appear. At the same time, I have another watchlist with a large number of objects that works all right. The issue may be because of the crossmatch time due to the the large association radii - the problematic watchlist has radii of hundreds arcsecs, and the watchlist that works all right has much smaller radii. But it’s just my hypothesis.
Can you please have a look at it? The Watchlist ids for investigation are 2306 (full list of sources) and 2336 (small sample).
Hi Alex
Let me do a few more tests. But my first thought is that globular clusters are all different sizes, and you would do better to specify a radius for each one. A single maximum radius will find a lot of false positives. So your file would have lines like RA | Dec | ID | radius. This individual radius overrides the single radius for the whole watchlist.
Another way to do it would be a watchmap (MOC file) instead of a watchlist, as we discussed before.
Can I do a few experiments? I will use your file here, is that right? Is ang_size_mass_3 the radius in arcsec?
Roy
Hi Roy,
well, yes, I used custom sizes for each source, I just meant that they are all on a scale 100-1000 arcsec, not something small.
ang_size_mass_3 is in arcsec, yes. Feel free to play around with it, of course.