-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update trigger detection tutorial #191
Conversation
@RayStick can you have a look at this PR and help @vinferrer with the tutorial update, please? |
Codecov Report
@@ Coverage Diff @@
## master #191 +/- ##
==========================================
+ Coverage 94.42% 94.46% +0.03%
==========================================
Files 7 7
Lines 574 578 +4
==========================================
+ Hits 542 546 +4
Misses 32 32
|
Also, @vinferrer take #181 into account on your PR title! 😉 |
I can review this soon. |
This is still a draft for the moment. So you don't have to review it yet. However if you wanna modifiy the tutorial_file please do so. I recommend you to run the new version with the atomatic threshold |
This way you can lower down one of the triggers below that threshold. |
Thanks in advance @RayStick |
I ran the latest phys2bids on the tutorial_file.txt (to check it works for me) and it works great (it automatically finds the threshold, and therefore the right number of time points). A really good improvement, thanks. I will use the threshold it finds to modify one of the triggers below that, and then see how the manual correction workflow can be implemented after that. Let me know if there is anything else that would help you with this draft PR, before it is time to review. |
The manual correction is already implemented. I want to modify the tutorial file just to make a tutorial where the user can see a case that this manual threshold is needed. Using the manual correction is pretty easy, you just have to enter a new threshold through |
Ah yes, I understand the idea. I just meant (1) I will make the new file with one trigger different and (2) check the manual correction then works (for me). |
Oh sure, sorry for the missinterpretation |
Please check it |
Do you get a warning in the log saying that the expected trigger amount is no the one founded? |
I mean in the first case when the thr is done automaticly |
Ah, sorry, should have included the output. Running Gives:
|
Nice job people! Way to go! |
I think we should have only one tutorial file so is more clear to the user. Therefore we can delete the previous one and leave @RayStick edited file. what do yo think? |
Changes done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think it flows very well, the changes make it clear, and if you can just add the two suggestion, I think we're ready to merge it in!
Good job guys!
Co-Authored-By: Stefano Moia <s.moia@bcbl.eu>
Co-Authored-By: Stefano Moia <s.moia@bcbl.eu>
I hope that's the last thing |
@vinferrer I opened a PR to your branch with tiny things. As soon as you merge that in, we can merge this in! |
Because it says "some checks haven't been completed yet" - do I wait until that is completed before merging? |
dont merge |
i need to add smoia changes |
Update skip trigger count message in both script and documentation
Ah okay! As he had approved the PR, I thought you had already incorporated all his changes, sorry. |
@vinferrer can you push an empty commit to restart the CI? |
pushing |
I think we can merge now |
Great! |
Closes #190
Proposed Changes