Skip to content

Commit

Permalink
doc: code sintaxe correction in base acceleration example
Browse files Browse the repository at this point in the history
  • Loading branch information
fabricix committed Dec 11, 2024
1 parent 6524a5c commit 8e4a7d8
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 5 deletions.
5 changes: 2 additions & 3 deletions docs/program_tutorial_manual.html
Original file line number Diff line number Diff line change
Expand Up @@ -164,14 +164,13 @@ <h3><a class="anchor" id="autotoc_md60"></a>
"fields":["displacement","velocity"]
}
}
</pre><p>When the "earthquake" keyword is defined in any plane in the mesh, the simulator will search for the acceleration record "base_acceleration.csv" in the working directory. This record must to be the data in the following structure: time, acceleration_x, acceleration_y, acceleration_z. The five first lines of the acceleration record is: </p><pre class="fragment">{
t,ax,ay,az
</pre><p>When the "earthquake" keyword is defined in any plane in the mesh, the simulator will search for the acceleration record "base_acceleration.csv" in the working directory. This record must to be the data in the following structure: time, acceleration_x, acceleration_y, acceleration_z. The five first lines of the acceleration record is:</p>
<pre class="fragment"> t,ax,ay,az
0.0,-1.8849555921538759,-0.9424777960769379,-0.0
5e-05,-1.8849554991350466,-0.9424777844495842,-0.0
0.0001,-1.884955220078568,-0.9424777495675233,-0.0
0.00015000000000000001,-1.8849547549844674,-0.9424776914307561,-0.0
...
}
</pre><p>Note that the base acceleration record must to contain a header, that will be ignored during the reading acceleration data.</p>
<p>Once we have the JSON input file, we can execute the simulator with the input file as parameter. When the simulation ends we can find the particle results in the "/particle" directory, and the grid mesh in the "/grid" directory. The particles results are written in uniformly separated times determined by the number of results defined in the "print" keyword. The number of total results must be 40. In this example, the particles results must be "particle_1.vtu", "particle_2.vtu", ..., "particle_41.vtu". Together with the "particle_i.vtu" results, a particle serie file "particleTimeSerie.pvd" is created. This time series file can be used to load all the results in the Paraview scientific visualization program.</p>
<p>In other to visualize the results, the "particleTimeSerie.pvd" can be open in the Paraview by "&gt; File &gt; Open &gt; particleTimeSerie.pvd". And the mesh can be loaded by open the "&gt; File &gt; Open &gt; eulerianGrid.vtu".</p>
Expand Down
4 changes: 2 additions & 2 deletions manual/tutorial.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,14 +61,14 @@ The complete JSON file with the keywords we write:

When the "earthquake" keyword is defined in any plane in the mesh, the simulator will search for the acceleration record "base_acceleration.csv" in the working directory. This record must to be the data in the following structure: time, acceleration_x, acceleration_y, acceleration_z. The five first lines of the acceleration record is:

{

t,ax,ay,az
0.0,-1.8849555921538759,-0.9424777960769379,-0.0
5e-05,-1.8849554991350466,-0.9424777844495842,-0.0
0.0001,-1.884955220078568,-0.9424777495675233,-0.0
0.00015000000000000001,-1.8849547549844674,-0.9424776914307561,-0.0
...
}


Note that the base acceleration record must to contain a header, that will be ignored during the reading acceleration data.

Expand Down

0 comments on commit 8e4a7d8

Please sign in to comment.