id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
565	psFitsWriteImage specification clarifications/enhancements	robert.desonia@…	eugene	"psFitsWriteImage is specified to write ""in the file at the current position of the psFits pointer"" (i.e., the 
CHDU).  Is it your intention that the existing HDU that the CHDU pointer was pointing at would be 
replaced with the new IMAGE HDU?  This is, of course, not a typical CFITSIO behavior.

The raw CFITSIO options are to a) have a new HDU appended to the end of the file, which is how it was 
originally implemented, b) inserted after the current HDU, or c) prepended to the beginning of the file, 
i.e., made the primary HDU.

I could insert a new HDU after the current HDU and then delete the previously set CHDU, but I don't 
know if it is really a good idea to implicitly delete data.  Would it be better/safer to either insert the new 
HDU before or after the CHDU and force the user to manually remove the old HDU via psFitsDeleteExt*?

-rdd"	defect	closed	high		PSLib SDRS	unspecified	normal	fixed