<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Flexible Feature Deletion: Companion Video?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Brian Schack</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rachael Summers</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Indiana University Bloomington</institution>
          ,
          <addr-line>Bloomington</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>As the number of cases in a case-base reasoning system increases, both storage cost and retrieval time also increase. Case-base maintenance mitigates this problem by deleting cases, and various orderings of the cases for deletion attempt to minimize the loss of problem solving competence. Existing methods assume (1) that the cases have a uniform size and (2) that the case contents are indivisible. In contrast to assumption (1), exible feature deletion balances the varying storage costs of di erent cases with their competence bene ts. And for assumption (2), exible feature deletion subdivides selected cases by deleting or compressing their features or subcomponents. Experimental results supported that, for suitable cases bases, exible feature deletion can outperform existing per-case strategies. In this companion video, a live-action, life-size CBR robot demonstrates each of the four phases of the CBR cycle: retrieve, reuse, revise, and retain. And a teacher explains exible feature deletion while the robot performs maintenance on articles of his clothing.</p>
      </abstract>
      <kwd-group>
        <kwd>Case-based Reasoning</kwd>
        <kwd>Case-base Maintenance</kwd>
        <kwd>Flexible Feature Deletion</kwd>
        <kwd>Feature Reduction</kwd>
        <kwd>Case Deletion</kwd>
        <kwd>Case-base Compression</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body />
  <back>
    <ref-list />
  </back>
</article>