Bugs: axbary

A list of bugs fixed in CIAO 4.0 is available.

Caveats

1. Running axbary multiple times on the same file

Bugs

1. axbary does not work on gzipped input event files

Caveats

1. Running axbary multiple times on the same file

   If axbary has been used to correct the times in a file, running the tool again on the same dataset will not make any further changes to the file. In order to apply different corrections to different parts of the obsid, you have to filter the event data first (e.g. with a region filter), then run axbary on each resulting dataset.

Bugs

1. axbary does not work on gzipped input event files

   axbary does not work on gzipped input event files, even if your CIAO installation was configured with gzip support. The resulting error will look like:

   axBary: Failed to re-open output file out_axbary.fits
   axBary: Error exit (error 112); output file out_axbary.fits NOT deleted 
   

   where out_axbary.fits is the value of the outfile parameter.

Bugs fixed in CIAO 4.0

The following is a list of bugs that were fixed in the CIAO 4.0 software release.

1. Input and output filename limit conflict (16 May 2007)

   There is a bug in axbary that appears when the input filename is > 49 characters and the output filename is < 49:

   ===> Barycenter correction applied to HDU 1
   Error occurred while closing header
   

   There are two issues that may arise from this:

   • part of the HISTORY records get skipped
   • the CHECKSUM and DATASUM keywords may not get updated

   The second item is a bigger concern, so use fchecksum if you get this error.