Monodepth regularization bug fix
- Fixed a bug where we were not switching to true depth loss, when true depth data is available.
It seems as though #2312 has a different idea, FYI
@AdamRashid96 New bug: the indexes of the current image samples and the indexes of the cached depth maps may not match at different launches. Therefore, either fix the train and validation, or generate the depth for all images, and then read by indexes.
@tancik maybe it's better to move the generation of depth maps from the dataset to a separate script?
@Ilyabasharov Thanks for pointing out this bug. I'll figure out whether to move the depth map generation to a different script or not, but I'll fix this indexing bug.
@AdamRashid96 did you plan to realize spatial continuity regularization from SparseNeRF?
@AdamRashid96 also I have found a bug that torch.nanmean useless in depth-ranking loss. if mask will be all False, torch.nanmean will give nan value.
@AdamRashid96 What's the status on this PR? Seems like generating the depth maps in ns-process-data could be a good option? @brentyi @kerrj