<?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=774&amp;output=omeka-xml&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-25T16:26:36+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>27</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10275" public="1" featured="1">
    <fileContainer>
      <file fileId="10288">
        <src>https://repository.horizon.ac.id/files/original/813a1f45f8649eca490473a5ac58f0bb.pdf</src>
        <authentication>2b19baa5bed9e998aecc32a43ed26655</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109859">
                <text>Navigating the digital shift: a service blueprint for coopetition technology-enabled networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109860">
                <text>Coopetition&#13;
Networks&#13;
SD logic&#13;
Service blueprint&#13;
Service science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109861">
                <text>This study addresses the gap in applying traditional service blueprint methodologies to technology-enabled coopetition networks characterized by simultaneous collaboration and competition among actors. Leveraging service science insights, it proposes an enhanced service blueprint framework designed for the complexities of digital coopetition. This framework introduces the cyber. Frontstage lane, physical backstage lane, and support stage lane aim to provide a holistic view of interactions, value co-creation processes, and resource allocations. Empirical validation within the Portuguese stone sector-a key player in the national economy-demonstrates the framework’s effectiveness in identifying network dysfunctions and its ease of use by industry professionals. Feedback confirms its relevance in capturing today’s coopetition environments’ multifaceted engagements and digital nuances. The study emphasizes adapting service blueprint methodology to better manage and innovate service processes in digital ecosystems. Future research should extend this framework’s application across various sectors and explore the integration of emerging technologies to optimize service delivery and value co-creation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109862">
                <text>Agostinho da Silva1,2, Antonio J. Marques Cardoso1</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="109863">
                <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="109864">
                <text>Jul 12, 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="109865">
                <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="109866">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109867">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109868">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10278" public="1" featured="1">
    <fileContainer>
      <file fileId="10291">
        <src>https://repository.horizon.ac.id/files/original/cc583db31b7c5479e4d5171293df90f3.pdf</src>
        <authentication>ee3e783fc5eb5fc4109b52d518dc3fe1</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109889">
                <text>MDI and PI XGBoost regression-based methods: regional best pricing prediction for logistics services</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109890">
                <text>Explainable artificial intelligence&#13;
Extreme gradient boosting&#13;
Mean decrease in impurity&#13;
Permutation importance&#13;
Retail price prediction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109891">
                <text>The logistics industry in Indonesia, with PT Pos Indonesia as the dominant player, is confronted with intense price competition. The challenge lies in establishing the most favorable price for regional logistics services in every region, with the aim of gaining a competitive edge and augmenting revenue. This intricate task encompasses local market conditions, competition, customer preferences, operational costs, and economic factors. To address this complexity, this study proposes the utilization of machine learning for price prediction. The price prediction model devised incorporates the extreme gradient boosting regression (XGBR), support vector machine (SVM), random forest, and logistics regression algorithms. This research contributes to the field by employing mean decrease in impurity (MDI) and permutation importance (PI) to elucidate how machine learning models facilitate optimal price predictions. The findings of this study can assist company management in enhancing their comprehension of how to make informed pricing decisions. The test results demonstrate values of 0.001, 0.005, 0.458, 0.009, and 0.9998. By employing machine learning techniques and explanatory models, PT Pos Indonesia can more accurately determine optimal prices in each region, bolster profits, and effectively compete in the expanding regional market.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109892">
                <text>Agus Purnomo1, Aji Gautama Putrada2, Roni Habibi3, Syafrianita4</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="109893">
                <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="109894">
                <text>May 26, 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="109895">
                <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="109896">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109897">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109898">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13158">
        <name>Explainable artificial intelligence Extreme gradient boosting Mean decrease in impurity Permutation importance Retail price prediction</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10260" public="1" featured="1">
    <fileContainer>
      <file fileId="10273">
        <src>https://repository.horizon.ac.id/files/original/361a80b737b1e0d203aec5c48636cbcb.pdf</src>
        <authentication>694d30b0eb6aa6cbd6c7dc62fe9a24b6</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109709">
                <text>Feature selection to improve distributed denial of service detection accuracy using hybrid N-Gram heuristic techniques</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109710">
                <text>Chi-square distance&#13;
