View on GitHub

IRAF Community Distribution

IRAF maintained by the community

Home | Installation | Packages | X11IRAF | PyRAF | Forum

mscred.ccdproc and IRAF 2.15

Robert Janusz wrote on Nov 29, 2010

I installed successfully the latest IRAF and installed the mscred package. The difference is that now making the ccdproc with bpmasks = "" and fixfile = "" I get the message:
List of output bad pixel masks:
(twice) and I must press [Enter] to continue. How can I switch it off to go automatically?

Francisco Valdes wrote on Nov 29, 2010

A query occurs when either the parameter is a "query" parameter and is not specified on the command line or there is no value (which is different than a null string values). Neither should be occurring. I suggest you do "unlearn ccdproc" and see if the problem remains. If it does post the output of "lpar ccdproc".

Frank Valdes

Robert Janusz wrote on Nov 29, 2010

This is the situation before the unlearned state
mscred
the output is:
This is the initial release of the IRAF FITSUTIL package
to include support for FITS tile compression via 'fpack'.
Please send comments and questions to seaman@noao.edu.
ccdhedit...

Now
mscred> lpar ccdproc
is:
       images = "b0116"         List of Mosaic CCD images to process
      (output = "")             List of output processed images
     (bpmasks = "")             List of output bad pixel masks
     (ccdtype = "")             CCD image type to process
      (noproc = no)             List processing steps only?\n
    (xtalkcor = no)             Apply crosstalk correction?
      (fixpix = no)             Apply bad pixel mask correction?
    (overscan = yes)            Apply overscan strip correction?
        (trim = yes)            Trim the image?
     (zerocor = no)             Apply zero level correction?
     (darkcor = no)             Apply dark count correction?
     (flatcor = no)             Apply flat field correction?
    (sflatcor = no)             Apply sky flat field correction?
       (split = no)             Use split images during processing?
       (merge = yes)            Merge amplifiers from same CCD?\n
   (xtalkfile = "")             Crosstalk file
     (fixfile = "")             List of bad pixel masks
  (saturation = "INDEF")        Saturated pixel threshold
       (sgrow = 0)              Saturated pixel grow radius
       (bleed = "INDEF")        Bleed pixel threshold
      (btrail = 20)             Bleed trail minimum length
       (bgrow = 0)              Bleed pixel grow radius
     (biassec = "[1020:1035,9:2024]") Overscan strip image section
     (trimsec = "[9:1016,9:2024]") Trim data section
        (zero = "")             List of zero level calibration images
        (dark = "")             List of dark count calibration images
        (flat = "")             List of flat field images
       (sflat = "")             List of secondary flat field images
  (minreplace = 1.)             Minimum flat field value\n
 (interactive = no)             Fit overscan interactively?
    (function = "legendre")     Fitting function
       (order = 12)             Number of polynomial terms or spline pieces
      (sample = "*")            Sample points to fit
    (naverage = 1)              Number of sample points to combine
    (niterate = 1)              Number of rejection iterations
  (low_reject = 3.)             Low sigma rejection factor
 (high_reject = 3.)             High sigma rejection factor
        (grow = 0.)             Rejection growing radius
          (fd = "")             
         (fd2 = "")             
        (mode = "ql")           

So I run the ccdproc with s1='b0108':
mscred> ccdproc(s1)
List of output bad pixel masks: # I press [ENTER]
List of output bad pixel masks: # The same

So now I unlearn and run again:
unl ccdproc
mscred> ccdproc(s1)

And here is the same question:
List of output bad pixel masks: 
List of output bad pixel masks: 

and then the error occurs (of course)
ERROR: Size of DATASEC and CCDSEC do not agree
  "low_reject=low_reject, high_reject=high_reject, grow=grow)"
     line 286: mscsrc$ccdproc.cl
     called as: `ccdproc (images=b0108)' 

Robert Janusz wrote on Nov 29, 2010

whom should I ask about the problem?

Francisco Valdes wrote on Nov 29, 2010

I have been trying to reproduce the problem with the query for bad pixel masks. I have not been able to do so. What you can do to help is turn on the verbose trace debugging output. Right before you execute the command type "d_tace". This will produce a lot of output. What we are interested in is the output before the problem for the bad pixel mask. In particular what task is being executed and all the parameter information. To turn off the debugging you type the same command again; i.e. d_trace. You might need to do scrollback a ways, though because there is a pause at the prompt you can scrollback and cut out the relevant information.

As for the mismatched sections I would need to see a header listing of at least one extension.

Frank

Robert Janusz wrote on Nov 29, 2010

I was trying to resolve the problem and I found the method to avoid it. I realized that when I make
epar _ccdtool
then I get
input   =                       List of input CCD images to process
output  =                       List of output processed CCD images
nointerp=                       List of output uninterpolated images
bpmasks =                       List of output bad pixel masks
(calproc=                     ) List of calibration images to be processed ...
what means the bpmasks is not hidden as it should be. So after saving the parameters with a dummy input I go to uparm/msd_ccdtl.par and I switch the line
bpmasks,s,a,"",,,"List of output bad pixel masks"
to the line
bpmasks,s,h,"",,,"List of output bad pixel masks"
so the hidden ccdproc.bpmasks corresponds to the hidden _ccdtool.bpmask now. This is anyway a work around method of doing it. To make the problem resolved I entered the /iraf/iraf/extern/mscred/src/_ccdtool.par and as root I made the analogous correction. Now the mscred.ccdproc does not ask about the List of output bad pixel masks anymore. Do you agree with this solution?

By the way. Need I have root privileges to be able to install IRAF? Can I install it as a local user? It would be very nice to have this possibility.

Regards,

rj

Robert Janusz wrote on Nov 29, 2010

In the mscred package the unlearned setinstr shows the directory mscdb$noao/ but there is no package mscdb anymore (and the mscdb$ as well) in the IRAF 2.15, so perhaps this should be somehow corrected.

Regards,

rj

Mike Fitzpatrick wrote on Nov 29, 2010

MSCDB never was distributed with the core system, it is a separate installation like the MSCRED package itself.

I just added this to the v2.15 dynamic package repository, however a manually installation will work as well.

Last post on Nov 29, 2010