Questions about xdimsum
kenney wrote on Jun 30, 2008
I am having trouble with xdimsum, which I am running on redhat, and was hoping someone might be able to help. First, I am determining my shifts interactively and am able to do so, but I get a message that the shifts files is undefined. When I create a blank file for the shifts to be written into, I get a different error about it being a blank file.
Second, I define root names and suffixes where asked, and the suffixes only sometimes work. For the combined input image, I have the root name defined in the parameter file, but I get:
The combined input image S0_fp does not exist.
How do I create template files, or how do I get this function to work?
Thank you!
Second, I define root names and suffixes where asked, and the suffixes only sometimes work. For the combined input image, I have the root name defined in the parameter file, but I get:
The combined input image S0_fp does not exist.
How do I create template files, or how do I get this function to work?
Thank you!
kenney wrote on Jun 30, 2008
I got through my previous problem, but now have a new one, which is pasted below. Note that all the parameters are also listed below. I've looked at similar problems in other threads, but the problems are not the same. Could anyone help, please?
-------Deregistering unzap mask subsections ---------------
Making object masks for image: ----------------------------------------------------------------------------
ERROR: Attempt to access undefined local variable `ix'.
"msect = "["//ix//":"//fx//","//iy//":"//fy//"]""
line 105: xdimsum$src/maskdereg.cl
called as: `maskdereg (omask=S0_fp.mski.pl, sections=S0_fp.corners, outlist=@tmp$xmaskpass2797g, y2n_angle=0., rotation=yes, mkcrmask=yes, update=yes)'
"rotation=rotation, update+, mkcrmask+)"
line 382: xdimsum$src/xmaskpass.cl
called as: `xmaskpass (input=S0_fp, inexpmap=S0_fp.exp, sections=S0_fp.corners, output=S0_mp, outexpmap=S0_mp.exp, statsec=, nsigrej=3., maxiter=20, mkmask=no, omask=.msk, chkmasks=no, mstatsec=, nsigcrmsk=1.5, nsigobjmsk=1.1, negthresh=yes, ngrow=3, maskdereg=yes, ocrmasks=.ocm, objmasks=.obm, xslm=yes, sslist=.sub, newxslm=no, hmasks=.hom, forcescale=yes, useomask=yes, nmean=6, nskymin=3, nreject=1, cache=no, maskfix=yes, bpmask=niri_bpm.pl, forcefix=yes, xzap=yes, crmasks=.crm, newxzap=no, badpixupdate=yes, nrepeats=11, xnregistar=no, shiftlist=, rmasks=.rjm, nprev_omask=0, fractional=no, pixin=yes, ab_sense=yes, xscale=1., yscale=1., a2x_angle=0., mag=1., blkrep=yes, ncoavg=1, secpexp=1., y2n_angle=0., rotation=yes, del_bigmasks=no, del_smallmasks=no)'
"del_smallmasks=del_smallmasks)"
line 186: xdimsum$src/xmosaic.cl
called as: `xmosaic (inlist=@HD19994.txt, reference=S0882nfm.fits, output=S0, expmap=.exp, mp_xslm=yes, mp_maskfix=yes, mp_xzap=yes, mp_badpixupdate=yes, mp_xnregistar=no, maxiter=20, cache=no, bpmask=niri_bpm.pl, nrepeats=11, mp_mag=1., mp_kpchking=no, mp_negthresh=yes, mp_ngrow=3)'
-------Deregistering unzap mask subsections ---------------
Making object masks for image: ----------------------------------------------------------------------------
ERROR: Attempt to access undefined local variable `ix'.
"msect = "["//ix//":"//fx//","//iy//":"//fy//"]""
line 105: xdimsum$src/maskdereg.cl
called as: `maskdereg (omask=S0_fp.mski.pl, sections=S0_fp.corners, outlist=@tmp$xmaskpass2797g, y2n_angle=0., rotation=yes, mkcrmask=yes, update=yes)'
"rotation=rotation, update+, mkcrmask+)"
line 382: xdimsum$src/xmaskpass.cl
called as: `xmaskpass (input=S0_fp, inexpmap=S0_fp.exp, sections=S0_fp.corners, output=S0_mp, outexpmap=S0_mp.exp, statsec=, nsigrej=3., maxiter=20, mkmask=no, omask=.msk, chkmasks=no, mstatsec=, nsigcrmsk=1.5, nsigobjmsk=1.1, negthresh=yes, ngrow=3, maskdereg=yes, ocrmasks=.ocm, objmasks=.obm, xslm=yes, sslist=.sub, newxslm=no, hmasks=.hom, forcescale=yes, useomask=yes, nmean=6, nskymin=3, nreject=1, cache=no, maskfix=yes, bpmask=niri_bpm.pl, forcefix=yes, xzap=yes, crmasks=.crm, newxzap=no, badpixupdate=yes, nrepeats=11, xnregistar=no, shiftlist=, rmasks=.rjm, nprev_omask=0, fractional=no, pixin=yes, ab_sense=yes, xscale=1., yscale=1., a2x_angle=0., mag=1., blkrep=yes, ncoavg=1, secpexp=1., y2n_angle=0., rotation=yes, del_bigmasks=no, del_smallmasks=no)'
"del_smallmasks=del_smallmasks)"
line 186: xdimsum$src/xmosaic.cl
called as: `xmosaic (inlist=@HD19994.txt, reference=S0882nfm.fits, output=S0, expmap=.exp, mp_xslm=yes, mp_maskfix=yes, mp_xzap=yes, mp_badpixupdate=yes, mp_xnregistar=no, maxiter=20, cache=no, bpmask=niri_bpm.pl, nrepeats=11, mp_mag=1., mp_kpchking=no, mp_negthresh=yes, mp_ngrow=3)'
Mike Fitzpatrick wrote on Jun 30, 2008
The 'ix' variable is filled when scanning the sections file, you're likely seeing the error because there were enough/any values in that file and so it is undefined.
The sections file in this case should be "S0_fp.corners" which should contain the image name and corner values; It appears the image name is not valid so you might examine that file to see what's in it. This file is apparently written by XNREGISTER. Frank is the current expert on the package and I'm sure will respond when he gets a chance, hopefully this will give you something to look for in the meantime.
-Mike
The sections file in this case should be "S0_fp.corners" which should contain the image name and corner values; It appears the image name is not valid so you might examine that file to see what's in it. This file is apparently written by XNREGISTER. Frank is the current expert on the package and I'm sure will respond when he gets a chance, hopefully this will give you something to look for in the meantime.
-Mike
kenney wrote on Jun 30, 2008
There was a problem in the .corners file, and this occurs when I first run xmosaic. For the first run, I leave the sections parameter as the suffix .corners. However, for this and each one of the other parameters that ask for suffixes, I get errors that the files do not exist. As I am new to iraf, the only fix I could think of was to have template files with the names xmosaic was looking for so xmosaic would overwrite them. This, obviously, did not work.
Do you know how to work with the actual problem?
Do you know how to work with the actual problem?
Mike Fitzpatrick wrote on Jun 30, 2008
Sorry, I don't know much about the package but have asked Frank to comment.
-Mike
-Mike
Francisco Valdes wrote on Jun 30, 2008
Hello,
I've been traveling so I apologize for the delay in responding. I would need to see the actual error messages being output to really comment. What would possibly lead to a quick resolution is if you would include a listing of the parameters you are using (the output of lpar or dpar) and the screen output that would show the command line you use and any output you see. Any input files that are either generated earlier or that you created outside of the program should also be included. I would then be able to duplicate your behavior, using dummy data since I don't think any of your problems depend on the specific data. If you have a list of images then include the number of images in the list.
It may be that the messages you mention are warnings which you can ignore. Some scripts attempt to delete files just to be safe and if the file doesn't exist it simply results in a warning message.
Yours,
Frank Valdes
I've been traveling so I apologize for the delay in responding. I would need to see the actual error messages being output to really comment. What would possibly lead to a quick resolution is if you would include a listing of the parameters you are using (the output of lpar or dpar) and the screen output that would show the command line you use and any output you see. Any input files that are either generated earlier or that you created outside of the program should also be included. I would then be able to duplicate your behavior, using dummy data since I don't think any of your problems depend on the specific data. If you have a list of images then include the number of images in the list.
It may be that the messages you mention are warnings which you can ignore. Some scripts attempt to delete files just to be safe and if the file doesn't exist it simply results in a warning message.
Yours,
Frank Valdes
Last post on Jun 30, 2008