This is just a listing I'm starting of error messages I see while doing UVOT analysis of supernovae , what the real problem was, and how to fix it. Most (possibly all) are not issues with the software but problems with how one is trying to use the software.
uvotmaghist getting hung up -- activity monitor listing uvotinteg as taking 99% of the CPU time but not getting anywhere.
problem -- region files contained two lines, one with the correct source position and one with some other position not in the field of view
fix -- fix the region files, rerun uvotmaghist
uvotmaghist reporting divide by zero error --
problem -- background region was not covered by the image (though it may have fallen within the zero count square made to encompass the full height and width of the image). Especially a problem when combining full field and smaller hardware/software windows.
fix -- fix the region so it stays within the image for all the images being processed with uvotmaghist
frankenstein images where parts of a summed image seem to be wrapped around rather than just mosaiced
problem -- I think the problem was having multiple instances of uvotimsum running at the same time so the parameter file contained values from the other terminal
fix -- do them one at a time rather than multi-tasking the same command in different windows
if the galaxy count rates come out as negative, it could be that the supernova comes from a clean region and the background region happens to have a higher average count rate. But the source region file could be bogus -- two entries for example -- confusing the standard 5" aperture that is computed for coincidence loss.
processing vv data for PSNJ09100885+5003396
# Beware of galaxy count rates > ~ 6
vv count rate is 1.65534055233002
ftcalc(4838,0x7fff7375f000) malloc: *** error for object 0x7fca3af001d0: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
^CAbort
Dumping CFITSIO error stack:
--------------------------------------------------
ffopen could not interpret primary array header of file:
PSNJ09100885+5003396_vv_phot.fits
--------------------------------------------------
CFITSIO error stack dump complete.
CFITSIO ERROR END_OF_FILE: tried to move past end of file
Task fthedit 2.00 terminating with status 107
fparkey4.3 : unable to open the FITS file PSNJ09100885+5003396_vv_phot.fits
fparkey4.3 : Error Status Returned : 107
fparkey4.3 : tried to move past end of file
fparkey4.3 : ***** FITSIO Error Stack Dump *****
ffopen could not interpret primary array header of file:
PSNJ09100885+5003396_vv_phot.fits
Dumping CFITSIO error stack:
--------------------------------------------------
ffopen could not interpret primary array header of file:
PSNJ09100885+5003396_vv_phot.fits
--------------------------------------------------
CFITSIO error stack dump complete.
CFITSIO ERROR END_OF_FILE: tried to move past end of file
Task fthedit 2.00 terminating with status 107
Dumping CFITSIO error stack:
--------------------------------------------------
ffopen could not interpret primary array header of file:
PSNJ09100885+5003396_vv_phot.fits
--------------------------------------------------
CFITSIO error stack dump complete.
CFITSIO ERROR END_OF_FILE: tried to move past end of file
Task fthedit 2.00 terminating with status 107
Dumping CFITSIO error stack:
--------------------------------------------------
fix -- this may have been caused by the '+' in the name. Changing the name to PSN it ran fine.