Distributed denial of service&#13;
Malware&#13;
N-Grams&#13;
Payload</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109711">
                <text>Distributed denial of service (DDoS) attacks servers and computers in various ways, such as flooding traffic. There are three DDoS detection methods, namely anomaly-based, pattern-based and heuristic-based. However, pattern-based methods cannot detect recent attacks, while anomaly-based methods have low accuracy and relatively high false positives. This research proposes increasing accuracy using a heuristic-based DDoS detection method and a new feature. The combination of CSDPayload+N-Gram and CSPayload+N-Gram features is called hybrid N-Gram, which is analysed on four datasets: CIC2017, CIC2019, MIB-2016, and H2NPayload. Next, calculate Chi-square distance (CSD) and cosine similarity (CS) using the N-Gram frequency value results. Subsequently, compute Pearson Chi-square using the N-Gram frequency value results. Compare the CSDPayload+N-Gram and CSPayload+N-Gram, along with the Pearson Chi-square value, to classify it as either DDoS or not. Finally, feature selection based on weight correlation and payload classification employs machine learning algorithms: support vector machine (SVM), K-nearest neighbors (KNN), and neural network (NN). The average accuracy rate for detecting DDoS attacks across four datasets, utilising the CSDPayload+4-Gram and CSPayload+4-Gram features with the SVM algorithm, is 99.71%, which surpasses the accuracy achieved by using KNN (96.22%) and NNs (99.50%) imitation. Thus, the best algorithm for detecting DDoS is SVM with hybrid 4-Gram.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109712">
                <text>Andi Maslan1, Abdul Hamid2, Dedy Fitriawan3, Anggia Dasa Putri1, Tukino1</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="109713">
                <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="109714">
                <text>May 26, 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="109715">
                <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="109716">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109717">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109718">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10281" public="1" featured="1">
    <fileContainer>
      <file fileId="10294">
        <src>https://repository.horizon.ac.id/files/original/448676fa5ba2c0343052ab3c6318dedb.pdf</src>
        <authentication>3a93fb22d44caa02014055712e312efc</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109919">
                <text>The causal loop diagram model of traceability system rental equipment in oil and gas supporting companies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109920">
                <text>Causal loop diagram&#13;
Oil and gas support company&#13;
Rental equipment&#13;
System thinking&#13;
Traceability</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109921">
                <text>Traceability in equipment rental systems enhances security, reliability, and operational transparency by providing the ability to accurately track leased equipment. Challenges in implementing traceability include difficulties in collecting accurate data, the absence of standardized recording practices, and the complexities of integrating technology to ensure complete tracking. This research aims to identify variables affecting the traceability system thinking to improve its efficiency in ongoing business processes. A qualitative descriptive approach is used to offer comprehensive insights into implementing traceability in equipment rental systems, focusing on oil and gas support companies. The study employs the causal loop diagram (CLD) method to dynamically map and identify traceability process variables. Findings show that traceability enables more precise tracking of equipment movement and usage, enhancing inventory management and streamlining maintenance. The CLD method reveals the dynamic relationships between system variables such as equipment availability, maintenance needs, and customer satisfaction, which guide continuous improvement. These results provide stakeholders with valuable insights for optimizing efficiency and service quality in equipment rental operations, particularly in oil and gas support companies. Enhanced traceability can significantly boost operational effectiveness and customer satisfaction.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109922">
                <text>Asep Endih Nurhidayat1,2, Rina Fitriana2,3,4, Didien Suhardini2,3,4, Asri Nugrahanti5</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="109923">
                <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="109924">
                <text>Jul 12, 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="109925">
                <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="109926">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109927">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109928">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13159">
        <name>Causal loop diagram Oil and gas support company Rental equipment System thinking Traceability</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10266" public="1" featured="1">
    <fileContainer>
      <file fileId="10279">
        <src>https://repository.horizon.ac.id/files/original/66bf0f5f5c81e159cf77fc893dec3775.pdf</src>
        <authentication>0f6bd1d084ed6cf5d2f324b3b0b96465</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109769">
                <text>Performance analysis of circular polarization X-band microstrip patch antenna combined with conical horn</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109770">
                <text>Circular polarization&#13;
