-
Notifications
You must be signed in to change notification settings - Fork 6
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
Running into errors when running algorithm #1
Comments
@szsb26 |
@xhd1203 I also ran into issues of the algorithm performing poorly. You can see this not only from the experiment in the paper but also from the colab notebook link given in this repo. The magnitudes of the estimated seasonal components do not match with the magnitudes of the synthetically generated true seasonal components at all. Granted, this is probably due to the paper not explaining things very well. For ex., the fast RobustSTL paper does not explain how any of the denoising and regularization parameters were chosen, and like the repo author mentioned, did not provide enough details for the GADMM portion to be replicated... |
@szsb26 |
Hi Aria,
First, I want to thank you immensely for implementing this algorithm, as I could not find an implementation anywhere to test the claims in the original fast robustSTL paper.
However, im running into some issues when trying to run the algorithm.
When running your ex. with N = 1231 (size of data vector y), the algorithm runs fine, as shown below
However, when replacing "y" with a same size vector called "data" which looks like the following:
I get the following error when running robustSTL
where the error is:
Since "y" and "data" are exactly the same size except with different values, and all parameters are fixed, im a bit confused as to what is going on and would really appreciate it if you can provide some help/insight.
If it helps, i've also attached the data used in "data" vector. It is in the attached dataframe under column "values"
internet_traffic_stl_results_complete.csv
Thanks!
Sichen
The text was updated successfully, but these errors were encountered: