This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
fdtd:fdtd_gsvit [2015/07/24 09:28] pklapetek |
fdtd:fdtd_gsvit [2019/01/14 08:01] pgrolich |
||
---|---|---|---|
Line 1: | Line 1: | ||
===== FDTD calculations via GSvit ===== | ===== FDTD calculations via GSvit ===== | ||
- | As shown on [[getting_started:your_first_simulation|First simulation]] page, there are three steps in a succesfull calculation. First step is to **setup model** that we want to use for the calculation. In brief this means to address the following questions: | + | As shown on [[start:your_first_simulation|First simulation]] page, there are three steps in a succesfull calculation. First step is to **setup model** that we want to use for the calculation. In brief this means to address the following questions: |
* What should be voxel size and real size of the computational domain? | * What should be voxel size and real size of the computational domain? | ||
* How many steps of the calculation will be used, are we searching for a steady solution or some transient effect? | * How many steps of the calculation will be used, are we searching for a steady solution or some transient effect? | ||
Line 8: | Line 8: | ||
* What should be the output, e.g. field amplitude in some position? | * What should be the output, e.g. field amplitude in some position? | ||
* Should the calculation be done on a computer processor(s) or a graphics card? | * Should the calculation be done on a computer processor(s) or a graphics card? | ||
- | All this can be setup via a parameter file, editable in a text editor or using XSvit parameter file viewer. | + | All this can be setup via a parameter file, editable in a text editor or using XSvit parameter file viewer. It is described in next paragraphs of this section. |
After this is done, we **run the calculation**, which means that we run the solver GSvit with parameter file as an argument, either manually or from XSvit GUI. We wait until computation is finished, which might take something between seconds and hours, depending on computational domain size, number of steps and complexity of algorithms used. | After this is done, we **run the calculation**, which means that we run the solver GSvit with parameter file as an argument, either manually or from XSvit GUI. We wait until computation is finished, which might take something between seconds and hours, depending on computational domain size, number of steps and complexity of algorithms used. | ||
Finally, we want to **analyse results**. Text outputs can be analysed in your favourite graph plotting or spreadsheet aplication, cross-section outputs can be analysed using [[http://gwyddion.net|Gwyddion]] and volume outputs can be analysed by [[http://www.paraview.org|Paraview]]. | Finally, we want to **analyse results**. Text outputs can be analysed in your favourite graph plotting or spreadsheet aplication, cross-section outputs can be analysed using [[http://gwyddion.net|Gwyddion]] and volume outputs can be analysed by [[http://www.paraview.org|Paraview]]. |