Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - RHenriques

Pages: 1 2 [3] 4 5 ... 15
31
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: September 24, 2021, 07:10:44 AM »
Hi Alexey

It says in the change log that this new beta version (1.8x) supports JPEG-R images. However, these files are imported as normal JPEG RGB files. What is the correct procedure for using them as radiometric files?
Cheers

32
General / Re: Thermal Reflectance Map from RJPG Images
« on: June 30, 2021, 05:48:50 AM »
Support for R-JPEG would be great.
Anyone has a comprehensive tutorial for making a thermal mosaic from R-JPEG converted to TIFF for use in Metashape?
Cheers

33
Hi Alexey

It seems that the Hardware detection problems from the previous beta are gone in build 1.7.4 (12584). So far so good.
Best regards


PS: This version also seems to spare a little bit the memory and the processing pressure on the hardware. The calculations are more stable. A few CUDA errors from previous versions are not happening now. 

34
General / Re: Metashape Professional and Coral Reef Measurement
« on: June 15, 2021, 08:01:56 PM »
Thank you so much SimonBrown

This is one of the most promising systems I saw so far for this purpose.
Best Regards

35
General / Re: Metashape Professional and Coral Reef Measurement
« on: June 13, 2021, 05:44:12 AM »
Hi Simon

What's the cost of a  UWIS GPS system?
Best Regards

36
Hello Renato,

We found the issue that could be a reason of lost CUDA support in 1.7.3 release version and we'll try to fix it as soon as possible.

But the information related to clinfo output may be helpful, as we expect that in 1.8 version CUDA support could be dropped in Metashape for macOS.

