System Preprocessors
|
Being based on Petsc, SysPro can tailor its workings by commandline options. Options are handled by PreprocessorsOptionsHandling(). This routine needs to be called explicitly by the user, after all calls to DeclarePreprocessor(). Commandline options can be set from the program source by the Petsc call PetscOptionsSetValue().
The following commandline options are understood.
"-syspro_exhaustive"
: every preprocessor is cycled exhaustively, unless otherwise limited."-syspro_someprocessor exhaustive"
: the specified preprocessor is tested exhaustively."-syspro_someprocessor choice1,choice2,..."
: the specified preprocessor takes on the specified values. This induces cycling on only the specified preprocessor; if the "-syspro_exhaustive"
option for exhaustive cycling of all preprocessors is given, the limited cycling takes precedence."-syspro_someprocessor not,choice1,choice2,..."
: limited cycling is setup, except that the the specified choices will not be used. (See TransformObjectsUseOnly() for details.)"-syspro_someprocessor_somechoice_values v1,v2,v3,... "
: if a preprocessor choice has option values, this sets the values. This is also induces exhaustive cycling over this preprocessor. Note: unless the cycling is explicitly limited `somechoice' (see the previous item), the exhaustive mode will cycle over all choices of this preprocessor.Any preprocessor can declare its own option handler routine. The option names it handles can be anything, but should presumably not clash with the above formats. E.g., use "-syspro_pc_iterative"
rather than "-syspro_pc iterative"
.