[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

# A. Tips and tricks

- Install the 'info' version of this user's guide! On your (Unix) system, this can be achieved by 1) copying all getdp.info* files to the place where your info files live (usually /usr/info), and 2) issuing the command 'install-info /usr/info/getdp.info /usr/info/dir'. You will then be able to access the documentation with the command 'info getdp'. Note that particular sections ("nodes") can be accessed directly. For example, 'info getdp functionspace' will take you directly to the definition of the FunctionSpace object.
- Use emacs to edit your files, and load the C++ mode! This permits automatic syntax highlighting and easy indentation. Automatic loading of the C++ mode for ``.pro'` files can be achieved by adding the following command in your `.emacs` file: `(setq auto-mode-alist (append '(("\\.pro$" . c++-mode)) auto-mode-alist))`.
- Define integration and Jacobian method in separate files, reusable in all your problem definition structures (see section 1.4 Includes). Define meshes, groups, functions and constraints in one file dependent of the geometrical model, and function spaces, formulations, resolutions and post-processings in files independent of the geometrical model.
- Use `All` as soon as possible in the definition of topological entities used as `Entity` of `BasisFunction`s. This will prevent GetDP from constructing unnecessary lists of entities.
- Intentionally misspelling an object type in the problem definition structure will produce an error message listing all available types in the particular context.
- If you don't specify the mandatory arguments on the command line, GetDP will give you the available choices. For example, 'getdp test -pos' (the name of the PostOperation is missing) will produce an error message listing all available PostOperations.

[ << ] | [ >> ] |  |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

Back to geuz.org/getdp