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.


Topics - David Cockey

Pages: [1]
1
The Windows X64 installer file for 1.4.2 downloaded as a .txt file, not as a .msi file. I changed the file type to .msi and the installer successfully ran.

2
Bug Reports / No model displayed.
« on: March 27, 2015, 07:45:25 PM »
Display of the model in PhotoScan has stopped.  Standard Edition, Version 11.4 build 2021 (64 bit).  NVIDIA GeForce GT 740M Driver 9.18.13.4725 1/9.2015  System has been restarted and problem remains.

Examples of log messages:


renderer_gl.cpp line 535: glDrawElements(encodePrimitiveType(type), (GLsizei) countElements(type, chunk), encodeFormat(ibuffer->format), (GLvoid *) ((char *) indices + offset)) failed, error 1285

renderer_gl.cpp line 121: glClearColor((color & 0xFF) / 255.f, ((color >> 8) & 0xFF) / 255.f, ((color >> 16) & 0xFF) / 255.f, 0.0f) failed, error 1285

renderer_gl.cpp line 506: glDrawArrays(encodePrimitiveType(type), (GLsizei) offset, (GLsizei) countElements(type, count)) failed, error 1285

3
Bug Reports / Dense Cloud Build - exponential time increase
« on: July 23, 2014, 06:08:14 AM »
Times for "filtering depth maps" during Build Dense Cloud appear to increase exponentially with the number of cameras used on my current project. Is this normal and expected? I don't recall encountering it before.  Attached is log file for a batch run with three chunks using 361, 402 and 502 cameras. (File edited to reduce size so it could be uploaded) Times for "filtering depth maps" were 626 sec, 2332 sec and 4484 sec.

PhotoScan Standard Edition Version 1.0.4 build 1847 (64 bit)
Windows 8.1
i7-3770 CPU, 4 core and 8 virtual threads, virtually 100% use of CPU during "filtering depth maps"
AMD 7770 GPU, not used during "filtering depth maps"
16GB memory, 8.4GB maximum used during run.

GPU is used during "depth reconstruction".

4
Feature Requests / Copy Camera command
« on: July 12, 2014, 10:06:55 PM »
A "Copy Cameras" command would be very useful for me. Same as "Move Cameras" except a copy of the cameras would remain in the source chunk.

5
Bug Reports / Aperture Value, not F-stop in Show Info... for photos
« on: February 18, 2014, 06:33:07 AM »
The number in the Aperture line of the Show Info for photos is the Aperture Value, not the F-stop number, even though the number is preceded by "F/" which implies it is the F-stop number. A photo taken at F/8 is has an Aperture of F/6 shown, and a photo taken at F/11 has an Aperture of F/7 shown. This is not a major problem but it is confusing when looking in PhotoScan to see what F-stop was used for a photo.

"Aperture Value" = log("F-stop") / log(sqrt2)
"F-stop = (sqrt 2) ^ "Aperture Value"

My understanding (perhaps incorrect) is the raw EXIF data contains the Aperture Value rather than F-stop. Most software converts it to the corresponding F-stop value before reporting.
   

6
General / Updates - 1824 or 1812
« on: February 16, 2014, 10:15:47 PM »
I currently have 1.0.1.1812 Windows 64 bit Standard installed. When I click on "Check for Updates" in the Help menu PhotoScan reports that 1.0.1.1812 is installed and it is the latest version. But when I look at the AgiSoft website for downloads (Download demo page) it shows version 1.0.2.1824 as the current version.

Is the "Check for Updates" feature not properly reporting the latest version?

7
Feature Requests / Save Job in Batch Processing
« on: November 26, 2013, 11:34:43 PM »
"Save" as a job which can be specified in batch processing. This would be in addition to the save after each task box. When working with projects which have large files saving after each task can consume considerable time. I'd like to be able to specify when the project would be saved.

It would be useful if there was the option to save to a new file name as well as saving to the current file name.

