GSvit documentation

open source FDTD solver with GPU support

User Tools

Site Tools


faq:faq

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq:faq [2018/01/30 15:31]
pklapetek
faq:faq [2018/09/04 17:30] (current)
pklapetek
Line 3: Line 3:
 == I have installed it, what to do next? == == I have installed it, what to do next? ==
  
-See the [[getting_started:your_first_simulationgetting ​started]] section. You may be confused that you have more executables installed. There are two command line solvers (gsvit, gsvit2d) and a single graphical user interface (XSvit). To have something easy-to-use,​ start with the XSvit.+See the [[start:getting_startedGetting ​started]] section. You may be confused that you have few different ​executables installed. There are two command line solvers (gsvit, gsvit2d) and a single graphical user interface (XSvit). To have something easy-to-use,​ start with the XSvit.
  
 == What is the GSvit2D and does it have any GUI? == == What is the GSvit2D and does it have any GUI? ==
Line 12: Line 12:
  
 In principle, all the Nvidia CUDA enabled cards should work, however a really cheap card can result in only very small calculation speedup. The best choice are gaming cards, that are already very powerful, but still not expensive like special computing ones. GSvit is intentionally written to work with floats wherever on graphics card possible to get reasonable speedup on older and less developed cards (as the doubles were supported later and also are still a bit slower). In principle, all the Nvidia CUDA enabled cards should work, however a really cheap card can result in only very small calculation speedup. The best choice are gaming cards, that are already very powerful, but still not expensive like special computing ones. GSvit is intentionally written to work with floats wherever on graphics card possible to get reasonable speedup on older and less developed cards (as the doubles were supported later and also are still a bit slower).
 +
 +== Results are strange while computing on graphics card, why? ==
 +
 +The algorithm that you want to use might be not implemented on graphics card yet. This is namely case of some newer algorithms or algorithms that are still in the phase of implementation. Some of these (and general discussion on graphics card performance) are listed on the [[opt:​graphics_cards|graphics card use]] page. There are also some automated [[start:​tests|tests]] available, however the possible number of source/​material/​boundary conditions is large and it is not easy to test all of them. The safe way is to cross-check the calculation on graphics card with results obtained on computer processor when setting up a novel simulation.
  
  
faq/faq.1517322718.txt.gz ยท Last modified: 2018/01/30 15:31 by pklapetek