January 9, 2018 Journal article Open Access

Bertolazzi, Enrico; Biral, Francesco; Ragni, Matteo

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <controlfield tag="005">20200120173758.0</controlfield>
  <controlfield tag="001">1139258</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DEPARTMENT OF INDUSTRIAL ENGINEERING, UNIVERSITY OF TRENTO</subfield>
    <subfield code="a">Biral, Francesco</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DEPARTMENT OF INDUSTRIAL ENGINEERING, UNIVERSITY OF TRENTO</subfield>
    <subfield code="a">Ragni, Matteo</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">244476</subfield>
    <subfield code="z">md5:00ea1b7b626924df565818f2a5cbfb09</subfield>
    <subfield code="u">https://zenodo.org/record/1139258/files/AF11.2018.79.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018-01-09</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-acta-futura</subfield>
    <subfield code="p">user-esa-act</subfield>
    <subfield code="o">oai:zenodo.org:1139258</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="c">79-90</subfield>
    <subfield code="p">Acta Futura</subfield>
    <subfield code="n">11</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">DEPARTMENT OF INDUSTRIAL ENGINEERING, UNIVERSITY OF TRENTO</subfield>
    <subfield code="a">Bertolazzi, Enrico</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">GTOC 9: Results from University of Trento (team ELFMAN)</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-acta-futura</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-esa-act</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">http://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;The GTOC9 competition requires the design of a sequence of missions to remove debris from the LEO orbit. A mission is a sequence of transfer of the spacecraft from one debris&amp;nbsp;to another. Both missions and transfer must fulfill a set of constraints. The work presents the procedures to develop a solution for the GTOC9 problem (i.e the mission sequence) that does not violate constraints.The solution is obtained through an evolutionary algorithm that combines pre-computed basic missions stored in a database. The main objective of the algorithm is to minimize the overall cost of the solution, in order to maximize the competition&lt;br&gt;
score. The database of pre-computed missions is derived by connecting transfers stored in a database of transfers, through a combinatorial approach that considers the problem constraints. The database of transfer is formulated through&lt;br&gt;
the solution of a constrained minimization problem upon the control action (the magnitude of the overall impulsive velocity changes &lt;span class="math-tex"&gt;\(\Delta\)&lt;/span&gt;V ). Only a subset of all possible transfers (selected on the basis of acceptable &lt;span class="math-tex"&gt;\(\Delta\)&lt;/span&gt; V ), enters in the database.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.1139257</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.1139258</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
</record>