ddempseyr

@gufengzhou Sorry for the delay! Thanks so much for looking into this and committing a fix. I'm hoping to test the fix this week and follow up with the results.

@gufengzhou Sorry again for my slow response. I wanted to follow up and let you know that we should have the results of our test sent over by end of...

@gufengzhou Great news. After installing Robyn locked to commit 38df2237943a45a9001bd05904d392d6a96adfc3, I re-ran the reproducible example above, and confirm that the results from the original model and recreated model are one-to-one....

@gufengzhou We rebuilt our docker images pointed to the commit for the fix, reran our pipelines, and are still seeing relatively large discrepancies on our customer's recreated models. Unfortunately, we...

@gufengzhou I was able to anonymize our data so that it can be sent over. See the script below and the three files required to recreate the model. Instructions to...

@gufengzhou Thanks for the update. I rebuilt our container pointed to the latest commit, created a new model, and recreated the model. Overall, the results (e.g. coefficients) are significantly closer...

@gufengzhou I ran a test and it appears the JSON file has a higher scale relative to the scale in OutputCollect$resultHypParam. The JSON file has a scale of 10 while...

@gufengzhou On a side note, do you know whether there were any changes to main since the v3.10.3 CRAN release that would impact the date_range in the robyn_allocator? We were...

@gufengzhou Thanks for the speedy response. I'll work on getting this over to you today.

@gufengzhou Good news. I believe the issue with robyn_allocator has been resolved. We updated Robyn to the latest commit on main and we are no longer seeing errors when passing...