Patch: Fix Manual Mistakes
Jeffrey Oldham
oldham at codesourcery.com
Tue Jul 30 17:11:33 UTC 2002
2002-Jul-30 Jeffrey D. Oldham <oldham at codesourcery.com>
* index.html: Fix incorrect hyperlink.
* manual/README.txt: Update tips on how to compile the
manual.
* manual/introduction.xml: Remove the duplicate history
section.
* manual/preface.xml: Replace existing history section with
one that is indexed.
Tested by viewing the HTML and remaking the manual on Linux RedHat 7.2.
Approved by Jim Crotinger
Thanks,
Jeffrey D. Oldham
oldham at codesourcery.com
-------------- next part --------------
Index: index.html
===================================================================
RCS file: /home/pooma/Repository/r2/docs/index.html,v
retrieving revision 1.1
diff -c -p -r1.1 index.html
*** index.html 2001/03/19 16:11:13 1.1
--- index.html 2002/07/30 17:04:19
*************** the new material, as well as the origina
*** 20,26 ****
<blockquote>
<h4><a href="parallelism.html">Parallelism Models: Messaging and Threads</a></h4>
! <h4><a href="layout.html">Layouts</a></h4>
<h4><a href="ParticlesDoc.txt">New description of Particles</a></h4>
<h4><a href="tut-11.html">Text I/O</a></h4>
<h4><a href="tut-12.html">Object I/O</a></h4>
--- 20,26 ----
<blockquote>
<h4><a href="parallelism.html">Parallelism Models: Messaging and Threads</a></h4>
! <h4><a href="Layout.html">Layouts</a></h4>
<h4><a href="ParticlesDoc.txt">New description of Particles</a></h4>
<h4><a href="tut-11.html">Text I/O</a></h4>
<h4><a href="tut-12.html">Object I/O</a></h4>
Index: manual/README.txt
===================================================================
RCS file: /home/pooma/Repository/r2/docs/manual/README.txt,v
retrieving revision 1.1
diff -c -p -r1.1 README.txt
*** manual/README.txt 2002/02/01 17:43:13 1.1
--- manual/README.txt 2002/07/30 17:04:19
*************** If you have having trouble with:
*** 37,42 ****
--- 37,43 ----
DocBook stylesheets.
Modify pooma.xml's DOCTYPE line to specify the location of the
DocBook docbookx.dtd.
+ Modify $(XML) in Makefile to the correct location for xml.dcl.
jadetex: Ensure it has large enough TeX capacities. See
http://jadetex.sourceforge.net.
Index: manual/introduction.xml
===================================================================
RCS file: /home/pooma/Repository/r2/docs/manual/introduction.xml,v
retrieving revision 1.7
diff -c -p -r1.7 introduction.xml
*** manual/introduction.xml 2002/01/30 23:51:45 1.7
--- manual/introduction.xml 2002/07/30 17:04:19
*************** while (iterA != A.end()) {
*** 426,613 ****
&poomatoolkit; is low-risk software.</para>
</section>
-
- <section id="introduction-pooma_history">
- <title>History of &pooma;</title>
-
- <indexterm zone="introduction-pooma_history">
- <primary>&pooma;</primary>
- <secondary>history</secondary>
- </indexterm>
- <indexterm zone="introduction-pooma_history">
- <primary>Los Alamos National Laboratory</primary>
- </indexterm>
-
- <para>The &poomatoolkit; was developed at Los Alamos National
- Laboratory to assist nuclear fusion
- <indexterm>
- <primary>fusion</primary>
- </indexterm>
- and fission
- <indexterm>
- <primary>fission</primary>
- </indexterm>
- research.
- In 1994, the &toolkit; grew out of the <application
- class='software'>Object-Oriented Particle Simulation</application>
- <indexterm>
- <primary>Object-Oriented Particle Simulation Library</primary>
- </indexterm>
- Class Library developed for particle-in-cell simulations. The goals
- of the Framework, as it was called at the time, were driven by the
- Numerical Tokamak's
- <indexterm>
- <primary>Tokamak</primary>
- </indexterm>
- <quote>Parallel Platform Paradox</quote>:
- <blockquote>
- <para>The average time required to implement a moderate-sized
- application on a parallel computer architecture is equivalent to
- the half-life of the latest parallel supercomputer.</para>
- </blockquote>
- <indexterm>
- <primary>Parallel Platform Paradox</primary>
- </indexterm>
- The framework's goal of being able to quickly write efficient
- scientific code that could be run on a wide variety of platforms
- remains unchanged today. Development, mainly at the
- Advanced Computing Laboratory
- <indexterm>
- <primary>Los Alamos National Laboratory</primary>
- <secondary>Advanced Computing Laboratory</secondary>
- </indexterm>
- at Los Alamos, proceeded rapidly. A matrix solver application was
- written using the framework.
- <!-- FIXME: Add citation to pooma-sc95. -->
- Support for hydrodynamics,
- <indexterm>
- <primary>hydrodynamics</primary>
- </indexterm>
- Monte Carlo simulations,
- <indexterm>
- <primary>Monte Carlo simulation</primary>
- </indexterm>
- and molecular dynamics
- <indexterm>
- <primary>molecular dynamics modeling</primary>
- </indexterm>
- modeling soon followed.</para>
-
- <para id="introduction-pooma_history-asci">
- By 1998, &pooma; was part of the U.S. Department of
- Energy's
- <indexterm>
- <primary>Department of Energy</primary>
- </indexterm>
- Accelerated Strategic Computing Initiative
- (<acronym>ASCI</acronym>).
- <indexterm zone="introduction-pooma_history-asci">
- <primary>Department of Energy</primary>
- <secondary>Accelerated Strategic Computing Initiative</secondary>
- </indexterm>
- <indexterm>
- <primary>Accelerated Strategic Computing Initiative</primary>
- <see>Department of Energy, Accelerated Strategic Computing Initiative.</see>
- </indexterm>
- The Comprehensive Test Ban Treaty
- <indexterm>
- <primary>Comprehensive Test Ban Treaty</primary>
- </indexterm>
- forbid
- nuclear weapons testing so they were instead simulated using
- computers. <acronym>ASCI</acronym>'s goal was to radically advance
- the state of the art in high-performance computing and numerical
- simulations so the nuclear weapon simulations could use 100-teraflop
- parallel computers. A linear accelerator code <application
- class='software'>linac</application> and a Monte Carlo neutron
- transport code <application class='software'>MC++</application> were
- among the codes written.
- <!-- FIXME: Add citation to pooma-siam98. -->
- </para>
-
- <para>&pooma; 2 involved a new conceptual framework and a
- complete rewriting of the source code to improve performance. The
- <!-- FIXME: Add a citation to iscope98.pdf. -->
- &array; class
- <indexterm>
- <primary>&array;</primary>
- </indexterm>
- was introduced with its use of &engine;s,
- <indexterm>
- <primary>&engine;</primary>
- </indexterm>
- separating
- container use from container storage. A new asynchronous scheduler
- permitted out-of-order execution
- <indexterm>
- <primary>out-of-order evaluation</primary>
- </indexterm>
- to improve cache coherency.
- Incorporating the <application class="software">Portable
- Expression Template Engine</application> (<acronym>PETE</acronym>)
- <indexterm>
- <primary>&pete;</primary>
- </indexterm>
- permitted faster loop execution. Soon, container views
- <indexterm>
- <primary>container</primary>
- <secondary>view</secondary>
- </indexterm>
- and
- <type>ConstantFunction</type>
- <indexterm>
- <primary>&engine;</primary>
- <secondary><type>ConstantFunction</type></secondary>
- </indexterm>
- and <type>IndexFunction</type>
- <indexterm>
- <primary>&engine;</primary>
- <secondary><type>IndexFunction</type></secondary>
- </indexterm>
- &engine;s were added. Release 2.1.0 included &field;s
- <indexterm>
- <primary>&field;</primary>
- </indexterm>
- with
- their spatial extent and &dynamicarray;s
- <indexterm>
- <primary>&dynamicarray;</primary>
- </indexterm>
- with the ability to
- dynamically change domain size. Support for particles and
- their interaction with &field;s were added. The &pooma; messaging
- implementation was revised in release 2.3.0. Use of the
- &cheetah; Library
- <indexterm>
- <primary>&cheetah;</primary>
- </indexterm>
- separated &pooma; from the actual messaging
- library used, and support for applications running on clusters of
- computers was added. <ulink
- url="http://www.codesourcery.com/">CodeSourcery, LLC</ulink>,
- <indexterm>
- <primary>CodeSourcery, LLC</primary>
- </indexterm>
- and
- <ulink url="http://www.proximation.com/">Proximation, LLC</ulink>,
- <indexterm>
- <primary>Proximation, LLC</primary>
- </indexterm>
- took
- over &pooma; development from Los Alamos National Laboratory.
- During the past two years, the &field;
- abstraction
- <indexterm>
- <primary>&field;</primary>
- </indexterm>
- and implementation was improved to increase its
- flexibility, add support for multiple values and materials in the
- same cell, and permit lazy evaluation.
- <indexterm>
- <primary>lazy evaluation</primary>
- </indexterm>
- Simultaneously, the
- execution speed of the inner loops was greatly increased.</para>
- </section>
-
</chapter>
--- 426,429 ----
Index: manual/preface.xml
===================================================================
RCS file: /home/pooma/Repository/r2/docs/manual/preface.xml,v
retrieving revision 1.2
diff -c -p -r1.2 preface.xml
*** manual/preface.xml 2002/03/04 23:48:09 1.2
--- manual/preface.xml 2002/07/30 17:04:19
***************
*** 281,350 ****
</section>
! <section id="preface-pooma_history">
<title>History of &pooma;</title>
<para>The &poomatoolkit; was developed at Los Alamos National
! Laboratory to assist nuclear fusion and fission research.
! In 1994, it grew out of the <application
class='software'>Object-Oriented Particle Simulation</application>
! Class Library developed for particle-in-cell simulations. The
! goals of the Framework, as it was called at the time, were driven
! by the Numerical Tokamak's <quote>Parallel Platform
! Paradox</quote>:<blockquote>
! <para>The average time required to implement a moderate-sized
! application on a parallel computer architecture is equivalent to
! the half-life of the latest parallel supercomputer.</para>
! </blockquote>The framework's goal of being able to quickly write efficient
! scientific programs that could be run on a wide variety of platforms
! remains unchanged today. Development, mainly at the Advanced
! Computing Laboratory at Los Alamos, proceeded rapidly. A matrix
! solver application was written using the framework. <!-- FIXME:
! Add citation to pooma-sc95. --> Support for hydrodynamics, Monte
! Carlo simulations, and molecular dynamics modeling soon
! followed.</para>
! <para id="preface-pooma_history-asci">By 1998, &pooma;
! was part of the U.S. Department of Energy's Accelerated Strategic
! Computing Initiative (<acronym>ASCI</acronym>). The Comprehensive
! Test Ban Treaty forbid nuclear weapons testing so they were instead
! simulated using computers. <acronym>ASCI</acronym>'s goal was to
! radically advance the state of the art in high-performance
! computing and numerical simulations so the nuclear weapon
! simulations could use 100-teraflop parallel computers. The linear
! accelerator code <application class='software'>linac</application>
! and the Monte Carlo neutron transport code <application
! class='software'>MC++</application> were among the codes written.
! <!-- FIXME: Add citation to pooma-siam98. --></para>
<para>&pooma; 2 involved a new conceptual framework and a
complete rewriting of the source code to improve performance. The
! <!-- FIXME: Add a citation to iscope98.pdf. --> &array; class was
! introduced with its use of engines, separating container use from
! container storage. A new asynchronous scheduler permitted
! out-of-order execution to improve cache coherency. Incorporating
! the <application class="software">Portable Expression Template
! Engine</application> (<acronym>PETE</acronym>) permitted faster
! loop execution. Soon, container views and
! <type>ConstantFunction</type> and <type>IndexFunction</type>
! &engine;s were added. Release 2.1.0 included &field;s with
! their spatial extent and &dynamicarray;s with the ability to
! dynamically change domain size. Support for particles and their
! interaction with &field;s were added. The &pooma; messaging
implementation was revised in release 2.3.0. Use of the
! &cheetah; Library separated &pooma; from the actual messaging
library used, and support for applications running on clusters of
computers was added. <ulink
! url="http://www.codesourcery.com/">CodeSourcery, LLC</ulink>, and
<ulink url="http://www.proximation.com/">Proximation, LLC</ulink>,
! took over &pooma; development from Los Alamos National Laboratory.
! During the past two years, the &field; abstraction and
! implementation was improved to increase its flexibility, add
! support for multiple values and materials in the same cell, and
! permit lazy evaluation. Simultaneously, the execution speed of the
! inner loops was greatly increased.</para>
</section>
-
<section id="preface-acknowledgements">
<title>Acknowledgements</title>
--- 281,468 ----
</section>
! <section id="introduction-pooma_history">
<title>History of &pooma;</title>
+ <indexterm zone="introduction-pooma_history">
+ <primary>&pooma;</primary>
+ <secondary>history</secondary>
+ </indexterm>
+ <indexterm zone="introduction-pooma_history">
+ <primary>Los Alamos National Laboratory</primary>
+ </indexterm>
+
<para>The &poomatoolkit; was developed at Los Alamos National
! Laboratory to assist nuclear fusion
! <indexterm>
! <primary>fusion</primary>
! </indexterm>
! and fission
! <indexterm>
! <primary>fission</primary>
! </indexterm>
! research.
! In 1994, the &toolkit; grew out of the <application
class='software'>Object-Oriented Particle Simulation</application>
! <indexterm>
! <primary>Object-Oriented Particle Simulation Library</primary>
! </indexterm>
! Class Library developed for particle-in-cell simulations. The goals
! of the Framework, as it was called at the time, were driven by the
! Numerical Tokamak's
! <indexterm>
! <primary>Tokamak</primary>
! </indexterm>
! <quote>Parallel Platform Paradox</quote>:
! <blockquote>
! <para>The average time required to implement a moderate-sized
! application on a parallel computer architecture is equivalent to
! the half-life of the latest parallel supercomputer.</para>
! </blockquote>
! <indexterm>
! <primary>Parallel Platform Paradox</primary>
! </indexterm>
! The framework's goal of being able to quickly write efficient
! scientific code that could be run on a wide variety of platforms
! remains unchanged today. Development, mainly at the
! Advanced Computing Laboratory
! <indexterm>
! <primary>Los Alamos National Laboratory</primary>
! <secondary>Advanced Computing Laboratory</secondary>
! </indexterm>
! at Los Alamos, proceeded rapidly. A matrix solver application was
! written using the framework.
! <!-- FIXME: Add citation to pooma-sc95. -->
! Support for hydrodynamics,
! <indexterm>
! <primary>hydrodynamics</primary>
! </indexterm>
! Monte Carlo simulations,
! <indexterm>
! <primary>Monte Carlo simulation</primary>
! </indexterm>
! and molecular dynamics
! <indexterm>
! <primary>molecular dynamics modeling</primary>
! </indexterm>
! modeling soon followed.</para>
! <para id="introduction-pooma_history-asci">
! By 1998, &pooma; was part of the U.S. Department of
! Energy's
! <indexterm>
! <primary>Department of Energy</primary>
! </indexterm>
! Accelerated Strategic Computing Initiative
! (<acronym>ASCI</acronym>).
! <indexterm zone="introduction-pooma_history-asci">
! <primary>Department of Energy</primary>
! <secondary>Accelerated Strategic Computing Initiative</secondary>
! </indexterm>
! <indexterm>
! <primary>Accelerated Strategic Computing Initiative</primary>
! <see>Department of Energy, Accelerated Strategic Computing Initiative.</see>
! </indexterm>
! The Comprehensive Test Ban Treaty
! <indexterm>
! <primary>Comprehensive Test Ban Treaty</primary>
! </indexterm>
! forbid
! nuclear weapons testing so they were instead simulated using
! computers. <acronym>ASCI</acronym>'s goal was to radically advance
! the state of the art in high-performance computing and numerical
! simulations so the nuclear weapon simulations could use 100-teraflop
! parallel computers. A linear accelerator code <application
! class='software'>linac</application> and a Monte Carlo neutron
! transport code <application class='software'>MC++</application> were
! among the codes written.
! <!-- FIXME: Add citation to pooma-siam98. -->
! </para>
<para>&pooma; 2 involved a new conceptual framework and a
complete rewriting of the source code to improve performance. The
! <!-- FIXME: Add a citation to iscope98.pdf. -->
! &array; class
! <indexterm>
! <primary>&array;</primary>
! </indexterm>
! was introduced with its use of &engine;s,
! <indexterm>
! <primary>&engine;</primary>
! </indexterm>
! separating
! container use from container storage. A new asynchronous scheduler
! permitted out-of-order execution
! <indexterm>
! <primary>out-of-order evaluation</primary>
! </indexterm>
! to improve cache coherency.
! Incorporating the <application class="software">Portable
! Expression Template Engine</application> (<acronym>PETE</acronym>)
! <indexterm>
! <primary>&pete;</primary>
! </indexterm>
! permitted faster loop execution. Soon, container views
! <indexterm>
! <primary>container</primary>
! <secondary>view</secondary>
! </indexterm>
! and
! <type>ConstantFunction</type>
! <indexterm>
! <primary>&engine;</primary>
! <secondary><type>ConstantFunction</type></secondary>
! </indexterm>
! and <type>IndexFunction</type>
! <indexterm>
! <primary>&engine;</primary>
! <secondary><type>IndexFunction</type></secondary>
! </indexterm>
! &engine;s were added. Release 2.1.0 included &field;s
! <indexterm>
! <primary>&field;</primary>
! </indexterm>
! with
! their spatial extent and &dynamicarray;s
! <indexterm>
! <primary>&dynamicarray;</primary>
! </indexterm>
! with the ability to
! dynamically change domain size. Support for particles and
! their interaction with &field;s were added. The &pooma; messaging
implementation was revised in release 2.3.0. Use of the
! &cheetah; Library
! <indexterm>
! <primary>&cheetah;</primary>
! </indexterm>
! separated &pooma; from the actual messaging
library used, and support for applications running on clusters of
computers was added. <ulink
! url="http://www.codesourcery.com/">CodeSourcery, LLC</ulink>,
! <indexterm>
! <primary>CodeSourcery, LLC</primary>
! </indexterm>
! and
<ulink url="http://www.proximation.com/">Proximation, LLC</ulink>,
! <indexterm>
! <primary>Proximation, LLC</primary>
! </indexterm>
! took
! over &pooma; development from Los Alamos National Laboratory.
! During the past two years, the &field;
! abstraction
! <indexterm>
! <primary>&field;</primary>
! </indexterm>
! and implementation was improved to increase its
! flexibility, add support for multiple values and materials in the
! same cell, and permit lazy evaluation.
! <indexterm>
! <primary>lazy evaluation</primary>
! </indexterm>
! Simultaneously, the
! execution speed of the inner loops was greatly increased.</para>
</section>
<section id="preface-acknowledgements">
<title>Acknowledgements</title>
More information about the pooma-dev
mailing list