Skip to content
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 an automated script to produce multiple sets of charts in the same folder not working as hoped #45

Open
jpn5089 opened this issue Jul 31, 2017 · 2 comments

Comments

@jpn5089
Copy link

jpn5089 commented Jul 31, 2017

In one R script I created multiple sets of charts using facet_trelliscope all named differently to keep them separate. When I source the script in R studio, everything works fine with a web browser opening up with my different sets of graphs, all saved to the folder I specify.

image

When I try and run the same R script with the Windows Task Scheduler, it runs with no error, but doesn't create a folder with "app files", "lib", or the index HTML file.

This leads to my question: what I'm wondering is, does the fact that a web browser is prompted to open after each call of facet_trelliscope, is that causing an issue when using Windows Task Scheduler. You may not have a direct answer for that, but regarding the facet_trelliscope function, is there a parameter like open_browser or something that can be set to FALSE, so a browser doesn't open and rather everything is just written to the folder at the path you specify?

Thanks in advance

@hafen
Copy link
Owner

hafen commented Aug 1, 2017

This is a good request and I actually have implemented a fix for it, but it's part of a few other enhancements I'm testing so hopefully it will be available in the next few days. You are correct that right now the index.html file, etc. are not written until the object is printed, but there's no reason for them not to be created beforehand.

@jpn5089
Copy link
Author

jpn5089 commented Aug 2, 2017

Thanks for the feedback. I will keep an eye out for that update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants