Make TrackMateImporter robust against non integer frame numbers #304
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.
This PR aims at making the TrackMateImporter more robust against non pure integer frame numbers.
I received a MaMuT file from a collaborator that contained frame numbers, such as
FRAME=0.0,FRAME=1.0, etc.While the decimal digit does not make any sense, it seems to be the case that some MaMuT version are storing them, cf. this snippet from a MaMuT file:
This lead to an exception while importing the MaMuT file into Mastodon:
This PR provides a workaround for this situation.