<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Thanks, Piero. That explains all. FTR setting that to 4 worked
for me and didn't hang up. Admittedly I'm only use four cores so
any SMP race conditions/deadlocks etc are much less likely to
affect me than someone running on 64 cores.</p>
<p>Very impressive results, 82 photos taken at 3m intervals, 30m
altitude using a Phantom 3 Advanced.</p>
<p>Out of curiosity: If I take photos with non-vertical orientation,
e.g. pointing the camera sideways or at an angle, can ODM
automatically integrate the results and avoid the voids under
overhangs?</p>
<p>I'm so impressed with this software and thank the developers for
it. If I had one wish it would be to get slightly higher
resolution results. Some of the detail from the original photos
is lost in the textured mesh. Is this a tunable parameter or a
limitation of the current implementation?<br>
</p>
<p>Stuart<br>
</p>
<br>
<div class="moz-cite-prefix">On 03/06/2017 14:22, Piero Toffanin
wrote:<br>
</div>
<blockquote
cite="mid:afdb631e-5b7a-84e3-787e-e83f7b7d419c@masseranolabs.com"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<p>Hi Stuart,</p>
<p>You can use more cores by setting the "opensfm-processes"
option. By default we've set it at 1 because a fault is causing
the program to get stuck sometimes with more cores: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/OpenDroneMap/OpenDroneMap/pull/579">https://github.com/OpenDroneMap/OpenDroneMap/pull/579</a></p>
<p>Increasing the number of cores at compilation does not
influence runtime behavior, it just compiles faster :)<br>
</p>
<br>
<div class="moz-cite-prefix">On 06/03/2017 06:54 AM, StuartL
wrote:<br>
</div>
<blockquote
cite="mid:be2222a8-1326-28ca-7aa5-6c0d0e9bd8a1@livings.co.uk"
type="cite">Hi, <br>
<br>
I'm running a new install of ODM in a VirtualBox Ubuntu guest VM
on Windows. The guest VM has four cores but ODM only seems to
use one core. <br>
<br>
Looking at some other posts people seem to be talking about
using massive numbers of cores so I feel like I must be doing
something wrong. <br>
<br>
Possibly relevant information: <br>
- ODM was originally compiled with only one core in the VM. I
later increased the number of cores. <br>
- I'm measuring it using one core by monitoring with 'top' and
pressing '1' to reveal individual CPU cores. At all steps so
far (currently up to Computing depthmap for...) it seems to
flatline one core but the others are nearly idle. <br>
<br>
Does it deduce the number of cores at point of compilation? Do
I need to enable something to allow multi-core support? Are the
steps I've observed so far all single-threaded? <br>
<br>
Thanks for a wonderful piece of software! <br>
<br>
Stuart <br>
_______________________________________________ <br>
OpenDroneMap-users mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:OpenDroneMap-users@lists.osgeo.org">OpenDroneMap-users@lists.osgeo.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://lists.osgeo.org/mailman/listinfo/opendronemap-users">https://lists.osgeo.org/mailman/listinfo/opendronemap-users</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>