Burst merge curation

[CBroz1]

TODO:

• Test V0 draft: here
• Test V1 draft
• Feedback on fix of combination bug, and indexing issues (1, 2)
• First pass review to ensure scientifically aligned with previous work
• Fix failing tests related to MetricCuration
• Reduce redundancy across V0/V1 burst merge
• Change schema names to add database instances
• Add notebook demos for both V0/V1
• Add pytests of this new work

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[CBroz1]

Chatted with Kyu: he's in favor of not overwriting

[MichaelCoulter]

thanks for making these burst merging tables!
i tried the notebook and it worked for me. i also tried one of my entries in curationV1 and it also worked!
there is a calculation i would like to use, but i couldn't find it: i would like a count of the number of spikes from each unit that are shown in the cross correlogram plot. is there a way to get that? thanks.

[edeno]

@MichaelCoulter do you know if the burst merge calculation is working as expected?

[CBroz1]

Note to self - looks like these restrictions should switch

[MichaelCoulter]

i haven't checked the calculations against the old code that i used before. i can work on that.
would it be possible to merge in this code to the main repo first? its hard for me to continue my other work and test this because i need to switch back and forth between the different repositories.

[CBroz1]

merge in this code to the main repo first

I understand the inconvenience, but I'd like to avoid merging anything that doesn't have the scientific stamp of approval. Arguably, instructing folks to pull from the master branch implies that anything there is ready for use. The counterarg would be that that implication should be reserved for published releases, but I still don't love putting something temporary like a username-prefix in the main branch

I'll reach out over DM to you, Mike, to see if I can help alleviate the inconvenience of switching