Bugs: Other Software Packages

Linux users may see this MAXREPEAT error if they have setup for other software packages that provide their own version of Python.

This includes, but may not be limited to, Fermi's Science Tools.

The problem is due to those packages setting the LD_LIBRARY_PATH environment variable to point to an incompatible version of the Python shared library: libpython.2.7.so.1.0

Workaround:

Due to the nature of the conflict, users should if at all possible setup CIAO in a separate terminal window from the interferring package.

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):
  Mode field "l" is invalid.

and

The following parameter:
"foo,i,h,INDEF,INDEF,INDEF,"description""
has the following error(s):
Problem converting minimum field "INDEF" to parameter type "i".
Problem converting maximum field "INDEF" to parameter type "i".

and

Parameter xoffset: invalid range (INDEF, INDEF).
Parameter yoffset: invalid range (INDEF, INDEF).
pset: unable to initialize tool/parameter file "tgdetect".


and
....
pquery: unable to prompt for parameter "-".
pquery: unable to prompt for parameter "-".
/Users/will_i_am/.conda/envs/ciao/bin/wavdetect: line 66: test: -ge: unary operator expected
ERROR: Input background file or a default normalized background filename must be specified as input for wrecon.

and
PMIx_Query_info returned: PMIX_ERR_UNREACH

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.

Any system environment variable - LD_LIBRARY_PATH, DYLD_LIBRARY_PATH, PATH, etc. - is not defined when a user sets up a CIAO environment. Rather, the variable is defined as needed in the wrapper scripts that call individual tools, and then undefined when the wrapper script exits. This is fine for the majority of CIAO users.

For the advanced user who want to override some of the CIAO defaults when running CIAO tools, there are additional steps needed. To append libraries to the CIAO library search path, set LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on a Mac). To prepend a library to the search path, should set CIAO_LD_LIBRARY_PATH (or CIAO_DYLD_LIBRARY_PATH). The user cannot prepend a search to PATH.

This means SE Linux is enabled on the user's system. ciao-install will perform the following chcon commands; however if users installed CIAO by following the step-by-step instructions there may still be problems.

There are 2 things that will fix this; do either of the following, not both:

1. On the CIAO libraries and executables in the following directories

   $ASCDS_INSTALL/lib 
   $ASCDS_INSTALL/bin 
   $ASCDS_INSTALL/binexe 
   $ASCDS_INSTALL/ots/lib 
   $ASCDS_INSTALL/ots/bin 
   

   run the commands:

   $ su root
   # cd (to above CIAO directories)
   # chcon -c -v -R -u system_u -r object_r -t lib_t *
   # chcon -t texrel_shlib_t *
   

2. Disable SE Linux

Users who try to run CIAO and FTOOLs on Linux machines in the same terminal may get an error like

unix% sherpa
-----------------------------------------------------
Welcome to Sherpa: CXC's Modeling and Fitting Package
-----------------------------------------------------
...

WARNING: failed to import sherpa.astro.xspec; XSPEC models will not be available
sherpa-1>