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

Pages: [1] 2 3
1
General / Re: incorrect alignment of the object from video
« on: Today at 12:44:56 PM »
Hi!

Did you try to change camera type from Frame to Fisheye in Tools menu -> Camera Calibration?

2
Bug Reports / Re: Look through shows the right view, but zoomed in
« on: January 29, 2025, 02:13:56 PM »
Hi, Mariusz

Look Through zoom will be adjusted for high field of view cameras in 2.2.1 update.

Regards, Egor

3
General / Re: Masks export undistortion
« on: January 23, 2025, 01:22:03 PM »
Hi!

When exporting masks using regular export we don't change them. It is the original image distortion.

Masks exported in colmap project are undistorted the same way as photos in this project. Masks match exported photos.

Regards, Egor.

4
General / Re: Issues Classifying Ground Points
« on: December 17, 2024, 05:14:01 PM »
Hi!

Here is an article https://agisoft.freshdesk.com/support/solutions/articles/31000160729-parameters-for-ground-point-classification
and an algorithm reference https://www.isprs.org/proceedings/Xxxiii/congress/part4/111_XXXIII-part4.pdf

Basically we initially split point cloud to cells with the specified size and looking for initial ground points in each cell. So each cell should be big enough to contain at least 1 ground point.

Max angle controls how smooth final ground points will be. Low value - almost flat, high - more detailed/noisy. Usually 15 works good.

About tweak, I rechecked, it appears to use local scaled coordinates instead of meters. Try to lower it to a factor of 10.
We will fix it to use meters in the next 2.2.0 release.

5
General / Re: Issues Classifying Ground Points
« on: December 16, 2024, 04:56:29 PM »
Hi!

There is a tweak that allows to add points near ground surface to the ground class.

You can set it in Tools->Preferences menu, Advanced tab, Tweaks... button

Parameter name is ClassifyGroundPoints/buffer_width and value is height above ground in meters.
Logs and rocks smaller than this value will be classified as ground. So you could set it to 0.4 for example.

As a side effect lower parts of high vegetation will be added to the ground as well, setting "Erosion radius" to the same value as buffer_width can help to avoid it.

Regards, Egor

6
Bug Reports / Re: Generating Block Model from Depth + Laser Scans
« on: December 11, 2024, 03:26:10 PM »
Hi!

You could try to increase maximum open files limit according to https://askubuntu.com/questions/1182021/too-many-open-files

Full processing log could help to determine the problem.

Regards, Egor

7
General / Re: Bad allocation
« on: November 20, 2024, 02:18:55 PM »
Hi!

High distortion handling was improved in 2.2.0 pre-release, please try to update from https://www.agisoft.com/forum/index.php?topic=16745.0
This error should not appear in that version.

Regards, Egor

8
Bug Reports / Re: Texture artifacts after mesh decimation
« on: November 19, 2024, 05:56:03 PM »
I've encountered similar problem.

Setting tweak

BuildUV/decimate_target

to 0 could help, but processing time will increase.

Next 2.2.0 pre-release should not have such artifacts.

Regards, Egor

9
General / Re: RAM Usage - Building Textures
« on: November 03, 2024, 10:43:47 AM »
Hi!

You may try to process original model. Number of triangles should not affect memory usage as much as texture resolution. Also disable ghosting filter to reduce usage a little.

Regards, Egor

10
General / Re: Processing Time - Build Point Cloud
« on: November 02, 2024, 06:55:36 PM »
Tas, yes, when you building a mesh - surfaces in front of laser scans are filtered out and small misalignments are likely to be merged to a single surface.

You can later convert it to a point cloud if you select Model as a "Source Data" in a "Build Point Cloud" task.
Either vertices will be extracted or uniform points will be scattered on the surface.

Regards, Egor

11
General / Re: Processing Time - Build Point Cloud
« on: November 02, 2024, 01:54:06 PM »
Quote
I'd really like to better understand the theory behind how laser scans are treated for alignment, depth map generation, and point cloud generation

Alignment of scans with images is currently done using features from panoramas either embedded in scans or extracted from colors and using markers (they have priority over features) with respect to reference from metadata. In the following steps scans and images are treated independently.

Regards, Egor

12
General / Re: Processing Time - Build Point Cloud
« on: November 01, 2024, 07:12:00 PM »
For an alignment preview you could build point cloud only from images (disable laser scans), they can be displayed together. You may even merge them later by selecting in the workspace, right click and Merge... without using Build Point Cloud if everything is OK.

Regards, Egor

13
General / Re: Processing Time - Build Point Cloud
« on: November 01, 2024, 02:31:50 PM »
In 2.2.0 "preloading data" stage was optimized to use depth maps for laser scans, if available. In 2.1 laser scans depth maps were not calculated, so it is required to rebuild depth maps. Sorry for missing that. This stage should not normally exceed 30 sec with usual ssd (you could check load just in case). Also I missed that extracting points is takes many time as well, so my ~2h estimate is really off.

Reagards, Egor

14
General / Re: Processing Time - Build Point Cloud
« on: October 31, 2024, 06:58:21 PM »
There is a note in 2.2 topic:

Project files created with 2.2.0 version can't be opened with Metashape 2.1 and earlier versions.

So it is not safe to say, but it typically should work. I can only remember, that multiple sets of masks may break compatibility.

Regards, Egor

15
General / Re: Processing Time - Build Point Cloud
« on: October 31, 2024, 04:39:00 PM »
Hi!

Please, try 2.2.0 pre-release from the topic https://www.agisoft.com/forum/index.php?topic=16745.0
There was significant performance improvements when building point cloud in a project with laser scans.

You can probably cancel processing and save the project to keep depth maps so you later can reuse them.

Building point cloud with 2.2.0 should probably reduce processing time for point cloud step of this project from ~15 hours to ~2 hours.

Regards, Egor

Pages: [1] 2 3