diff options
author | allen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2002-06-25 13:24:21 +0000 |
---|---|---|
committer | allen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2002-06-25 13:24:21 +0000 |
commit | caf2fae6b4bf91513a434cf14c9e704383d4de6d (patch) | |
tree | 6b30b662ff66747499075a24203ef27aa4069654 /doc/FAQ | |
parent | 7777e05fb7b4b32dc37a42b48869e04f61ff3c4c (diff) |
Removing the entry about not being able to schedule routines without a driver
thorn present, now you can, you just can't have any grid functions.
git-svn-id: http://svn.cactuscode.org/flesh/trunk@2914 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/FAQ')
-rw-r--r-- | doc/FAQ | 25 |
1 files changed, 6 insertions, 19 deletions
@@ -1,7 +1,7 @@ Cactus Code Frequently Asked Questions -$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.34 2002-06-25 13:22:11 allen Exp $ +$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.35 2002-06-25 13:24:21 allen Exp $ Also available at http://www.cactuscode.org/Documentation/FAQ @@ -429,20 +429,7 @@ Also available at http://www.cactuscode.org/Documentation/FAQ ------------------------------------------------------------------------------- -31. I have a single Cactus thorn which schedules a simple routine at STARTUP, - which prints output to the screen. If I schedule this routine at - EVOL though I don't see any output. - - You need a driver thorn activated for anything other than routines - scheduled at STARTUP to run. Drivers provide memory for grid - variables, etc. - - If you add e.g. CactusPUGH/PUGH to your ActiveThorns parameter things - should work as you expect. - -------------------------------------------------------------------------------- - -32. Compiling files in Cactus seems to involve three steps, preprocessing, +31. Compiling files in Cactus seems to involve three steps, preprocessing, compiling, and then postprocessing. What is the postprocessing step for? @@ -453,7 +440,7 @@ Also available at http://www.cactuscode.org/Documentation/FAQ ------------------------------------------------------------------------------- -33. How does Cactus manage to so seamlessly call Fortran routines from +32. How does Cactus manage to so seamlessly call Fortran routines from C, and vice versa? Part of the configuration step on a machine involves automatically @@ -472,7 +459,7 @@ Also available at http://www.cactuscode.org/Documentation/FAQ ------------------------------------------------------------------------------- -34. When trying to create the Cactus executable I get the error +33. When trying to create the Cactus executable I get the error Creating cactus_origin in /data2/convCactus/exe from CactusBase/IOASCII CactusBase/Boundary CactusPUGH/PUGHInterp @@ -494,7 +481,7 @@ Also available at http://www.cactuscode.org/Documentation/FAQ ------------------------------------------------------------------------------- -35. When running GetCactus it tells me it is refusing to update my thorn +34. When running GetCactus it tells me it is refusing to update my thorn because it is installed from a different repository. What GetCactus does is look in the thorn's CVS/Root to get the repository @@ -510,7 +497,7 @@ Also available at http://www.cactuscode.org/Documentation/FAQ ------------------------------------------------------------------------------- -36. I get a segmentation fault running Cactus, right after the schedule +35. I get a segmentation fault running Cactus, right after the schedule tree is printed to screen? Check to see if you are passing CCTK_ARGUMENTS into any routines |