I change the version to iraf 2.12.2 and Gemini 1.9 and add some lines into GMOSgratings.dat. The error never come again. I don't know why I have to use older version.
1) call to gsflat and the list of parameters
specflat,s,a,"nflat",,,"Output normalized flat (MEF)"
fl_slitcorr,b,h,no,,,"Correct output for Illumination/Slit-Function"
slitfunc,s,h,"",,,"Slit Function (MEF output of gsslitfunc)"
fl_keep,b,h,no,,,"Keep imcombined flat?"
combflat,s,h,"",,,"Filename for imcombined flat"
fl_over,b,h,no,,,"Subtract overscan level"
fl_trim,b,h,yes,,,"Trim off overscan region"
fl_bias,b,h,yes,,,"Subtract bias image"
fl_dark,b,h,no,,,"Subtract (scaled) dark image"
fl_qecorr,b,h,no,,,"QE correct the input images? (NOT YET IMPLEMENTED)"
fl_fixpix,b,h,yes,,,"Interpolate across chip gaps"
fl_vardq,b,h,no,,,"Create variance and data quality frames"
key_exptime,s,h,"EXPTIME",,,"Exposure time header keyword"
key_biassec,s,h,"BIASSEC",,,"Header keyword for overscan strip image section"
key_datasec,s,h,"DATASEC",,,"Header keyword for data section (excludes the overscan)"
rawpath,s,h,"",,,"GPREPARE: Path for input raw images"
sci_ext,s,h,"SCI",,,"Name of science extension"
var_ext,s,h,"VAR",,,"Name of variance extension"
dq_ext,s,h,"DQ",,,"Name of data quality extension"
key_mdf,s,h,"MASKNAME",,,"Header keyword for the MDF"
mdffile,s,h,"",,,"MDF to use if keyword not found"
mdfdir,s,h,"gmos$data/",,,"MDF database directory"
bpm,s,h,"",,,"Name of bad pixel mask file or image"
gaindb,s,h,"default",,,"Database with gain data"
gratingdb,s,h,"gmos$data/GMOSgratings.dat",,,"Gratings database file"
filterdb,s,h,"gmos$data/GMOSfilters.dat",,,"Filters database file"
bpmfile,s,h,"gmos$data/chipgaps.dat",,,"Info on location of chip gaps"
refimage,s,h,"",,,"Reference image for slit positions"
qe_refim,s,h,"",,,"QE wavelength reference image. (NOT YET IMPLEMENTED)"
fl_keep_qeim,b,h,yes,,,"Keep QE correction? (NOT YET IMPLEMENTED)"
qe_corrpref,s,h,"qecorr",,,"Prefix for QE correction files. (NOT YET IMPLEMENTED)"
qe_corrimages,s,h,"",,,"Name for QE correction data. (NOT YET IMPLEMENTED)"
qe_data,s,h,"gmosQEfactors.dat",,,"Data file that contains QE information. (NOT YET IMPLEMENTED)"
qe_datadir,s,h,"gmos$data/",,,"Directory containg QE data file. (NOT YET IMPLEMENTED)"
sat,s,h,"default",,,"Saturation level in raw images"
xoffset,r,h,INDEF,,,"X offset in wavelength [nm]"
yoffset,r,h,INDEF,,,"Y offset in unbinned pixels"
yadd,r,h,0.,,,"Additional pixels to add to each end of MOS slitlet lengths"
wave_limit,r,h,INDEF,,,"Upper wavelength limit of cut spectra (nm). Only for use with fl_detec=no."
fl_usegrad,b,h,no,,,"Use gradient method to find MOS slits"
fl_emis,b,h,no,,,"mask emission lines from lamp (affected pixels set to 1. in output)"
nbiascontam,s,h,"default",,,"Number of columns removed from overscan region"
biasrows,s,h,"default",,,"Rows to use for overscan region"
minval,r,h,INDEF,,1.,"Minimum pixel value in normalized flat"
fl_inter,b,h,no,,,"Fit response interactively?"
fl_answer,b,h,yes,,,"Continue interactive fitting?"
fl_detec,b,h,no,,,"Fit response detector by detector rather than slit by slit?"
fl_seprows,b,h,yes,,,"Fit and normalize each row separately?"
function,s,h,"spline3",spline3|legendre|chebyshev|spline1,,"Fitting function for response"
order,s,h,"15",,,"Order of fitting function, minimum value=1"
low_reject,r,h,3.,,,"Low rejection in sigma of response fit"
high_reject,r,h,3.,,,"High rejection in sigma of response fit"
niterate,i,h,2,,,"Number of rejection iterations in response fit"
zero,s,h,"none",,,"Image zeropoint offset"
nlow,i,h,1,0,,"minmax: Number of low pixels to reject"
nhigh,i,h,1,0,,"minmax: Number of high pixels to reject"
nkeep,i,h,0,0,,"Minimum to keep or maximum to reject"
mclip,b,h,yes,,,"Use median in sigma clipping algorithms?"
lsigma,r,h,3.,,,"Lower sigma clipping factor"
hsigma,r,h,3.,,,"Upper sigma clipping factor"
key_ron,s,h,"RDNOISE",,,"Keyword for readout noise in e-"
key_gain,s,h,"GAIN",,,"Keyword for gain in electrons/ADU"
ron,r,h,3.5,0.,,"Readout noise rms in electrons"
gain,r,h,2.2,1.0000000000000E-5,,"Gain in e-/ADU"
snoise,s,h,"0.0",,,"ccdclip: Sensitivity noise (electrons)"
sigscale,r,h,0.1,,,"Tolerance for sigma clipping scaling correction"
pclip,r,h,-0.5,,,"pclip: Percentile clipping parameter"
grow,r,h,0.,,,"Radius (pixels) for neighbor rejection"
ovs_flinter,b,h,no,,,"Interactive overscan fitting?"
ovs_med,b,h,no,,,"Use median instead of average in column bias?"
ovs_func,s,h,"chebyshev",spline3|legendre|chebyshev|spline1,,"Overscan fitting function"
ovs_order,i,h,1,,,"Order of overscan fitting function"
ovs_lowr,r,h,3.,,,"Low sigma rejection factor"
ovs_highr,r,h,3.,,,"High sigma rejection factor"
ovs_niter,i,h,2,,,"Number of rejection iterations"
fl_double,b,h,no,,,"Make double flats for nod-and-shuffle science"
nshuffle,i,h,0,,,"Number of shuffle pixels (unbinned)"
status,i,h,1,,,"Exit status (0=good)"
scanfile,*struct,h,"",,,"Internal use only"
Thank you for the information. You should not have to resort to using old versions of IRAF and the Gemini IRAF package.
Your home and uparm variables look good, as does the path to your uparm directory. However, I'm not sure why your login.cl is located in a different directory to your uparm directory. Did you move the login.cl file? Did you edit that file in any way? When you started iraf, were you located in the /home/by/use_iraf/ directory?
Can you confirm that you have write permissions to the /home/by/use_iraf/Q49/By_m101/tes/ directory (i.e., where the logfile is written to)?
I just ran gsflat on some random GMOS flats using the same parameters that you are using (including using a path to the logfile) and everything worked fine. Do you get the same error if you just set gsflat.logfile="mylog.log"?
There is a task in the Gemini IRAF package called install_check.cl that can be used to check a Gemini IRAF installation. You can define and execute the task by typing the following at the IRAF or PyRAF prompt:
There are some errors when I run the install_check.cl.
1) It seems that I don't have extern_check.log.
ERROR: No such environment variable
called as: `show (extern)'
"show extern | tee ("extern_check.log", out_type="text", append+)"
line 30: gemini$install_check_f.cl
called as: `install_check ()'
2) After I comment out the 30th line, it displays that some packages are not the most recent versions.
IRAF installation 2.14.1 with patch is up to date. PASS
stsdas v3.14 installed. PASS
tables v3.14 installed. PASS
no files found
fitsutil package not up to date. FAIL.
gmisc package not up to date. FAIL
gemini version: v1.11.1
gemini package less than v1.11. Need to update. FAIL
Linux localhost.localdomain 22.214.171.124-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 i686 i386 GNU/Linux
Apologies about the bug, I will fix that for the next release.
I noticed that your iraf installation is located in /home/iraf/iraf/ but the Gemini IRAF package is installed in /iraf/extern/gemini/. Do you have two installations of IRAF on your computer? Do you have an /iraf/iraf/ directory that contains another installation of IRAF? Where are all your other external packages located? Are they all in /home/iraf/extern/ or are they in /iraf/extern/? Which extern.pkg file did you edit?
I interlinked the folder /iraf to /home/iraf, so every user can use iraf.
I only have one IRAF, version 2.14.1, on the computer and all the IRAF packages are installed in the directory /iraf/extern/.
/home/iraf/extern/ and /iraf/extern/ are the same folders.
# External (non core-system) packages. To install a new package, add the
# two statements to define the package root directory and package task,
# then add the package helpdb to the `helpdb' list.
Are you able to provide me with details of your installation procedure? Did you get any errors when you ran the install script? I looked through http://iraf.net/irafdocs/pciraf.pdf and noted that the $iraf variable was set prior to running the install script. I assume this is when you set $iraf to /home/iraf/iraf/? Was the /iraf link set prior to running the install script?
Are you in a position to install IRAF in the standard location (i.e., /iraf) as a test to see if that solves the problem?
When you are testing the two different versions of the Gemini IRAF package, how are you switching between them? Do you have both versions installed somewhere on your machine or are you overwriting the installation in the gemini directory in the extern directory each time?
Finally, are you able to provide me with a copy of your ~/.cshrc file? It is possible that something is set in this file that could be causing the problem.
Thank you for the information. I am a little confused ... you said that you have IRAF installed in /home/iraf ... if that was the case, then when you made all the IRAF directories, wouldn't you have made /home/iraf/irafbin etc? Also, the install_check output indicates that you set iraf to /home/iraf/iraf/ (rather than /iraf/iraf/local as you mentioned in your last message). I do think the problem is related to your IRAF installation (especially because I am unable to reproduce the problem).
Would it be possible for you to re-install IRAF on your laptop in the standard location (i.e., /iraf) to see if that solves the problem? I can help you through this, if required. Just let me know
I just wanted to let you know that I have been working with another user via the Gemini HelpDesk who had a very similar problem to you (they even had the same setup!), and a fresh install solved their problem
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum