Both CIAO and FTOOLS use parameter files to store parameter
values for tools, and provide tools for manipulating these
files (e.g. plist,
pset,
punlearn; they have the same name in both
systems). The location of the parameter files is taken from
the $PFILES environment variables for CIAO and
FTOOLS (or $UPARM if $PFILES does not exist).
Common errors are:
pget: could not get parameter "foo"
and
The following parameter:
"foo,b,l,no,,,"Keyword""
has the following error(s):
o Mode field "l" is invalid.
and
The following parameter:
"foo,i,h,INDEF,INDEF,INDEF,"description""
has the following error(s):
o Problem converting minimum field "INDEF" to parameter type "i".
o Problem converting maximum field "INDEF" to parameter type "i".
We recommend that you start FTOOLS before
CIAO to minimize problems.
More information on this problem is available in the
CIAO and FTOOLS
section of the Starting CIAO thread.
Also refer to the related FAQ "The
tool is failing because ")sval" has somehow shown up in the
parameter value.".
Certain CIAO tools (e.g. axbary, dmgti, evalpos, detect, wavdetect)
are actually shell scripts.
If FTOOLS is set to launch automatically in the startup script, these tools may
reinitialize it and cause a parameter file conflict. Commenting the FTOOLS
startup out of your .cshrc/.bashrc/.zshrc file and starting FTOOLS manually
before starting CIAO should resolve this issue.