Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

solve-field ignoring --cpulimit? #9

Open
vterron opened this issue Apr 7, 2014 · 1 comment
Open

solve-field ignoring --cpulimit? #9

vterron opened this issue Apr 7, 2014 · 1 comment

Comments

@vterron
Copy link

vterron commented Apr 7, 2014

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?
@anshula
Copy link

anshula commented Jul 20, 2014

Having the same issue. My solver went on for an hour before stopping (it didn't stop until it solved it). Has anyone found a solution?

@vterron vterron mentioned this issue Sep 4, 2014
Open
vterron pushed a commit to vterron/lemon that referenced this issue Sep 4, 2014
Add --timeout option
bddfacd 
This option sets the time limit before Astrometry.net gives up trying
to find the astrometric solution for each FITS image. This is exactly
what the --cpulimit option of solve-field does, but there is a (known)
bug that causes it to be ignored unless the 'inparallel' option is set
in the configuration file (astrometry.cfg). Until this is fixed, use
the 'timeout' argument of subprocess.call() — it was added in Python
3.3, so we need the module 'subprocess32', a backport for use on 2.x.

astrometry/usermanual#9
https://groups.google.com/forum/#!topic/astrometry/gyWYg3bQmZ0

This merges branch 'add-timeout-option'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@anshula @vterron