Welcome to iraf.net Tuesday, May 14 2024 @ 05:10 PM GMT


 Forum Index > Help Desk > Applications New Topic Post Reply
 xnregistar problem
   
ginger
 07/27/2010 03:53AM (Read 3048 times)  
+----
Newbie

Status: offline


Registered: 07/26/2010
Posts: 2
I am attempting to use xnregistar to combine the xdimsum demo images (subtracted) using offsets computed with xdshifts. However, I continue to be unsuccessful. Here is the epar for xnregister:
PACKAGE = xdimsum,
TASK = xnregistarinlist = shifts List of sky subtracted images, N and E shifts, and exposures
rmasks = Input rection mask keyword or rejection mask list
output = firstpassfinal The output combined image name
expmap = expmap The output exposure map image
sections= sections The optional output sections file
(sinlist= demo.list) The list of image names to be written to sections
(blkrep = yes) Use blkrep rather than magnify ?
(mag = 1.) Block replication factor
(fractio= yes) Use fractional pixel shifts if mag = 1?
(pixin = yes) Are input coords in ref object pixels?
(ab_sens= yes) Is A thru B counterclockwise?
(xscale = 1.) X pixels per A coordinate unit
(yscale = 1.) Y pixels per B coordinate unit
(a2x_ang= 0.) Angle in degrees from A CCW to X
(ncoavg = 1) Number of coaverages per image
(secpexp= 1.) Seconds per unit exposure time
(y2n_ang= 0.) Angle in degrees from Y to N N thru E
(rotatio= yes) Is N thru E CCW?
(imglist= )
(nimglis= )
(rimglis= )
(shimgli= )
(cmimgli= )
(mode = ql)the shifts file is just the output of xdshifts that looks like:subdemo01 0.000 0.000 1.0
subdemo02 -6.354 -0.133 1.0
subdemo03 -13.224 -0.581 1.0
subdemo04 -19.420 -0.697 1.0
subdemo05 -25.969 -0.504 1.0
subdemo06 -1.375 -7.244 1.0
subdemo07 -7.778 -7.623 1.0
subdemo08 -12.664 -6.165 1.0
subdemo09 -19.014 -6.265 1.0
subdemo10 -25.917 -6.238 1.0
subdemo11 -0.661 -13.033 1.0
subdemo12 -7.332 -13.368 1.0
subdemo13 -13.968 -13.422 1.0
subdemo14 -20.312 -13.922 1.0
subdemo15 -25.416 -12.502 1.0
subdemo16 -0.487 -19.006 1.0
subdemo17 -7.006 -19.019 1.0
subdemo18 -13.347 -19.352 1.0
subdemo19 -20.040 -19.675 1.0
subdemo20 -26.873 -20.209 1.0
subdemo21 -1.772 -26.404 1.0
subdemo22 -6.034 -25.005 1.0
subdemo23 -12.896 -25.258 1.0
subdemo24 -19.155 -25.533 1.0
subdemo25 -26.271 -25.476 1.0
The error message I get is, "The input and sections image lists are not the same size"Perhaps I misunderstand, but I thought the sections file was an output file, so if it is just the name of a file, why is it necessary to match the input (which I assume is "inlist") to it? I've also tried: specifying infile=@shifts and/or specifying sections="", but this gives the error messages:Warning: Cannot open file (subdemo010.0000.0001.0)
Warning: Cannot open file (subdemo02-6.354-0.1331.0)
Warning: Cannot open file (subdemo03-13.224-0.5811.0)
Warning: Cannot open file (subdemo04-19.420-0.6971.0)
Warning: Cannot open file (subdemo05-25.969-0.5041.0)
Warning: Cannot open file (subdemo06-1.375-7.2441.0)
Warning: Cannot open file (subdemo07-7.778-7.6231.0)
Warning: Cannot open file (subdemo08-12.664-6.1651.0)
Warning: Cannot open file (subdemo09-19.014-6.2651.0)
Warning: Cannot open file (subdemo10-25.917-6.2381.0)
Warning: Cannot open file (subdemo11-0.661-13.0331.0)
Warning: Cannot open file (subdemo12-7.332-13.3681.0)
Warning: Cannot open file (subdemo13-13.968-13.4221.0)
Warning: Cannot open file (subdemo14-20.312-13.9221.0)
Warning: Cannot open file (subdemo15-25.416-12.5021.0)
Warning: Cannot open file (subdemo16-0.487-19.0061.0)
Warning: Cannot open file (subdemo17-7.006-19.0191.0)
Warning: Cannot open file (subdemo18-13.347-19.3521.0)
Warning: Cannot open file (subdemo19-20.040-19.6751.0)
Warning: Cannot open file (subdemo20-26.873-20.2091.0)
Warning: Cannot open file (subdemo21-1.772-26.4041.0)
Warning: Cannot open file (subdemo22-6.034-25.0051.0)
Warning: Cannot open file (subdemo23-12.896-25.2581.0)
Warning: Cannot open file (subdemo24-19.155-25.5331.0)
Warning: Cannot open file (subdemo25-26.271-25.4761.0)
The input and sections image lists are not the same size
I am at a loss. I'm not sure if I'm just putting my files in the wrong format, or misunderstanding something else. Any help is greatly appreciated!
-Ginger

 
Profile Email
 Quote
