Bugs: dmcontour - CIAO 3.4

[CIAO Logo]

CIAO 3.4 Homepage
CIAO 4.1 Homepage
Introduction: Welcome; Tools & Applications
Data Analysis: Analysis Guides; Science Threads; Sherpa Threads; ChaRT Threads; Why Topics; Help Pages (AHELP)
Sherpa (Modeling & Fitting)
S-Lang in CIAO
Documentation: "Watch Out" List; Bug List; Frequently Asked Questions (FAQ); Manuals; Dictionary; Chandra Publications; Software Survey Results
Download CIAO: Download CIAO 3.4; Platform Support; Release Notes; Version History; Analysis Scripts; CIAO Web Pages; Contributed Software
Data Products: Data Basics; Data Products Guide; Data Caveats; Reprocessing III; Pipeline Processing (SDP); Chandra Archive
Workshops
CXC Links: CALDB; ATOMDB; WebGUIDE; ChaRT; Astrostatistics Collaboration; CXO Cross-calibration Page
Site Map

Matching CIAO and CALDB Versions

CIAO 3.4 requires CALDB 3.3.0 or higher to operate properly.

CALDB 3.4.0 and higher should not be used unless you are running CIAO 3.4 or CIAO 4.0.

Are your versions mismatched? Time to update CIAO and CALDB!

News Previous Items

11 Nov 2008

These are the webpages relative to the CIAO 3.4 release (18 December 2006). They are no longer actively updated, however the CXC will continue limited support of CIAO 3.4 for the near future.

CIAO 3.4 users should check the CALDB 3 website for compatible calibration updates.

15 Dec 2008

The newest version of the Chandra Interactive Analysis of Observations software, is CIAO 4.1, released on 15 December 2008. Read the release notes for detailed information. This release requires that CALDB 4.1.0 be installed for the software to work correctly.

Bugs

Problems at the edge of images (01 Dec 2006)

When a contour intersects the edge of an image, dmcontour draws a frame around the image and creates contours that are marked as "exclude" regions (i.e. have a red line through them when displayed in ds9).

Workaround:

If you are running into this problem, you have to make sure that your contours don't have a value that occurs at the edge of the image. The safest way to do this is to check the max value for the bounding rows/edges and then choose your contour level to be greater than that. It looks tedious, but you could script this if you are doing it often:

unix% dmlist image.fits blocks
 
--------------------------------------------------------------------
Dataset: image.fits
--------------------------------------------------------------------
 
     Block Name                          Type         Dimensions
--------------------------------------------------------------------
Block    1: CONVOLVE                       Image      Real4(263x218)


unix% dmstat image.fits"[#2=1]" median=yes centroid=no |grep max
    max:        2.8171137093e-18              @:        ( 3856.13 4208.04 )

unix% dmstat image.fits"[#1=1]" median=yes centroid=no |grep max
    max:        3.6766300528e-18              @:        ( 3840.33 4214.44 )

unix% dmstat image.fits"[#1=263]" median=yes centroid=no |grep max
    max:        5.2055576098e-18              @:        ( 3866.53 4229.24 )

unix% dmstat image.fits"[#2=218]" median=yes centroid=no |grep max
    max:        7.753583262e-18               @:        ( 3863.73 4229.64 )

So as long as the contour level is > 7.75e-18, you won't get the frame/exclude behavior.

This doesn't mean that you can't choose contours lower than the max value. It just means that by setting your bar above the highest, you know that you will not run into this bug.