Question on a problem with IRAF Wavelength calibration via d
Guest wrote on Aug 31, 2006
Hi,
I have encountered a problem while reducing spectra with doecslit. The
problem appeared during the wavelength calibration. This is the output at
that point.
ECREIDENTIFY: NOAO/IRAF V2.12.1-EXPORT christip@dbs012 Wed 14:39:15
30-Aug-2006
Reference image = fpd_lwavl.2001-02-15T11_10_52.680.ec, Refit = yes
Image Found Fit Pix Shift User Shift Z Shift RMS
crfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.680.ec
106/107 106/106 -0.00251 0.00434 7.04E-9 0.284
Dispersion correct crfpd_datal.2001-02-15T00_51_21.822
Warning: Cannot open file
(database/eccrfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.)
Warning: Cannot open file
(database/idcrfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.)
Warning: crfpd_datal.2001-02-15T00_51_21.822.ec.imh: Dispersion data not
found
Now as you notice the reference image is
fpd_lwavl.2001-02-15T11_10_52.680.ec
but in the warnings it says that it can not find
fpd_lwavl.2001-02-15T11_10_52.
which is to be expected since it is not the right name but misses the last
3 digits.
I have also run the task with iraf v12.2 but the same thing happens and I
cannot pinpoint where the trouble comes from. In the past I have run this
task but no such probem ever occured. I would be grateful if you could
provide me a solution or a hint to find the problem.
Thank you in advance.
Christina
--
Papadaki Christina
PhD Student
Royal Observatory of Belgium
Avenue Circulaire 3
B - 1180 Bruxelles
e-mail:Christina.Papadaki@oma.be
tel: +32 (0) 23730291
Post generated using Mail2Forum (http://www.mail2forum.com)
I have encountered a problem while reducing spectra with doecslit. The
problem appeared during the wavelength calibration. This is the output at
that point.
ECREIDENTIFY: NOAO/IRAF V2.12.1-EXPORT christip@dbs012 Wed 14:39:15
30-Aug-2006
Reference image = fpd_lwavl.2001-02-15T11_10_52.680.ec, Refit = yes
Image Found Fit Pix Shift User Shift Z Shift RMS
crfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.680.ec
106/107 106/106 -0.00251 0.00434 7.04E-9 0.284
Dispersion correct crfpd_datal.2001-02-15T00_51_21.822
Warning: Cannot open file
(database/eccrfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.)
Warning: Cannot open file
(database/idcrfpd_datal.2001-02-15T00_51_21.822fpd_lwavl.2001-02-15T11_10_52.)
Warning: crfpd_datal.2001-02-15T00_51_21.822.ec.imh: Dispersion data not
found
Now as you notice the reference image is
fpd_lwavl.2001-02-15T11_10_52.680.ec
but in the warnings it says that it can not find
fpd_lwavl.2001-02-15T11_10_52.
which is to be expected since it is not the right name but misses the last
3 digits.
I have also run the task with iraf v12.2 but the same thing happens and I
cannot pinpoint where the trouble comes from. In the past I have run this
task but no such probem ever occured. I would be grateful if you could
provide me a solution or a hint to find the problem.
Thank you in advance.
Christina
--
Papadaki Christina
PhD Student
Royal Observatory of Belgium
Avenue Circulaire 3
B - 1180 Bruxelles
e-mail:Christina.Papadaki@oma.be
tel: +32 (0) 23730291
Post generated using Mail2Forum (http://www.mail2forum.com)
Francisco Valdes wrote on Aug 31, 2006
Hello Christina,
I am not sure what is causing your problem. It can be a little confusing because when there are long file names IRAF error messages sometime truncate the name. So you can't tell if the file name is really being truncated or just the error message. In any case my suggestion would be to try renaming your data to shorter names and seeing if that solves the problem. If you can do this that would have two benefits. One is that you would be able to reduce your data. The other is that by telling me that long names was the source of the problem the code could be potentially fixed and we would also have a record for other users.
Yours,
Frank Valdes
I am not sure what is causing your problem. It can be a little confusing because when there are long file names IRAF error messages sometime truncate the name. So you can't tell if the file name is really being truncated or just the error message. In any case my suggestion would be to try renaming your data to shorter names and seeing if that solves the problem. If you can do this that would have two benefits. One is that you would be able to reduce your data. The other is that by telling me that long names was the source of the problem the code could be potentially fixed and we would also have a record for other users.
Yours,
Frank Valdes
Last post on Aug 31, 2006