ROC Curves not calculated in 4.2

[mgamer]

Hello all,
I have a problem with a workflow that runs normally under 4.1.3 but crashes in 4.2. Problem is the ROC Curve node, I get strange error messages that I do not understand (enclosed screenshot). The workflow is a quite straight forward DT-Learner (here part of a Meta-node).

Any suggestions?

[mlauber71]

After installing 4.2 on a Mac I had to reconfigure the settings for the JavaScript graphics in the preferences (using default internal chromium browser). Since then I experience strange problems. Sometimes graphics would not render sometimes they would not.

It could be associated with doing more than one graphic at a time, but I am not sure yet. I think I will try some alternative rendering options to see if that makes any difference.

[mgamer]

@mlauber71: Thank your for this advice. This solved the problem

[ipazin]

Hello!

From https://www.knime.com/whats-new-in-knime-42 under General Release Notes:

• Using an external (pre-installed) Chrome to view JavaScript views is no longer available due to API changes between different versions of Chrome. Instead, use the Chromium binaries provided via the KNIME update site (pre-installed on Linux and Windows).
• Chromium binaries are no longer pre-installed on MacOS due to Apple’s notarization process. They can be installed separately using “File” -> “Install KNIME Extensions”

Maybe it helps

Br,
Ivan

[mlauber71]

The problem seems to be that under MacOSX I experience various problems with this settings. Sometimes it does produce a SVG that can be converted into an PNG but sometimes it just gives an error like this:

I have not yet been able to reproduce the error in a systematic way but it happens all the time. Seems the implementation has some problems. Switching out the engine does not seem to have any effect at all.

[ipazin]

Hello!

ticket is created for this one. (Internal reference: AP-14862)

Br,
Ivan

[albrecht]

Hi,

I can’t exactly reproduce the problem described here, but noticed that when using an old workspace with 4.2 (depending on your previous settings) PhantomJS might be tried to be used, which is not available anymore. It then tries to use Chromium automatically instead, which for me always worked, but going to the preference page once and applying the settings got rid of that behaviour.

A question to your problem. When the error occurs, does the node take a long time to execute? Or does it take a long time to execute in the first place? There might be a timeout that the node runs into if the image generation takes too long. Is there additional output in the log file that could be used to identify the issue?

Cheers,
Christian

[mgamer]

Hi,

when the problem occurred the node did not execute - it failed. Now it runs normally (after installing the chromium).

Greetings from Steinheim

Mike