Difference between revisions of "SELFE FAQ"
| Line 13: | Line 13: | ||
The simplest way is to use SELFE 2D. If you have to use SELFE 3D, make sure the bottom boundary layer is reasonably resolved. | The simplest way is to use SELFE 2D. If you have to use SELFE 3D, make sure the bottom boundary layer is reasonably resolved. | ||
| + | ==My run crashed; how can I find out why? == | ||
| + | |||
| + | See [[Debugging after a run crashes]]. | ||
<!--==I'd like to add some passive tracer transport to SELFE. How can I interface my own code to it?== | <!--==I'd like to add some passive tracer transport to SELFE. How can I interface my own code to it?== | ||
| Line 19: | Line 22: | ||
==How do I prepare my own netcdf files for atmospheric model (nws=2)?== | ==How do I prepare my own netcdf files for atmospheric model (nws=2)?== | ||
==I have large velocity at open boundary== | ==I have large velocity at open boundary== | ||
| − | + | --> | |
Latest revision as of 19:48, 15 September 2013
Contents
My results show platform/compiler/CPU dependency
Due to some intricate differences between different compilers/platforms some minor differences in results are expected. Bit-by-bit match of results using different numbers of CPUs is impossible also. But the differences should be small and should stablize over time iteration.
Run crashed with a fort.11 error message "QUICKSEARCH: no intersecting edge...."
First you need to check the results before the crash (e.g. surface velocity) to see if anything is outrageously wrong. If the results look reasonable, this may be related to the version of SELFE you are using; contact the developers for more info.
How to do a tidal simulation with SELFE?
The simplest way is to use SELFE 2D. If you have to use SELFE 3D, make sure the bottom boundary layer is reasonably resolved.
My run crashed; how can I find out why?
See Debugging after a run crashes.
