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 - jansawicki

Pages: [1] 2
1
General / Frequent moving of node-locked license
« on: December 29, 2020, 03:41:33 AM »
Hello,
I am planning to start frequently activate/deactivate nodelocked license between my personal laptop and office workstation, possibly a couple of times a week. To avoid accidentally leaving the license at the office (forgetting to deactivate) I may even try to setup the workstation so that it automatically deactivates the licence every evening (of course not when its computing etc.).

Are there any limits on how often can the node-locked license be activated/deactivated like this?
Do you have any suggestions on how to automate this the best way? (I am familiar with Python scripting)
Is it possible to activate the node-locked license temporarly, so that it is automatically deactivated after specified time?

I know the last question may suggested that I need a Floating type of license, but after reading some older topics on this forum regarding no limits in moving the nodelocked license between various computers (even including VMs) I am a little confused about where is the border between this two.

Cheers

2
General / Re: Project with 220K images for processing
« on: September 16, 2019, 01:31:19 PM »
Hello jivago,


Our company provides services for processing large amounts of image data  sets on a high performance workstation. If you are interested in our help, please direct message me - we will find a way to cooparate :)

Cheers

3
Feature Requests / Volume measurement above mesh as a reference level
« on: July 24, 2019, 11:54:08 AM »
Hello,
I do a lot of volume measurements in Agisoft Metashape. In some cases, I don't like the way it computes the volume above the reference plane (mean level, best fit plane, custom level). On steep slopes, I believe the volume should be calculated above a TIN mesh generated from the surroundings of the measured material, similary as CloudCompare volume measurement works. Right now to achieve this, I need to export some of the data to CloudCompare, which takes a lot of time for me - I think this method can be easily implemented directly in Metashape.

Thanks!

4
Anything new? The issue still exists.

Greetings,

5
Bug Reports / Re: Draw patch button not working
« on: March 13, 2019, 12:05:27 PM »
Hello Alexey,
Yes, I am interested - please send me the pre-release version, thanks!

6
Bug Reports / Re: Draw patch button not working
« on: March 12, 2019, 11:54:17 AM »
Hello Alexey,
I know about this workaround, but it is a lot slower workflow, especially on larger areas. When can I expect version 1.5.2 to be released?

7
Bug Reports / Draw patch button not working
« on: March 11, 2019, 05:38:53 PM »
Hello,
Nothing seems to happen when I press "Draw Patch" Button in Ortho view since I updated to Metashape 1.5.1. Other buttons in this toolbar (Draw Line, Draw Point, Draw polygon) work fine. Is there any other way to start drawing patches? Please help and fix this error, Thank you.

Best regards

8
Bug Reports / Re: Missing Advanced/Miscellaneous options in Metashape 1.5.0
« on: February 18, 2019, 04:24:14 PM »
Thank you Alexey, everything is fine.

9
Hello Alexey,
Thank you for sharing benchmark project. I just ran it on both 1.4 and 1.5 versions. Version 1.4 was still faster than 1.5, but the difference was "only" about 20-25% (1.4 total time = 27minutes  compared to 1.5 total time= 35minutes) so not that huge as in larger projects. I attach log files from both runs.

I've noticed that the name of GPU driver changed slightly in the beginning of the file, and "Depth reconstruction devices performance" was different. On the other hand, 1.4 was faster on both stages of the process - not only reconstructing depth but also generating pointcloud.

Of course I didn't do any GPU driver updates between these tests, and I made sure no other processes were running in the background.

I don't think it is the issue, but I would also like to mention that I am using the computer with remote desktop access, without full OpenGL support. This is what I see in the console at the start:

Code: [Select]
2019-02-18 13:09:10 Agisoft Metashape Professional Version: 1.5.0 build 7492 (64 bit)
2019-02-18 13:09:10 Platform: Windows
2019-02-18 13:09:10 CPU: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (server)
2019-02-18 13:09:10 CPU family: 6 model: 79 signature: 406F1h
2019-02-18 13:09:10 RAM: 127.9 GB
2019-02-18 13:09:11 OpenGL Vendor: Google Inc.
2019-02-18 13:09:11 OpenGL Renderer: ANGLE (Microsoft Basic Render Driver Direct3D9Ex vs_3_0 ps_3_0)
2019-02-18 13:09:11 OpenGL Version: OpenGL ES 2.0 (ANGLE 2.1.99f075dade7c)
2019-02-18 13:09:11 Maximum Texture Size: 16384
2019-02-18 13:09:11 Quad Buffered Stereo: not enabled
2019-02-18 13:09:11 ARB_vertex_buffer_object: supported
2019-02-18 13:09:11 ARB_texture_non_power_of_two: supported

I have no direct access to this machine, but this worked fine in the past.

10
Any updates on this?

11
Unfortunately not. Will it be OK if i re-run just the "build dense cloud" process and share the logs? I didn't use any tweaks during these tests.

12
Bug Reports / Missing Advanced/Miscellaneous options in Metashape 1.5.0
« on: February 11, 2019, 04:42:59 PM »
Hello,
I think it's some GUI bug, that 2 options from Preferences, Advanced Tab, Miscellaneous labelframe went missing.
I attach a screenshot which explains it all.

13
Hello again,

I attach some processing reports:
-old one, generated a couple of months ago, processed with PhotoScan 1.43 (normal time of processing)
- new one, generated with Metashape 1.5 (long depth maps generation time)
- new one, generated after downgrading back to Photoscan 1.43 (normal time again)

I think last two reports show that depth maps generation time increased drastically after updating to Metashape 1.5.
Every time in Preferences window I've had GPU devices enabled and "Use CPU..." option unticked.

Please help me if you have any ideas.

Greetings,

 

14
Python and Java API / Re: Setting camera accuracy with Python
« on: February 01, 2019, 11:28:43 AM »
It worked, thanks!

15
Python and Java API / Re: Setting camera accuracy with Python
« on: January 31, 2019, 06:35:15 PM »
Hello Marcel,

If you wish to change the accuracy for all the cameras (change the default accuracy for the chunk), use the following line:
Code: [Select]
PhotoScan.app.document.chunk.accuracy_cameras = (x, y, z)where x, y, z are values in corresponding direction. Could be the same number for all three, of course.

To change the accuracy for certain camera use:
Code: [Select]
camera.reference.accuracy = (x, y, z)


Can someone pleasy verify my code? I am trying to itterate through cameras and set various accuracies for each camera, although I am having a problem to change even one of them. Below code brings no error messages but doesn't update the data in Reference tab.

Code: [Select]
import Metashape

doc = Metashape.app.document
chunk = doc.chunk
camera = chunk.cameras[0]
camera.Reference.accuracy = (5,5,5)

print(camera.Reference.accuracy)

Thanks,
Jan

Pages: [1] 2