Papers › Multi-Task Temporal Shift Attention Networks for On-Device Contactless Vitals Measurement

Multi-Task Temporal Shift Attention Networks for On-Device Contactless Vitals Measurement

6 Jun 2020NeurIPS 2020 12arXiv:2006.03790archive 2025-07-28

Xin Liu, Josh Fromm, Shwetak Patel, Daniel McDuff

Telehealth and remote health monitoring have become increasingly important during the SARS-CoV-2 pandemic and it is widely expected that this will have a lasting impact on healthcare practices. These tools can help reduce the risk of exposing patients and medical staff to infection, make healthcare services more accessible, and allow providers to see more patients. However, objective measurement of vital signs is challenging without direct contact with a patient. We present a video-based and on-device optical cardiopulmonary vital sign measurement approach. It leverages a novel multi-task temporal shift convolutional attention network (MTTS-CAN) and enables real-time cardiovascular and respiratory measurements on mobile platforms. We evaluate our system on an Advanced RISC Machine (ARM) CPU and achieve state-of-the-art accuracy while running at over 150 frames per second which enables real-time applications. Systematic experimentation on large benchmark datasets reveals that our approach leads to substantial (20%-50%) reductions in error and generalizes well across datasets.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 8 samples from 1 repository, 6 ran (6 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xin71/MTTS-CAN officialmentioned on GitHubtfMITSyntology: 8 samples, 6 ran (0 instrument-failed) · 2 unverified report
buet94/non-Contact mentioned on GitHubtfMITSyntology: not harvested report
xliucs/MTTS-CAN mentioned on GitHubtfMITSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

6ran
2unverified

Licence: 0 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from xin71/MTTS-CAN. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

xin71/MTTS-CAN official repository 8 samples, 6 ran (0 instrument-failed) · 2 unverified
CAN code/model.py ran MIT (permissive) · 5e5bdb364e642d70 · report fixture: signature nb_filters1:int/0/int, nb_filters2:int/0/int, input_shape:tuple/1/int, kernel_size:tuple/1/int, dropout_rate1:float/0/float, dropout_rate2:float/0/float, pool_size:tuple/1/int, nb_dense:int/0/int · returned Functional · level recorded 2026-09-25
detrend in 8 papers code/inference_preprocess.py ran fingerprinted MIT (permissive) · 9f063d3ca0da3fcd · report fixture: signature signal:ndarray/1/float, Lambda:int/0/int · returned ndarray · level recorded 2026-09-25
get_nframe_video code/pre_process.py ran MIT (permissive) · 78c50f6ccff6b241 · report fixture: signature path:str/0/str · returned int · level recorded 2026-09-25
get_nframe_video_val code/pre_process.py ran MIT (permissive) · 458a7fdb0e205e18 · report fixture: signature path:str/0/str · returned int · level recorded 2026-09-25
preprocess_raw_video code/inference_preprocess.py ran MIT (permissive) · f67cd52ce15699d9 · report fixture: signature videoFilePath:str/0/str, dim:int/0/int · returned ndarray · level recorded 2026-09-25
split_subj code/pre_process.py ran MIT (permissive) · 043f5cee98e9150d · report fixture: signature data_dir:str/0/str, cv_split:int/0/int, subNum:ndarray/1/int · returned tuple · level recorded 2026-09-25
MT_CAN code/model.py unverified MIT (permissive) · 25437cf49e32cdbc · report
TSM_Cov2D code/model.py unverified MIT (permissive) · c9dce5ddd6127a4d · report

Tasks

Photoplethysmography (PPG) heart rate estimation

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Photoplethysmography (PPG) heart rate estimation MMSE-HR TS-CAN MAE 3.04 #2 of 6 Archive leaderboard report
Photoplethysmography (PPG) heart rate estimation MMSE-HR TS-CAN MAPE (%) 3.41% #2 of 6 Archive leaderboard report
Photoplethysmography (PPG) heart rate estimation MMSE-HR TS-CAN Pearson Correlation 0.89 #2 of 6 Archive leaderboard report
Photoplethysmography (PPG) heart rate estimation UBFC-rPPG TS-CAN RMSE 2.72 #8 of 8 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections