-
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
out_dim or n_features #3
Comments
We do it like this because we do not always want to forecast and reconstruct all input features. Lines 40 to 53 in 8f907cc
That is why we for MSL and SMAP use [0] as target dim (dim of the telemetry value). In Lines 54 to 70 in 8f907cc
To get correct loss during training (forecastings and recons are compared against the correct input features) we must also check for this: Lines 111 to 115 in 8f907cc
|
Thanks for the explanation. I did miss that part in train.py. It helps a lot. |
Trainer class
# 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
mtad-gat-pytorch/mtad_gat.py
Line 62 in 8f907cc
self.recon_model = ReconstructionModel(window_size, gru_hid_dim, recon_hid_dim, out_dim, recon_n_layers, dropout)
should the "out_dim" be changed to "n_features" to match the shape of input x while the loss is calculated by MSELoss(recons, x) ??
The text was updated successfully, but these errors were encountered: