Conversation
GiZano
changed the title
GiZano
force-pushed
the
fix/v2.1.1-demo-endpoint
branch
from
September 12, 2026 14:46
1ee8f7f to
6a684c4
Compare
…tude This commit corrects the hardcoded Milan epicenter in the demo endpoint by fetching the zone's polygon centroid. It also fixes the calibration constant in the reverse-engineering mock from 160 to 1.6 to match the actual worker, changes default magnitude to 5.0 for plausibility, and rewrites Appendix A to document the full behavior.
GiZano
force-pushed
the
fix/v2.1.1-demo-endpoint
branch
3 times, most recently
from
September 12, 2026 16:26
bd6c7a2 to
51940b4
Compare
This commit bumps all reference to version v2.1.0 to v2.1.1 in documentation, code artifacts, and metadata. Also re-generated the whitepaper PDF.
GiZano
force-pushed
the
fix/v2.1.1-demo-endpoint
branch
from
September 12, 2026 16:32
51940b4 to
c6b989e
Compare
…ate to alerts log
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR finalizes the
v2.1.1release for QuakeGuard. It corrects critical bugs in the mock simulation endpoint (/demo/trigger-earthquake), synchronizes the documentation and whitepaper with these changes, adds Pisa to the Hollywood Simulator, and performs a complete repository-wide version bump to2.1.1in preparation for the final release tag.Changes Made
backend/src/main.py&backend/src/schemas.py: Fixed the/demo/trigger-earthquakeendpoint. Epicenter coordinates are now dynamically fetched from the zone's PostGIS centroid. The mock calibration coefficient was corrected from160to1.6to align with the actual worker logic. Default magnitude was lowered to 5.0 for realistic demonstrations.scripts/seed_world_zones.py&scripts/hollywood.py: Added Pisa to the Hollywood Demo orchestration environment.firmware/esp32_config.env: Set static GNSS fallback coordinates to Pisa for local video recordings.docs/whitepaper/16-appendix.typ&QuakeGuard_Technical_Report_v2.1.1.pdf: Rewrote Appendix A to fully document the cascade effect of the demo endpoint (DB inserts, AI Worker trigger, fake telemetry generation). Re-compiled the Typst whitepaper.2.1.0to2.1.1acrosspackage.json,.cff,.js,settings.tsx, OpenAPI docs, SVGs, andCHANGELOG.md. Also removed a ghost "Timeseries" roadmap item that was already completed in v1.2.1.backend/tests/unit/test_schemas.py: Fixed a failing unit test asserting the old7.5magnitude default. All 157 tests now pass.Impact & Next Steps
This ensures the QuakeGuard demo functionality is statistically robust, spatially accurate, and safely bounded for public exhibitions. It also guarantees a completely clean
v2.1.1release with no mismatched tags or documentation ghosts.Testing Performed
pytestsuite locally on backend (157 passed).cffi,paho-mqttundisturbed).main.typmanually to ensure PDF generation works with the new roadmap and versions.Related Issues
Closes QuakeGuard v2.1.1 hotfix sprint.