Ok, just about ready to start compiling. I plan to proceed in an orderly fashion, slow but starting from a working base. So,
phase 0. become familiar with the algorithms inherent in the ODM code, especially the ones that take hours to complete.
phase 1. Would be nice to get the compile instructions for each program, sans Docker. I would like to run the first tests natively for several reasons, including a) unfettered benchmark comparisons to the ones already published, and b) never developed in Docker so don’t know it’s requirements separate from bare metal.
phase 2. Then, once the programs are compiled and verified as working correctly, switch over to Qt Creator so I can interactively test sections of code to find the actual bottlenecks. Which functions, are we I/O bound, compute bound, or what.
phase 3. Start incorporating the Cuda instructions. 3a. verify each function with the code changes to ensure they are still operating correctly and give the right information.
phase 4. Look at the package overall and see if there is any gain to passing/leaving work files for the next program to pick up and use. Not likely, but it’s in the path.
phase 5. Release pre-alpha for you guys to test. Pre-alpha will require an nVidia graphics GPU and Linux. It’s what I have so just need to proof it before striking out to supporting other GPU’s, Windows, and etc.
phase 6. Expand utility to use by other sytems and GPU’s. (1st alpha)
phase 7. If anyone wants to, include the ability to spread their workload
phase 8. Determine if it is possible and makes sense to reduce the need for mega-memory in your computer to get good runs. User will need large, fast disks. The larger and faster, the better. (Ain’t it always so?)
phase 9. Trying to incorporate feed back and bug reports as we go along, and hopefully release 1st beta.
Sound like a plan?
No matter what, I need the information to 1) not use docker and 2) get (non-docker) compile parameters for each program, OpenSFM, ODM, etc. Please.