Closed OrangOrangUtan closed 6 years ago
You can try resizing the images using --resize-to
which will make mvs-texturing less memory intensive. We are working on building some turn-key parameters for smaller machines and also looking at ways to simplify the process for users who only want specific outputs.
ok I will try resizing!
Did this work? If not please reopen.
Running OpenDroneMap using a prebuilt Docker image on Mac OS X 10.13. I am testing out this program using the "aukerman" example data (https://github.com/OpenDroneMap/odm_data_aukerman). Things run fine until:
I know this must be because of my computer's small amount of RAM (4 GB, all of which I've allocated to Docker). My friend has tried running the same process on his Windows machine (8 GB RAM) and runs into the same error at the same spot.
Our ultimate goal is to generate a DSM to look at canopy height in a forested area; thus, we're not specifically interested in 3D models, orthomosaics, or anything else OpenDroneMap can produce other than the DSM. Is there any way to bypass the texturing step, and/or any other steps necessary for producing specifically the 3d model/orthomosaic, in order to make the entire process require less memory?