mscred ccdproc and mosaic2 xtalk file
Edward Olszewski wrote on Dec 14, 2010
For my late-Nov 2010 CTIO Mosaic2 data, the crosstalk file embedded
in the header is mscdb$noao/Mosaic2/CAL0102/xtalkB0102
This file does not seem to exist.
CCDPROC is unhappy.
My collaborator, at the telescope, fooled iraf by copying xtalkA0102
into B0102, but there must be a real B0102?
We were using Mosaic2 with 8 amps.
ed olszewski
steward observatory
in the header is mscdb$noao/Mosaic2/CAL0102/xtalkB0102
This file does not seem to exist.
CCDPROC is unhappy.
My collaborator, at the telescope, fooled iraf by copying xtalkA0102
into B0102, but there must be a real B0102?
We were using Mosaic2 with 8 amps.
ed olszewski
steward observatory
Francisco Valdes wrote on Dec 14, 2010
Hi Ed,
This (changing what goes into the header) is something that someone at CTIO must have done. I don't know about the file you reference or where it might be located. As you say it is not in the mscdb$ files. I'm not sure who to ask but it might be Andrea Kunder or Tim Abbot. I've not have anything to do with the data taking system at CTIO for many years.
It is certainly reasonable to do what you did to "fool" the code. You can also just tell ccdproc to use a particular file rather than referencing the value of a keyword in the header. Since the crosstalk file is independent of the extension there is no real need to use the header keyword to get different values for different extensions. Or you could edit the header of course.
But there must be a good reason for the alternate file. In particular, the crosstalk for 16 vs 8 is definitely different.
Good hunting,
Frank
If you find out anything I would be interested though it seems I ought to make an inquiry myself.
This (changing what goes into the header) is something that someone at CTIO must have done. I don't know about the file you reference or where it might be located. As you say it is not in the mscdb$ files. I'm not sure who to ask but it might be Andrea Kunder or Tim Abbot. I've not have anything to do with the data taking system at CTIO for many years.
It is certainly reasonable to do what you did to "fool" the code. You can also just tell ccdproc to use a particular file rather than referencing the value of a keyword in the header. Since the crosstalk file is independent of the extension there is no real need to use the header keyword to get different values for different extensions. Or you could edit the header of course.
But there must be a good reason for the alternate file. In particular, the crosstalk for 16 vs 8 is definitely different.
Good hunting,
Frank
If you find out anything I would be interested though it seems I ought to make an inquiry myself.
travisrector wrote on Dec 14, 2010
I have encountered the same issue. Ed, Frank, did either of you find the answer to this?
-Travis
-Travis
Francisco Valdes wrote on Dec 14, 2010
I may have dropped the ball on communicating this. Below is the email I have on this subject. I did not change anything at the telescope because at this point the instrument is on its way out. I hope this exchange helps.
Frank
Frank
From: Frank Valdes <valdes@noao.edu>
Date: December 14, 2010 10:47:17 AM MST
To: Andrea Kunder <akunder@ctio.noao.edu>
Subject: Mosaic2 crosstalk
Hi Andrea,
I have been out of touch with what goes on with Mosaic2 at the telescope for a long time. I also can't remember who the instrument scientist is though I think it is now you? I got an email from Ed Olszewski about the crosstalk for Mosaic2. The gist of his question was
The header keyword for the crosstalk points to mscdb$noao/Mosaic2/CAL0102/xtalkB0102 which he doesn't know where to find.
I assume someone edited one of the KTM files to get this to happen for 8-amp data. The file does not exist for most people. Can I get a copy of this file?
Frank
From: Andrea Kunder <akunder@ctio.noao.edu>
Date: December 19, 2010 1:18:36 PM MST
To: Frank Valdes <valdes@noao.edu>
Subject: Re: Mosaic2 crosstalk
Hi Frank,
Sorry, sorry for the delay in my response. I was on vacation back packing through Torres del Paine National Park (in Patagonia) and had no internet access. I forgot to put an auto-reply to let people know I was gone.
The best cross talk file to use is attached here for 8 amplifier mode. Would it be possible for you to change the iraf pointer so that it points to this file instead? Or could you just rename this file and place it in the correct directory so that the crosstalk file exists?
I am the Mosaic2 Instrument Scientist, so please don't hesitate to bother me with any Mosaic2 suggestions/requests.
Best Regards,
Andrea
# XTCOEFF: NOAO/IRAF V2.13-BETA akunder@ctiow8.ctio.noao.edu Mon 13:33:59 08-Mar-2010
# Images Victim Bkg Source Bkg Victim Mask
# obj1034.fits Line median Line median
# obj1035.fits Line median Line median
im1 im2 0.001227 (0.000006, 222.9)
im2 im1 0.000611 (0.000004, 158.5)
im3 im4 0.001658 (0.000002, 820.5)
im4 im3 0.000050 (0.000003, 15.4)
im5 im6 0.000297 (0.000002, 122.7)
im6 im5 0.001571 (0.000019, 82.1)
im7 im8 0.001019 (0.000004, 262.2)
im8 im7 0.000929 (0.000004, 219.6)
travisrector wrote on Dec 14, 2010
Thanks!
Last post on Dec 14, 2010