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 3
1
General / Re: Incremental images alignement not working
« on: April 26, 2024, 11:24:10 AM »
Dear djyoung,

During the incremental alignment, the chunk.transform changes, so you can observe a slight shift in the original tie point cloud. If you want to leave the first part unchanged, then as a workaround we can offer the following workflow:
- In one chunk, perform alignment for the data that you would like not to change.
- After that, duplicate it (select Duplicate... command from the Chunk context menu on the Workspace pane).
- Add the part you want to align to the duplicated chunk and perform the alignment.
- After that, using Python, you can apply the transformation matrix from the first chunk to the second. To do this, open the Console pane (select View > Console) and run the following command:
Metashape.app.document.chunks[1].transform.matrix = Metashape.app.document.chunks[0].transform.matrix



2
Feature Requests / Re: pointcloud intensity import and export
« on: March 14, 2024, 11:58:13 AM »
Dear Remco,

Metashape 2.x displays the Intensity for a point cloud. Since point clouds may have a very different range of intensity, the values for your point cloud may be too small, so it is displayed in black. In this case, for the convenience of display, we can suggest using the - Set Brightness tool (select Tools > Set Brightness).

But we want to note that if there are images in the project, then the tool will be applied to them as well. We will think about how to improve this tool so that it is convenient to adjust the values for display.

For now, we can offer the workflow described above. We hope it will suit you.

3
General / Re: 3D Pipe Modelling
« on: March 14, 2024, 11:49:33 AM »
Dear Sandy006,

The problem is related to the texture of the object. The object is quite glossy and reflects a lot of light. Therefore, unfortunately, you observe irregularities in the geometry.

If it is possible spread some talc powder (or anything similar) over it to change it from glittering to the dull surface. Also in some case we can offer use Smooth Mesh tool (select Tools > Mesh > Smooth Mesh). The Smooth tool allows you to make the model smoother and remove irregularities on the surface.

4
Bug Reports / Re: Selection-Tools adds more points than before
« on: February 05, 2024, 11:30:31 AM »
Dear Kalanka,

We apologize for the inconvenience. Thank you for the bug report.

We fixed the problem.  The changes will be included in the next version of Metashape.

5
General / Re: Import coordinates for laserscans
« on: January 24, 2024, 12:00:02 PM »
Dear Dieter,

1) Unfortunately, there is no such possibility now. But we can offer our script like workaround. You need to open a project with alignment (where you removed lock transform and the external orientation for laser scans was changed). After that, run the script. After running the script, there will be a dialog box where you need to select the source file with the laser scan. As a result, the script will shift the result of your alignment to this laser scan.

2) Yes, the key points of both types are optimized together.

3)We can suggest using the Measure Profile tool for horizontal surfaces (you can find information about this tool in our article -  https://agisoft.freshdesk.com/a/solutions/articles/31000170365) . You can also use markers (specify the markers on two clouds and check the error in the Reference pane). Unfortunately, other methods are not currently implemented in Metashape.

6
General / Re: Import coordinates for laserscans
« on: January 10, 2024, 04:32:19 PM »
Dear Dieter,

Thank you for your test and your feedback.  Please clarify if we understood correctly that many matches were found between the images and the laser scans, but they were not aligned?

If yes, do you have the opportunity to send us your project and the images that you used in the project to analyze the problem on our side? Please send the data to support@agisoft.com.


7
General / Re: Export confidence as a texture map?
« on: December 29, 2023, 04:17:18 PM »
Dear J.K.,

Thank you for your feedback.

You can use the scripts from Github that you have linked to. The vertices of the model will be colored according to the parameters you need. And after that, you can start building a texture and simply use the desired model as the source data (a model with altitude coloring and a model with overlay coloring). This way you will create the texture you need. I've added texture building commands to the scripts.

You are welcome, have a nice day!

8
General / Re: Export confidence as a texture map?
« on: December 27, 2023, 01:59:23 PM »
Good afternoon,

We can suggest testing our script as a workaround (recommend testing the script on a small project). 

The script colors the vertices by confidence, and then bake texture. Also please note that the model is built from depth maps and with vertex colors.

Select Tools > Run script... and choose the script. After that select Scripts > Texture Model with Confidence.


9
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).


10
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.

11
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.

12
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.

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

14
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.

15
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?

Pages: [1] 2 3