Search results

Fixed! (2.44.6) Also, ICYMI, there's now a "Satellte Mode" under the Camera Menu that works a lot better when pointing the camera more straight up or down. Also, fixed that annoying judder when panning rotated camera.

There's a bit of an issue with labels in the look view, which might be confusing things. I will fix.

The stars are fine. The satellite is just a bit off. It's because it's a manually created TLE, made from visual observations. Based on that, the angular difference is perfectly acceptable.

It seems to be a query around the tile center, not stars. Vasco60 use the 90' as you have a default search_radius_arcmin: float = 90.0 in class SpikeConfig: and cli_pipeline.py:610 does not override it to 1.5

No, it's not. It's reducing the PS1 bright star fetch from 35' to 3.0' (which should actually be 45' to cover the 60x60' tile). The 90' is still there.

That's fixed in my version of the code, vasco/external_fetch_usnob_vizier.py Hunk 1 — default cap bumped: - row_limit: int = 20000, + row_limit: int = 200000...

But it seems in your code, the 5-arcsecond Gaia cone match is done before the PM back-propagation, and the back-propagation is then only applied to the sources that matched — i.e., the ones already eliminated as known Gaia stars. The sources that drifted more than 5″ from their Gaia J2016...

Your code also uses 90', is this to replicate their code? https://github.com/jannefi/vasco60/blob/5dbf452/vasco/mnras/spikes.py#L117 class SpikeConfig: rmag_key: str = "rMeanPSFMag" rules: List[Any] | None = None search_radius_arcmin: float = 90.0 rmag_max_catalog: float =...

My (computer-generated) notes so far.

I got some of the code running and experimented with visualizing the filtering. What the pipeline is doing is finding all the blobs of light in the planes, and then rejecting ones that are known stars or that don't look like points of light. The first step is filtering against the Gaia...

Better quality videos extracted from Instagram for analysis

What is this demonstrating? I find it difficult to see how a 3x3 region can have a radial profile that's valid past 2 pixels when there's something nearby. This diagram looks like you have a 21x21px region with two point sources, and you are taking the radial profile (i.e. the average...

Very interesting results. Seems like something that needs a response. If the original MNRAS 2022 is basically noise, then that has significant implications for the downstream papers that use that set as a starting point. I think it might benefit from a wider understanding if you could include...

I used Claude Code quite a bit here. Using my new MCP bridge it was able to control Sitrec, but it also just went ahead and wrote code using satellite.js to do its own propagation. But the thing that found the TLE was Grok.

https://www.satobs.org/seesat/Apr-2026/0032.html From: Kevin Fetter via Seesat-l <seesat-l_at_lists.seesatmail.org> Date: Tue, 7 Apr 2026 21:57:04 -0400 A fellow observer tipped me off, that a show would happen for me [image: ] So I aimed, and took it in [image: ] Passed near eta uma ( Alkaid )...

In Sitrec, there's an AI assistant you can bring up with the Tab key. https://www.metabunk.org/sitrec/?action=new

Bledsoe is now publishing AI "enhanced" version of his bokeh. It still appears to be the same thing. This is up close detail from my big camera recording in Raw data of an orb taken at my home in NC. Thanks to my friend Peter Osborne Truth in focus for doing the video enhancements. More...

Actually, that message means you are not logged into Metabunk on that browser window. Possibly, you were in an incognito/private window. Or had just logged out of Metabunk.

Probably. You can always try changing the agent in settings.

Try again, and then in the Help menu, click on "Export Debug Log", and then attach that here, or send it to me in a DM.