Attribute's role gets lost in "work on subset"

qwertz
qwertz New Altair Community Member
edited November 5 in Community Q&A

Dear community,

in the following process I generate a dataset including a label attribute. But when feeding the dataset into the "work on subset" operator the role of the label attribute seems to be set temporarily to "regular" (see result at breakpoint).

I believe this is why the weighting operator doesn't provide any results in the end. However, after the whole process finished, the label attribute has its former role again. Is there any setting that could be wrong in my process?

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<process version="5.2.008">
  <context>
    <input/>
    <output/>
    <macros/>
  </context>
  <operator activated="true" class="process" compatibility="5.2.008" expanded="true" name="Process">
    <process expanded="true" height="424" width="743">
      <operator activated="true" class="generate_data" compatibility="5.2.008" expanded="true" height="60" name="Generate Data" width="90" x="45" y="30">
        <parameter key="number_examples" value="10"/>
        <parameter key="number_of_attributes" value="3"/>
        <parameter key="attributes_lower_bound" value="0.0"/>
      </operator>
      <operator activated="true" class="work_on_subset" compatibility="5.2.008" expanded="true" height="94" name="Work on Subset" width="90" x="179" y="30">
        <parameter key="attributes" value="|att1|att2|label"/>
        <parameter key="include_special_attributes" value="true"/>
        <process expanded="true" height="424" width="743">
          <operator activated="true" breakpoints="after" class="weight_by_correlation" compatibility="5.2.008" expanded="true" height="76" name="Weight by Correlation (2)" width="90" x="45" y="30">
            <parameter key="normalize_weights" value="false"/>
            <parameter key="sort_direction" value="descending"/>
          </operator>
          <connect from_port="exampleSet" to_op="Weight by Correlation (2)" to_port="example set"/>
          <connect from_op="Weight by Correlation (2)" from_port="weights" to_port="through 1"/>
          <connect from_op="Weight by Correlation (2)" from_port="example set" to_port="example set"/>
          <portSpacing port="source_exampleSet" spacing="0"/>
          <portSpacing port="sink_example set" spacing="0"/>
          <portSpacing port="sink_through 1" spacing="0"/>
          <portSpacing port="sink_through 2" spacing="0"/>
        </process>
      </operator>
      <connect from_op="Generate Data" from_port="output" to_op="Work on Subset" to_port="example set"/>
      <connect from_op="Work on Subset" from_port="example set" to_port="result 1"/>
      <connect from_op="Work on Subset" from_port="through 1" to_port="result 2"/>
      <portSpacing port="source_input 1" spacing="0"/>
      <portSpacing port="sink_result 1" spacing="0"/>
      <portSpacing port="sink_result 2" spacing="0"/>
      <portSpacing port="sink_result 3" spacing="0"/>
    </process>
  </operator>
</process>
Kind regards
Sachs
Tagged:

Answers

  • qwertz
    qwertz New Altair Community Member
    There is another sample process:

    In this case I try to just pass the label through the "work on subset" operator but with AND without having the feature "include special attributes" checked, the result doesn't include the label.

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <process version="5.2.008">
      <context>
        <input/>
        <output/>
        <macros/>
      </context>
      <operator activated="true" class="process" compatibility="5.2.008" expanded="true" name="Process">
        <process expanded="true" height="424" width="743">
          <operator activated="true" class="generate_data" compatibility="5.2.008" expanded="true" height="60" name="Generate Data" width="90" x="45" y="30">
            <parameter key="number_examples" value="10"/>
            <parameter key="number_of_attributes" value="3"/>
            <parameter key="attributes_lower_bound" value="0.0"/>
          </operator>
          <operator activated="true" class="work_on_subset" compatibility="5.2.008" expanded="true" height="76" name="Work on Subset" width="90" x="179" y="30">
            <parameter key="attribute_filter_type" value="single"/>
            <parameter key="attribute" value="att1"/>
            <parameter key="include_special_attributes" value="true"/>
            <process expanded="true" height="424" width="743">
              <operator activated="true" breakpoints="before" class="weight_by_correlation" compatibility="5.2.008" expanded="true" height="76" name="Weight by Correlation" width="90" x="45" y="30"/>
              <connect from_port="exampleSet" to_op="Weight by Correlation" to_port="example set"/>
              <connect from_op="Weight by Correlation" from_port="example set" to_port="example set"/>
              <portSpacing port="source_exampleSet" spacing="0"/>
              <portSpacing port="sink_example set" spacing="0"/>
              <portSpacing port="sink_through 1" spacing="0"/>
            </process>
          </operator>
          <connect from_op="Generate Data" from_port="output" to_op="Work on Subset" to_port="example set"/>
          <connect from_op="Work on Subset" from_port="example set" to_port="result 1"/>
          <portSpacing port="source_input 1" spacing="0"/>
          <portSpacing port="sink_result 1" spacing="0"/>
          <portSpacing port="sink_result 2" spacing="0"/>
        </process>
      </operator>
    </process>

    All the best
    Sachs


    EDIT: Have submitted a report now in the bug tracker system (bug 1353)
  • Nils_Woehler
    Nils_Woehler New Altair Community Member
    Hi Sachs,

    this seems to be a bug. Thanks for reporting :-)

    Best,
    Nils
  • qwertz
    qwertz New Altair Community Member

    Update: Just found another curiosity concerning the "work on subset" operator concerning the "include special attributes" function.

    Details and a sample process can be found under the same tracking number as I thought it might be correlated to the first issue and it affects the same operator. http://bugs.rapid-i.com/show_bug.cgi?id=1353


    Kind regards
    Sachs