GSvit documentation

open source FDTD solver with GPU support

User Tools

Site Tools


start:tests

Differences

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

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
start:tests [2015/07/17 22:28]
pklapetek created
start:tests [2018/01/24 08:14]
127.0.0.1 external edit
Line 10: Line 10:
  
 Automated tests available are as follows (run gsvit with no arguments for a list of them): Automated tests available are as follows (run gsvit with no arguments for a list of them):
- * **./gsvit test 0** checks available GPUs only, printing their main characteristics. +  ​* **./gsvit test 0** checks available GPUs only, printing their main characteristics. 
- * **./gsvit test 1** makes single test on CPU and all GPUs (if there are any) +  * **./gsvit test 1** makes single test on CPU and all GPUs (if there are any) 
- * **./gsvit test 2** tests key algorithms performance,​ running approximately ten different tests for 100x100x100 voxels, 100 steps, which takes some ten minutes. +  * **./gsvit test 2** tests key algorithms performance,​ running approximately ten different tests for 100x100x100 voxels, 100 steps, which takes some ten minutes. 
- * **./gsvit test 3** tests key algorithms performance,​ running approximately ten different tests for 200x200x200 voxels, 300 steps, which can take tens of minutes, however+  * **./gsvit test 3** tests key algorithms performance,​ running approximately ten different tests for 200x200x200 voxels, 300 steps, which can take tens of minutes, however
 is more precise regarding peak GSvit performance estimation. is more precise regarding peak GSvit performance estimation.
- * **./gsvit test 12** compares GPU/CPU time scaling up to 200x200x200 voxels +  ​* **./gsvit test 12** compares GPU/CPU time scaling up to 200x200x200 voxels 
- * **./gsvit test 13** compares GPU/CPU time scaling up to 300x300x300 voxels +  * **./gsvit test 13** compares GPU/CPU time scaling up to 300x300x300 voxels 
- * **./gsvit test 14** compares GPU/CPU time scaling up to 400x400x400 voxels +  * **./gsvit test 14** compares GPU/CPU time scaling up to 400x400x400 voxels 
- * **./gsvit test 15** compares GPU/CPU time scaling up to 500x500x500 voxels +  * **./gsvit test 15** compares GPU/CPU time scaling up to 500x500x500 voxels 
- * **./gsvit test 20** compares GPU time scaling up to 400x400x400 voxels +  * **./gsvit test 20** compares GPU time scaling up to 400x400x400 voxels 
- * **./gsvit test 3N** tests multiple threads speedup on N00xN00xN00 voxels (i.e. 100 to 900 for 31 to 39) +  * **./gsvit test 3N** tests multiple threads speedup on N00xN00xN00 voxels (i.e. 100 to 900 for 31 to 39) 
- * **./gsvit test AAABCDEF** is a general test format. The eigth digit number AAABCDEF means:+  * **./gsvit test AAABCDEF** is a general test format. The eigth digit number AAABCDEF means: ​
     * AAA - cube size in pixels (i.e. if XXX = 100, cube size is 100 x 100 x 100)     * AAA - cube size in pixels (i.e. if XXX = 100, cube size is 100 x 100 x 100)
     * B - boundary condition: 0 - none, 1 - PEC, 2 - Liao, 3 - CPML     * B - boundary condition: 0 - none, 1 - PEC, 2 - Liao, 3 - CPML
Line 28: Line 28:
     * E - run Near-to Far Field transformation for a single point: 0 - no, 1 - yes     * E - run Near-to Far Field transformation for a single point: 0 - no, 1 - yes
     * F - source: 0 - point source, 1 - total/​scattered field, 2 - scattered field     * F - source: 0 - point source, 1 - total/​scattered field, 2 - scattered field
-The "​AAABCDEF"​ naming is used also to store the precomputed data that are compared with tests results. The precomputed +   
-data for comparison are typically single near field or far field point time dependence.+The "​AAABCDEF"​ naming is used also to store the precomputed data that are compared with tests results. ​ 
 +The precomputed data for comparison are typically single near field or far field point time dependence.
  
 There are two more tests designed for benchmarking HPC systems: There are two more tests designed for benchmarking HPC systems:
- * **./gsvit benchmark N** tests N threads computational time on 900x900x900 voxels +    ​* **./gsvit benchmark N** tests N threads computational time on 900x900x900 voxels 
- * **./gsvit bigbenchmark N** tests N threads computational time on 4000x4000x4000 voxels+    * **./gsvit bigbenchmark N** tests N threads computational time on 4000x4000x4000 voxels
  
  
start/tests.txt · Last modified: 2019/01/17 09:48 by dnezval