AI & ML
AMISS: An Integrity Framework for Magnetic Navigation
arXiv cs.SY0 views
arXiv:2611.24893v1 Announce Type: new Abstract: Magnetic Navigation (MagNav) is a promising alternative to traditional systems like Global Navigation Satellite Systems (GNSS), offering resistance to jamming or spoofing attacks to which the latter are vulnerable. MagNav matches scalar magnetic measurements over time against a known map of Earth's magnetic anomaly in order to position a vehicle. MagNav is therefore sensitive to the quality of these maps, especially to errors in the survey data that the maps are derived from. In order to be a reliable and mature navigation technology, MagNav must satisfy integrity requirements for mitigation of such faults. To this end, a solution-separation monitoring algorithm is developed that performs a role equivalent to Advanced Receiver Autonomous Integrity Monitoring (ARAIM) in GNSS, which detects faults as well as generates worst-case bounds (protection levels) on estimation error for faults too small to be detected. It is shown how these integrity methods can be developed in a \emph{windowed-in-time} sense, where subsets of measurements over a time window are compared with each other in order to detect outliers that can potentially result from errors in the map. The applicability of the approach is demonstrated using results obtained using synthetic aircraft data with injected faults.
Source:https://arxiv.org/abs/2611.24893PreviousHierarchical Traffic Engineering for Scalable Software-Defined Satellite NetworksNextChebyshev Polynomial Zonotope Abstractions for Certified Reachability of Learning-Enabled Systems
Related posts
How to detect user frustration in chatbot conversations
0dev.to
Mình Đã Biến Gemini Thành Trợ Lý Cá Nhân Như Thế Nào (Lịch, Drive, Gmail và Những Lần Suýt Toang)
0dev.to
Im looking fr any free ai models / tools are there?, leaVE UR Lights💡
0dev.to
I checked 10 SEO agency websites for AI-search readiness. The real bugs were the boring ones.
0dev.to

How much GPU memory does an LLM need? The whole sum, worked out on real cards
0dev.to

Routing Upscaling Jobs by Output Size, Not Input Size
0dev.to