You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During bidsification, I am checking if a specific parameter matches specific recordings across the session. Therefore, the parameter is written to a global variable and checked for each recording in RecordingEP. In SessionEndEP, the global variable is reset to its starting value which works fine during the bidsification, but does not happen during the Bidsmapping step, leading to a warning due to a mismatch.
Moving the same step to one of the beginning EPs avoided the warning, but doesn't fit my purpose. I did not test if the problem occurs only with SessionEndEP or also with other EndEP's. Again, this problem only occurs during Bidsmap creation, not during the actual data bidsification.
The text was updated successfully, but these errors were encountered:
Indeed, during mapping, there's no call for SessionEndEP (or SubjectEndEP). Not sure if it was just forgotten, or there was a reason. I'll fix it at next release.
For a quick fix, will it be possible for you to move the reset of global variable to SessionEP?
During bidsification, I am checking if a specific parameter matches specific recordings across the session. Therefore, the parameter is written to a global variable and checked for each recording in RecordingEP. In SessionEndEP, the global variable is reset to its starting value which works fine during the bidsification, but does not happen during the Bidsmapping step, leading to a warning due to a mismatch.
Moving the same step to one of the beginning EPs avoided the warning, but doesn't fit my purpose. I did not test if the problem occurs only with SessionEndEP or also with other EndEP's.
Again, this problem only occurs during Bidsmap creation, not during the actual data bidsification.
The text was updated successfully, but these errors were encountered: