nona not called with gpu

[jpe]

Under the current version of Hugin, compiled from the lates source Pre-Release 2015.1.0.e65b6b93a955
when I stitch a project through the PTBatch, the output says it is using GPU, but I can see that this does not happen

it uses the CPU.

on the other hand if I run with the same pto file (generated by hugin)

 hugin_executor --stitching -t 8 ~/canon/stluc/dsc09-dsc09711.pto then it DOES use the GPU

(I guess the batcher calls hugin_stitch_project and I checked that it
indeed uses the 8 threads on my machine)

so perhaps there is some subtle difference between hugin_stitch_project and hugin_executor ?

[tmodes (tmodes)]

I think you mix things: The gpu remapping has nothing to do with the number of threads.
Nona can use the gpu for the remapping step. For this the number of threads has no effect.
But there are more steps which are always done by the CPU.

PTBatcherGUI, hugin_stitch_project and hugin_executor are using all the same code. So there is difference in the calling path.
PTBatcherGUI is reading the settings like Hugin, but with hugin_executor you are overwriting these settings with -t 8.
So there are possible ways: you setted the number of threads explicit in the Hugin preferences (tab stitching (2)) or on your computer the environment variable OMP_NUM_THREADS is set to a lower number.

[jpe (jean-pierre-eckmann)]

Thanks

If I set threads =0 in "preferences" then indeed, nona uses the GPU and 1
thread in CPU

But if I set Threads=4 (having 8 threads available) then, it seems to me
that nona ONLY uses the 4 threads (I can see that with "top") and, as far
as I can judge from the time it takes to map the images, NO GPU.

Is that what you want?

(If so, perhaps it might be useful to say that one should NOT fix the
number of threads in the menu to anything else than 0, if one wants to use
GPU)

Thanks, for me it works now

On Fri, 16 Oct 2015, tmodes wrote:

->I think you mix things: The gpu remapping has nothing to do with the number of threads.
->Nona can use the gpu for the remapping step. For this the number of threads has no effect.
->But there are more steps which are always done by the CPU.
->
->PTBatcherGUI, hugin_stitch_project and hugin_executor are using all the same code. So there is difference in the calling path.
->PTBatcherGUI is reading the settings like Hugin, but with hugin_executor you are overwriting these settings with -t 8.
->So there are possible ways: you setted the number of threads explicit in the Hugin preferences (tab stitching (2)) or on your computer the environment variable OMP_NUM_THREADS is set to a lower number.
->
->
->** Changed in: hugin
-> Status: New => Incomplete
->
->--
->You received this bug notification because you are subscribed to the bug
->report.
->https://bugs.launchpad.net/bugs/1506803
->
->Title:
-> nona not called with gpu
->
->Status in Hugin:
-> Incomplete
->
->Bug description:
-> Under the current version of Hugin, compiled from the lates source Pre-Release 2015.1.0.e65b6b93a955
-> when I stitch a project through the PTBatch, the output says it is using GPU, but I can see that this does not happen
->
-> it uses the CPU.
->
-> on the other hand if I run with the same pto file (generated by
-> hugin)
->
-> hugin_executor --stitching -t 8 ~/canon/stluc/dsc09-dsc09711.pto
-> then it DOES use the GPU
->
-> (I guess the batcher calls hugin_stitch_project and I checked that it
-> indeed uses the 8 threads on my machine)
->
-> so perhaps there is some subtle difference between
-> hugin_stitch_project and hugin_executor ?
->
->To manage notifications about this bug go to:
->https://bugs.launchpad.net/hugin/+bug/1506803/+subscriptions
->

[Launchpad Janitor (janitor)]

[Expired for Hugin because there has been no activity for 60 days.]