<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     naa a22        4500</leader>
  <controlfield tag="001">510809820</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180411083437.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">180411e20130501xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1134/S1064230713020020</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1134/S1064230713020020</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="4">
   <subfield code="a">The use of evolutionary programming based on training examples for the generation of finite state machines for controlling objects with complex behavior</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[A. Aleksandrov, S. Kazakov, A. Sergushichev, F. Tsarev, A. Shalyto]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">It is proposed to use evolutionary programming to generate finite state machines (FSMs) for controlling objects with complex behavior. The well-know approach in which the FSM performance is evaluated by simulation, which is typically time consuming, is replaced with comparison of the object's behavior controlled by the FSM with the behavior of this object controlled by a human. A feature of the proposed approach is that it makes it possible to deal with objects that have not only discrete but also continuous parameters. The use of this approach is illustrated by designing an FSM controlling a model aircraft executing a loop-the-loop maneuver.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Pleiades Publishing, Ltd., 2013</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Aleksandrov</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Kazakov</subfield>
   <subfield code="D">S.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Sergushichev</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Tsarev</subfield>
   <subfield code="D">F.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Shalyto</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Journal of Computer and Systems Sciences International</subfield>
   <subfield code="d">SP MAIK Nauka/Interperiodica</subfield>
   <subfield code="g">52/3(2013-05-01), 410-425</subfield>
   <subfield code="x">1064-2307</subfield>
   <subfield code="q">52:3&lt;410</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">52</subfield>
   <subfield code="o">11488</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1134/S1064230713020020</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1134/S1064230713020020</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Aleksandrov</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Kazakov</subfield>
   <subfield code="D">S.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Sergushichev</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Tsarev</subfield>
   <subfield code="D">F.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Shalyto</subfield>
   <subfield code="D">A.</subfield>
   <subfield code="u">St. Petersburg National Research University of Information Technologies, Mechanics, Optics, and Automation, St. Petersburg, Russia</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Journal of Computer and Systems Sciences International</subfield>
   <subfield code="d">SP MAIK Nauka/Interperiodica</subfield>
   <subfield code="g">52/3(2013-05-01), 410-425</subfield>
   <subfield code="x">1064-2307</subfield>
   <subfield code="q">52:3&lt;410</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">52</subfield>
   <subfield code="o">11488</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
