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

When plot = FALSE, don't call plot.new #3

Merged

Conversation

isalgueiro
Copy link
Owner

See twitter#61 and issue twitter#60

plot.new() is generally unfriendly to call unless it will actually be
used for drawing, and certainly not if we ask for no plots to be
created.

plot.new triggers the completion of the previous plotting action, and as
such can't be used in combination with any multithreading or forked R
processes.

plot.new also does not return a "plot" object, it always returns `NULL`,
so although it appears to be used here as a way of returning a "null
plot", all that really happens is that AnomalyDetection* returns
`list(..., plot = NULL)`.

This commit resolves twitter#60
@isalgueiro isalgueiro merged commit fd74906 into isalgueiro:master Nov 24, 2017
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

Successfully merging this pull request may close these issues.

2 participants