That would be awful to Macusers with CUDA capable machines :-(
At least it would be great to replace it by Metal for instance.

Sent clinfo output by email.

37
Hi Alexey

Your message caught my attention because I guess that CUDA is not being activated in my hardware using the current 1.7.3 version and that's the problem.
The appearence of only 1 Nvidia in OpenCL is an old issue and I was already aware of it. Since while using CUDA that was not a problem, I was ignoring it. By reading your message I went back to the images and SAW that CUDA is off in the latest version.  Probably it can be forced with the CUDA activation tweak. What is the right syntax?

Meanwhile, I'll install clinfo.

Best Regards

PS - I have the tweak to force CUDA to "true" and it's not being respected. I guess that the problem is the activation of CUDA. Latest "faulty" 1.7.3 versions were mounting all the hardware just fine.

38
Yes

Here is the output from 1.7.2

Metashape.app.enumGPUDevices()
2021-05-30 13:00:27 Found 4 GPUs in 0.062248 sec (CUDA: 0.059628 sec, OpenCL: 0.002573 sec)
Out[1]: 2021-05-30 13:00:27
2021-05-30 13:00:27 [{'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 13:00:27   'vendor': 'AMD',
2021-05-30 13:00:27   'version': 'OpenCL 1.2 ',
2021-05-30 13:00:27   'compute_units': 24,
2021-05-30 13:00:27   'mem_size': 3221225472,
2021-05-30 13:00:27   'clock': 725,
2021-05-30 13:00:27   'pci_bus_id': 0,
2021-05-30 13:00:27   'pci_device_id': 0},
2021-05-30 13:00:27  {'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 13:00:27   'vendor': 'AMD',
2021-05-30 13:00:27   'version': 'OpenCL 1.2 ',
2021-05-30 13:00:27   'compute_units': 24,
2021-05-30 13:00:27   'mem_size': 3221225472,
2021-05-30 13:00:27   'clock': 150,
2021-05-30 13:00:27   'pci_bus_id': 0,
2021-05-30 13:00:27   'pci_device_id': 0},
2021-05-30 13:00:27  {'name': 'GeForce GTX 1080 Ti',
2021-05-30 13:00:27   'vendor': '',
2021-05-30 13:00:27   'version': '',
2021-05-30 13:00:27   'compute_units': 28,
2021-05-30 13:00:27   'mem_size': 11810963456,
2021-05-30 13:00:27   'clock': 1582,
2021-05-30 13:00:27   'pci_bus_id': 79,
2021-05-30 13:00:27   'pci_device_id': 0},
2021-05-30 13:00:27  {'name': 'GeForce GTX 1080 Ti',
2021-05-30 13:00:27   'vendor': '',
2021-05-30 13:00:27   'version': '',
2021-05-30 13:00:27   'compute_units': 28,
2021-05-30 13:00:27   'mem_size': 11810963456,
2021-05-30 13:00:27   'clock': 1582,
2021-05-30 13:00:27   'pci_bus_id': 237,
2021-05-30 13:00:27   'pci_device_id': 0}]


Cheers

PS: In previous 1.7.3 versions the detection was allright

39
Hi Alexey

Here is the echo from 1.7.3:

Metashape.app.enumGPUDevices()
2021-05-30 12:31:41 Found 3 GPUs in 0.001334 sec (CUDA: 0.000403 sec, OpenCL: 0.000913 sec)
Out[2]: 2021-05-30 12:31:41
2021-05-30 12:31:41 [{'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 12:31:41   'vendor': 'AMD',
2021-05-30 12:31:41   'version': 'OpenCL 1.2 ',
2021-05-30 12:31:41   'compute_units': 24,
2021-05-30 12:31:41   'mem_size': 3221225472,
2021-05-30 12:31:41   'clock': 725,
2021-05-30 12:31:41   'pci_bus_id': 0,
2021-05-30 12:31:41   'pci_device_id': 0},
2021-05-30 12:31:41  {'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 12:31:41   'vendor': 'AMD',
2021-05-30 12:31:41   'version': 'OpenCL 1.2 ',
2021-05-30 12:31:41   'compute_units': 24,
2021-05-30 12:31:41   'mem_size': 3221225472,
2021-05-30 12:31:41   'clock': 150,
2021-05-30 12:31:41   'pci_bus_id': 0,
2021-05-30 12:31:41   'pci_device_id': 0},
2021-05-30 12:31:41  {'name': 'GeForce GTX 1080 Ti',
2021-05-30 12:31:41   'vendor': 'NVIDIA',
2021-05-30 12:31:41   'version': 'OpenCL 1.2 ',
2021-05-30 12:31:41   'compute_units': 28,
2021-05-30 12:31:41   'mem_size': 11811160064,
2021-05-30 12:31:41   'clock': 1139,
2021-05-30 12:31:41   'pci_bus_id': 0,
2021-05-30 12:31:41   'pci_device_id': 0}]

The same echo from 1.7.1

Metashape.app.enumGPUDevices()
2021-05-30 12:30:57 Found 4 GPUs in 0.000635 sec (CUDA: 0.000541 sec, OpenCL: 7.9e-05 sec)
Out[3]: 2021-05-30 12:30:57
2021-05-30 12:30:57 [{'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 12:30:57   'vendor': 'AMD',
2021-05-30 12:30:57   'version': 'OpenCL 1.2 ',
2021-05-30 12:30:57   'compute_units': 24,
2021-05-30 12:30:57   'mem_size': 3221225472,
2021-05-30 12:30:57   'clock': 725,
2021-05-30 12:30:57   'pci_bus_id': 0,
2021-05-30 12:30:57   'pci_device_id': 0},
2021-05-30 12:30:57  {'name': 'AMD Radeon HD - FirePro D500 Compute Engine',
2021-05-30 12:30:57   'vendor': 'AMD',
2021-05-30 12:30:57   'version': 'OpenCL 1.2 ',
2021-05-30 12:30:57   'compute_units': 24,
2021-05-30 12:30:57   'mem_size': 3221225472,
2021-05-30 12:30:57   'clock': 150,
2021-05-30 12:30:57   'pci_bus_id': 0,
2021-05-30 12:30:57   'pci_device_id': 0},
2021-05-30 12:30:57  {'name': 'GeForce GTX 1080 Ti',
2021-05-30 12:30:57   'vendor': '',
2021-05-30 12:30:57   'version': '',
2021-05-30 12:30:57   'compute_units': 28,
2021-05-30 12:30:57   'mem_size': 11810963456,
2021-05-30 12:30:57   'clock': 1582,
2021-05-30 12:30:57   'pci_bus_id': 79,
2021-05-30 12:30:57   'pci_device_id': 0},
2021-05-30 12:30:57  {'name': 'GeForce GTX 1080 Ti',
2021-05-30 12:30:57   'vendor': '',
2021-05-30 12:30:57   'version': '',
2021-05-30 12:30:57   'compute_units': 28,
2021-05-30 12:30:57   'mem_size': 11810963456,
2021-05-30 12:30:57   'clock': 1582,
2021-05-30 12:30:57   'pci_bus_id': 237,
2021-05-30 12:30:57   'pci_device_id': 0}]




Both versions are running simultaneously to get the above data, so the mchine is in the same conditions.
Cheers

40
Bug Reports / Metashape 1.7.3 not detecting all available hardware
« on: May 28, 2021, 09:21:07 PM »
Metashape 1.7.3 is not detecting all available eGPUs on Macos. In exactly the same conditions the GPU tab in both versions appear as attached images.
Best Regards

41
Sorry Alexey, my fault. By default I had the View Errors Button selected from previous projects and did not notice.
After change to view source everything is fine  :D

42
There's another small hiccup in the latest version. In a model with local coordinates, after creating 2 markers to build a scale bar, it's impossible to edit the distance. The accuracy field is available but the distance field is locked. It works in version 1.6.x.

43
Hi Dmitry

It is working quite good now!
I was able to finish the problematic step without any problem.
Thank you for all the effort and concern.
Best Regards

44
The issue starts immediatly after the depth maps build, in the beginning od the DEM build. The quality does not have any effect. The crash happens in any quality choice, precisely after the "Projecting depth maps..." line in the processing log.

45
General / Re: Wrong altitude data from drone location coordinates
« on: May 22, 2021, 02:33:02 AM »
Be aware that most UAV's use WGS84 with ellipsoidal height. To have errors around 2-3 meters, compatible with local altimetric datums, you have to correct the UAV height with a geoidal model for your area. To have sub-metrical precision, you have to use Ground Control Points obtained with GNSS.

Pages: 1 2 [3] 4 5 ... 15