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 - e.spiridonova

Pages: [1] 2
1
Dear noodlez,

We modified the script. Now a shape is taken from the layer with the name - base (or Base, or BASE).
Left-to-right shape parameter - it is necessary to remove the checkbox when the shape is drawn from right to left.
Use hard normals parameter - for sharp corners (for example, for buildings), for smooth curves it is necessary to disable (in your case it is better to disable).


2
Dear Beda,

Thank you for the information.

On the headless server we were able to reproduce the problem. We are investigating the problem.

But for now we can only offer the following workarounds:

1. Use:
metashape-pro/metashape -platform offscreen -r general_workflow.py data output
 
2. Or check the success of the script execution through a self-written exif code. For example, save a text file at the end of the script "finished.txt " with the text "ok". And at the beginning of the script, delete it if there is one.

3
Bug Reports / Re: Checker grid like lines in depth map generation.
« on: October 10, 2023, 03:59:57 PM »
Hello,

We have published a pre-release version of Metashape 2.1: https://www.agisoft.com/forum/index.php?topic=15894.0

There is a minor improvement in mesh generation algorithm that reduces banding in some cases.

4
General / Re: Weird banding/noise pattern in mesh from depth maps
« on: October 10, 2023, 03:59:52 PM »
Hello,

We have published a pre-release version of Metashape 2.1: https://www.agisoft.com/forum/index.php?topic=15894.0

There is a minor improvement in mesh generation algorithm that reduces banding in some cases.

5
Bug Reports / Re: Space mouse in Agisoft Metashape
« on: August 07, 2023, 04:56:10 PM »

6
Bug Reports / Re: 2.0.2 Standard: Displacement maps not exporting
« on: July 27, 2023, 12:39:06 PM »
Dear taran,

You can check the displacement map in the UV Mapping dialog window (select Tools > Mesh > View Mesh UV ), the texture is actually not completely black.

Displacement map records offsets in the scale of the model coordinates, if the model coordinates are small, then some programs can display Displacement map almost black (or almost white if the coordinates are large). This is done so that users have the opportunity to use real offsets, and not selected "by eye".