Conical horn&#13;
Microstrip antenna&#13;
Parabolic reflector&#13;
Satellite&#13;
X-band</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109771">
                <text>A ground station antenna system features a conical horn attached to a microstrip antenna as an alternate receiving feed antenna. The proposed microstrip antenna has circular polarization and operates in the X-band. The far-field parameters of the antenna are measured after developing and simulating the combination of a conical horn and a microstrip antenna. The modeling results for a microstrip antenna with a conical horn offer a working bandwidth of 930 MHz, spanning frequencies 7.44 GHz to 8.37 GHz. The axial ratio measurements for a microstrip antenna joined with a conical horn produce a working bandwidth of 150 MHz, covering frequencies ranging from 7.72 GHz to 7.87 GHz. The conical horn is attached to a microstrip antenna and has a gain of 15.1 dB. The proposed antenna is designed to meet ground station antenna requirements by pairing it with a parabolic reflector with a diameter of 3.7 meters. The primary focus antenna of the proposed design was chosen. The feed antenna and parabolic reflector should be positioned at a focus point distance of 1110 mm for a total gain of 38.9 dB at 7.8 GHz frequency. The proposed antenna can be applied on X-band remote sensing ground stations as a receiving antenna.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109772">
                <text>B. Pratiknyo Adi Mahatmanto1, Dedi Irawadi1, Hidayat Gunawan1, Nugroho Widi Jatmiko1, Dinari Nikken Sulastrie Sirin1, Supriyono1, Suhermanto1, Bambang Dewandaru2, Catur Apriono3</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="109773">
                <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="109774">
                <text>May 26, 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="109775">
                <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="109776">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109777">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109778">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10265" public="1" featured="1">
    <fileContainer>
      <file fileId="10278">
        <src>https://repository.horizon.ac.id/files/original/651f49c79c34a4e252b6f8bdb1c5e287.pdf</src>
        <authentication>7d52c21b65906dc0f4a3db646db738ae</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109759">
                <text>Analysis comparison, calibration, and application of low-cost soil moisture in smart agriculture based on internet of things</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109760">
                <text>Calibration&#13;
Capacitive sensor&#13;
Internet of things&#13;
Resistive sensor&#13;
Soil moisture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109761">
                <text>The gravimetric method is one of the most accurate for determining soil water content (SWC). Several low-cost sensors have been developed to simplify measuring water content in soil by measuring soil moisture. However, the sensor must be calibrated to determine soil moisture parameters accurately. In this research, comparative analysis, and calibration of resistive and capacitive low-cost sensors were carried out. The calibration method for each sensor uses the gravimetric water content (GWC) and volumetric water content (VWC) methods. Measuring changes in SWC using sensors is performed in real time based on internet of things (IoT). Based on the measurements of the capacitive, resistive type 1, and resistive type 2 sensors with three repetitions, the linear regression R2 values were obtained at 0.980, 0.827, and 0.942, respectively. Furthermore, a stability test is carried out to see how stable the sensor is when making measurements over a long period. The result is that the capacitive, resistive type 1, and resistive type 2 sensors have errors 1.971×10-4, 7.001×10-4, and 6.270×10-4. Based on the results obtained, capacitive sensors have the highest level of accuracy and stability. Furthermore, capacitive sensors are applied to IoT-based agriculture with long range (LoRa) as communication data.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109762">
                <text>Beny Agustirandi1, Inayatul Inayah1,2, Nina Siti Aminah1, Maman Budiman1</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="109763">
                <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="109764">
                <text>May 26, 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="109765">
                <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="109766">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109767">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109768">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13149">
        <name>Calibration Capacitive sensor Internet of things Resistive sensor Soil moisture</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10269" public="1" featured="1">
    <fileContainer>
      <file fileId="10282">
        <src>https://repository.horizon.ac.id/files/original/89cd16c503b35f087c5f41c621233444.pdf</src>
        <authentication>10cc90a655ad834366207c9a0c8c5291</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109799">
                <text>Smart hydroponic agriculture using genetic algorithm based k-nearest neighbors</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109800">
                <text>Genetic algorithms&#13;
