mkimsets question
aoxsic wrote on Mar 17, 2007
I have now tried to run mkimsets with every possible combination of "idfilters" I can think of.
I always get the following warnings and an empty output file
<Warning>: Image li100108.fits filter id 2 B#74 does not belong to the filter set U#7 B#74 V#75
<Warning>: Image li100109.fits filter id 3 V#75 does not belong to the filter set U#7 B#74 V#75
<Warning>: Image li100111.fits filter id 1 U#7 does not belong to the filter set U#7 B#74 V#75
Parameter list is
imlist = *fits The input image list
idfilters = U#7 B#74 V#75 The list of filter ids
imsets = observations The output image set file
(imobsparams = ) The output image observing parameters file
(input = images) The source of the input image list
(filter = FILTER) The filter keyword
(fields = ARIMASS,TCSTGT) Additional image list fields
(sort = image) The image list field to be sorted on
(edit = no) Edit the input image list before grouping
(rename = no) Prompt the user for image set names
(review = no) Review the image set file with the editor
(list = )
(mode = al)
I've tried setting 'idfilters' to "U,B,V", "1,2,3","U#7,B#74,V#75","1U#7,2B#74,3V#75","1U,2B,3V" and even the exact value of the FILTER keyword from the images headers, which includes whitespace. I tried separating all 5 versions both with commas and with whitespace. Same result.
Exact FILTER keyword values in headers are
'1 U#7 '
'2 B#74 '
'3 V#75 '
'4 R#76 '
'5 i#12 '
'8 Open '
'6 I#11 '
Any ideas why it doesn't work?
I always get the following warnings and an empty output file
<Warning>: Image li100108.fits filter id 2 B#74 does not belong to the filter set U#7 B#74 V#75
<Warning>: Image li100109.fits filter id 3 V#75 does not belong to the filter set U#7 B#74 V#75
<Warning>: Image li100111.fits filter id 1 U#7 does not belong to the filter set U#7 B#74 V#75
Parameter list is
imlist = *fits The input image list
idfilters = U#7 B#74 V#75 The list of filter ids
imsets = observations The output image set file
(imobsparams = ) The output image observing parameters file
(input = images) The source of the input image list
(filter = FILTER) The filter keyword
(fields = ARIMASS,TCSTGT) Additional image list fields
(sort = image) The image list field to be sorted on
(edit = no) Edit the input image list before grouping
(rename = no) Prompt the user for image set names
(review = no) Review the image set file with the editor
(list = )
(mode = al)
I've tried setting 'idfilters' to "U,B,V", "1,2,3","U#7,B#74,V#75","1U#7,2B#74,3V#75","1U,2B,3V" and even the exact value of the FILTER keyword from the images headers, which includes whitespace. I tried separating all 5 versions both with commas and with whitespace. Same result.
Exact FILTER keyword values in headers are
'1 U#7 '
'2 B#74 '
'3 V#75 '
'4 R#76 '
'5 i#12 '
'8 Open '
'6 I#11 '
Any ideas why it doesn't work?
aoxsic wrote on Mar 17, 2007
ok, it doesn't work because there's whitespace in the FILTER keyword value. If I edit that to 1U#7 and 2B#74 etc. and match it with idfilters 1U#7,2B#74,etc then it works. How annoying, now I have to edit keywords :shock:
I can ask something else though: how would I tell mkimset not to group different targets into one observations set?? Now targets that are consequtive get groupped together.
I can ask something else though: how would I tell mkimset not to group different targets into one observations set?? Now targets that are consequtive get groupped together.
aoxsic wrote on Mar 17, 2007
I thought I had it figured out when I read that mknobsfile has a tolerance parameter for matching images in an observations set, but that doesn't work either. I have a tolerance of 5.0 pixels and yet I get the output(from mknobsfile)
Image set: OBS13 2 stars written to the observations file
Image set: OBS14 7 stars written to the observations file
Image set: OBS15 15 stars written to the observations file
Image set: OBS16 3 stars written to the observations file
All these OBS* sets should be discarded because each contains a standard star field and a number of galaxy fields that are at completely different coordinates. What happened to the tolerance level of 5 pixels??? I don't know, maybe I'm just tired but this makes no sense to me at all.
any help will be greatly, greatly appreciated.
Image set: OBS13 2 stars written to the observations file
Image set: OBS14 7 stars written to the observations file
Image set: OBS15 15 stars written to the observations file
Image set: OBS16 3 stars written to the observations file
All these OBS* sets should be discarded because each contains a standard star field and a number of galaxy fields that are at completely different coordinates. What happened to the tolerance level of 5 pixels??? I don't know, maybe I'm just tired but this makes no sense to me at all.
any help will be greatly, greatly appreciated.
aoxsic wrote on Mar 17, 2007
I'm now running only std files through mkimsets. I've tried sorting by right ascention and sidereal time, it still gets it wrong. Some OBS subsets are ok, others are completely wrong, mixing two different stars together.
Really, this is not a joke. Could someone give me an example of the right way to use mkimsets? It's NOT as easy as it's described in the User's Guide to Stellar CCD Phot.
And I want to avoid user input, so the resulting file can't be edited by the user. What can I do to make this work?
Really, this is not a joke. Could someone give me an example of the right way to use mkimsets? It's NOT as easy as it's described in the User's Guide to Stellar CCD Phot.
And I want to avoid user input, so the resulting file can't be edited by the user. What can I do to make this work?
Last post on Mar 17, 2007