Error In Image Section Specification
»Systems »Misc »Sources »Virtual Observatory »Python »Non-IRAF Software »Open Positions »Resumes »Sitemail Archives »Test Forum Index>Help Desk>General IRAF New ccdproc iraf Topic Post Reply CCDPROC-Error in image section specification ccdproc astropy mwh 06/08/2010 08:06PM(Read 5938 times) Newbie Status: offline Registered: 06/04/2010 Posts: 9 Hello,I have been flatcombine iraf trying to process images using CCDPROC but have been getting the error message "Error in image section specification". According to other forum posts I have seen, iraf zerocombine this means that there is a problem in the image headers for my images. However, I have been unable to track down this error. One potential issue is that the headers were written by ACP and Maxim DL, but I'm not sure what this means for IRAF. How can I fix this? Here is a sample image header: [code:1:f733aadcb2] 001.B.100.2.2.fts[1528,1528][ushort]: 00021 No bad pixels, min=0., max=0. (old) Line storage mode, physdim [1528,1528], length of user area 5589 s.u. Created Tue 14:54:22 08-Jun-2010, Last modified Tue 10:11:00 08-Jun-2010 Pixel file "001.B.100.2.2.fts" [ok] EXTEND = T / File may contain extensions BSCALE = 1.000000E0 / REAL = TAPE*BSCALE + BZERO BZERO = 3.276800E4 / ORIGIN = 'NOAO-IRAF FITS Image Kernel July 2003' / FITS file originator DATE = '04/05/10 ' / Date FITS file was generated IRAF-TLM= '2010-06-08T15:11:00' / Time of last modification OBJECT = '00021 ' / Name of the object observed DATE-OBS= '2010-05-04T04:12:53' / [ISO 8601] UTC date/time of exposure start EXPTIME = 1.00000000000E+002 / [sec] Duration of exposure EXPOSURE= 1.00000000000E+002 / [sec] Duration of exposure SET-TEMP= -25.000000000000000 /CCD temperature setpoint in C CCD-TEMP= -24.783261750000005 /CCD temperature at start of exposure in C XPIXSZ = 24.000000000000000 /Pixel Width in microns (after binning) YPIXSZ = 24.000000000000000 /Pixel Height in microns (aft
Using ccdproc A Note on Errors Getting Started -- Changing the Default File Type Once you have taken all of your images and have transferred them to your computer, you will have to reduce them in order to get rid of background noise due to bias, dark, and flats. But first, you will need to set IRAF to handle fits files as default. Otherwise you will have to use the rfits command (See UNM Tutorial). In order to change the default, type in these steps: show imtype IRAF will print the type of image that is set as the default. It will probably print "imh" http://iraf.net/forum/viewtopic.php?showtopic=1464536 the first time you try this. set imtype="fits,noinherit" This will set the default image type to fits files. When you process images, IRAF will automatically spit out a fits file. Be sure to execute these commands at the cl prompt, or else it will not work correctly. If you want IRAF to always have fits files set as the default, you can alter your login file. In the Unix command http://www.physics.hmc.edu/Astronomy/Ireduce.html window, move into your iraf directory. Type ls. There will be a file called "login.cl". Open it in emacs by entering emacs login.cl & Look for the section, # Uncomment and edit to change the defaults. Underneath, on the last row, will be the parameter for image type. Change the last row to read set imtype = "fits,noinherit". Be sure to delete the "#" sign, or else this will not work. Press Ctrl+x Ctrl+s to save, then Ctrl+x Ctrl+c to exit. Open up iraf and check the image type. It will print "fits,noinherit". To display images, enter: display filename frame The file you have chosen will be displayed in the DS9 window. The frame parameter is a number which indicates which frame you want the image to pop up in. This way, you can have multiple images open. (See the DS9 Guide for more information.) If you don't enter a number, IRAF will prompt you for one. If you're not concerned about having more than one image open at a time, just choose "1" each time. Combining Bias Images In order to combine your bias images, you will have to use the task zerocombine. The first thing you should do is move into the appropriate directo
Admonition Images Image Figure Body Elements Topic Sidebar Line Block Parsed Literal Block Code Math Rubric Epigraph Highlights Pull-Quote Compound Paragraph Container Tables Table CSV Table List Table Document Parts Table of Contents Automatic Section Numbering Document Header & Footer References Target Footnotes Footnotes Citations HTML-Specific Meta Imagemap Directives for Substitution Definitions Replacement Text Unicode Character Codes Date Miscellaneous Including an External Document Fragment Raw Data Pass-Through Class Custom Interpreted Text Roles Setting the Default Interpreted Text Role Metadata Document Title Restructuredtext-Test-Directive Common Options This document describes the directives implemented in the reference reStructuredText parser. Directives have the following syntax: +-------+-------------------------------+ | ".. " | directive type "::" directive | +-------+ block | | | +-------------------------------+ Directives begin with an explicit markup start (two periods and a space), followed by the directive type and two colons (collectively, the "directive marker"). The directive block begins immediately after the directive marker, and includes all subsequent indented lines. The directive block is divided into arguments, options (a field list), and content (in that order), any of which may appear. See the Directives section in the reStructuredText Markup Specification for syntax details. Descriptions below list "doctree elements" (document tree element names; XML DTD generic identifiers) corresponding to individual directives. For details on the hierarchy of elements, please see The Docutils Document Tree and the Docutils Generic DTD XML document type definition. For directive implementation details, see Creating reStructuredText Directives. Admonitions Specific Admonitions Directive Types:"attention", "caution", "danger", "error", "hint", "important", "note", "tip", "warning", "admonition" Doctree Elements:attention, caution, danger, error, hint, important, note, tip, warning, admonition, title Directive Arguments:None. Directive Options::class:, :name: Directive Content:Interpreted as body elements. Admonitions are specially marked "topics" that can appear anywhere an ordinary body element can. They contain arbitrary body elements. Typically, an admonition is rendered as an offset block in a document, sometimes outlined or shaded, with a title matching the admonition type. For example: .. DANGER:: Beware killer rabb