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 - feiko.lai

Pages: 1 [2] 3
16
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 21, 2017, 11:56:01 AM »
Thank you Alexey,

So it means we really don't have sufficient memory. But it is weird that this chunk has much less images than the other chunk which we handled it without any problem on the same machine. Can I safely conclude that: the number of images doesn't necessarily mean more memory required and the contend of images matters as well?

17
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 17, 2017, 05:27:39 AM »
download link

- removed

18
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 16, 2017, 03:16:00 AM »
Alexey, I PM you with a download link of project files with depth map, please check it

19
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 15, 2017, 12:30:32 PM »
Alexes,


We need to provide to project files with depth map enabled?

how to share it with your side as the size is quite large.

20
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 14, 2017, 05:21:51 AM »
Sorry Alexey, we didn't save project with depth map, do you recommend us doing so? We can enable it. While at the same time, any possible solution for us to try to deal with this problem?

Thanks

21
Bug Reports / [Build dense cloud] Error: bad allocation
« on: February 13, 2017, 06:28:34 AM »
Environment:
AgiSoft 1.2.6
Xeon dual CPU
128GB ram
Win 10 64bit
AMD R390x


I have a dataset with >5k images so I split it into 2 chunks

The first chunk with 3.7k images and it had no problem all the way through alignment-> dense cloud generation -> mesh generation

and then we turned to the second chunk with 2.8k images and which were taken by same camera and settings as the 1st chunk, but we always failed at "build dense cloud" step (High quality, 24Mpixel multi-spectral, tie points=12Millions), with such log:

2017-02-12 01:49:45 filtering depth maps... done in 76.53 sec
2017-02-12 01:51:02 preloading data... done in 63.463 sec
2017-02-12 01:52:06 accumulating data... done in 19.836 sec
2017-02-12 01:52:30 building point cloud... done in 3.238 sec
2017-02-12 01:53:17 Finished processing in 57848.2 sec (exit code 0)
2017-02-12 01:53:17 Error: bad allocation

and then we upgraded AgiSoft to v1.3.0 and tried again, but we got same failure and log:

2017-02-13 09:47:47 filtering depth maps... done in 42.662 sec
2017-02-13 09:48:30 preloading data... done in 23.542 sec
2017-02-13 09:48:53 accumulating data... done in 9.791 sec
2017-02-13 09:49:05 building point cloud... done in 2.018 sec
2017-02-13 09:52:02 Finished processing in 75365.2 sec (exit code 0)
2017-02-13 09:52:02 Error: bad allocation

It looks like dense cloud generation was finished but failed at the after steps.

22
Python and Java API / Re: Load images as multiplane cameras
« on: October 20, 2016, 07:44:07 AM »
+1 for this feature

23
Feature Requests / Re: Export Google Map Tiles by Python API
« on: October 19, 2016, 05:59:39 AM »
is it correct that XYZ + PNG = Google Maps Tiles in 1.25 ?

24
Feature Requests / Re: Export Google Map Tiles by Python API
« on: October 19, 2016, 05:57:20 AM »
Alex,

Thank you for your reply and I just checked with the document of 1.3 Python API but I can not find a particular combination of the formats you mentioned that is exactly identical to "Export Google Map Tiles", cloud u might to give me some hints or exact parameters?

25
Feature Requests / Export Google Map Tiles by Python API
« on: October 18, 2016, 06:42:36 PM »
It is only possible with GUI interfaces now and I wish this is possible soon.

Thanks

26
Python and Java API / Re: chunk.addPhotos() for micasense
« on: October 18, 2016, 06:38:35 PM »
+1 for this feature!

27
Feature Requests / Export Terrain Tiles for Cesium.js
« on: September 21, 2016, 08:48:56 AM »
It will be very useful if Agisoft can export Cesium.js terrain tiles for web visualization.

Reference is here https://github.com/AnalyticalGraphicsInc/cesium/wiki/Cesium-Terrain-Server

Thanks.

28
I exported Orthomosaic with "index value" raster transform,

When I exported it with JPG/PNG format, it was perfect and able to be view in QGIS.

But when I used Tiff as output format and opened it with QGIS, I could only see a blank white image, but it was okay with Photoshop.


FYI,

PhotoScan ver. 1.2.3, 1.2.4, 1.2.5 all tried with same result

29
Bug Reports / Re: Problems with Orthomosaic Export, since 1.2.5
« on: July 26, 2016, 12:16:50 PM »
Btw, I really wish there is Python API for import folders as multi spectral layers. Looking forward to it, thanks.

30
Bug Reports / Re: Problems with Orthomosaic Export, since 1.2.5
« on: July 26, 2016, 11:28:59 AM »
Hi Alexey,

I tried two kinds of input data, both turned out to be the same result:

1. JPG, 3channels
2. multispectural JPGS, each camera has 2 jpgs containing 3 channels, in total 6 channels

Thanks

Pages: 1 [2] 3