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 interface for 2p imaging data, suite2p and spike2 signals in dual acquisition modality #25

Merged
merged 8 commits into from
Jun 11, 2024

Conversation

alessandratrapani
Copy link
Collaborator

@alessandratrapani alessandratrapani commented May 31, 2024

Small PR to add interfaces as in the 2p-only configuration #22

  • add interface for 2p data in dual modality (probably just reusing the one for 2p only acquisition)
  • add suuite2p interface
  • add spike 2 signals
  • add correct metadata for dual acquisition
  • time alignment

PS: no behavioral video present. Facemap output will be added in a followup PR after solving #19

@alessandratrapani alessandratrapani self-assigned this Jun 8, 2024
@alessandratrapani alessandratrapani changed the title Add extractors and interfaces for imaging data in dual acquisition modality Add interface for 2p imaging data, suite2p and spike2 signals in dual acquisition modality Jun 11, 2024
@alessandratrapani alessandratrapani marked this pull request as ready for review June 11, 2024 08:13
@alessandratrapani
Copy link
Collaborator Author

stub nwb file here

Comment on lines 38 to 39
- name: OnePhotonImagingPlaneRedChannel
description: Imaging plane for the Green channel recorded with 2p microscope.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it not 1p microscope then?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good Catch! NO it should be 1p, I corrected it

@weiglszonja
Copy link
Collaborator

The wheel signal here has [100, 1] dimension, while in the other example it was [100], I think it should be [100] here as well, is it not?

@weiglszonja
Copy link
Collaborator

The OnePhotonMicroscope is added here, but there is not ImagingPlane linked to it, is it intentional?

@alessandratrapani
Copy link
Collaborator Author

The OnePhotonMicroscope is added here, but there is not ImagingPlane linked to it, is it intentional?

Yes, I created already the complete metadata yaml, I am going to add the one photo series in a next PR

Copy link
Collaborator

@weiglszonja weiglszonja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, looks good!

@alessandratrapani
Copy link
Collaborator Author

The wheel signal here has [100, 1] dimension, while in the other example it was [100], I think it should be [100] here as well, is it not?

That's weird, I re-run it and now they both have shape (100,1)

@weiglszonja
Copy link
Collaborator

weiglszonja commented Jun 11, 2024

The wheel signal here has [100, 1] dimension, while in the other example it was [100], I think it should be [100] here as well, is it not?

That's weird, I re-run it and now they both have shape (100,1)

Hmm is that from Spike2? But this can also be discussed in a follow-up

@alessandratrapani
Copy link
Collaborator Author

alessandratrapani commented Jun 11, 2024

The wheel signal here has [100, 1] dimension, while in the other example it was [100], I think it should be [100] here as well, is it not?

That's weird, I re-run it and now they both have shape (100,1)

In that case I think we should store as (100,) if it's a single trace, but can also discuss in a follow-up

Yes the interface is custom but the extractor is from neuroconv (CedRecordingExtractor)

@weiglszonja
Copy link
Collaborator

weiglszonja commented Jun 11, 2024

Yeah I would squeeze the last dimension if this is a single trace. The extractor is from spikeinterface, the interface would be from NeuroConv

Yes, sorry, I meant the interface is ad hoc while the extractor is the CedRecordingExtractor from spikeinterface. So, should I also implement an ad hoc extractor?

@weiglszonja
Copy link
Collaborator

Yeah I would squeeze the last dimension if this is a single trace. The extractor is from spikeinterface, the interface would be from NeuroConv

Yes, sorry, I meant the interface is ad hoc while the extractor is the CedRecordingExtractor from spikeinterface. So, should I also implement an ad hoc extractor?

No, you can just edit this line here:

@alessandratrapani
Copy link
Collaborator Author

No, you can just edit this line here:

Ah yes, thanks! I will do it here #23 since this affect both conversions

@weiglszonja
Copy link
Collaborator

okok, good to go then

@alessandratrapani alessandratrapani merged commit 6fbc653 into main Jun 11, 2024
@alessandratrapani alessandratrapani deleted the add_dual_imaging_interface branch August 15, 2024 13:52
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.

2 participants