Papers › A Multimodal Anomaly Detector for Robot-Assisted Feeding Using an LSTM-based...

A Multimodal Anomaly Detector for Robot-Assisted Feeding Using an LSTM-based Variational Autoencoder

2 Nov 2017arXiv:1711.00614archive 2025-07-28

Daehyung Park, Yuuna Hoshi, Charles C. Kemp

The detection of anomalous executions is valuable for reducing potential hazards in assistive manipulation. Multimodal sensory signals can be helpful for detecting a wide range of anomalies. However, the fusion of high-dimensional and heterogeneous modalities is a challenging problem. We introduce a long short-term memory based variational autoencoder (LSTM-VAE) that fuses signals and reconstructs their expected distribution. We also introduce an LSTM-VAE-based detector using a reconstruction-based anomaly score and a state-based threshold. For evaluations with 1,555 robot-assisted feeding executions including 12 representative types of anomalies, our detector had a higher area under the receiver operating characteristic curve (AUC) of 0.8710 than 5 other baseline detectors from the literature. We also show the multimodal fusion through the LSTM-VAE is effective by comparing our detector with 17 raw sensory signals versus 4 hand-engineered features.

PaperPDFCodeCode 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 10 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 10 samples from 2 repositories, 9 ran (8 with no instrument failure; 1 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

chickenbestlover/RNN-Time-series-Anomaly-Detection mentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 8 ran (1 instrument-failed) · 1 unverified report
danyleb/variational-lstm-autoencoder mentioned on GitHubtfMITSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
freedombenLiu/RNN-Time-series-Anomaly-Detection mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to LSTM-based Encoder-Decoder for Multi-sensor Anomaly Detection (arXiv:1607.00148; that paper's own run record: 7 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; 1 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
freedombenLiu/https-github.com-chickenbestlover-RNN-Time-series-Anomaly-Detection mentioned on GitHubpytorchApache-2.0Syntology: not harvested report
timyadnyda/variational-lstm-autoencoder 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

10 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 1 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.

1ran · our draft was wrong
8ran
1unverified

Licence: 0 of the 10 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

chickenbestlover/RNN-Time-series-Anomaly-Detection community (archive-listed) 9 samples, 8 ran (1 instrument-failed) · 1 unverified
alphanum_key in 5 papers png2gif.py ran fingerprinted Apache-2.0 (permissive) · 052b2ec0f82abb8e · report fixture: signature s:str/0/str · returned list · level recorded 2026-09-26
fit_norm_distribution_param anomalyDetector.py ran Apache-2.0 (permissive) · cc97ebc512306ea0 · report fixture: signature args:Args/0/?, model:callable/0/?, train_dataset:list/1/Tensor, channel_idx:int/0/int · returned tuple · level recorded 2026-09-26
get_batch in 82 papers 1_train_predictor.py ran · our draft was wrong Apache-2.0 (permissive) · 566787f11a729568 · report fixture: signature args:Args/0/?, source:Tensor/1/float, i:int/0/int · returned tuple · level recorded 2026-09-22
get_precision_recall anomalyDetector.py ran Apache-2.0 (permissive) · 5ae112cc846cc62e · report fixture: signature args:Args/0/?, score:Tensor/1/float, label:Tensor/1/float, num_samples:int/0/int, beta:float/0/float, sampling:str/0/str, predicted_score:NoneType/0/? · returned tuple · level recorded 2026-09-26
normalization in 70 papers
census: 4 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
preprocess_data.py ran fingerprinted Apache-2.0 (permissive) · ebbdec7d25441eb9 · report fixture: signature seqData:Tensor/2/float, max:float/0/float, min:float/0/float · returned Tensor · level recorded 2026-09-26
reconstruct in 9 papers preprocess_data.py ran fingerprinted Apache-2.0 (permissive) · 4b937bb49e947c19 · report fixture: signature seqData:Tensor/2/float, mean:Tensor/2/float, std:Tensor/2/float · returned Tensor · level recorded 2026-09-26
standardization in 8 papers preprocess_data.py ran fingerprinted Apache-2.0 (permissive) · 61729d480bdea1de · report fixture: signature seqData:Tensor/2/float, mean:Tensor/2/float, std:Tensor/2/float · returned Tensor · level recorded 2026-09-26
tryint png2gif.py ran fingerprinted Apache-2.0 (permissive) · 77ebbd9cfb0ed6a4 · report fixture: signature s:str/0/str · returned int · level recorded 2026-09-26
anomalyScore anomalyDetector.py unverified Apache-2.0 (permissive) · 1ef6ff831cff2270 · report
danyleb/variational-lstm-autoencoder community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
LstmVAE/prepare_data.py ran fingerprinted MIT (permissive) · 78a18734bb0a2f00 · report fixture: signature df:ndarray/2/float · returned ndarray · level recorded 2026-09-26

Tasks

Anomaly Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Anomaly Detection voraus-AD LSTM-VAE Avg. Detection AUROC 86.7 #2 of 3 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