Add MRC Input Compatibility When Not Using Denoiser#50
Merged
Conversation
This file contains hidden or 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
1 participant
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.
Adds support for direct MRC input files in the dataloader, enabling MRC processing without requiring the denoiser. This extends PartiNet's flexibility for users who want to work with MRC files directly.
Changes
Added MRC file input function to the dataloader
Updated PartiNet/DynamicDet/detect.py to support MRC inputs
Enhanced PartiNet/DynamicDet/utils/datasets.py with MRC handling
Updated version numbers across the project
Updated Singularity container definition
Related Issue
Closes #45
TO-DO
Review raw MRC detection weights to ensure optimal performance when not using denoiser: https://huggingface.co/MihinP/PartiNet