RM 5.xx hangs when exception occurs

marcin_blachnikmarcin_blachnik Member Posts: 61 Guru
edited November 2018 in Help
I think it is a bug:
and it is related to the RapidMiner version 5.xx. For example it appears in version 5.13 and 5.15
Whenever an exception appears inside a loop, it doesn't influence next iteration. However, if there is any operator inside the loop which is conected to the output of operator throwing an exception the system hangs
This is shown in the example process:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<process version="5.3.013">
  <operator activated="true" class="process" compatibility="5.3.013" expanded="true" name="Process">
    <process expanded="true">
      <operator activated="true" class="retrieve" compatibility="5.3.013" expanded="true" height="60" name="Retrieve Iris" width="90" x="309" y="122">
        <parameter key="repository_entry" value="//Samples/data/Iris"/>
      <operator activated="true" class="loop_parameters" compatibility="5.3.013" expanded="true" height="76" name="Loop Parameters" width="90" x="450" y="119">
        <list key="parameters">
          <parameter key="Generate Macro (10).use_standard_constants" value="false"/>
        <parameter key="parallelize_subprocess" value="true"/>
        <process expanded="true">
          <operator activated="true" class="generate_macro" compatibility="5.3.013" expanded="true" height="76" name="Generate Macro (10)" width="90" x="183" y="272">
            <list key="function_descriptions">
              <parameter key="b_b" value="%{a_a}*5"/>
            <parameter key="use_standard_constants" value="false"/>
          <operator activated="true" class="log" compatibility="5.3.013" expanded="true" height="76" name="Log" width="90" x="421" y="277">
            <list key="log">
              <parameter key="dataset" value="operator.Generate Macro (10).value.applycount"/>
          <connect from_port="input 1" to_op="Generate Macro (10)" to_port="through 1"/>
          <connect from_op="Generate Macro (10)" from_port="through 1" to_op="Log" to_port="through 1"/>
          <portSpacing port="source_input 1" spacing="0"/>
          <portSpacing port="source_input 2" spacing="0"/>
          <portSpacing port="sink_performance" spacing="0"/>
          <portSpacing port="sink_result 1" spacing="0"/>
      <connect from_op="Retrieve Iris" from_port="output" to_op="Loop Parameters" to_port="input 1"/>
      <portSpacing port="source_input 1" spacing="0"/>
      <portSpacing port="sink_result 1" spacing="0"/>
In RM 6.x this problem  is solved.

Will it be possible that you correct it in the version 5




  • Options
    Marco_BoeckMarco_Boeck Administrator, Moderator, Employee, Member, University Professor Posts: 1,993 RM Engineering

    while we will fix critical showstoppers in RM 5, I'm afraid this does not classify.. You are very welcome to create a pull request with the fix in Github though!

Sign In or Register to comment.