Code for robust monocular depth estimation described in "Ranftl et. al., Towards Robust Monocular Depth Estimation: Mixing Datasets for Zero-shot Cross-dataset Transfer, TPAMI 2022"
MIT License
4.27k
stars
599
forks
source link
Type 1 Font files - Can they be stopped from being written along with the depthmap images in the output? #177
I'm assuming it writes these "Type 1 Font file"s for everyone in the output folder along with the depth map images..
I don't know the purpose of these files, but I don't use them for anything. They seem to just take up a whole lot of space, as they're upwards of 10x or so the size of the depth map image itself.
How can we get these to stop being saved to storage? Otherwise you may have to babysit the process and delete these files manually periodically as the depth maps are being created, so your storage space doesn't fill up so quickly. Besides likely significantly reducing the lifespan of storage drives.
I'm assuming it writes these "Type 1 Font file"s for everyone in the output folder along with the depth map images..
I don't know the purpose of these files, but I don't use them for anything. They seem to just take up a whole lot of space, as they're upwards of 10x or so the size of the depth map image itself.
How can we get these to stop being saved to storage? Otherwise you may have to babysit the process and delete these files manually periodically as the depth maps are being created, so your storage space doesn't fill up so quickly. Besides likely significantly reducing the lifespan of storage drives.