<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="19674" public="1" featured="0" 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://archives.christuniversity.in/items/show/19674?output=omeka-xml" accessDate="2026-04-29T06:40:01+00:00">
  <collection collectionId="16">
    <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="51377">
                <text>Conference Papers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</description>
  </itemType>
  <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="171039">
              <text>Decoupling Identification Method of Continuous Working Conditions of Diesel Engines Based on a Graph Self-Attention Network</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171040">
              <text>Decoupling; Diseal Engine; Graph Self-Attention Network (GSAN); Normal and Typical Scenario; Signal Preprocessing; Working Condition</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171041">
              <text>For diesel engine malfunction detection, machine learning-based intelligent detection approaches have made great strides, but some performance deterioration is also observed due to the significant ambient noise and the change in operating circumstances in the actual application situations. Diesel engine fault diagnostic models can be negatively impacted by complex and erratic working circumstances. Identifying the working condition can provide as a baseline for the current unit operating state, which is crucial information when trying to pinpoint the source of an issue. Many existing techniques for identifying operational states use power as an identifier, segmenting it into discrete intervals from which the current state's power may be derived using a classification model. However, the working condition characteristics should be constant, and defining it exclusively in terms of power would lead to the connection of speed and load elements. In this study, we offer a regular working situation model that is independent of speed and load characteristics, and we use a graph self-attention network to construct a model for identifying the working condition. On a diesel engine research bench, a vast amount of experimental data is acquired for training and testing models, including 32 different operating situations under normal and typical fault scenarios. The R2 adj values of 99.70% and 99.27% for normal and typical defect experimental data, correspondingly, demonstrate the efficacy of the suggested technique under the circumstance of uninformed nnerating situations.   2023 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171042">
              <text>Vijayasharathi N.; Selukar N.B.; Ganesh Kumar G.; Chauhan A.; Ramachandran L.; Ravindra Sonawane P.</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="171043">
              <text>7th International Conference on Electronics, Communication and Aerospace Technology, ICECA 2023 - Proceedings, pp. 49-54.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="171044">
              <text>Institute of Electrical and Electronics Engineers Inc.</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="171045">
              <text>2023-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="171046">
              <text>&lt;a href="https://doi.org/10.1109/ICECA58529.2023.10394998" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICECA58529.2023.10394998&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85186114491&amp;amp;doi=10.1109%2FICECA58529.2023.10394998&amp;amp;partnerID=40&amp;amp;md5=aca8e08490cab75b3074fef0024e217b" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85186114491&amp;amp;doi=10.1109%2fICECA58529.2023.10394998&amp;amp;partnerID=40&amp;amp;md5=aca8e08490cab75b3074fef0024e217b&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171047">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="171048">
              <text>ISBN: 979-835034060-0</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="171049">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171050">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="171051">
              <text>Conference paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="171052">
              <text>Vijayasharathi N., Panimalar Engineering College, Tamilnadu, Chennai, India; Selukar N.B., SGB Amravati University, Chemical Technology Department, Maharashtra, Amravati, India; Ganesh Kumar G., Kakatiya Institute of Technology and Science, Department of Mechanical Engineering, Telangana, Warangal, India; Chauhan A., Department of life sciences, Christ University Bangalore, Karnataka, India; Ramachandran L., R.M.K.Engineering College, Kavaraipettai, Tamilnadu, Tiruvallur, India; Ravindra Sonawane P., JSPM'S Rajarshi Shahu College of Engineering Tathawade, Mechanical Engineering, Maharashtra, Pune, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