Internet of things&#13;
K-nearest neighbor&#13;
Machine learning&#13;
Raspberry Pi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109801">
                <text>In this research, researcher has implemented supervised machine learning, namely k-nearest neighbor (k-NN) which is optimized using genetic algorithms, and the internet of things (IoT) on the nutrient film technique (NFT) hydroponic system. The aim of this research is to improve the accuracy of classification of nutrient and light conditions in NFT system, and evaluating the harvest of hydroponic farming. The dataset was obtained by observing and recording nutritional and light conditions using sensors for 35 days during the growing period of lettuce in the NFT system, thus obtaining 1,680 data. Then, a training dataset is created based on that dataset. The system architecture is divided into 3 parts, namely the sensor system, data processing, and actuator system. The conclusion of this research is the IoT can be used to monitor the nutritional and light conditions of NFT system in real time and automatic control actions can be carried out using actuators controlled by the Raspberry Pi, the impact of applying the k-NN algorithm and the genetic algorithms is the accuracy of classifying nutritional and light conditions is 92%, the lettuce in a NFT system controlled by the system grow better than the lettuce in a NFT system controlled manually.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109802">
                <text>Budi Sutrisno1, Nico Surantha1,2</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="109803">
                <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="109804">
                <text>May 26, 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="109805">
                <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="109806">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109807">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109808">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13152">
        <name>Genetic algorithms Internet of things K-nearest neighbor Machine learning Raspberry Pi</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10262" public="1" featured="1">
    <fileContainer>
      <file fileId="10275">
        <src>https://repository.horizon.ac.id/files/original/fa3008cc2df9681371d32f6f06c9e40a.pdf</src>
        <authentication>eaf175d874dfe2fc3e7834fa866fd64c</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109729">
                <text>Video semantic segmentation with low latency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109730">
                <text>Convolutional neural network&#13;
Decision network&#13;
FlowNet&#13;
Latency&#13;
Object detection&#13;
SegNet&#13;
Semantic segmentation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109731">
                <text>Recent advances in computer vision and deep learning algorithms have yielded intriguing results. It can perform tasks previously requiring human eyes and brains. Semantic video segmentation for autonomous cars is difficult due to the high cost, low latency, and performance requirements of convolutional neural networks (CNNs). Deep learning architectures like SegNet and FlowNet 2.0 on the Cambridge-driving labeled video database (CamVid) dataset enable low-latency pixel-wise semantic segmentation of video features. Because it uses SegNet and FlowNet topologies, it is ideal for practical applications. The decision network chooses an optical flow or segmentation network for an image frame based on the expected confidence score. Combining this decision-making method with adaptive scheduling of the key frame approach can speed up the process. ResNet50 SegNet has a “54.27%” mean intersection over union (MIoU) and a “19.57” average FPS. In addition to decision network and adaptive key frame sequencing, FlowNet2.0 increased graphics processing unit (GPU) frame processing per second to “30.19” with a MIoU of “47.65%”. The GPU is used “47.65%” of the time. This performance gain illustrates that the video semantic segmentation network is faster without sacrificing quality.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109732">
                <text>Channappa Gowda D. V., Kanagavalli R.</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="109733">
                <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="109734">
                <text>Mar 26, 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="109735">
                <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="109736">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109737">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109738">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13147">
        <name>Convolutional neural network Decision network FlowNet Latency Object detection SegNet Semantic segmentation</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10277" public="1" featured="1">
    <fileContainer>
      <file fileId="10290">
        <src>https://repository.horizon.ac.id/files/original/b55be8f9f40a1204ee647340310b83a1.pdf</src>
        <authentication>2b19baa5bed9e998aecc32a43ed26655</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109879">
                <text>Augmented reality in customer experience: systematic review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109880">
                <text>Attitude&#13;
