Differences

This shows you the differences between two versions of the page.

--- start:first_simulation [2018/09/04 15:54]
pgrolich
+++ start:first_simulation [2018/09/04 16:05]
pgrolich
@@ Line 62: / Line 62: @@
 {{:start:screenshots:first-simulation-run.png?400|}}
-<p>While computation is running we can see the GSvit output (if the verbose level is not 0) and we can choose any text file output
+While computation is running we can see the GSvit output (if the verbose level is not 0) and we can choose any text file output to be visualised in the graph window. You can also watch preview of last saved images - slices through the computational volume - directly in 3D view. The GSvit output is directly what you would see if you run it at console, with no GUI. Note that graph is updated at maximum as often as the data are saved, so if we skip every 100 points while setting the output we will see the graph updated only e.g. every few seconds (depending on computational volume size, etc.). Similarily, the images in the 3D view are updated when these are saved by the computational core (so you can affect the update frequency by image output skipping parameter).
-to be visualised in the graph window. You can also watch preview of last saved images - slices through the computational volume - directly in 3D view.
-The GSvit output is directly what you would see if you run it at console, with no GUI.
-Note that graph is updated at maximum as often as the data are saved, so if we skip every 100 points
-while setting the output we will see the graph updated only e.g. every few seconds (depending on computational volume size, etc.).
-Similarily, the images in the 3D view are updated when these are saved by the computational core (so you can affect the update frequency
-by image output skipping parameter).</p>
-<p>When computation is finished or killed by the Stop command (again via toolbar or menu), we can <b>open the output</b> file. As most of the
+When computation is finished or killed by the Stop command (again via toolbar or menu), we can **open the output file**. As most of the data are output in Gwyddion file we can directly open it using Gwyddion called from the menu or toolbar. Gwyddion is a powerfull 2D/3D data processing software, however we will only use it to see the images in this example. As image outputs are saved succesively as the GSvit is running, we will be probably having more channels to see in Gwyddion, so we pick what is interesting for us in the Gwyddion Data Browser.
-data are output in Gwyddion file we can directly open it using Gwyddion called from the menu or toolbar. Gwyddion is a powerfull 2D/3D data
-processing software, however we will only use it to see the images in this example. As image outputs are saved succesively as the GSvit
-is running, we will be probably having more channels to see in Gwyddion, so we pick what is interesting for us in the Gwyddion Data Browser.</p>
-<a href="http://gsvit.net/images_v18/ex1_shortwrong.png"><img src="http://gsvit.net/images_v18/ex1_shortwrong.png" width="800"></a>
-<p>Note that in this example we have clicked on <i>Data Process->Presentation->Logscale</i> for every displayed output to see the data in
-better scale. We can see that in different cross-sections of the computational space there is a wave similar to a dipole output.</p>
-<p>If we check the data in further time steps, we can see that they look much worse.</p>
+{{:start:first-simulation-shortwrong.png?400|}}
-<a href="http://gsvit.net/images_v18/ex1_longwrong.png"><img src="http://gsvit.net/images_v18/ex1_longwrong.png" width="800"></a>
-<p>This behavior is caused by unset <b>boundary conditions</b> that behave like mirrors here.
+Note that in this example we have clicked on //Data Process->Presentation->Logscale// for every displayed output to see the data in better scale. We can see that in different cross-sections of the computational space there is a wave similar to a dipole output.
-In order to let the wave go out of the computational
-space we need to apply an absorbing boundary condition, so we click on any entry in "Boundary conditions" set to change the boundary conditions
-on all the faces to a simple absorbing condition (Liao).</p>
-<img src="http://gsvit.net/images_v18/ex1_bcs.png">
-<p>After that (and saving the file, running computation and redisplaying data again) we can see that the output is already propagating
+If we check the data in further time steps, we can see that they look much worse.
-freely outside of the computation volume.</p>
-<a href="http://gsvit.net/images_v18/ex1_longok.png"><img src="http://gsvit.net/images_v18/ex1_longok.png" width="800"></a>
+{{:start:screenshots:first-simulation-longwrong.png?400|}}
+This behavior is caused by unset **boundary conditions** that behave like mirrors here. In order to let the wave go out of the computational space we need to apply an absorbing boundary condition, so we click on any entry in "Boundary conditions" set to change the boundary conditions on all the faces to a simple absorbing condition (Liao).
+{{:start:first-simulation-boundary-conditions.png?400|}}
+After that (and saving the file, running computation and redisplaying data again) we can see that the output is already propagating freely outside of the computation volume.
+{{:start:screenshots:first-simulation-longok.png?400|}}

GSvit documentation

User Tools

Site Tools

Differences

Page Tools