<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://repository.horizon.ac.id/items/browse?collection=766&amp;output=omeka-xml&amp;page=3" accessDate="2026-04-14T17:34:51+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>24</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10096" public="1" featured="1">
    <fileContainer>
      <file fileId="10109">
        <src>https://repository.horizon.ac.id/files/original/e2fdf36779a4d8edc98ff3ec75773ebf.pdf</src>
        <authentication>e673fc6f831e3ecd1a335f9caac2342c</authentication>
      </file>
    </fileContainer>
    <collection collectionId="766">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107820">
                  <text>VOL. 22, NO.3 2024</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107921">
                <text>Consistency, local stability, and approximation of Shapash explanation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107922">
                <text>Explainable artificial intelligence&#13;
Interpretable artificial intelligence&#13;
Interpretable machine learning&#13;
Model explanation&#13;
Predictive analytics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107923">
                <text>Consistency, scalability, and local stability properties ensure that a model or method produces reliable and predictable outcomes. The Shapash helps users understand how the model makes its decisions. With machine learning (ML) system, healthcare experts can identify individuals at higher risk and implement interventions to reduce the occurrence and severity of disease. ML had achieved higher prediction accuracy even though the accuracy of their prediction depends on the quality and quantity of the data used for training. Despite the wider application and higher accuracy of different ML for disease prediction, the explanation of their predictive outcome is much more important to the healthcare professional, the patient, and even their developers. However, most of the ML systems do not explain their outcomes. To address the explainability issue various techniques such as local model agnostic explanation (LIME), and shapley additive explanation (SHAP) have been proposed over the recent years. Furthermore, the consistency, local stability, and approximation of the explanation remained one of the research topics in ML. This study investigated the consistency, stability, and approximation of LIME and SHAP in predicting heart disease (HD). The result suggested that LIME and SHAP generated a similar explanation (distance=0.35), compared to the active coalition of variable (ACV) explanation (distance=0.43).</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107924">
                <text>Tsehay Admassu Assegie1, Bommy Manivannan2, Komal Kumar Napa3, Bindu Kolappa Pillai Vijayammal4, Rajkumar Govindarajan3, Sangeetha Murugan2, Atinkut Molla Mekonnen5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="107925">
                <text>Journal homepage: http://telkomnika.uad.ac.id</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107926">
                <text>Feb 2, 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107927">
                <text>PERI IRAWAN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107928">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107929">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107930">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12903">
        <name>Explainable artificial intelligence Interpretable artificial intelligence Interpretable machine learning Model explanation Predictive analytics</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10092" public="1" featured="1">
    <fileContainer>
      <file fileId="10105">
        <src>https://repository.horizon.ac.id/files/original/9ca25b0e4ec739efb1581144a6453013.pdf</src>
        <authentication>4dd83338be53fff73eb91b207345cbf3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="766">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107820">
                  <text>VOL. 22, NO.3 2024</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107877">
                <text>A survey on the dataset, techniques, and evaluation metric used for abstractive text summarization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107878">
                <text>Abstractive summarization&#13;
Attention mechanism&#13;
Automatic text summarization&#13;
Deep learning&#13;
Extractive summarization&#13;
Transformers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107879">
                <text>Whenever there is too much information out there, it is desirable to summarize. If humans are trying to create the summary, it will take lot of time. Now to make the problem of summarizing information easier and more effortless one can automate the summarization process which can reduce the time taken in creating summary. This is called as automatic summarization. The two ways of summarization are extractive summarization and abstractive summarization. Extractive summarization and its applications have been the subject of extensive research and have received state of art solution. But abstractive summarization still is a progressive field as it is difficult to create abstractive summary as humans do. Also, it is still a question i.e., how to evaluate the quality of a summary? Therefore, this paper is a comprehensive survey on the dataset used with its details and statistics, analysis of various abstractive summarization techniques and important parameters for evaluating the quality of summary. Deep leaning based models have given new direction in this field. The author also focuses on problems and challenges faced in the generation of summary which are opening the future research scope in this domain.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107880">
                <text>Shivani Sharma1, Gaurav Aggarwal1, Bipin Kumar Rai2</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="107881">
                <text>Journal homepage: http://telkomnika.uad.ac.id</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107882">
                <text>Feb 8, 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107883">
                <text>PERI IRAWAN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107884">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107885">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107886">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12896">
        <name>Abstractive summarization Attention mechanism Automatic text summarization Deep learning Extractive summarization Transformers</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10090" public="1" featured="1">
    <fileContainer>
      <file fileId="10103">
        <src>https://repository.horizon.ac.id/files/original/8b91b88044506cc39180215f1c10c702.pdf</src>
        <authentication>ce091e7f03cfebd0f0ba6c15fa7cb4ea</authentication>
      </file>
    </fileContainer>
    <collection collectionId="766">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107820">
                  <text>VOL. 22, NO.3 2024</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107855">
                <text>Igniting transistor to control three-phase alternating current motor servo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107856">
                <text>Controlled Igniting Position Rate&#13;
