[cig-commits] r3823 - short/3D/PyLith/branches/pylith-0.8/doc/userguide/tutorials

baagaard at geodynamics.org baagaard at geodynamics.org
Tue Jun 20 09:01:42 PDT 2006


Author: baagaard
Date: 2006-06-20 09:01:41 -0700 (Tue, 20 Jun 2006)
New Revision: 3823

Modified:
   short/3D/PyLith/branches/pylith-0.8/doc/userguide/tutorials/tutorialbm5.xml
Log:
Fixed viz2 step in tutorial.

Modified: short/3D/PyLith/branches/pylith-0.8/doc/userguide/tutorials/tutorialbm5.xml
===================================================================
--- short/3D/PyLith/branches/pylith-0.8/doc/userguide/tutorials/tutorialbm5.xml	2006-06-20 15:44:05 UTC (rev 3822)
+++ short/3D/PyLith/branches/pylith-0.8/doc/userguide/tutorials/tutorialbm5.xml	2006-06-20 16:01:41 UTC (rev 3823)
@@ -423,12 +423,12 @@
           information with the output at a given time step into a
           complete <acronym>UCD</acronym> file. For example, use
           <command>cat</command> to merge the nodal coordinates file
-          (<filename>bm5.mesh.inp</filename>) and the nodal
+          (<filename>bm5_1.0.mesh.inp</filename>) and the nodal
           displacements at time step 10 file
-          (<filename>bm5.mesh.time.00010.inp</filename>) into
-          <filename>bm5.mesh.t00010.inp</filename>, <command>cat
-          bm5.mesh.inp bm5.mesh.time.00010.inp >
-          bm5.mesh.t00010.inp</command>.
+          (<filename>bm5_1.0.mesh.time.00010.inp</filename>) into
+          <filename>bm5_1.0.mesh.t00010.inp</filename>, <command>cat
+          bm5_1.0.mesh.inp bm5_1.0.mesh.time.00010.inp >
+          bm5_1.0.mesh.t00010.inp</command>.
         </para>
       </listitem>
       <listitem>
@@ -483,7 +483,12 @@
   <section>
     <title>Run the simulation on two processors</title>
     <para>
-      In this step we will run the simulation on two processors.
+      In this step we will run the simulation on two processors. Even
+      if your machine only has one processor, a "multprocessor" job
+      will run as multiple processes on the single processor. In such
+      cases, the job will run slightly slower than the single
+      processor run, but the two processes will behave independently
+      as if they are on different processors.
     </para>
     
     <orderedlist numeration="arabic">
@@ -513,9 +518,13 @@
   <!-- SECTION +++++++++++++++++++++++++++++++++++++++++++++++++++ -->
   <section>
     <title>Visualize the two processor run</title>
+
     <para>
-      Now we will visualize the output from the two processor run
-      using <application>ParaView</application>.
+      PyLith does not currently support parallel output, so each
+      PyLith processor writes its <acronym>UCD</acronym> output to a
+      different file. This means that you need to form complete
+      <acronym>UCD</acronym> files for each processor and then load in
+      each one into <application>ParaView</application>. 
     </para>
     
     <orderedlist numeration="arabic">
@@ -528,9 +537,39 @@
       </listitem>
       <listitem>
 	<para>
-          ADD STUFF HERE
+          As in the case of the single processor run, the first step
+          is to combine the mesh topology information with the output
+          at a given time step into a complete <acronym>UCD</acronym>
+          file. For example, use <command>cat</command> to merge the
+          nodal coordinates file
+          (<filename>bm5_1.0.mesh.inp</filename>) and the nodal
+          displacements at time step 10 file
+          (<filename>bm5_1.0.mesh.time.00010.inp</filename>) into
+          <filename>bm5_1.0.mesh.t00010.inp</filename>, <command>cat
+          bm5_1.0.mesh.inp bm5_1.0.mesh.time.00010.inp >
+          bm5_1.0.mesh.t00010.inp</command>. Repeat this for processor
+          1, <command>cat bm5_1.1.mesh.inp bm5_1.1.mesh.time.00010.inp
+          > bm5_1.1.mesh.t00010.inp</command>.
         </para>
       </listitem>
+      <listitem>
+	<para>
+          Start <application>ParaView</application> by executing
+          <command>paraview</command>.
+        </para>
+      </listitem>
+      <listitem>
+	<para>
+          Load the <acronym>UCD</acronym> files that you just created
+          by selecting
+          <menuchoice><guimenu>File</guimenu><guimenuitem>Open
+          Data</guimenuitem></menuchoice>. Select the file in the
+          dialog box and the click the <guibutton>Open</guibutton>
+          button. Click the <guibutton>Accept</guibutton> button. You
+          can now visualize the datasets just like you did for the
+          single processor case.
+        </para>
+      </listitem>
     </orderedlist>
   </section>
 



More information about the Cig-commits mailing list