Skip to content
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jcpetkovich
Copy link

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 #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
@jhochenbaum
Copy link

Thanks @jcpetkovich !

@akejariwal
Copy link
Contributor

@caniszczyk The PR looks good. Please merge.

@jcpetkovich
Copy link
Author

Anything holding this back from a merge?

@wlopata
Copy link

wlopata commented Feb 10, 2016

Ping! Just hit into this issue myself.

@trh178
Copy link

trh178 commented Mar 4, 2016

Also just hit the issue. Does anyone else have write access to perform the merge?

@gonzalodiaz
Copy link

+1 to this change. I was about to do the same.

@dmpe
Copy link

dmpe commented May 21, 2016

/cc @caniszczyk

@Winterflower
Copy link

+1 for this change - please let me know if I can help in any way to get this merged into the codebase. I'm hitting this issue when trying to run AnomalyDetectionTs in a subprocess.

@CLAassistant
Copy link

CLAassistant commented Jul 18, 2019

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Successfully merging this pull request may close these issues.

Using AnomalyDetection in parallel or in any forked environment fails
9 participants