We can offer you to export the texture in *.tiff format (since *.jpg doesn't support 32-bit floating point) and use this texture file if necessary in a third-party texture editing program.

7
Bug Reports / Re: Assertion "3478972301441" failed at line 720
« on: April 05, 2023, 12:08:43 PM »
Hello Everyone
I just encountered very similar problem.
I have a bunch of scans from leica scanner orinted in Cyclone and exported to e57 separately. I can process all of them in ContextCapture, but some of them (3 out of 20 scans) fail to process to mesh in Agisoft giving error: failed #44 BuildModel.prepairDepthMaps (1/1): Assertion "23671468921001171" failed at line 1149!
It is curious, that same 3 scans in e57 fail to convert to RCP in recap...
Have proceed with some small investigation...
1. changing region in Agisoft does not help (smaller, bigger, different parts of the scan).
2. deleting points not in range, updating, compressing point cloud in Agisoft does not help.
3. eksporting without color or intensity does not help
4. filtering point cloud containing 700.000.000 points giving 0.5mm resolution gives point cloud with 1.700.000.000 :O (something is not right... should be smaller if i understand correctly)
5. importing point cloud with different coordinate precision settings didnt help.
6. using 2.0.2 or 2.0.1 - no difference - fresh projects each time.
7. Two desktops (64 GB RAM and 128 GB ram, different hardware) - same error.
Two of them are in scanners high resolution giving 700.000.000 points, but one of them is in medium resolution with about 200.000.000 points (as all of working scans) so I guess this is not the size problem.
What we noticed is that the scan is processing in Agisoft and Recap if we delete points close to the scanner position in Cyclone before exporting. Is it possible that the problem is too dense point cloud on objects near the scanner??? If i delete same points inside Agisoft (after import) it does not solve the problem - scan is still "faulty" in some way and does not want to process to mesh.
Anyway, the workflow would require to load the scans and just process. Identifing 3 out of 20 scans which is cousing the problem is a bit time consuming (assertation error does not give strait information about the name of scan/scans in project, so I guess it would be best if you could check and solve the problem on importing clouds.
I can send you a link with a sample scan or two. Please provide me an email (or other private masseging system) I can use for passing it.
Best regards

Dear pima,

Could you please send us an example of your data set to support@agisoft.com?

8
I'm also experiencing the issue with the red/pink point cloud bounding box in V2.0. This seems to appears after duplicating the point cloud. The point cloud bounding box is also then visible on the original point cloud until the project is closed and opened again. I can't find a way to remove or make invisible the bounding box.

Dear rmowbs,
We can offer the following solution: could you please left-click on the Workspace pane (for example, click on the name of the chunk) and then the red bounding box will not be visible in the Model view.
If you double-click on point cloud, the red bounding box will appear again.

9
Dear Phogi,
Starting Metashape 2.0 in the Model view there are 2 Regions visible around the point cloud. The red color indicates the Point cloud Bounding box. The green color indicates general bounding box for this chunk. Now in Metashape available to change the color for it (Tools > Preferences > Appearance tab).  You can also left-click on the Workspace pane (for example, click on the name of the chunk) and the red bounding box will not be visible in the Model view. If you double-click on point cloud, it will appear again.

About Source and Sequential preselections: such a difference in the alignment results shouldn't be observed. Please check that when using Source preselection you correctly specified the coordinate system for the chunk and for the cameras in the Reference Settings dialog window (click Settings button on the Reference pane). Also please check that the image coordinates data was imported correctly.

10
General / Re: Agisoft Metashape 2.0.0 pre-release
« on: January 24, 2023, 06:02:44 PM »
This may seem like a minimal thing to look for, but the change of "Build Dense Cloud" to "Build Point Cloud" is fine, but now the order in the Workflow dropdown is out of order it seems and can be confusing. it is nice to have the workflow items in order of common workflow process order. Now Build Point Cloud is below Build Tiled Model.

Dear smiller,
Thank you for your feedback.

Usually, when building a model and a tiled model, users can skip building a point cloud and use depth maps as source data. Users who need a point cloud as a result usually process aerial data, after that they build DTM/DSM, Orthomosaic. Therefore, the workflow is divided into such sections and the order of commands has been changed.

11
General / Re: Import Point - Issue with import Dense Cloud
« on: December 28, 2022, 03:20:52 PM »
Dear Daniele,
Thank you, we downloaded the data.
We wish you Merry Christmas and Happy New Year!

12
General / Re: Import Point - Issue with import Dense Cloud
« on: December 26, 2022, 01:09:25 PM »
Hello,
It would be helpful, if you can share your data set.
If you are able to share the data, please send the download link to support@agisoft.com.

13
Python and Java API / Re: Add tweaks to script in Metashape
« on: November 07, 2022, 12:25:42 PM »
Dear ehxz,
Please note, that the 1st solution this is an analogue of setting tweaks through the interface.
The second solution (using tasks) is suitable for using tweaks during the script.

14
Python and Java API / Re: Add tweaks to script in Metashape
« on: November 07, 2022, 11:52:15 AM »
Hello,

We can offer the following solutions:
1. Use the following command:
Code: [Select]
Metashape.app.settings.setValue("BuildModel/ooc_surface_blow_up",0.95)
Metashape.app.settings.setValue("BuildModel/ooc_surface_blow_off",0.95)
‚Äč
2. Or try using tasks, as an example below:
Code: [Select]
chunk = Metashape.app.document.chunk
task = Metashape.Tasks.BuildModel()
task["ooc_surface_blow_up"] = "0.95"
task["ooc_surface_blow_off"] = "0.95"
[i]#add other paramerters for building model[/i]
task.apply(chunk)

15
General / Re: Hovermap SLAM normals
« on: November 03, 2022, 05:59:24 PM »
Dear Chani,
We analyzed your data and imported the trajectory file into the project and the normals are calculated correctly. 

Unfortunately, the *.xyz format for normals is not supported now, and before using it, you need to re-save it to the *.txt format and then use the *.txt file.  Also, the first column in the file cannot be excluded through the GUI of the program (there is a value of 0), you need to delete this column if you want to import the file through the GUI and specify the following parameters (see screen 1.png).

Or we can only suggest resaving the file in *txt format without deleting the first column in the file and using the command via Python for import point cloud.
import Metashape
Metashape.app.document.chunk.importPoints("/path/to/laz_file.laz", use_trajectory=True, traj_path="/path/to/traj.xyz.txt", traj_skip_rows=1, traj_columns="0txyz")

where:
/path/to/laz_file.laz - path to the laz file with the cloud
/path/to/traj.xyz.txt - the path to the txt file with the trajectory
traj_skip_rows=1 - there is 0 in the first column of the trajectory file, so we added the option to skip this column in the script.


Then we can offer the following workflow:
- re-save the file with the trajectory in *txt format;
- open Console pane (select View > Console) and use the command:
import Metashape
Metashape.app.document.chunk.importPoints("/path/to/laz_file.laz", use_trajectory=True, traj_path="/path/to/traj.xyz.txt", traj_skip_rows=1, traj_columns="0txyz")


To check whether the trajectory file was taken into account when importing, you will see similar lines as in screenshot 2.png

Pages: [1] 2