You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to refresh a Robyn model persisted to JSON. The (re)training went fine, but R displays an error when trying to save refreshed plots and CSVs to file. Here is the code I ran.
Most output is generated and present, except the files prefixed report_*. There are no report_decomposition.png and report_actual_fitted.png; the associated CSVs are absent, too.
This problem disappears if I do not specify a plot_folder when calling robyn_refresh.
Provide reproducible example
Here is the obfuscated CSV containing refreshed data, along with a JSON file of the model I intend to refresh. (Extension .json changed to .txt, so that GitHub would allow the upload.)
Thanks for reporting this issue and special thanks for sharing a reproducible example; without it would have been pretty hard to debug. That said, I've deployed a fix into the master branch that should take care of this case. Can you please update Robyn to the latest dev version, retry, and let me know if it ran OK?
Project Robyn
Describe issue
I am trying to refresh a Robyn model persisted to JSON. The (re)training went fine, but R displays an error when trying to save refreshed plots and CSVs to file. Here is the code I ran.
And here is a screenshot of the error.
Most output is generated and present, except the files prefixed
report_*
. There are noreport_decomposition.png
andreport_actual_fitted.png
; the associated CSVs are absent, too.This problem disappears if I do not specify a
plot_folder
when callingrobyn_refresh
.Provide reproducible example
Here is the obfuscated CSV containing refreshed data, along with a JSON file of the model I intend to refresh. (Extension .json changed to .txt, so that GitHub would allow the upload.)
RobynModel-1_433_1.txt
bug_report.csv
Environment & Robyn version
Robyn 3.7.2, R 4.2.1
The text was updated successfully, but these errors were encountered: