#631 Removed M0 Bsup warning from xASL_bids_parseM0#635
Merged
Conversation
Member
|
This looks good, I asked @BeatrizPadrela to check if this warning is not repeated anymore. In fact, this may be a general problem, what to do if the same warning is mentioned 100 times when you have 100 subjects. Perhaps we could think of a general transparent solution for this? |
Member
|
I see now that I'm confusing this issue with the other... So this comment should be moved then (typing this in my bed from my phone... Tried the laptop in bed but Kyra gets mad (that rhymes) |
Contributor
No this is the right issue, but Jan rmeoved the wrong warning |
HenkMutsaerts
approved these changes
Jun 12, 2021
jan-petr
force-pushed
the
optimize_#631-MultipleM0warning
branch
from
e6f3369 to
fb4a618
Compare
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
3 participants
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.
Linked issue
#631
How to test
Run Flavors to see if this doesn't appear twice anymore - tested by Jan.