From anita@barolo.as.utexas.edu Thu Mar 30 11:34:23 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 10:34:22 -0600 (CST) From: Anita Cochran To: raugh@astro.umd.edu, ludmilla@astro.umd.edu Subject: Another minor typo MIME-Version: 1.0 In the data set file for DIIV9P_ENC the overview says: This data set contains reduced comet 9P/Tempel 1 images acquired by the Deep Impact Impactor Target Sensor's Visible CCD (ITS) after after the Impactor was released from the Flyby spacecraft on July 3, 2005 UT. Note that the end of line two and beginning of line three both have "after" in them. -- Anita Cochran The University of Texas at Austin, Astronomy Department, 1 University Station C1400, Austin TX 78712-0259 EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 ______________________________________________________________________________ From anita@barolo.as.utexas.edu Thu Mar 30 12:14:31 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 11:14:30 -0600 (CST) From: Anita Cochran To: raugh@astro.umd.edu, ludmilla@astro.umd.edu Subject: typos, etc for calinfo.txt for DIIV9P_ENC MIME-Version: 1.0 X-Status: X-Keywords: X-UID: 141846 In contents The files are the result instrument calibration analysis, both of ground-based thermal-vacuum data and in-flight science calibrations. missing word "of". -- Anita Cochran The University of Texas at Austin, Astronomy Department, 1 University Station C1400, Austin TX 78712-0259 EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 ______________________________________________________________________________ From anita@barolo.as.utexas.edu Thu Mar 30 12:33:10 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 11:33:09 -0600 (CST) From: Anita Cochran To: raugh@astro.umd.edu, ludmilla@astro.umd.edu Cc: Anita Cochran Subject: Need help to understand some data MIME-Version: 1.0 X-Status: X-Keywords: X-UID: 141856 I am poking at DIIV9P_ENC and I am now thoroughly confused. I was looking at the abscalvs file. This is a fits file but appears to be only 2 numbers so I am not sure why it is fits. But, more importantly, I cannot make sense of it within IRAF. I can check the header and it tells me there are 2 pixels. I can imstat it and it will give me the values. But, since it says it is a look-up table I was assuming I could tdump or tprint it and see what those values are. The first of those gives "error" and the second "warning" but no numbers. What ARE these files? What am I supposed to do with these. I have not probed further yet but assume that I may have these issues with other files. I am pretty data savy and I am stumped. -- Anita Cochran The University of Texas at Austin, Astronomy Department, 1 University Station C1400, Austin TX 78712-0259 EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 ______________________________________________________________________________ From anita@barolo.as.utexas.edu Thu Mar 30 12:36:51 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 11:05:30 -0600 (CST) From: Anita Cochran To: raugh@astro.umd.edu, ludmilla@astro.umd.edu Subject: typo's etc in data_set for DIIV9P_ENC MIME-Version: 1.0 X-Status: X-Keywords: X-UID: 141858 Same data_set as the last one, under processing calibraton. For impact images, geometric parameters suc such as the target-to-spacecraft distance were computed with respect to the impact site, not the center of the comet. look at end of line 1 and beginning of line 2. And this gem makes no sense: The pipeline also creates a FITS image extension a signal-to-noise ratio map. Misspelling: pnuemonic and Calibration steps and files applied to each reduced FITS image is provided by PROCESSING_HISTORY_TEXT in the image labels. I think the verb should be are not is. and A 2-dimensional, reduced CCD images in this data set are stored in FITS format. either needs "image" and "is" or remove the word "A". and The first extension uses eight, bit flags to describe the quality of each pixel in the primary image. remove the comma after eight. Anita Cochran The University of Texas at Austin, Astronomy Department, 1 University Station C1400, Austin TX 78712-0259 EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 ______________________________________________________________________________ From stefmcl@astro.umd.edu Thu Mar 30 13:53:12 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 13:53:10 -0500 (EST) From: Stephanie McLaughlin To: Anita Cochran Cc: Ludmilla Kolokolova , Anne Raugh , Michael A'Hearn Subject: Re: Need help to understand some data (fwd) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-758783491-1143744790=:28012" X-Status: X-Keywords: X-UID: 141876 Content-Length: 61945 Hi Anita, Ludmilla forwarded your email to me. I am not familiar with IRAF. However, I have no problems reading and displaying the contents of the abscalvs file, itsvis_050112_3_0_1.fit, in IDL. The values are 3.5510000e-05 and 1426.2076. The FITS header and PDS label provide a description of each value. Could IRAF be complaining because the FITS file has only one axis with two elements? I read the abscalvs file into IDL, reformed the data into a 2-axis array, and wrote the results to a new FITS file. It's attached to this email as itsvis_050112_3_0_1_2axes.fit. Is IRAF happier with this file? Please let me know. This FITS file was provided by the mission's science data center, as it was used in the calibration pipeline. It is possible that we will need to reform the abscalvs FITS file into a two axis file for the final archive to accomodate non-IDL users. I see there is one other calibration file, named itsvis_000101_1_0.fit in the adclut subdirectory, that has only one axis. I bet IRAF will not like it, either, so I reformed it into a two-axis FITS and attached it as itsvis_000101_1_0_2axes.fit. Again, let me know you can see the data values via IRAF. All of the other calibration files have two or three axes, so IRAF should be able to handle them. Regards, stef On Thu, 30 Mar 2006, Ludmilla Kolokolova wrote: > Date: Thu, 30 Mar 2006 11:33:09 -0600 (CST) > From: Anita Cochran > To: raugh@astro.umd.edu, ludmilla@astro.umd.edu > Cc: Anita Cochran > Subject: Need help to understand some data > > I am poking at DIIV9P_ENC and I am now thoroughly confused. > I was looking at the abscalvs file. This is a fits file > but appears to be only 2 numbers so I am not sure why it is > fits. But, more importantly, I cannot make sense of it > within IRAF. I can check the header and it tells me > there are 2 pixels. I can imstat it and it will give > me the values. But, since it says it is a look-up table > I was assuming I could tdump or tprint it and see what > those values are. The first of those gives "error" and > the second "warning" but no numbers. What ARE these files? > What am I supposed to do with these. I have not probed further > yet but assume that I may have these issues with other files. > I am pretty data savy and I am stumped. > > -- > Anita Cochran > The University of Texas at Austin, Astronomy Department, > 1 University Station C1400, Austin TX 78712-0259 > EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 > ______________________________________________________________________________ From anita@barolo.as.utexas.edu Thu Mar 30 14:04:22 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 13:04:17 -0600 (CST) From: Anita Cochran To: Stephanie McLaughlin Cc: Ludmilla Kolokolova , Anne Raugh , "Michael A'Hearn" , Anita Cochran Subject: Re: Need help to understand some data (fwd) MIME-Version: 1.0 X-Status: X-Keywords: X-UID: 141877 Hi, Stephanie. I guess I did not explain the issue well. I can "look" at the file in iraf and do something like imstat (image statistics) and find out the two value. I can look at the headers. I can display the "image" of the two numbers. All that was fine in the original. I even figured out the two values. However, where I apparently tripped was that it says it is a table and the file has a .fits ending so I assumed it was therefore a fits table. That has a specific meaning. It is NOT a fits table and your email confirms this. So the problem is one of description. That said, does it really make any sense to have a two number fits file? It would seem to make more sense to have a flat ascii file. Note, that I could have used IDL but I always trend towards iraf for fits files and anything must be usable in either. I guess this is something we need to discuss at the review. -- Anita Cochran The University of Texas at Austin, Astronomy Department, 1 University Station C1400, Austin TX 78712-0259 EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 ______________________________________________________________________________ From stefmcl@astro.umd.edu Thu Mar 30 14:27:05 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Date: Thu, 30 Mar 2006 14:27:03 -0500 (EST) From: Stephanie McLaughlin To: Anita Cochran Cc: Ludmilla Kolokolova , Anne Raugh , Michael A'Hearn Subject: Re: Need help to understand some data (fwd) MIME-Version: 1.0 X-Status: A X-Keywords: X-UID: 141882 Hi Anita, Thank you for the additional information. And, I'm glad you figured out the two values in the abscalvs FITS file. We elected to archive all calibration files in the format used in the IDL-based calibration pipeline - FITS. The data center found it more convenient to work with FITS. We can discuss this file's format for the PDS archive at the review. I've made a note/lien to change the description for the abscalvs file because it is not a table. Regards, stef On Thu, 30 Mar 2006, Anita Cochran wrote: > Hi, Stephanie. I guess I did not explain the issue well. I can "look" > at the file in iraf and do something like imstat (image statistics) > and find out the two value. I can look at the headers. I can > display the "image" of the two numbers. All that was fine in > the original. I even figured out the two values. > > However, where I apparently tripped was that > it says it is a table and the file has a .fits ending so I assumed > it was therefore a fits table. That has a specific meaning. > It is NOT a fits table and your email confirms this. So the > problem is one of description. That said, does it really make > any sense to have a two number fits file? It would seem to > make more sense to have a flat ascii file. > > Note, that I could have used IDL but I always trend towards iraf > for fits files and anything must be usable in either. > > I guess this is something we need to discuss at the review. > > -- > Anita Cochran > The University of Texas at Austin, Astronomy Department, > 1 University Station C1400, Austin TX 78712-0259 > EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 > ______________________________________________________________________________ From ma@astro.umd.edu Thu Mar 30 17:00:11 2006 X-Original-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@icarus.astro.umd.edu Delivered-To: raugh@astro.umd.edu Mime-Version: 1.0 X-Sender: ma@halley.astro.umd.edu Date: Thu, 30 Mar 2006 17:00:18 -0500 To: Anita Cochran , Stephanie McLaughlin From: Mike A'Hearn Subject: Re: Need help to understand some data (fwd) Cc: Ludmilla Kolokolova , Anne Raugh , "Michael A'Hearn" , Anita Cochran X-Status: X-Keywords: X-UID: 141915 Amen - this makes no sense as a FITS file. mike At 1:04 PM -0600 30 3 2006, Anita Cochran wrote: >Hi, Stephanie. I guess I did not explain the issue well. I can "look" >at the file in iraf and do something like imstat (image statistics) >and find out the two value. I can look at the headers. I can >display the "image" of the two numbers. All that was fine in >the original. I even figured out the two values. > >However, where I apparently tripped was that >it says it is a table and the file has a .fits ending so I assumed >it was therefore a fits table. That has a specific meaning. >It is NOT a fits table and your email confirms this. So the >problem is one of description. That said, does it really make >any sense to have a two number fits file? It would seem to >make more sense to have a flat ascii file. > >Note, that I could have used IDL but I always trend towards iraf >for fits files and anything must be usable in either. > >I guess this is something we need to discuss at the review. > >-- > Anita Cochran > The University of Texas at Austin, Astronomy Department, > 1 University Station C1400, Austin TX 78712-0259 > EMAIL: anita@barolo.as.utexas.edu PHONE: 512-471-1471 -- Michael F. A'Hearn Tel: 301 405 6076 Department of Astronomy FAX: 301 405 3538 University of Maryland College Park MD 20742-2421 ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________