Augmented reality&#13;
Consumer experience&#13;
Customer experience&#13;
Customer satisfaction&#13;
Interactivity&#13;
Systematic review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109881">
                <text>Augmented reality (AR) is an emerging technology that offers the opportunity to explore a new way of shopping in the customer experience, showcasing its benefits, such as the superimposition of virtual elements in a physical environment or the high degree of interactivity provided by this technology. Despite its great potential to satisfy customer needs, the evaluation of the customer experience has not been fully studied. The main of this study is to identify the constructs that influence customer experience using the systematic review technique. A total of 88 studies published between 2016 and 2021, which relate to customer experience, were identified. Relevant information, such as the definitions of AR and customer experience, and the constructs that various authors use to assess customer experience, was extracted. The results of the review indicate that five fundamental constructs–attitude, interactivity, customer satisfaction, purchase intention, and hedonic value–are used to assess customer experience. These results contribute to a better understanding of the customer experience with AR.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109882">
                <text>Christian Cervantes1, Sussy Bayona-Oré2, Nicolás Pintado Torre1</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="109883">
                <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="109884">
                <text>May 26, 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="109885">
                <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="109886">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109887">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109888">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13157">
        <name>Attitude Augmented reality Consumer experience Customer experience Customer satisfaction Interactivity Systematic review</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10272" public="1" featured="1">
    <fileContainer>
      <file fileId="10285">
        <src>https://repository.horizon.ac.id/files/original/fcac93a3c41141d9a0e6fb344678c031.pdf</src>
        <authentication>5c582d0a68652a872627b9131c9c8185</authentication>
      </file>
    </fileContainer>
    <collection collectionId="774">
      <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="109708">
                  <text>VOL. 22, NO.5 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="109829">
                <text>Class-G series audio power amplifier for subwoofer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109830">
                <text>Audio power amplifier&#13;
Class-AB&#13;
Class-G&#13;
Power efficiency&#13;
Subwoofer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109831">
                <text>An audio power amplifier is an electronic device used to amplify a small signal&#13;
source power at the input into a large signal power at the output that is speaker.&#13;
In general, audio power amplifiers use class-AB amplifiers. In the process of&#13;
amplifying the signal power, there will be power losses in the amplifiers which&#13;
results in relatively lower amplifier power efficiency because there is a difference&#13;
between the supply and output voltage levels. In this paper a class-G series&#13;
audio power amplifier for subwoofers is designed to minimize these power&#13;
losses and increase the power efficiency of the amplifier. The designed amplifier&#13;
voltage supply is 40 V with a maximum output power of 80 W at an 8 Ω&#13;
load. The amplifier has frequency response from 20–200 Hz and gain twice.&#13;
Realization of the power amplifier and measurements were carried out using&#13;
the circuit maker simulator, and the measurement results of the class-G power&#13;
amplifier were compared with the class-AB power amplifier. The measurement&#13;
results show that both power amplifiers meet the design specifications. The proposed&#13;
class-G amplifier has 0.14% larger total harmonic distortion (THD) but&#13;
has 10.4% greater power efficiency advantages over the class-AB amplifier.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109832">
                <text>Class-G series audio power amplifier for subwoofer</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="109833">
                <text>Journal homepage: http://journal.uad.ac.id/index.php/TELKOMNIKA</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="109834">
                <text>May 26, 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="109835">
                <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="109836">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109837">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109838">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="13155">
        <name>Audio power amplifier Class-AB Class-G Power efficiency Subwoofer</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
