-
Notifications
You must be signed in to change notification settings - Fork 350
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
Robyn error while running OutputModels <- code - Error in { : task 1 failed - "arguments imply differing number of rows: 19, 20" #619
Comments
Some additional context, my data has range from 1/1/22 - 12/31/22 but I am looking to run this model from 8/15 - 12/31.... If i use the window start and window end as 1/1 - 12/31 then the model works..... |
@Amyhaoming, any updates on that issue ? I am having the same issue when trying to read and reproduce a model made under the 3.7.0 version in the 3.9.0 version. The error message is the following:
And this is the code:
This works perfectly in the 3.7.0 version And the traceback Not sure what is going on, I have spend some time investigating, but couldn't find the issue. Thanks for your help |
It looks like you're loading an old model that was built using older version, then recreating using the new version. This might the reason. Esp. Because after 3.9 there's a new hyperparameter train_size that didn't exist before. Can you please rerun your model using the latest package with the narrower ranges as in your old model. |
@gufengzhou, yes it works with the 3.7 version. Nonetheless, I am not sure this is due to the hyperparameter train_size, as it is created automatically if not detected (its value is equal to 1). |
@Amyhaoming Is there an update on this bug? I have tried using different Robyn versions with the same dataset and I see this error coming up starting version 3.9.0 which makes me think this it relates to addition of ts_validation starting this version. However, setting ts_validation to False or train_size to 1 does not fix the error. In my case, the error only shows up in certain modeling periods. For example, For 1 year training data it works without issues, but not 9 months or less. I am not trying to load an old model, these are all building models from scratch |
Hi! I can report I am having the same issue. Interestingly is only happening with one of my clients. I tried different date ranges with no success in neither version 3.9 and 3.10. I was successful in running robyn back on version 3.7.2 for this client. |
@gufengzhou @laresbernardo Can you guys kindly take a look at this bug again? as I mentioned in my previous comment, I am not trying to load a model based on an older version, I am building a model from scratch and I see this error after version 3.9.0 for some datasets. I can send you guys a sample dataset through our Meta marketing science partner for the debug if it helps |
Hi @sahbakn, please do. That will help us debug and understand what's happening in your specific case. Thanks! |
I am getting the same error message when I try to pass a character vector to context_vars However, if I unhash and use the factor_vars argument, it works. What am I misunderstanding here? |
@SeanRichterWalsh not sure that's actually the case here. What version are you on?
Also keep in mind that this message won't show up if you add |
Thanks @laresbernardo . Yes, I am using the latest dev version. I restarted my R session and tried again with my dataset and it seems to work fine now. My own data set's events variable is now being auto-forced to factor as expected and I don't have to explicitly use the factor_vars argument. Not sure what was up earlier. Thanks. |
Hi, we're running into the same issue with both version 3.9 and 3.10: |
Hi @TrunckYagora we haven't been able to replicate this issue yet. Can you please provide a reproducible example that returns that error so it can help us debug? |
Just a final comment from me on this. I know my issue may not be related but I did get a similar error message when exploring different modelling windows. I believe what may have caused it is my events variable having zero variance (all "na"). I mistakenly shortened the window too much and lost the events I had coded in the variable. |
Interesting point. This might have happened to me as well. I will do some tests tomorrow see if I can reproduce that error with those circumstance. Will circle back if so.
… On May 15, 2023, at 10:54 AM, Sean Walsh ***@***.***> wrote:
Just a final comment from me on this. I know my issue may not be related but I did get a similar error message when exploring different modelling windows. I believe what may have caused it is my events variable having zero variance (all "na"). I mistakenly shortened the window too much and lost the events I had coded in the variable.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
YES! That was it. We actually checked for no variance on raw input data before running |
@laresbernardo I looked into my data and during the modeling time frame that I was getting the error, I had one variable with 0 variance, fixing that I do not see the error anymore! |
Oh great! A silly mistake on my part but I am glad it has helped lead to a resolution here. I can confirm that the latest dev version gives a very informative message when a variable has zero variance. Thanks a lot. |
Great! Thanks for confirming. I'll check with @richa-makhija and @dmacoritto as well! This should have fixed the issue for everyone. Will close ticket after a week or confirmation. |
Hi @laresbernardo, thanks for the update, interestingly enough we're receive the error even when we're running the model without the factor_vars. For privacy reasons I altered the original data but the error can still be reproduced. You can find the data we're using to reproduce the error here: package Version is: ‘3.10.3.9000’ The code is as follows:
|
@TrunckYagora thanks for reporting this and providing a reproducible example. The problem was occurring when there were some variables not being used so weren't found when unselecting them. Can you please update to latest dev version and check? You should get this error given your dummy dataset now:
|
awesome - thank you very much for your support. In the latest dev version I get the error message you mentioned and we can run Robyn as usual with the correct parameters. |
Project Robyn
Describe issue
My code takes in all the inputs correctly but while running the OutputModels <- code, I get the above error
Error:
Provide reproducible example
Issues are often related to custom input data that is difficult to debug without. If necessary, please modify your data to mask real values and share a dataset that is able to reproduce the issue. Please also share your model configuration and exported JSON files if available.
Environment & Robyn version
The text was updated successfully, but these errors were encountered: