Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
wrong array syntax for keyword MAG_APER
04-09-2010, 10:35 (This post was last modified: 04-09-2010 11:15 by J.F. Le Borgne.)
Post: #1
wrong array syntax for keyword MAG_APER
Hi there

I am using SExtractor 2.8.6 for the first time (64bits, red hat). I used SExtractor with earlier version until now.
The config file was build with: sex -dd

Trying to get aperture magnitudes I got the following messages:
----- SExtractor 2.8.6 started on 2010-04-09 at 11:04:21 with 8 threads

> Setting catalog parameters
> *Error*: wrong array syntax for keyword MAG_APER

works fine when MAG_AUTO is selected.

Cheers
Jean-Francois
By the way, the param file was created with sex -dp
I noticed a difference with the default file default.param where the aperture mag. is requested by MAG_APER(1) and sex -dp create just a MAG_APER
trying with MAG_APER(1) in param file I got a different error:
----- SExtractor 2.8.6 started on 2010-04-09 at 12:06:18 with 8 threads

> Setting catalog parameters
> *Error*: too many dimensions for keyword MAG_APER

???
Jean-Francois
Find all posts by this user
Quote this message in a reply
04-14-2010, 09:33
Post: #2
RE: wrong array syntax for keyword MAG_APER
Hi Jean-Francois,

this is strange, there must be something wrong with the .param file or the .sex file. I checked here with a very simple configuration and got no warning. Would you mind posting a complete copy of your .param and .sex files? Thanks!
- Emmanuel.
Visit this user's website Find all posts by this user
Quote this message in a reply
04-14-2010, 09:54
Post: #3
RE: wrong array syntax for keyword MAG_APER
(04-14-2010 09:33)Emmanuel Bertin Wrote:  Hi Jean-Francois,

this is strange, there must be something wrong with the .param file or the .sex file. I checked here with a very simple configuration and got no warning. Would you mind posting a complete copy of your .param and .sex files? Thanks!
- Emmanuel.

Hi Emmanuel

Thanks for your reply
Here are the files attached.

Jean-Francois


.gz  m.sex.gz (Size: 2.38 KB / Downloads: 1151)

.gz  m.param.gz (Size: 4.14 KB / Downloads: 1088)
Find all posts by this user
Quote this message in a reply
07-07-2010, 00:00
Post: #4
RE: wrong array syntax for keyword MAG_APER
I've had this same problem, and I'm not sure what actually caused it, but I did discover a workaround:

I had originally used a dumped .param file from sex -dp, and uncommented the lines I wanted, including MAG_APER(10) for my ten aperture magnitudes, and received the same error messages as above.

The errors disappeared when I retyped the .param file from scratch (including all the same parameters!), rather than editing the dumped parameter file, so I assume it's a syntax issue of some kind -- carriage returns, comment flags, I don't know what.

Hope that helps!
Find all posts by this user
Quote this message in a reply
03-01-2011, 12:20
Post: #5
RE: wrong array syntax for keyword MAG_APER
Hi

I eventually found a solution to this problem.
I encounter it again trying to use psfex were parameter arrays are mandatory.
I noticed it is necessary to either remove the parameter description or put a '#' between parameter name and description. This is necessary ONLY for array parameters. When the parameter is a single value, commenting out the line by removing the '#' works alright.
This explains why Paul Thorman solved it by typing all the parameters, without the descriptions I guess.
Here is an example of parameters for sextractor before running psfex:

FLUX_APER(1) # Flux vector within fixed circular aperture(s) [count]
FLUXERR_APER(1) # RMS error vector for aperture flux(es) [count]
FLUX_MAX Peak flux above background [count]
X_IMAGE Object position along x [pixel]
Y_IMAGE Object position along y [pixel]
FLAGS Extraction flags
ELONGATION A_IMAGE/B_IMAGE
VIGNET(10,10) # Pixel data around detection [count]
FLUX_RADIUS(1) # Fraction-of-light radii [pixel]

Note that it was necessary to add FLUX_MAX to make psfex work, though it is not requested in the documentation.
This does not help to make sextractor work with fitting psf, but this is another story.

Jean-Francois
Find all posts by this user
Quote this message in a reply
04-23-2016, 23:21
Post: #6
RE: wrong array syntax for keyword MAG_APER
This solution seemed promising, but once I commented out the description of MATRIX_MODELERR, I got a segfault. If I leave it uncommented, I get the error "wrong array syntax for keyword MATRIX_MODELERR".

(03-01-2011 12:20)J.F. Le Borgne Wrote:  Hi

I eventually found a solution to this problem.
I encounter it again trying to use psfex were parameter arrays are mandatory.
I noticed it is necessary to either remove the parameter description or put a '#' between parameter name and description. This is necessary ONLY for array parameters. When the parameter is a single value, commenting out the line by removing the '#' works alright.
This explains why Paul Thorman solved it by typing all the parameters, without the descriptions I guess.
Here is an example of parameters for sextractor before running psfex:

FLUX_APER(1) # Flux vector within fixed circular aperture(s) [count]
FLUXERR_APER(1) # RMS error vector for aperture flux(es) [count]
FLUX_MAX Peak flux above background [count]
X_IMAGE Object position along x [pixel]
Y_IMAGE Object position along y [pixel]
FLAGS Extraction flags
ELONGATION A_IMAGE/B_IMAGE
VIGNET(10,10) # Pixel data around detection [count]
FLUX_RADIUS(1) # Fraction-of-light radii [pixel]

Note that it was necessary to add FLUX_MAX to make psfex work, though it is not requested in the documentation.
This does not help to make sextractor work with fitting psf, but this is another story.

Jean-Francois
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)