I'm trying to lower the CPU time limit before solve-field stops. However, it seems that the --cpulimit option is being ignored. The example below runs for nine minutes before giving up, when I would expect it to stop after only one or, at worst, the five minutes defined in the backend configuration file.
vterron@iaa:~/data$ solve-field | grep Revision
Revision 24247, date 2013-12-17 14:33:48 +0000 (Tue, 17 Dec 2013).
vterron@iaa:~/data$ grep cpulimit /usr/local/astrometry/etc/backend.cfg
cpulimit 300
vterron@iaa:~/data$ time solve-field ferM_4440s.fits --cpulimit 60
Reading input file 1 of 1: "ferM_4440s.fits"...
Base: "./ferM_4440s", basefile "ferM_4440s.fits", basedir ".", suffix "fits"
Checking if file "ferM_4440s.fits" is xylist or image: image
[...]
cpulimit 60.000000
timelimit 0
total_timelimit 0
total_cpulimit 0.000000
[...]
Field 1 did not solve (index index-4203-19.fits, field objects 191-200).
Field 1 did not solve (index index-4202-19.fits, field objects 191-200).
Field 1 did not solve (index index-4201-19.fits, field objects 191-200).
Field 1 did not solve (index index-4200-19.fits, field objects 191-200).
Field: ferM_4440s.fits
Did not solve (or no WCS file was written).
real 9m2.213s
user 8m45.769s
sys 0m6.388s
Is it normal that total_timelimit and total_cpulimit are zero?
I'm trying to lower the CPU time limit before
solve-field
stops. However, it seems that the--cpulimit
option is being ignored. The example below runs for nine minutes before giving up, when I would expect it to stop after only one or, at worst, the five minutes defined in the backend configuration file.Is it normal that
total_timelimit
andtotal_cpulimit
are zero?