<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02508nam a2200277Ia 4500</leader>
  <controlfield tag="003">MX-MdCICY</controlfield>
  <controlfield tag="005">20260521091657.0</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">CICY</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">B-19288</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Optimizing the Endmembers Using Volume Invariant Constrained Model</subfield>
  </datafield>
  <datafield tag="490" ind1="0" ind2=" ">
    <subfield code="v">IEEE Transactions on Image Processing, 24(11), p.3441-3449, 2015</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">The linear mixture model (LMM)plays a crucial role in the spectral unmixing of hyperspectral data. Under the assumption of LMM, the solution with the minimum reconstruction error is considered to be the ideal endmember. However, for practical hyperspectral data sets, endmembers that enclose all the pixels are physically meaningless due to the effect of noise. Therefore, in many cases, it is not sufficient to consider only the reconstruction error, some constraints (for instance, volume constraint)need to be added to the endmembers. The two terms can be considered as serving two forces: minimizing the reconstruction error forces the endmembers to move outward and thus enlarges the volume of the simplex while the endmember constraint acts in the opposite direction by driving the endmembers to move inward so as to constrain the volume to be smaller. Many existing methods obtain their solution just by balancing the two contradictory forces. The solution acquired in this way can not only minimize the reconstruction error but also be physically meaningful. Interestingly, we find, in this paper, that the two forces are not completely contradictory with each other, and the reconstruction error can be further reduced without changing the volume of the simplex. And more interestingly, our method can further optimize the solution provided by all the endmember extraction methods (both endmember selection methods and endmember generation methods). After optimization, the final endmembers outperform the initial solution in terms of reconstruction error as well as accuracy. The experiments on simulated and real hyperspectral data verify the validation of our method.</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">HYPERSPECTRAL DATA</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ENDMEMBER</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">SIMPLEX</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">LMM</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">VOLUME</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Geng, X.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Sun, K.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Ji, L.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Zhao, Y.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Tang, H.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://drive.google.com/file/d/15jFRa4H5IRM_nAitYp008GqDmdIVqUbU/view?usp=drivesdk</subfield>
    <subfield code="z">Para ver el documento ingresa a Google con tu cuenta: @cicy.edu.mx</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">Loc</subfield>
    <subfield code="c">REF1</subfield>
  </datafield>
  <controlfield tag="008">250602s9999    xx |||||s2   |||| ||und|d</controlfield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">29364</subfield>
    <subfield code="d">29364</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">Loc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">F1</subfield>
    <subfield code="a">CICY</subfield>
    <subfield code="b">CICY</subfield>
    <subfield code="c">RE</subfield>
    <subfield code="d">2025-06-25</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">B-19288</subfield>
    <subfield code="r">2025-06-25 16:24:28</subfield>
    <subfield code="w">2025-06-25</subfield>
    <subfield code="y">REF1</subfield>
  </datafield>
</record>
