Update to v1.19.0 - New nodes, new features, bug fixes

[Vernalis]

The nightly build of the Vernalis community contribution has just been updated, with a number of new nodes, new features to existing nodes, and bug fixes:

New Nodes

• Added Run Garbage Collector node

• Added Run Heavy Garbage Collector node

  

Bug fixes / Enhancements

• Major overhaul of performance monitoring plugin:
  • Optional monitoring of individual loop body node timings (preserves legacy behaviour by default)
  • Improved error handling for missing / mismatched loop starts
  • Refactored most nodes and rationalised class structure
  • Node descriptions now all created dynamically, allowing simplification of addition of further nodes with alternative port types
• Missing icons restored to MMP Nodes
• Fixed URL change for SMARTSViewer node
• Update core plugin about.ini file with current date
• Enhanced error handling in MemoryUtils class and corresponding nodes (Benchmarking loops and Memory use node)
• Allowed unix-style dates in ‘Load Bruker AMIX Peaklist Files’ node
• Added createTab method to NodeDescriptionUtils (core plugin)

This adds nodes and features referenced in the following posts:

[Bug] Memory Use ArrayIndexOutOfBoundsException

Hi, the Memory Use Node throws an error on my OS X machine with 16 GB of memory: ERROR Memory Use 2:1224 Execute failed: ("ArrayIndexOutOfBoundsException"): -1 Any idea what this might cause since it’s working perfectly on another Windows machine. Kind regards Mike

[Bug] Benchmark "breaks" table row to variable loop

Hi, I’ve noticed that by placing a benchmark node within a table row to variable loop, it’s looping just once. After moving it out it worked again but it’s rather tricky to collect meaningful information about possible memory leakage. Edit: Modified the workflow but the issue still persists. By deselecting all nodes after start execution of everything it does not continue to run after the first iteration. [2019-03-25%2022_25_43-bans2065%20-%20Remotedesktopverbindung] In fact if seems that b…

and

Reset/Free WF memory

Hi How one can Reset the workflow memory after execution? If i reset the nodes i still see that the Knime memory over the Task Manager still capture the last size they have been used after the end of the WF. If i re-run the Workflow i would expect the memery of the WF is reset and released. In order to free teh WF memroy i forced to exit the Knime and restart it again. Best Malik

For any node developers who happen to have subclassed any of the NodeFactory implementions in the benchmarking plugin, there is a very small possibility that this update will have broken things - if that is the case, please get in touch and I can point you to how to fix things.

Steve

[Vernalis]

This update has now additionally been applied to the 3.7 stable build. In this case, it also rolls in the following improvements, which had not previously been applied to the stable build:

Update to v1.18.3 (Nightly only) - MMP Performance improvement

The nightly build has just been updated to v 1.18.3, which provides significant performance improvement in the MMP Maximum Cuts (RDKit) node. On our test machine, the node processed 5000 molecules from ChEMBL with HAC <= 40 in 3.8 seconds (the previous version took 375-400 seconds for the same data set) [image] We will push this to the stable releases in the coming weeks. Steve

and

Update to v 1.18.2 (Nightly only)

This is a minor bug fix release as follows: Fixes international Locale support for the Memory Usage (including the memory monitoring loops) in Windows Provides MacOS support for these nodes This update will be ported to the stable builds later this week. Steve

Steve