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 found that whenever I start RStudio, the data paths (e.g., raw_dir, data_dir) are reset to the default ones. And I have to run rave::rave_options() to correct those paths again. I'm running RAVE on win10, R4.0.2, RSudio 1.3.1056.
Can you replicate this bug in your environment?
Best regards,
Xiaoyu
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue @XiaoyuZeng I was trying to fix this issue yesterday. RAVE was developed on Mac and its Windows side was not well tested. Sorry for this obvious bug.
Could you try rave::check_dependencies() to update rave?
Also just in case you didn't noticed, there is a "Set Directory" link below the text input. You might want to click on it to save the settings.
Thanks for reporting this issue @XiaoyuZeng I was trying to fix this issue yesterday. RAVE was developed on Mac and its Windows side was not well tested. Sorry for this obvious bug.
Could you try rave::check_dependencies() to update rave?
Also just in case you didn't noticed, there is a "Set Directory" link below the text input. You might want to click on it to save the settings.
Please let me know if the solution works or not.
Thank you!
Surely I click 'Set directory' whenever I reset the datapath using rave::rave_options().
I just tried rave::check_dependencies(), and it worked! The data path remained what I set before I restart RStudio.
Also, I found the 'Maximum number of CPU cores to be used' can be above 3 after the update (3 is the maximum before this update for windows 10).
Hi all.
I found that whenever I start RStudio, the data paths (e.g., raw_dir, data_dir) are reset to the default ones. And I have to run rave::rave_options() to correct those paths again. I'm running RAVE on win10, R4.0.2, RSudio 1.3.1056.
Can you replicate this bug in your environment?
Best regards,
Xiaoyu
The text was updated successfully, but these errors were encountered: