<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">465742424</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180323111811.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170327e19901001xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/BF00935000</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/BF00935000</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="4">
   <subfield code="a">The Navy's new standard digital signal processor, the AN/UYS-2</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[G. Melcher, G. Thomas, D. Kaplan]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Current Navy signal processing requirements range from tens of millions to hundreds of millions of multiply-add operations per second. It is expected that these requirements will increase tenfold within the next ten years. To accommodate these expanding requirements, the Navy is building the Signal Processor (AN/UYS-2). The AN/UYS-2 design is driven by the fact that it is the Navy standard signal processor. Being a stantard, it must satisfy more requirements than just high throughput. It must be programmable, modular, expandable, flexible supportable, reliable and provide this capability for the next 20 years to support existing and future users. In order to make it programmable (and therefore reduce the total life cycle ownership cost), the AN/UYS-2 utilizes a Navy developed signal processing graph language methodology called PGM. The implementation of PGM on AN/UYS-2, provides the AN/UYS-2 user with a convenient and cost effective way of specifying the signal proccessing algorithms to be executed for a given application. The AN/UYS-2 desgin approach is to implement PGM and to develop a modular, multiprocessor that could meet a wide range of air, sea, and shore signal processing applications. In order to meet this requirement, a hybrid control-flow/data-flow architecture was chosen to enable evolutionary technology infusion. VLSI component technology is required to implement the primary processing engine in the architecture. The AN/UYS-2 architecture consists of a variable combination of multiple types of Functional Elements (FEs), a data transfer network, a control bus, and a built-in-test (BIT) control bus. This paper provides a review of AN/UYS-2 basic design and growth potential.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Kluwer Academic Publishers, 1990</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Melcher</subfield>
   <subfield code="D">G.</subfield>
   <subfield code="u">Space and Naval Warfare Systems Command, U.S. Navy, Washington, DC</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Thomas</subfield>
   <subfield code="D">G.</subfield>
   <subfield code="u">Naval Sea Systems Command, U.S. Navy, Washington, DC</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Kaplan</subfield>
   <subfield code="D">D.</subfield>
   <subfield code="u">Naval Sea Systems Command, U.S. Navy, Washington, DC</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Journal of VLSI Signal Processing</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">2/2(1990-10-01), 103-109</subfield>
   <subfield code="x">0922-5773</subfield>
   <subfield code="q">2:2&lt;103</subfield>
   <subfield code="1">1990</subfield>
   <subfield code="2">2</subfield>
   <subfield code="o">11265</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/BF00935000</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.1007/BF00935000</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">Melcher</subfield>
   <subfield code="D">G.</subfield>
   <subfield code="u">Space and Naval Warfare Systems Command, U.S. Navy, Washington, DC</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">Thomas</subfield>
   <subfield code="D">G.</subfield>
   <subfield code="u">Naval Sea Systems Command, U.S. Navy, Washington, DC</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">Kaplan</subfield>
   <subfield code="D">D.</subfield>
   <subfield code="u">Naval Sea Systems Command, U.S. Navy, Washington, DC</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 VLSI Signal Processing</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">2/2(1990-10-01), 103-109</subfield>
   <subfield code="x">0922-5773</subfield>
   <subfield code="q">2:2&lt;103</subfield>
   <subfield code="1">1990</subfield>
   <subfield code="2">2</subfield>
   <subfield code="o">11265</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>
