Conversation
|
Found the reason. How sonpy uses release version number is unorthodox. It is an easy fix. |
smoia
left a comment
There was a problem hiding this comment.
LGTM (let's wait for the tests)!
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #410 +/- ##
==========================================
+ Coverage 94.25% 95.01% +0.76%
==========================================
Files 8 8
Lines 974 903 -71
==========================================
- Hits 918 858 -60
+ Misses 56 45 -11
|
|
hmmm all python 3.6 checks failed. Looks like a sonpy problem - they use the versioning numbers in a very special way (1.6.x -> python 3.6 support; 1.7.x -> python 3.7 etc) |
|
More than that, I believe that sonpy only supports python 3.7 and above (If I understood their page )
WDYT? |
|
Ah good to know!
Dealing with deprecation and adding a new function in one PR might be too much |
|
Agreed! Let's exclude 3.6 testing for sonpy. |
|
I will have a look and likely working on this next week |
|
@htwangtw I tried to update this PR to merge it in. As a temporary solution, I marked as xfail the sonpy test. I don't love this, but I don't know how to solve it at the moment. If you agree with the changes, we merge! |
The current implementation uses the official API, SONPY, from CED. SONPY is closed sourced. The scanner volumen trigger in the test file was stored as "marker" channel. The SONPY API returns time points of markers, rather than a timeserie. The module I wrote has been tested on client machine. Will check if this breaks other tests.
…ersion not minor release.
|
🚀 PR was released in |
Addresses #405.
The current implementation uses the official API,
sonpy, from CED.sonpyis closed sourced.In order to support
sonpy, the minimal python version should be 3.7. Hence I will mark this as part of the major release.The scanner volume trigger in the test file was stored as a "marker" channel. The
sonpyAPI returns time points of markers, rather than a timeseries. The module I wrote has been tested locally. I cannot run the full test due to bandwidth and data limit. Will check if this breaks other tests.Proposed Changes
phys2bids.io.load_smrChange Type
bugfix(+0.0.1)minor(+0.1.0)major(+1.0.0)refactoring(no version update)test(no version update)infrastructure(no version update)documentation(no version update)otherChecklist before review