Giters

khundman / telemanom

A framework for using LSTMs to detect anomalies in multivariate time series data. Includes spacecraft anomaly data and experiments from the Mars Science Laboratory and SMAP missions.

Home Page:https://arxiv.org/abs/1802.04431

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Question about selection of the telemetry variable

minhuw opened this issue · comments

commented

First of all, thank you for your excellent paper and source code!

I notice that in your algorithm design and implement, only a feature was selected as the telemetry variable. In paper, such a choice was explained as

Since our aim is to predict telemetry values for a single channel we consider the situation where d = 1.

In source code, it seemed that the first feature was selected as the telemetry variable for all channels.

y = data[:,-config.n_predictions:,0] #telemetry value is at position 0

So I wonder whether the same feature was selected as the telemetry one for all channels or the orders of features were different for different channels and the telemetry variable was set as the first feature?

What's more, could you give some general advice on how to choose a good telemetry variable?
I would appreciate if you could reply.

commented

chinglish

commented

Thanks for the note!

The individual telemetry channel was always in the first position in the arrays for this work and the ordering was consistent.

I'm not sure what you mean by "choosing a good telemetry variable"?