vatsal.j3

Alright last devlog….phew. Right so first thing first the project has been left incomplete,because i simply didnt have enough time during submission. So what all have i left? Ive left out 2-3 things in the physics field, and also i wanna create a whole website for this project that actually makes it easier for the public to see and understand particle physics, but ig for now shipping as python cli package is the way to go. My first public project ever, should be good, fingers crossed.

Ive added stuff like mostly recursive decay login and helicity and 1 other decay in these few hours. While also prepping for shipping. As well ass auto decay detection to generate appropriate graphs.

Built the full detection pipeline for groundshift today
satellite imagery goes in, anomaly alerts come out.

what shipped:
→ preprocessing pipeline cloud masking, co-registration,
Z-score normalisation
→ NDVI-based change detector computes per-pixel change
scores between two satellite scenes
→ alerting layer; converts change scores to GeoJSON polygons,
fires webhooks when anomalies exceed threshold
→ 24 tests, all passing

the interesting bit: groundshift doesn’t just flag change
it scores how anomalous that change is against the historical
seasonal baseline for that exact location. a field turning
brown in october is normal. the same field in april is an alert.

next up: building the UI–> a full geospatial intelligence
dashboard. dark map, live anomaly overlays, alert feed.
think mission control, not a settings page.

Started building groundshift — an open source Python framework
for satellite change detection. The idea: point it at any polygon
on Earth, get alerted when something changes. Deforestation,
floods, conflict damage — all from free ESA Sentinel satellite data.

Day 1: built the full ingestion and preprocessing pipeline from
scratch. Sentinel-2 scenes now download automatically from the
Copernicus archive, get cloud masked, co-registered, and
normalised. 13 tests passing. Detection layer (NDVI-based change
scoring) is next.

WOAHHH, ok so cool its been a while. Plenty of work has been done. Ran my first 3 body decay, generated a few graphs, made my event time lesser, added support for N-Body decay, worked on an accept-reject mechanism to improve efficiency, added code for unweighted events and matrix element based physics. Project is now ready for more advanced and probably close to the end of the advanced physics
Also i kinda realized, ColliderX dosent suit, cause like im doing mainly decays. Any naming ideas in the comments would be cool.

PFA: There’s a few cool looking graph related to a muon decay that ive been able to generate to confirm if the reactions are actually physically valid or not.

Right so far ive built a basic physics event/decay generator, using some momentum conservation, kinematics and other rules and laws, blah blah. Ive also started recording events and storing them in my db tables. Right now i have to fix some basic physics and computational issues before i move on to avoid conflict. After that i can move on to enhancing my physics engine and algorithm to improve the project. Soon enough ill have to start the front end work as well.
Ive attached a picture of a snippet o