Agisoft PhotoScan 1.0.0 pre-release

[andyroo]

Another followup on my dense point cloud processing time observation above.

I decided to process a similar sized dataset (but from an aircraft covering 30 sq km instead of a crane covering ~10,000 sq m) and the dense point cloud processing finished in <6 hours. I am guessing that the increased overlap on the project I mentioned earlier is the main cause for the increase in processing time, as opposed to the total number of images.

(I also updated to build 1742)

And on another note I have a question about this build (and my workflow). Previously I had been processing about 20km-long flights in four 5km-long chunks, with vertices set at 50 million, to try to maximize detail. Disadvantage is that I had to enter many of the GCPs twice since I am overlapping the chunks to improve the fit.

With the new pointcloud generation step, I decided to try generating the whole model at medium (sparse->dense->mesh), inputting all of the GCPs, then regenerating the whole model at a higher resolution. I figure at worse case I can clip the model into chunks again and regenerate those if it gets too slow, but things seem to be working well. My big question is - to maintain the same grid resolution, should I increase my faces to ~150 million? that seems... daring...

[clardic]

Hello
I'm MAC user on Snow.
I have a blocking of the complete computer during blending texture sometimes.
Regards

[Wishgranter]

clardic - try monitor CPU usage, if it blocking it is because code is efficiently written and all cpu resources are used for the blending subroutine......

[clardic]

Thanks for your fast reply. You suggest to use 3/4 CPU instead 4/4 ?
 

[Wishgranter]

best if the workstation on what is processed do just reconstruction.... setting the CPU amount in settings will have no impact on this step......  just enjoy cup of coffee :-D 

[RHenriques]

Hi Clardic

In the application preferences, OpenCL tab, do not activate any OpenCL devices. Use only the CPU cores available. I was having the same problem (OSX; Mountain Lion) and this solved my problem without any major slow down of the reconstruction process. Something must be made to avoid this overflow of the graphical card, until the machine becomes unusable. Before deactivating opencl devices, I had to force the restart of the machine to be able to use it again. This wont happen in small datasets but it's almost inevitable if you have more than 150 photos and use high quality point cloud.
Cheers

[andyroo]

I have a strange thing in PS 1.0 build 1472 - the View>Perspective/Orthographic option has a "5" next to it. Just noticed after optimization and a batch dense point cloud/mesh build when I came in this AM. screenshot attached. Will update later today.

[edit] Thank you chadfx for explaining

[chadfx]

It's a hotkey for toggling the Perspective/Orthographic views. It seems there are a number of non-modifier hotkeys in there if you look under the Predefined Views submenu.

[Paulov]

Nice improvement on this version.

The photo matching still need improvement as photosets that I'm able to match with other softs fail to match in photoscan. Shall I increase the point number analized in the matching?

Som coments:

As seen in the atached images some tiles are visible in the point clouds, probably due to how the app processes the data, the visible tile borders is not the worst but some of the tiles having less point resolution so the point cloud has no unirom density. There is a shot where it is more visible because theh Microstation reduces the point count by a %  when rotating the scene.

[clardic]

Thanks RHenriques,
The Open CL was deactivated !
I'm on 3/4 CPU core and always the same problem...
Do to investigate again

[clardic]

Hello
It's blocking also for Mersh construction.
34 pictures about 8 to 9 Mo by picture.
Mac leopart Snow
It seams that we don't have the problem with the version 9.1
Probably a problem due to the version 10

[andyroo]

I noticed that I can't make models with as much detail - as many vertices in the mesh - from PS 10. I set Workflow/batch/build mesh/face count=custom, and custom face count to 50 000 000, and I was only able to get 23 669 280 faces and 11 840 381 vertices.

I am using Quality=high, depth filtering = moderate in the point cloud. I haven't really been able to resolve individual logs on gravel bars since 0.8.5. That is, in 0.8.5 the DSM more faithfully reproduced smaller logs than it does now.

There is great improvement in orthophoto generation speed in this version I think.

Andy

[airmap3d]

Can anyone tell me what the default settings for 'classify ground points' are (max distance, max angle, cell size)?  I have adjusted mine and forgotten what the defaults were.  Every time I close and re-open PS it maintains my last set parameters and does not return to the default.

Many thanks.

[Alexey Pasumansky]

Hello clardic,

Could you please send us the log file and reconstruction parameters used?


Hello Andy,

Custom face count parameter defines number of faces the model should be decimated to if reconstruction provides bigger number. The maximal number of faces is mostly determined by the quality selected, so if you've got less faces than in face count field, this means that you've got the maximal possible faces for the parameters used.

[James]

Can anyone tell me what the default settings for 'classify ground points' are (max distance, max angle, cell size)?  I have adjusted mine and forgotten what the defaults were.  Every time I close and re-open PS it maintains my last set parameters and does not return to the default.

Many thanks.

max distance: 15
max angle: 1
cell size: 50

in build 1754