8
General / Mesh Build in PhotoScan 1.0 - My Workflow
« on: November 26, 2013, 03:11:29 PM »
PhotoScan 1.0 (pre-release available in http://www.agisoft.ru/forum/index.php?topic=1476.0 ) separates building the mesh from building the dense cloud. Below is a summary of the workflow I'm using in projects involving objects such as boats.

Mesh Creation in PhotoScan 1.0
 
Workflow

1)  Trim significant noise and unwanted parts such as supports from the Dense Point Cloud before creating the mesh. The undo arrow in the icon toolbar at the top can be used to back up during the trimming process. If significant trimming is needed it may be best to create a copy of the chunk, and then trim the copied chunk.

2)  Click on Build Mesh in the Workflow and set the Build Mesh parameters:
Surface type:      Arbitrary
Source data:      Dense cloud
Polygon count:   40000000  (40 million, or a similar very large number)
Advanced:   
Interpolation:   Enabled (default)
Click on okay and build the mesh.

3)  The mesh can be decimated in a separate operation if a smaller mesh is needed than the result from Build Mesh. The Decimate Mesh tool is found under the Tools menu.
    Tools
      > Mesh
         > Decimate Mesh
Specify the number of faces desired and click okay.

4)  Build Texture if needed. A reasonable choice for the settings is:
   Mapping mode:   Generic
   Blending mode:   Mosaic (default)
   Texture size/count:   2048 x 1
   Advanced
      Enable color correction box not checked
 
Notes

Specifying a very large polygon count in Build Mesh results in the smallest amount of memory being used during the mesh generation process, contrary to what may seem obvious. The size of the mesh initially created during Build Mesh depends only on the number of points in the Dense Cloud and the geometry of those points, not on the value specified for Polygon count. The number of faces in the initial mesh is then compared to the specified Polygon count value, and the initial mesh is then decimated if needed so that the number of faces does not exceed the specified Polygon count value. Mesh decimation can use more memory than used for the creation of the initial mesh.

If the desired size of the decimated mesh is not certain, copy the chunk and then decimate the mesh in the copied chunk. If a different size mesh is desired then the original chunk can be copied again and the mesh in the second chunk decimated to the different size.

Enabled is generally the best choice for the mesh interpolation type for objects with strong three-dimensional shape.. Build Texture may not work properly if the mesh was created with Interpolation Disabled. Extrapolation attempts to create a closed mesh without any holes, and the result may not be the desired shape.

Texture should be created if the file is to be exported as a .obj and the mesh needs to have visual texture. Texture can also result more apparent detail and a more pleasing appearance with a relatively coarse mesh. If color correction is enabled for Build Texture the execution time may become much longer, particularly with a large number of photos.

David Cockey
26 November 2013


9
Bug Reports / Disabled photos used to Align Chunks
« on: July 23, 2013, 06:18:39 AM »
Disabled photos are used by Align Chunks when the Camera Based method is selected. This has caused problems for me when I have disabled an obviously incorrectly aligned photo/camera in a chunk.

Is "Disable" for a photo in a chunk intended to only apply to certain tasks? If so what tasks use photos which have been set to "Disable"?

10
Feature Requests / OBJ Texture Names Chunk Specific
« on: July 07, 2013, 05:23:58 AM »
When OBJ meshes are exported use the chunk name instead of "Textured" for the "material" in the associated .mtl and .obj files.
.mtl file: "newmtl Textured" becomes "newmtl ChunkName"
.obj file: "usemtl Textured" becomes "usemtl ChunkName"

I export multiple chunks as OBJ meshes from a single project. I then have to go in and manually edit the sets of .mtl and .obj files so that the names of the "materials" are different for each mesh.

11
Bug Reports / 0.9.1 Build 1647 crashes graphics
« on: March 28, 2013, 10:41:21 PM »
(Also reported in Agisoft PhotoScan 0.9.1 pre-release thread.)

Build Geometry in 1647 Standard Version crashes the AMD 7770 graphics on my system when OpenCL is used. I have not had the problem with previous builds. Align Photos is fine. A second or so after Build Geometry is started the screen goes black and then a message appears saying graphics was shut down and restarted. PhotoScan continues to run but with low CPU usage and no GPU usage. Not obvious any progress is made. The behaviour is repeatable.

