Difference between revisions of "Reading Material Points from a Previous Simulation"

From OSUPDOCS
Jump to navigation Jump to search
(Created page with "Sometimes it is useful to run a simulation, output the material point locations, and them use those settings for a new MPM simulation. One approach is to extract all material ...")
 
Line 12: Line 12:
where <tt>Archive.1843</tt> is desired time archive containing material point locations. The points will be written to an <tt>XML</tt> file called <tt>particles.xml</tt>. The output file will have one [[PointList Block|<tt><PointList</tt> block]] with one<tt><mp></tt>element for each material point. See the [[ExtractMPM]] tool documentation for more details on an XML extraction.</li>
where <tt>Archive.1843</tt> is desired time archive containing material point locations. The points will be written to an <tt>XML</tt> file called <tt>particles.xml</tt>. The output file will have one [[PointList Block|<tt><PointList</tt> block]] with one<tt><mp></tt>element for each material point. See the [[ExtractMPM]] tool documentation for more details on an XML extraction.</li>


<li>Finally, include this saved file in another commands file using an <tt>XML</t> entity reference. First, define the path to the new file in the file's <tt>DOCTYPE</tt> element such as:
<li>Finally, include this saved file in another commands file using an <tt>XML</tt> entity reference. First, define the path to the new file in the file's <tt>DOCTYPE</tt> element such as:


<pre>&lt;!DOCTYPE JANFEAInput SYSTEM '/full path to/NairnMPM.dtd'
<pre>&lt;!DOCTYPE JANFEAInput SYSTEM '/full path to/NairnMPM.dtd'
Line 19: Line 19:
</pre>
</pre>


Then, import that file in the <tt><MaterialPoints></tt> element using
In scripted files, you can define this entity with an Entity command. Then, import that file in the <tt><MaterialPoints></tt> element using
 
<pre>&lt;MaterialPoints&gt;
<pre>&lt;MaterialPoints&gt;
   &amp;mpfile;
   &amp;mpfile;
&lt;/MaterialPoints&gt;</pre>
&lt;/MaterialPoints&gt;</pre>
In scripted files, it can be included with an XMLData command:
<pre>XMLData,MaterialPoint
  &amp;mpfile;
EndXMLData
</pre>


</ol>
</ol>

Revision as of 08:35, 7 December 2013

Sometimes it is useful to run a simulation, output the material point locations, and them use those settings for a new MPM simulation. One approach is to extract all material point locations to an XML file using the ExtractMPM tool, and then input that file to a new commands file. The process is:

  1. Run an MPM simulation
  2. Select an archive time and use ExtractMPM to extract particle data to an XML file. A typical command would be:
    ExtractMPM -Xh -q mass -o particles Archive.1843
    
    where Archive.1843 is desired time archive containing material point locations. The points will be written to an XML file called particles.xml. The output file will have one <PointList block with one<mp>element for each material point. See the ExtractMPM tool documentation for more details on an XML extraction.
  3. Finally, include this saved file in another commands file using an XML entity reference. First, define the path to the new file in the file's DOCTYPE element such as:
    <!DOCTYPE JANFEAInput SYSTEM '/full path to/NairnMPM.dtd'
    [   <!ENTITY mpfile SYSTEM "pointlist.xml">
    ]>
    

    In scripted files, you can define this entity with an Entity command. Then, import that file in the <MaterialPoints> element using

    <MaterialPoints>
       &mpfile;
    </MaterialPoints>

    In scripted files, it can be included with an XMLData command:

    XMLData,MaterialPoint
       &mpfile;
    EndXMLData