-
Notifications
You must be signed in to change notification settings - Fork 85
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
add link spike_event_series to UnitSeries #825
base: enh/add_UnitSeries
Are you sure you want to change the base?
Conversation
the issues here should be fixed by 99281d7 |
Codecov Report
@@ Coverage Diff @@
## enh/add_UnitSeries #825 +/- ##
======================================================
- Coverage 73.85% 73.79% -0.06%
======================================================
Files 60 60
Lines 7191 7198 +7
Branches 1514 1517 +3
======================================================
+ Hits 5311 5312 +1
- Misses 1453 1455 +2
- Partials 427 431 +4
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## enh/add_UnitSeries #825 +/- ##
======================================================
- Coverage 73.85% 73.79% -0.06%
======================================================
Files 60 60
Lines 7191 7198 +7
Branches 1514 1517 +3
======================================================
+ Hits 5311 5312 +1
- Misses 1453 1455 +2
- Partials 427 431 +4
Continue to review full report at Codecov.
|
Oliver wants to talk about this PR on Thursday before we merge |
@oruebel what do you think? Can we merge this in? |
Since this changes the schema, at the very least the version of the schema should then change as well. Since the change is backward compatible with 2.0.0, I guess the version should probably be 2.0.1. We then also need to update the release notes in the nwb-schema repo to document the schema change. I assume this change will also affect MatNWB, i.e., we would need to update it as well. We should create a guideline document for updating the schema, i.e., how changes get reviewed and approved and what steps we need to take to get them in. |
Yes I agree. I have tested these changes with matnwb and they work with the
repo as is.
…On Tue, Mar 12, 2019 at 6:01 PM Oliver Ruebel ***@***.***> wrote:
Since this changes the schema, at the very least the version of the schema
should then change as well. Since the change is backward compatible with
2.0.0, I guess the version should probably be 2.0.1. We then also need to
update the release notes in the nwb-schema repo to document the schema
change. I assume this change will also affect MatNWB, i.e., we would need
to update it as well. We should create a guideline document for updating
the schema, i.e., how changes get reviewed and approved and what steps we
need to take to get them in.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#825 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAziEiPW_cep0lDopITJIJlkxdHVzrM2ks5vWCPLgaJpZM4bB-Hu>
.
--
----------
Ben Dichter, PhD
Data Science Consultant
|
the same goes for #822 |
@bendichter @oruebel Has this PR gone the way of #822? |
Trying to get links working. Having some trouble. help @ajtritt?