Next: Format of Housekeeping Files
Up: DH_Final
Previous: Intermediate Data File Header
Contents
If a user chooses to rerun the CalFUSE pipeline, occasional warning messages might appear
in the trailer files if a pipeline module fails to run successfully. Below is a list of
selected warning messages from CalFUSE and how to address them.
- cf_bad_pixels: Array overflow. Truncating pseudo-photon list.
To make the array larger, replace nmax *= 1.5 with
nmax *= 2 on line 508 of src/fuv/cf_bad_pixels
- cf_hist_init: More than 10 hot pixels found.
"Hot pixels" in histogram data result from flips of
high-order bits in the raw image array. A large number
of bit flips suggest that the data may be corrupted.
- cf_hist_init: [Input file] contains no extensions.
Raw data file contains no FITS extensions.
- cf_apply_dead_time: DET_DEAD > 1.5. Setting dead-time correction to unity, or
IDS_DEAD > 1.5. Setting dead-time correction to unity.
Dead-time correction is unreliable. Observation is not
photometric.
- cf_apply_filters: Sum of day and night time differs from EXPTIME by > 10%.
The photon-screening routines have gotten confused. You may have found a bug in the code.
- cf_astig_farf: Overflow of ASTG_CAL file in aperture [n].
Either there is a problem with the astigmatism-correction
file, or you've found a bug in the routine that applies
this correction.
- various
- : Environment variable [variable name] undefined.
You must set the environment variables CF_CALDIR and
CF_PARMDIR before running CalFUSE.
- cf_check_digitizer: Digitizer keyword [keyword name] is out of bounds.
Keywords are read from the input file header. If their
values are out of bounds, then the detector was not
properly configured, and the data are suspect, if not
useless.
- cf_fpa_position: Keyword FPALXPOS is out of bounds. Setting FPADXLIF = 0.
Keyword FPASXPOS is out of bounds. Setting FPADXSIC = 0.
Reported position of focal-plane assembly (FPA) is out
of bounds. Expect a wavelength shift of the extracted
spectrum.
- cf_fuv_init: Keyword [keyword name] in master_calib_file.dat is unknown.
File parmfiles/master_calib_file.dat may be corrupted.
- cf_fuv_init: Detector bias keywords are corrupted.
Minimum and maxximum detector voltage values are stored in the input
file header. If high-voltage information is available in
the housekeeping file, then the header values are ignored.
- cf_geometric_distort: X and Y distortion images not the same size.
Geometric distortion calibration file (GEOM_CAL) is corrupted.
- cf_init_support: Exposure appears to span [number] ks. Truncating.
If exposure time appears to be greater than 55 ks,
photon arrival times are corrupted.
The following warnings are issued by cf_init_support only if there are
no housekeeping data and the relevant file header keywords appear to be
corrupted.
- -Engineering snapshot time less than or equal to zero.
- -Estimating LiF, SiC, FEC and AIC count rates from EXPSTART and EXPEND.
- -Estimating LiF, SiC, FEC and AIC count rates from EXPTIME.
- -Bad SiC counter. SiC count rate will be set to zero.
- -Bad LiF counter. LiF count rate will be set to zero.
- -Bad FEC counter
- FEC count rate will be computed from NEVENTS and EXPTIME.
- Electronic deadtime correction will be underestimated.
- Y stretch will be underestimated.
- -Bad AIC counter
-
- AIC count rate will be computed from NEVENTS and EXPTIME.
- IDS deadtime correction will be underestimated.
If cf_init_support cannot read the SiC count-rate array from the
housekeeping file, it issues one of the following warnings and uses
file-header information to populate all of the count-rate arrays in the IDF:
Data missing from housekeeping column. Will treat file as missing.
Data column missing from housekeeping file. Will treat file as missing.
If any of the count rates computed by cf_init_support is absurdly high,
then the program will issue one of these warnings and set the offending
array elements to zero:
LIF_CNT_RATE out of bounds. Setting bad values to zero.
SIC_CNT_RATE out of bounds. Setting bad values to zero.
FEC_CNT_RATE out of bounds. Setting bad values to zero.
AIC_CNT_RATE out of bounds. Setting bad values to zero.
- cf_make_wave_array: Requested value of W0 is less than recommended value.
Requested value of WMAX is greater than recommended value.
Requested value of WPC is less than recommended value.
The user can set the wavelength scale of the extracted
spectrum by modifying the parameter files in the parmfiles
directory. Bad choices trigger these warnings.
- cf_pha_x_distort: NAXIS1 of [PHAX_CAL] != 16384
Walk-correction calibration file is corrupted.
- cf_proc_check: Exiting. [Program name] has already been run on this file.
If you try to run a calibration step twice, you'll get
this warning.
- cf_proc_update: No PROCESSING STEP keyword is defined for [program name].
CalFUSE modifies file-header keywords, changing PERFORM
to COMPLETE, as pipeline steps are completed. This
warning means that the program cannot determine which
keyword is associated with the current program. This
should never happen.
- cf_screen_high_voltage: Detector voltage is < 90% of optimal value.
Detector voltage is low, but data may still be OK.
Examine pulse-height distribution. Look for strong
fixed-pattern noise in the extracted spectrum.
- cf_set_photon_flags: Time [XXX] not included in timeline table.
Photon-arrival time lies outside the range of values
tabulated in the IDF. It will get a status flag, but
perhaps not the correct one.
- cf_thermal_distort: Cannot determine left STIM position. Estimating.
Cannot determine right STIM position. Estimating.
If cf_thermal_distort cannot determine a STIM position,
it will attempt to estimate the position using data
in the STIM_CAL file. Wavelength errors may result.
- read_tle: Orbital elements are more than 5 days old.
You are using an old version of the FUSE.TLE file.
Get the end-of-mission version from the FUSE FTP site.
Next: Format of Housekeeping Files
Up: DH_Final
Previous: Intermediate Data File Header
Contents