Re: Mavericks: I recently upgraded my Mac Mini OS X from Mountain Lion (10.8.5) to Mavericks (10.9) and found that I can't open my PhotoScan projects that I could open previously using the older Mountain Lion OS. I'm using PhotoScan Standard Edition 0.9.1, which I installed before the OS X upgrade to Mavericks. I'm guessing my difficulty is due to a lack of memory resources, but I'm not sure why Mavericks OS X would have more of a problem than the older Mountain Lion.
Basic info: CPU: Intel quad-core i7 2.6 GHz, integrated Intel HD 4000 graphics, 16 Gb RAM.
Side question: What should my preference settings be for this processor? In the Preferences dialogue for OpenCL, I've set the CPU to use 3 out of 8 possible cores (I subtracted 4 from 8 cores to eliminate hyperthreading and subtracted 1 more because I checked the box to use the Intel HD 4000 for OpenCL processing, per the note below the box). For some operations, checking the Intel HD 4000 box for OpenCL causes display issues (flickering, horizontal bands, and crashes), and for others it seems to make no difference in performance. I haven't noticed any advantage by checking the OpenCL box. Is it better to uncheck the OpenCL box with the integrated graphics and use 4 or possibly even 8 cores with hyperthreading?
For an example of the difficulty I'm having with Mavericks OS X, I tried opening a project with 171 cams with a .psz file size of nearly 10 Gb. It loads 100%, but the program hangs without rendering the point cloud or shaded mesh (I haven't added texture to it yet). I could open this project on the older Mountain Lion OS X with a long wait, but now the program hangs and the computer completely stops after it loads the file. I can't even force quit the program and I have to turn the power off to reboot.
I'm also having problems processing new PhotoScan projects on the Mavericks OS. On a new project with 68 cams, image alignment (mild filtering) worked fine, but when I tried to generate the mesh (high resolution with the limit on faces set to 0) it crashed two times after it reached the end of the "generate mesh" step, which took about 3.5 hours for each run. The progress bar reached 100%; the log file indicates the process was completed successfully and makes no mention of any problems; but I never had a chance to save the results because the program just closed when it reached the end.
Also, when I checked "Reuse depth maps" in the generate mesh dialogue box so as not to have to repeat the work it already completed, it simply gave me an error and said it couldn't construct the model, so I had to start mesh generation over from scratch after each crash. I didn't have this problem generating a mesh with 171 cams in Mountain Lion OS, using images from the same data set.
Thank you for your responses and suggestions!