Topics

1

Feature Requests / Batch Jobs [Apply to] support current chunk option

« on: April 18, 2024, 07:18:50 AM »

I am wondering if it possible to support the drop down menu of batch jobs with  [current chunk] or [active chunk]

My current batch job workflow needs to apply for the last new added chunk after data collection each day. However, I tried the [unprocessed chunks] option but it sometimes run all chunks rather than the new chunk. Manual editing [selected] every time is an option but a little bit time-consuming and frustrating.

I do understand that using python script is possible to completely control and apply to the active chunk, but writing python code is not so efficient and clear compare to the batch Job UI setting (and for other collages who are not familiar with API), especially for these jobs with dozens of parameters.

In this case, personally believe supporting the Apply to [current chunk] could be a better option for this senenario.

Any ideas or comments for this feature request?

2

Bug Reports / Can not launch tkinter on Intel MacOS

« on: November 29, 2022, 08:54:19 AM »

to reproduce:

Code: [Select]

2022-11-29 14:53:37 Populating font family aliases took 324 ms. Replace uses of missing font family "Courier" with one that exists to avoid this cost.
2022-11-29 14:53:38 OpenGL Vendor: ATI Technologies Inc.
2022-11-29 14:53:38 OpenGL Renderer: AMD Radeon Pro 5500M OpenGL Engine
2022-11-29 14:53:38 OpenGL Version: 2.1 ATI-4.8.101
2022-11-29 14:53:38 Maximum Texture Size: 16384
2022-11-29 14:53:38 Quad Buffered Stereo: not enabled
2022-11-29 14:53:38 ARB_vertex_buffer_object: supported
2022-11-29 14:53:38 ARB_texture_non_power_of_two: supported
2022-11-29 14:53:38 Agisoft Metashape Professional Version: 1.8.4 build 14856 (64 bit)
2022-11-29 14:53:38 Platform: Mac OS
2022-11-29 14:53:38 CPU: Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (laptop)
2022-11-29 14:53:38 CPU family: 6 model: 158 signature: 906EDh
2022-11-29 14:53:38 RAM: 64.0 GB
2022-11-29 14:53:39 Using simple console. Rich console can be enabled in Preferences dialog.
>>> import tkinter
>>> tkinter._test()   # this may raise no such function error, run >>> tkinter._test, first will solve this problem
2022-11-29 14:47:40 Traceback (most recent call last):
2022-11-29 14:47:40   File "<console>", line 1, in <module>
2022-11-29 14:47:40   File "/Applications/MetashapePro.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python3.8/tkinter/__init__.py", line 4557, in _test
2022-11-29 14:47:40     root = Tk()
2022-11-29 14:47:40   File "/Applications/MetashapePro.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python3.8/tkinter/__init__.py", line 2272, in __init__
2022-11-29 14:47:40     self._loadtk()
2022-11-29 14:47:40   File "/Applications/MetashapePro.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python3.8/tkinter/__init__.py", line 2288, in _loadtk
2022-11-29 14:47:40     raise RuntimeError("tk.h version (%s) doesn't match libtk.a version (%s)"
2022-11-29 14:47:40 RuntimeError: tk.h version (8.6) doesn't match libtk.a version (8.5)

The 1.7.6 also has the same error.

This command can run without any problem on my local python.

3

Python and Java API / Modify the capture distance in the chunk reference setting by python

« on: June 15, 2022, 03:28:33 PM »

Hello, I am writing scripts for batch processing, but hard to find the API to modify this value. Any ideas to implement this without manually changing chunks one by one?



Thanks for your help.

4

Bug Reports / Duplicate image file names override each other when build dense cloud [Solved]

« on: December 04, 2021, 08:32:06 AM »

Apologize, it is caused by the poor amount of tie points (4549 by high - fail;  46646 by highest - success), not caused by the duplicate image names.

Please archive or delete this post if necessary.



I am using "Foldio 360" rotation platform to take object images for 3D reconstruction,  it will rotate 10 degrees (horizontally) each time and take 36 images, and always name as follows: [01.jpg, 02.jpg, 03.jpg, ... , 36.jpg]



The camera position is always fixed, but scanned object is flipped for 45 degrees (vertically), and finally got 8 image groups:

/root/
|- rotation 0/
|   |- 01.jpg
|   |- 02.jpg
|   |- ...
|   |- 36.jpg
|- rotation 45/
|   |- 01.jpg
|   |- ...
|   |- 36.jpg
|- rotation 90/
|- rotation 135/
|- ...
|- rotation 315/

(please note, for each folder, the subimages have the same image name)

Then, I added all these images in one chunk, and grouped them by camera groups, and make masks for each image to remove the static backgrounds.



Successfully aligned photos by [highest accuracy, generic preselection, sequential reference preselection, apply mask to key points, exclude stationary tie points and adaptive camera model fitting], got expected tie points (left subimg). But build dense cloud, it produces point cloud with a missing part (right subimg), which is almost the same result from only 36 images from "rotation 90" folder.




Then I copied and rename the project folder like this, given unique image names:

/root/
|- rotation 0/
|   |- c0_01.jpg
|   |- c0_02.jpg
|   |- ...
|   |- c0_36.jpg
|- rotation 45/
|   |- c45_01.jpg
|   |- ...
|   |- c45_36.jpg
|- rotation 90/
|- rotation 135/
|- ...
|- rotation 315/

Doing the same thing like before (except ranaming image.label c0_01 -> 01 for sequential reference preselection by script in Metashape project, otherwise unable to align all images at all), and got expected dense cloud:



The only difference between two projects, is whether image names are unique or not. I personally guess it is caused by a bug in the MVS steps of building dense cloud, the duplicate image name override previous calculation results. A simple compairson: