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.

Topics - dcm39

Pages: [1]
Feature Requests / Ground control based pre-selection for chunk alignment
« on: September 08, 2014, 02:24:56 PM »
Hi, not sure if this exists some how already, but I don't think it does.

When running chunk alignment, I have ground control for each chunk separately, but it seems that the "preselection" option for the point based alignment is just the simple "generic preselection".

For a nice linear survey with three chunks, the software really shouldn't need to try and match all of the photos, only the nearby ones. Can we have a "ground control" preselection for chunk alignment?

Bug Reports / path structure failiure in Linux
« on: September 08, 2014, 01:19:31 PM »
Somewhere around the dense cloud reconstruction step, the path to the photos gets mixed up within the project.

When the photos were loaded into the project, they were navigated to via a soft link. I suspect this problem is due to a mistake in treating soft links in the linux version of the software, but it only became a problem later after resaving the project.

Question: If the paths to all the photos in the project have been corrupted in this way (4000 photos for this project), is there any way to relink them? I really don't want to spend several days rebuilding the dense point cloud.

Bug Reports / Bug in "Export Ground Control data to file"
« on: February 21, 2014, 06:37:03 PM »

There seems to be a bug in using the "export ground control data to file" tool in the ground control panel. I have run as follows:

- Import photos
- Import ground control data (the rough guess positions and orientations of cameras)
- Align photos
- Export ground control data (I want to export the newly estimated values.)

I chose the column based text format for output, then in the given dialog box I tick the box "save estimated values" and the "save orientation" boxes.

The resultant text file is NOT the new estimated values, but instead the original source camera locations... This doesn't seem right! I need the new positions, not the old ones.

I am running build 1812


Bug Reports / Memory leak in point matching
« on: November 21, 2013, 12:28:44 PM »
I am using a 16core system with 384GB RAM - Running out of RAM should not be an issue!

When I run a large photoset (1500-2500 photos) I expect the matching to run for somewhere between 5-8 days, but there appears to be a slow memory leak. As a result, once the matching starts, the amount of memory in use slowly increases without halt, until all 384GB is in use... but it doesn't crash immediately, it only crashes once the matching is basically finished!

I have tried this on both 0.9.1 and 1.0.0. The memory appears to leak more slowly on the beta version 1.0.0, but it is still a problem for anything longer than about 2 days.

Any help much appreciated.

Pages: [1]