Torque</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107857">
                <text>The background of research try to use an open loop system, without feedback, by building torque in the target position. Theoretical basis manages the turning round of servo motor change direct currents to alternating currents by adjusting the rate input used. Methodology in simple terms, the flowchart of code processing from igniting transistors to managing the turning round of a three-phase alternating current (AC) servo motor. The result of the transistor ignition time with room phasor pulse width modulation (PWM) to set the ignition of a three-phase AC servo motor in the process of igniting as ordered, for manage position only igniting transistors in target position, and building torque at there. Discussion, igniting transistors to manage the turning round of servo motors, allows motion of servo motor, allows motion of servo motor to be added faster, accurately, soft, and steady. In conclusion, in this case the researcher uses it more specifically by turning on the transistor only at the target position, so that the torque generated is only at the target position, the servo motor motion from the start position immediately ends at the target position. Suggestions, this system igniting can be applied at a motion high-velocity system like a missile system controlled.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107858">
                <text>Syafruddin Rustam1, Andrew Ghea Mahardika2, Givy Devira Ramady1, Arif Rakhman3, Rahmad Hidayat1, Muchamad Sobri Sungkar3</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="107859">
                <text>Journal homepage: http://telkomnika.uad.ac.id</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107860">
                <text>Feb 2, 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107861">
                <text>PERI IRAWAN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107862">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107863">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107864">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12894">
        <name>Controlled Igniting Position Rate Torque</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10089" public="1" featured="1">
    <fileContainer>
      <file fileId="10102">
        <src>https://repository.horizon.ac.id/files/original/ebaeea563559553e054a01bb91410f35.pdf</src>
        <authentication>1c4eb6f4d835bb874921f83a0a165fe3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="766">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107820">
                  <text>VOL. 22, NO.3 2024</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107845">
                <text>Sclera boundary localization using circular hough transform and a modified run-data based algorithm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107846">
                <text>Biometrics&#13;
Circular hough transfrom&#13;
Compound local binary pattern&#13;
Modified run-data algorithm&#13;
Sclera boundary localization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107847">
                <text>Security challenges over the years has led to the need for an improvement in the traditional security approaches. This led to the advent of biometrics. Recently, among the biometric approaches, sclera has been an area of imense study. This is due to its accuracy; however, segmentation of the sclera has been a limiting factor to the application of this biometric trait. Several approaches have been proposed in literature but there is still the need to improve the segmentation accuracy. This study proposes the use of circular hough transform and a modified run-data based algorithm. The study also presented a sclera recognition system using the compound local binary pattern for features extraction and Manhattan distance for classification. The system produced a segmentation accuracy of 99.9% for sclera blood vessels, periocular and iris (SBVPI) sclera database and 100% for manually captured sclera database. The system produced an accuracy of 99.98 for SBVPI sclera database and 99.99% for manually captured sclera database.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107848">
                <text>Tunde Taiwo Adeniyi1, Oladele Tinuke Omolewa1, Jide Kehinde Adeniyi2</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="107849">
                <text>Journal homepage: http://telkomnika.uad.ac.id</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107850">
                <text>Feb 13, 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107851">
                <text>PERI IRAWAN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107852">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107853">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107854">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12893">
        <name>Biometrics Circular hough transfrom Compound local binary pattern Modified run-data algorithm Sclera boundary localization</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