When OpenCL is disabled Build Geometry runs okay.

Machine is running Windows 7, Intel i7-3770, 16 GB memory, AMD Radeon HD 7700 graphics with 3 GB memory, AMD driver 9.2.0.0 9/27/2012. I checked for driver updates from AMD and driver is shown as most recent.

I normally run PhotoScan with OpenCL enabled and 6/8 Active Cores.

Correction: Graphics has 2 GB memory, not 3 GB.

12
Bug Reports / Chunk Align, Camera Method - Batch Only
« on: October 30, 2012, 06:52:08 AM »
The only way I can use the Camera Method for aligning chunks is to go through Batch Process. Then I can select it. If I select Align Chunks directly from the Workflow menu then I don't have a choice of methods to use. Only the Points Method is available. The Camera Method is several orders of magnitude faster for my current project and appears to be as accurate given the large number of cameras common between chunks.


13
Bug Reports / Undo and Redo not working
« on: October 29, 2012, 04:43:50 AM »
The Undo and Redo icons are never active for me. I'm using PhotoScan Standard Version 0.9.0 build 1586 (64 bit) with Windows 7.

14
Feature Requests / Start button for batch processing
« on: October 29, 2012, 04:40:29 AM »
Request - A separate "Start" button to begin executing batch processing instead of having it start when the Batch Process window is closed with the OK button.

Rationale - Ability to close the Batch Process window without starting processing. I frequently need to close the Batch Process window while adding tasks to either check something using another window. Currently I have to click OK, have batch processing start, and then cancel batch processing.

15
General / OpenCL Prefrence Settings: Intel i7-3770, AMD Radeon HD 7770 2GB
« on: September 15, 2012, 07:28:38 AM »
I'm a new user of PhotoScan and I experimented to find the "best" settings for OpenCL with my hardware. Bottom line is performance is very close when OpenCL is turned on and number of active CPU cores is set to 4, 5, 6 or 7 for my 8 thread CPU. Execution time for "Build Geometry" is cut in half and "Total Performance" more than doubles. Now for some details.

PhotoScan 0.8.5 build 1423 (64 bit)

HP Pavillion H9
Motherboard: Petragon 2AD5, Intel Z75 chipset
CPU: Intel i7-3770 CPU, rated 3.4GHz (3.9GHz max observed), 4 cores / 8 threads
Graphics: AMD Radeon HD 3770, 2GB memory (HP version), 1000MHz, Capeverde 10 core processor
Memory: 12GB

I used the first 10 photos in the sample01 download set. Align Photos was run with Accuracy: High.
The bounding box was reduced to be tight to the statue and plinth. No masking was used.

The OpenCL settings box shows a maximum of 8 active CPU cores.

Build Geometry (Arbitrary, High) was run 28 times with various combinations of OpenCL off/on and number of active CPU cores.

Execution Time (seconds) and  Performance (million samples/sec) were recorded for Device 1 (CPU), Device 2 (Capeverde, graphics processor) and Total Performance. There was considerable variation in the total times for repeat runs with the same settings, up to 12%. Performance results were much tighter. Times given below are typical.

OpenCL,  Active CPU Cores, Time (sec), CPU (ms/s), GPU (ms/s), Total (ms/s)
Off, Any, 315, 130, 0, 130
On, 8, 219, 127, 80, 205
On, 7, 155, 127, 175, 302
On, 6, 158, 126, 187, 312
On, 5, 155, 124, 190, 315
On, 4, 150, 124, 192, 317
On, 2, 172, 108, 195, 303
On, 1, 214, 73, 200, 272
On, 0, 237, 0, 197, 197

Clearly turning OpenCL on and a setting for number of active CPU cores of 4 to 7 yields the best performance, with 4 slightly better than 5, 6, or 7.

The percent of utilization for the CPU cores was observed using Open Hardware Monitor and Windows Performance Monitor. The work was distributed across the cores regardless of the number of active CPU cores setting selected. This was true both with OpenCL on and off.

Pages: [1]