Skip to content
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 testing with ITC-1600 [backport] #1922

Merged
merged 16 commits into from
Oct 31, 2023

Conversation

t-b
Copy link
Collaborator

@t-b t-b commented Oct 24, 2023

Will merge once CI passes and #1900 is approved and merged.

In a future commit we want to introduce testing with ITC1600 so the
current name is too general.
@t-b t-b self-assigned this Oct 24, 2023
@t-b t-b requested a review from timjarsky as a code owner October 24, 2023 18:01
@t-b t-b changed the title Add testing with ITC-1600 [backport Add testing with ITC-1600 [backport] Oct 24, 2023
t-b added 15 commits October 24, 2023 20:10
Only that is available on the test machine.
…for ITC1600

In 7dc07c7 (LNB: Save decimated stim set length for TTL channels,
2023-07-05) we changed the stored stimset lengths to be decimated. But the
test assertion for ITC1600 was incorrectly adapted as the sampling
interval is different for ITC1600.
…recedence

This makes the code easier to understand.
These are in the range [0, 3] as well.
Mention that the channels are GUI channel numbers.
…hardware

Since 2637e08 (Add channel types support to EpochsWave as chunk index,
2023-07-07) we have support for exporting epoch information of TTL
channels into NWBv2.

Unfortunately that commit failed to realize that we have to export TTL
information per ttlBit for ITC hardware. As the tests were also wrong,
this was found until now with the ITC1600 tests.
…s for ITC rack one

This should catch errors better.
The current code did not correctly store the stimsets for ITC hardware if
rack one is active with the ITC1600. As fixing it quickly would have made
complicated code worse, we rewrote the TTL channel export to be hardware
independent.
… suffix generation in NWB

Since 5f0f447 (NWB_AppendSweepLowLevel: Add support for TTL data from NI
hardware, 2018-09-12) we don't use the ttlBit as channelSuffix anymore but
2^ttlBit. It is unclear at this point why this was changed.

Introduce functions to convert between the two representations to avoid
even more confusion in the future.
@t-b t-b force-pushed the feature/1922-add-testing-with-ITC1600-backport branch from f365873 to 611677f Compare October 24, 2023 18:12
@t-b t-b merged commit 0a33c3f into release/2.7 Oct 31, 2023
18 checks passed
@t-b t-b deleted the feature/1922-add-testing-with-ITC1600-backport branch October 31, 2023 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant