On Wed, 04 Mar 2015 08:55:33 +1100, Terry Duell <[email protected]>
wrote:
Hello Thomas,
On Wed, 04 Mar 2015 08:48:10 +1100, T. Modes <[email protected]> wrote:
Am Dienstag, 3. März 2015 21:53:51 UTC+1 schrieb Tduell:
Interesting. I don't think that's what I'm seeing here.
When running align_image-stack (ais) via the shell script for 4 stacks,
each ais run must complete before the next can start. When run this
way I
only see one core of my system running at 100%.
Strange. Theres is something with your build, or a bug in tue build
system, or you have set the environment variable OMP_NUM_THREADS to 1.
Align_image_stacks runs on all cores here.
OK, thanks for that info.
I'll do some checking.
I haven't found anything obviously wrong with the build process, so tried
running my script again and monitored cpu activity with a different tool,
that gives a much better view of what's going on.
align_image_stack does indeed use all the cores for quite short periods of
time, with periods in between where activity drops back to one core. When
I run the script with calls to ais run as background tasks the cpu
activity peaks at 100% (all cores) for most of the time.
I note that the output images from ais don't have any the exif data that
hugin uses to automatically detect stacks.
Cheers,
--
Regards,
Terry Duell
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/op.xux8rgc1rs0ygh%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.
