GE_DMI3_Torso dataset #111
Merged
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
Output of
|
|
@casperdcl could be interesting to add this to our test runs in the leaderboard |
casperdcl
reviewed
Sep 25, 2024
KrisThielemans
force-pushed
the
GE_DMI3_Torso
branch
from
fd2992a
to
dcc50a6
Compare
|
@casperdcl I've removed the commits trying to cope with nonTOF multfactors for TOF data (and moved it to #114). This should now be to your liking 😄 . |
added to #91... |
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.
Files for GE_DMI3_Torso. I also made an attempt to adjust the examples to cope with non-TOF multfactors for TOF data, but there are remaining problems in the BSREM set-up, so instead, I've chosen to create the data with TOF multfactors as well.