Add setting the objective magnification when patching #287
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current code only supports patching at a specified 'patch_level' of the WSI. However, in actual research, the objective magnification is usually specified for patching.
Therefore, I added functionality to the fast patching pipeline to allow specifying the objective magnification during patching. The objective magnification attribute is set to 'None' by default. When the objective magnification is specified, the 'patch_level' will be ignored, and the code will automatically select an appropriate 'patch_level' and corresponding 'custom_downsample' based on the WSI. Additionally, I made corresponding modifications to 'dataset_h5.py' to enable custom downsampling during feature extraction.