emma
 07/27/2010 03:53AM  
++++-
Regular Member

Status: offline


Registered: 01/23/2006
Posts: 101
Hello ginger,In the helpfile for xnregistar, it says that the sections parameter is 'The optional output sections or corners file suitable for input to the maskdereg task. If defined sections contains the name of the input images in sinlist if it is defined or inlist, the x and y coordinates of the lower left corner of the input image in the combined output image, and the x and y coordinates of the upper right corner of the input image in the output image in columns 1 through 5 respectively.' while the sinlist parameter is 'The list of image names that will be written to the sections file. If sinlist is undefined then the input image names in inlist are used.'I notice that you have the sinlist parameter set to 'demo.list'. What is contained in this file? Does it exist? I think that if you set sections="" [i:9ed76b3008]and[/i:9ed76b3008] sinlist="" then the task should run without complaining WinkHope that helps?Many thanks,Emma Smile

 
Profile Email
 Quote
ginger
 07/27/2010 03:53AM  
+----
Newbie

Status: offline


Registered: 07/26/2010
Posts: 2
Emma,
Thanks! That did work, and led me to find the answer to my problem.It seems I just was putting @ signs where I didn't need them and not putting them where I did. Here's an epar of the configuration that worked:PACKAGE = xdimsum,
TASK = xnregistarinlist = shifts List of sky subtracted images, N and E shifts, a
rmasks = Input rection mask keyword or rejection mask lis
output = firstpassfinal The output combined image name
expmap = expmap The output exposure map image
sections= sections The optional output sections file
(sinlist= @demo.list) The list of image names to be written to section
(blkrep = yes) Use blkrep rather than magnify ?
(mag = 1.) Block replication factor
(fractio= yes) Use fractional pixel shifts if mag = 1?
(pixin = yes) Are input coords in ref object pixels?
(ab_sens= yes) Is A thru B counterclockwise?
(xscale = 1.) X pixels per A coordinate unit
(yscale = 1.) Y pixels per B coordinate unit
(a2x_ang= 0.) Angle in degrees from A CCW to X
(ncoavg = 1) Number of coaverages per image
(secpexp= 1.) Seconds per unit exposure time
(y2n_ang= 0.) Angle in degrees from Y to N N thru E
(rotatio= yes) Is N thru E CCW?
(imglist= )
(nimglis= )
(rimglis= )
(shimgli= )
(cmimgli= )
(mode = ql)sinlist is just a list of names of images that I would like to end up in the "sections" file. Here's what demo.list contains:
demo01
demo02
demo03
demo04
demo05
demo06
demo07
demo08
demo09
demo10
demo11
demo12
demo13
demo14
demo15
demo16
demo17
demo18
demo19
demo20
demo21
demo22
demo23
demo24
demo25
Emma, thanks a lot for your help. Your suggestion of changing sinlist, was what I needed. I didn't think to include it in my many iterations of @'s and no @'s. The help file is a little confusing about this. Thanks again!
-Ginger

 
Profile Email
 Quote
emma
 07/27/2010 03:53AM  
++++-
Regular Member

Status: offline


Registered: 01/23/2006
Posts: 101
Glad I could help! Wink However, it is a bit strange that for a given task, you need to use a '@' in one parameter and not another ... especially when there is nothing about it in the help file!Mike, I'm not sure if you can comment on this? I know xdimsum is an external package, but do you know if there is someone working actively on this package who would take suggestions for improvements?Thanks!Emma Smile

 
Profile Email
 Quote
valdes
 07/27/2010 03:53AM  
+++++
Active Member

Status: offline


Registered: 11/11/2005
Posts: 728
Hello Emma and Ginger,xdimsum is not actively being worked on. However, I would be glad to update the help pages to something you recommend that might be clearer.Frank Valdes

 
Profile Email
 Quote
emma
 07/27/2010 03:53AM  
++++-
Regular Member

Status: offline


Registered: 01/23/2006
Posts: 101
Hi Frank,Thanks for your message Smile I guess one of two things could be done ... either change the code, specifically change the inlist parameter to accept a list in the usual format (i.e., @shifts rather than shifts), or change the help page, specifying that the inlist parameter is weird and you can supply a list without using the regular @shifts syntax.Would either of those be possible?Thanks!Emma Smile

 
Profile Email
 Quote
   
Content generated in: 0.13 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login