HEAsoft v6.17 - Known Issues
If you are using HEASOFT v6.15 and don't want to upgrade to v6.17 just yet,
see the HEASOFT 6.16 Issues List.
Several packages track issues separately from this page:
The following is a list of known issues in v6.17 of HEAsoft not covered
by the above pages.
Last modified Monday, 17-Aug-2015 12:22:24 EDT
For input files with more than 1000 rows, the task ftconvert (heatools)
mistakenly repeats only the first 1000 rows in the output file. To fix your
1) Initialize your environment to use HEASoft.
2) Download the update to ftconvert: ftconvert
3) Copy the new ftconvert into your $HEADAS/bin directory, overwriting
the previous version ($HEADAS/bin/ftconvert).
4) Run the lhea-fixperl utility (included in $HEADAS/bin, so it
should be in your path already after step 1) on the new ftconvert:
% lhea-fixperl $HEADAS/bin/ftconvert
- "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.17/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.17/nustar/tasks/nuexpomap
% hmake clean
% hmake all install
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:
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.
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
- 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
- HEASoft and other software packages (CIAO, XMM-SAS):
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:
If you have any questions about the information above, please write to
us at the FTOOLS help desk.
Web page maintained by
Bryan K. Irby
HEASARC Home |
Last modified: Monday, 17-Aug-2015 12:22:24 EDT