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.
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
[MRG] Fixing quickstart doc bug, write_raw_bids doc bug, and coordsystem.json overwriting error #675
[MRG] Fixing quickstart doc bug, write_raw_bids doc bug, and coordsystem.json overwriting error #675
Changes from 4 commits
40bca42
2765c1b
444e048
2a8ba6c
ba40dfd
30cd8f1
3da2805
8402893
eb575b4
c887113
27ede5b
795a44b
ebf8567
9249da0
2d934f6
a5f6897
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@adam2392 I don't have time to review in details but please monitor test time when you add tests. Add such big parametrize has a cost in CI time and needs to be fully justified. It's a general statement. I'd to avoid having mne-bids having a test time lasting tens of minutes. I find it already quite long actually
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.
I ran these locally and it's actually quite fast because all these files are very very small. The chunk using
write_raw_bids
as a result is very fast.The tests that generally seem to be taking long periods of time are actually the ones where we test for
split
of fif files correctly (need a humongous chunk to split it up > 2GB?), and the ones where we test the inspector. This is due to qualitative observation though, not an explicit profiling.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.
I can take these out, but I added these cases for the sake of covering a multiple coordsystems per datatype. Do we want to limit the parametrizations?
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.
Actually realized I could do profiling with a one liner cuz I have worked with pytest-profiler before:
If anything, I think the
test_eegieeg
I parametrized could be widdled down (if possible). Otw, these other tests are at least for now the longest 20.