You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are created with permission 600 so they aren't readable by others without changing permissions using the root user.
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
The above files should be created with permission 644 so they are readable by everyone, this is the behavior in ODM v3.1.0.
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
git clone https://github.com/pierotofy/drone_dataset_brighton_beach.git
docker run -ti --rm -v $(pwd)/drone_dataset_brighton_beach:/datasets opendronemap/odm:3.5.3 --project-path /datasets .
ls -ltr drone_dataset_brighton_beach/odm_meshing/
The text was updated successfully, but these errors were encountered:
How did you install ODM? (Docker, installer, natively, ...)?
Docker
What is the problem?
The files:
-rw------- 1 root root opensfm/undistorted/openmvs/scene_dense.ply
-rw------- 1 root root opensfm/undistorted/openmvs/scene_dense_dense_filtered.ply
-rw------- 1 root root odm_meshing/odm_mesh.ply
-rw------- 1 root root odm_meshing/odm_25dmesh.ply
Are created with permission 600 so they aren't readable by others without changing permissions using the root user.
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
The above files should be created with permission 644 so they are readable by everyone, this is the behavior in ODM v3.1.0.
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
The text was updated successfully, but these errors were encountered: