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

release 0.2 #365

Closed
15 tasks done
jasmainak opened this issue Jun 17, 2021 · 6 comments
Closed
15 tasks done

release 0.2 #365

jasmainak opened this issue Jun 17, 2021 · 6 comments

Comments

@jasmainak
Copy link
Collaborator

jasmainak commented Jun 17, 2021

hi guys,

I think it's time for another release. 3 month cycles are usually recommended but 6 months is also fine. I'd like to get it out before getting busy with next grant cycle. I'm thinking that these are the goals for this release:

Priorities

Connectivity API

  • Add .drop(probability, src_gids, target_gids) .plot
  • Function to search for specific connections in net.connectivity list: conns = pick_connecitivity(conns, src=‘L2_pyramidal')
  • Viz function that plots connections weights with color bar as plot_connectivity(net, conn)
  • Merge the functions used for drives and cell-cell connections. This is partially done as everything is funneled through net.add_connection, but the next step is allowing the drives to target specific gids in a similar API [MRG+1] unify cell connectivity and drive connectivity #369
    - Make _Connectivity a proper class with public and private attributes
  • Pass probability argument to drives allowing for inputs to subsets of cells [MRG] Add probability arguments to drives API #416

Bump to 0.3

anything else? It's going to be a bombshell of a release!

@cjayb
Copy link
Collaborator

cjayb commented Jun 17, 2021

Made some edits/proposals. Perhaps need to prioritise... ;)

@ntolley
Copy link
Contributor

ntolley commented Jun 17, 2021

I'd be interested in taking up the calcium dynamics. I am already laying the groundwork with #348 which is nearing completion (just need to take an afternoon and play with the simulations).

I have also made a lot of progress on what is likely the most difficult task remaining for the connectivity API #367.

The remaining stuff for more verbose warnings when adding connections might be a good exercise for @kenloi as a more intermediate level PR. This would involve creating a list of what is considered "valid connections" (example, pyramidal cells shouldn't make GABA synapses), and referencing that list from net.add_connection.

@jasmainak
Copy link
Collaborator Author

@rythorpe any issues that are close to your heart and/or you'd want to tackle? we're thinking of an august release

@ntolley
Copy link
Contributor

ntolley commented Jun 23, 2021

Something that's been on my mind for awhile, do you guys thinks it'd be possible to add a sentence or two to the main hnn-core page? At the moment it is extremely cryptic and requires you to go the HNN-GUI repo to figure out that this is a simulator for a neocortical column.

Perhaps

This is a leaner and cleaner version of the code based off the HNN repository, a user friendly tool for the biophysical simulation of a neocortical column. However, a Graphical User Interface is not supported at the moment in this repository.

I can open a PR if you guys agree. Perhaps later it'd also be great to have a picture of the model there as well to make it immediately clear what this repo is for.

@jasmainak
Copy link
Collaborator Author

yes, that's fine! PR is welcome :)

@jasmainak jasmainak pinned this issue Jul 14, 2021
@jasmainak
Copy link
Collaborator Author

okay, I checked some boxes and reordered the issues so it's clearer to what's done and what's left. Expanded the connectivity checklist so it's clear to see what needs to be done there. This issue has also been pinned so it's on top of the priority list.

@jasmainak jasmainak unpinned this issue Jan 3, 2023
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

No branches or pull requests

3 participants