FARGO3D User Guide¶
- Contributing to the code
- Citing FARGO3D
- First Steps
- Directory tree
- Make Process
- Mesh and Fields
- Default SETUPS
- .opt files
- Non-uniform meshes
- N-Body solver
- Induction equation
- Defining a new SETUP
- Run-time visualization.
- Cuda translator (C2CUDA.py).
- Execution flags.
- VTK Compatibility.
- Improving CUDA Performance
- GPU vs CPU Benchmarking
- Developing a complex setup
- Tips, Tricks, Todos and Troubleshooting
- How do I add a new parameter to a setup ?
- How do I create a new
- How do I write a
- What is the way to merge the outputs of a run spawned with the
- I see lots of “!” or “:” instead of “.” at execution. What does that mean?
- Where my last run data has been output ?
- My build produces unexpected results. Some files should have been remade and they have not. How do I fix this ?
- My code does not run much faster on the GPU than on the CPU. Why is this ?
- What is this @ sign at the beginning of the outputs’ path ?
- I see that there are .par files in each setup directory, and the same .par files are found in the in/ sub directory. What is this for ?
- I have noticed a directory named
.fargo3drcin my home directory. What is it here for ?
- How can I see the output of python scripts (in particular the CUDA files) ?
- Tweaking the CUDA executable for memory optimization
- Speeding up reduction operations on platform >= 3.5
- A very incomplete TODO list