Skip to content
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

What is the best setup of SAITS to improve imputation results within missing gap and single missing over time data? #44

Open
clevilll opened this issue Nov 1, 2024 · 3 comments

Comments

@clevilll
Copy link

clevilll commented Nov 1, 2024

Hi,
I was experimenting this DL architecture to see how the performance of its imputation over uni-variante time-series data for:

  • missing gap
  • single missing

using this setup:

    def __init__(self, columns=None,
                 n_steps=100,
                 n_features=1,   #uni-variante time-series data
                 n_layers=2,
                 d_model=256,
                 n_heads=4,
                 d_k=64,
                 d_v=64,
                 d_ffn=128,
                 dropout=0.1,
                 epochs=100):
...

I have reached the following results:

image

So let's zoom and see the performance of SAITS() with other classic treatments of missing data - X['avgcpu'].interpolate(method=...) as well as Average Median of all instances replacement via X['avgcpu'].median().

Fig. 1: Comparison of imputations for missing gap Fig. 2: Comparison of imputations for single missing sequence

I don't see much differences between imputation of SAITS() and median() especially over missing gaps and comparing results for single missing, results of other classic interpolation fillers (Linear\Nearest) are comperable with SAITS(). I expected at least over missing gap case, DL-based models could perform and replace meaningful values.

I’d appreciate any insights based on your experience if I need to adjust hyper-parameters of SAITS() for further improvement. I also read closed issues in this repo but did not find something helpful about improvement for these missing scenarios.


Note: The resolution of used time data is epoch=5mins (sometimes some models are not good with high-frequency time data)

@WenjieDu
Copy link
Owner

WenjieDu commented Nov 1, 2024

Hi there,

Thank you so much for your attention to SAITS! If you find SAITS is helpful to your work, please star⭐️ this repository. Your star is your recognition, which can let others notice SAITS. It matters and is definitely a kind of contribution.

I have received your message and will respond ASAP. Thank you again for your patience! 😃

Best,
Wenjie

Copy link

This issue had no activity for 14 days. It will be closed in 1 week unless there is some new activity. Is this issue already resolved?

@github-actions github-actions bot added the stale label Nov 16, 2024
@clevilll
Copy link
Author

This issue had no activity for 14 days. It will be closed in 1 week unless there is some new activity. Is this issue already resolved?

The problem has not been solved and no answer provided so far from @WenjieDu

@github-actions github-actions bot removed the stale label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants