Only show wrong mesh scale warning in console if not matching to any segmentation layer resolution #7921
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the warning that the scale of a loaded pre-computed mesh does not match the dataset scale factor is printed even in case, the mesh was calculated in a valid lower res mag. The changes of this PR now check whether the provided scale of the mesh matches any of the resolutions supported by the active segmentation layer multiplied with the dataset scale. Only in case none matches, the warning is printed to the console.
URL of deployed dev instance (used for testing):
Steps to test:
Please test locally. I was unable to prepare a dev instance testing scenario due to not having an already uploaded dataset with a meshfile creating the mesh scale mismatch warning on the current state of the master.
I suggest testing with the l4_sample dataset. The one on the dev instances does not seem to have the mesh files triggering the warning. The mesh files likely were computed in the finest mag.
Issues: