HEAsoft v6.20 - Known Issues

If you are using HEASOFT v6.19 and don't want to upgrade to v6.20 just yet, see the HEASOFT 6.19 Issues List.

Several packages track issues separately from this page:

The following is a list of known issues in v6.20 of HEAsoft not covered by the above pages.

Last modified Wednesday, 18-Jan-2017 18:29:37 EST
  • Ubuntu 16.10:

    Several HEASoft tasks (including extractor, ximage, et al.) suffer memory faults under this new Ubuntu OS, so until further notice, please avoid updating to 16.10 and stay with 16.04 (LTS) if possible.

  • Apple XCode vs. MacPorts gcc/g++:

    Some HEASoft tasks may fail with memory errors on Mac OS X when compiled with the MacPorts gcc/g++, so we continue to recommend that users build HEASoft only with the Apple XCode (Clang/LLVM) gcc/g++ compilers (and the XCode perl and python interpreters as well). This may be ensured by setting the relevant environment variables prior to running the configure script:
     In C-shell variants (tcsh/csh):       In Bourne shell variants (bash/sh):
        % setenv CC /usr/bin/gcc              % export CC=/usr/bin/gcc
        % setenv CXX /usr/bin/g++             % export CXX=/usr/bin/g++
        % setenv PERL /usr/bin/perl           % export PERL=/usr/bin/perl
        % setenv PYTHON /usr/bin/python       % export PYTHON=/usr/bin/python
    As Apple does not provide a Fortran compiler, you will need to use one installed from MacPorts (or elsewhere), so for example:
        % setenv FC /opt/local/bin/g95            % export FC=/opt/local/bin/g95
        % setenv FC /opt/local/bin/gfortran-mp-5  % export % FC=/opt/local/bin/gfortran-mp-5
        % setenv FC /usr/local/bin/gfortran       % export FC=/usr/local/bin/gfortran
    We stress that you avoid using /opt/local/bin/gcc-* and /opt/local/bin/g++-* when building HEASoft from the source code distribution.

  • "relocation R_X86_64_32 against `.rodata' can not be used when making a shared object":

    Users building HEASoft from the source code distribution may run into this error which refers to a "Bad value" in the file heacore/wcslib/C/cel.o, from which the linker "could not read symbols". It also suggests that you "recompile with -fPIC". This situation most likely occurrs when users perform a re-build after a previously unsuccessful build attempt. To get past this issue, try the following:
       $ cd heasoft-6.20/BUILD_DIR
       $ make distclean
    When that finishes, restart the build procedure beginning with "./configure", then "make", and let us know if this does not resolve the problem.

  • fv - XPA_METHOD:

    Some users of the fv GUI may experience long delays at startup, or error messages of the type "XPA$ERROR: invalid host name specified: $host:$port" when using the ds9 display device. These issues tend to occur on Macs with customized firewall settings, or on machines without valid IP addresses. This can be resolved by setting the XPA_METHOD environment variable to the value "local" (to use local/UNIX sockets instead of inet sockets):
            export XPA_METHOD=local          # Bourne shell (bash/sh)
            setenv XPA_METHOD local          # C-shell (csh/tcsh)
  • nuexpomap (PC Cygwin):

    The NuSTAR task "nuexpomap" may fail with a segmentation fault in the Cygwin environment for Windows. To get past the error, users may increase the stack size for that task in the following way:
       Edit the file
       to add "-Wl,--stack,10000000" to the CFLAGS and LDFLAGS_C
       variables (on lines 81 and 107, respectively), then:
       % cd heasoft-6.20/nustar/tasks/nuexpomap
       % hmake clean
       % hmake all install
  • ximage:

    HEASoft includes Tcl/Tk version 8.5.15, which may result in a known but apparently harmless issue on some platforms. After using the /XTK plot device, the following message may be displayed upon exit:
        [XIMAGE> quit
        X Error of failed request:  RenderBadPicture (invalid Picture parameter)
          Major opcode of failed request:  ### (RENDER)
          Minor opcode of failed request:  # (RenderFreePicture)
          Picture id in failed request: #########
          Serial number of failed request:  ####
          Current serial number in output stream:  ####
  • Perl version mismatch::

    Pre-compiled Perl libraries used extensively by mission software (Swift, Suzaku, NuSTAR) and other packages are not especially portable, so we generally recommend building HEASoft from the source code distribution.

  • uvotgrplot:

    This Swift/UVOT task may fail with a Fortran runtime error while generating a postscript plot when compiled using certain versions of gfortran (e.g. v4.6.2 installed via fink) on Mac OS X. At present we suspect a compiler bug and recommend using an alternate compiler from the options on our support page.

  • xspec / PLT - wenv, whead, wdata:

    Some GNU Fortran compilers (gfortran 4.4.x, 4.0.x, 4.1.x) appear to have internal issues which prevent the PLT commands wenv, whead and wdata from working unless an output file is specified; i.e. attempts at producing terminal output may fail with "Fortran runtime error: Invalid argument". To get around this, provide an output file name when using these commands, for example:
         wenv myFile1.qdp
         whead myFile2.qdp
         wdata myFile3.qdp

  • HEASoft and other software packages (CIAO, XMM-SAS):

    Please note:

    Users may wish to download and run our hwrap script to create an alternate runtime environment for HEASOFT to help avoid conflicts with other software packages, but if not, please take note of the potential pitfalls below:

    • CIAO:

      Please see the following notes at the CXC website regarding the potential dangers of using CIAO and HEASOFT together in the same session:

    • XMM:

      When the XMM-SAS is initialized after HEASoft (when both are used in the same session), the SAS setup changes the value of the environment variable PGPLOT_FONT with the result that plots in e.g. Xspec may (or may not, depending on the software distributions in use) have no axis labels or values. Users can fix this by resetting PGPLOT_FONT to point to the HEASoft location:
               setenv PGPLOT_FONT $HEADAS/lib/grfont.dat
           Bourne shell:
               export PGPLOT_FONT=$HEADAS/lib/grfont.dat
      or by simply re-initializing HEASoft:
               source $HEADAS/headas-init.csh
           Bourne shell:
               . $HEADAS/headas-init.sh
      This may in turn have consequences for plotting in XMM-SAS, in which case users may need to return PGPLOT_FONT to the SAS setting when using it for data analysis.

If you have any questions about the information above, please write to us at the FTOOLS help desk.
Help lines: FTOOLS or xanprob@athena.gsfc.nasa.gov

Web page maintained by Bryan K. Irby

HEASARC Home | Observatories | Archive | Calibration | Software | Tools | Students/Teachers/Public

Last modified: Wednesday, 18-Jan-2017 18:29:37 EST