STScI Logo

CALCOS v2.17.5 Release Notes

---------------------CALCOS v2.17.5--------------------- 

This describes changes from calcos version 2.17.3 to 2.17.5.

Relevant Trac tickets and PRs:
Trac   PR
----  -----
 761  69143  Calcos should flag gain-sagged regions in FUV data.
 865  70786  Calcos needs a reasonable default value for x1dsum array size.


The option to use a gsagtab to flag gain sagged regions has been

When averaging x1d tables to make an x1dsum table, there are several
columns that contain arrays.  If all the input x1d tables are empty, the
array length was being set to 0, which is not a valid array length.  The
array length is now set to a positive value, at least 1 but usually the
length of an FUV or NUV x1d array.


Changes to

The changes that had been made to calcos 2.17.3 to disable use of the
gain sag table (GSAGTAB) have been removed.  In particular, gsagtab has
been added to the `temp` dictionary in missingRefFiles, and a check on
its existence has been added just after checking for bpixtab.
Trac #761, PR 69143

Changes to

In getDQArrays, the gain sag table will be used for all FUV data, not just
for TIME-TAG data.
Trac #761, PR 69143

Changes to

Function getRefFileNames was modified to remove the code that set
reffiles["gsagtab"] to "N/A".
Trac #761, PR 69143

Changes to

In __init__ for OutputX1D, self.output_nelem is initialized to 1, instead
of to 0.  In method computeOutputInfo, if the input spectra are empty,
self.output_nelem is set to the extended array length (16384 for FUV,
1274 for NUV) instead of to 0.  If there are input spectra, self.output_nelem
will only be updated if the computed value for the number of elements is
greater than zero, not just greater than or equal to zero.  The problem was
that self.output_nelem is used to set the array length for x1dsum columns
that are arrays, and zero is not a valid length.
Trac #865, PR 70786