Generalized Robust MTL Semantics for Problems in Cardiac Electrophysiology

Loading...
Thumbnail Image

Embargo Date

Degree type

Discipline

Subject

CPS Medical
CPS Formal Methods
Biomedical
Computer Engineering
Electrical and Computer Engineering
Systems and Communications

Funder

Grant number

License

Copyright date

Distributor

Related resources

Author

Mangharam, Rahul

Contributor

Abstract

Robustness-Guided Falsification (RGF) is an efficient testing technique that tries to find a system execution that violates some formal specification, by minimizing the robustness of the specification over the set of initial conditions of the system. Robustness uses an underlying distance function on the space of system executions. As RGF is applied to new fields like medicine, it is essential to determine whether our distances still capture the domain expert’s intuition of which executions are similar and which are not. Motivated by the problem of testing the algorithms of cardiac defibrillators implanted in millions of patients worldwide, this work develops a (pseudo- )distance function, called conformance, over the space of cardiac signals. By using it to distinguish between fatal and non-fatal arrhythmias obtained from real patients, it is demonstrated that conformance measures the meaningful distance between cardiac signals much better than distances used in medical devices today. Next, conformance is used to re-define the robustness degrees of Metric Temporal Logic (MTL), and it is shown that conformance-based robust semantics of MTL can bound the (conformance-based) robustness degree, thus enabling a principled application of RGF to problems in the cardiac domain, using the appropriate distance notion. Using existing robust semantics based on sup norm can yield incorrect conclusions, with potentially severe consequences to patients.

Advisor

Date of presentation

2018-03-01

Conference name

Real-Time and Embedded Systems Lab (mLAB)

Conference dates

2023-05-17T20:22:54.000

Conference location

Date Range for Data Collection (Start Date)

Date Range for Data Collection (End Date)

Digital Object Identifier

Series name and number

Volume number

Issue number

Publisher

Publisher DOI

Journal Issues

Comments

Recommended citation

Collection