-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The purpose of adjust_anomaly_scores
#4
Comments
Hi, thanks for your question. Recall that SMAP and MSL actually consist of multiple individual time-series (A-1, C-2, etc.), each of which has 24/54 (SMAP/MSL) one-hot encoded features and 1 continuous feature. Each of these time-series is very short (typically 1-3k timesteps), so most implementations (including ours) concatenate all these time-series in the time direction, creating one large time-series. So, the dataset will "jump" up and down whenever it transitions to a new channel. This has some effects on the forecastings and reconstructions of the model:
These two steps are performed in |
Experiments
# This is the 1st commit message: feat: possibility to specify target dim # The commit message ML4ITS#2 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#3 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#4 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#5 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#6 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#7 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#8 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#9 will be skipped: # feat: possibility to specify target dim # The commit message ML4ITS#10 will be skipped: # fix # The commit message ML4ITS#11 will be skipped: # fix # The commit message ML4ITS#12 will be skipped: # feat: writing results to txt file # The commit message ML4ITS#13 will be skipped: # feat: writing results to txt file # The commit message ML4ITS#14 will be skipped: # .. # The commit message ML4ITS#15 will be skipped: # .. # The commit message ML4ITS#16 will be skipped: # .. # The commit message ML4ITS#17 will be skipped: # trying new anomaly score # The commit message ML4ITS#18 will be skipped: # trying new anomaly score # The commit message ML4ITS#19 will be skipped: # trying new anomaly score # The commit message ML4ITS#20 will be skipped: # trying new anomaly score # The commit message ML4ITS#21 will be skipped: # fix # The commit message ML4ITS#22 will be skipped: # results from all experiments, plotting, ++ # The commit message ML4ITS#23 will be skipped: # added plotter class and jupyter notebook file to visualize results
Thanks for your briliiant work. I would like to know the purpose of
adjust_anomaly_scores
. Thanks for your time.The text was updated successfully, but these errors were encountered: