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

Nomenclature: 'feeds', 'drives' and 'biases' #222

Closed
cjayb opened this issue Dec 1, 2020 · 6 comments · Fixed by #221
Closed

Nomenclature: 'feeds', 'drives' and 'biases' #222

cjayb opened this issue Dec 1, 2020 · 6 comments · Fixed by #221
Labels
docs Extra attention is needed

Comments

@cjayb
Copy link
Collaborator

cjayb commented Dec 1, 2020

Driver

  • Standard neuroscience parlance refers to things like feedforward and feedback drive that is valid for both single cells and groups of them.
  • Neymotin et al. (2020) refers to “Exogenous driving inputs” (pp. 29–31)
    • “Evoked” driver: “trains of synaptic inputs to the local network during a sensory stimulus”
    • “Rhythmic” driver: “typically bursts of action potentials that drive the local network rhythmically”
  • Proximal (a.k.a. “granular”, i.e., via L4) or distal (See Fig 7A)
    • Both have strong semantic connotations in HNN: not a general-purpose simulation tool, but rather one that incorporates (imposes) physiological constraints
    • Related to target dispersion of FF vs. FB (or associative thalamic) pathways (drives)

Bias ?

Neymotin et al. (2020)

  • “Tonic inputs are modeled as somatic current clamps with a fixed current amplitude (nA)”
    • for each modeled neuron type separately
  • “Noisy Inputs are trains of action potentials that follow a Poisson Process and create excitatory AMPA or NMDA synaptic inputs to the somata of all neurons of a given type.”

Feed ?

  • was this used as an umbrella for both the above?
@cjayb cjayb changed the title Nomenclature: Nomenclature: 'feeds', 'drives' and 'biases' Dec 1, 2020
@jasmainak jasmainak added the docs Extra attention is needed label Dec 1, 2020
@cjayb
Copy link
Collaborator Author

cjayb commented Dec 1, 2020

Moved this discussion here from #221
Ping @jasmainak @rythorpe @ntolley others?

@cjayb
Copy link
Collaborator Author

cjayb commented Dec 1, 2020

As far as I can tell, the reference paper does not mention feeds, so I don't think the API should either; wdyt? Note also how tonic and poisson inputs are grouped as 'biases', as opposed to evoked or rhythmic 'drivers'. I feel this is a bigger decision than the 'docs'-label, @jasmainak : should #221 implement 'drives' or 'feeds'?

@rythorpe
Copy link
Contributor

rythorpe commented Dec 1, 2020

As far as I can tell, the reference paper does not mention feeds, so I don't think the API should either; wdyt? Note also how tonic and poisson inputs are grouped as 'biases', as opposed to evoked or rhythmic 'drivers'. I feel this is a bigger decision than the 'docs'-label, @jasmainak : should #221 implement 'drives' or 'feeds'?

I think we should maintain the vocabulary used in Neymotin et al. and separate the API accordingly. "Drive" can be used to connote an evoked or rhythmic input that emerges via a feed-forward or feedback pathway. "Bias" can be used to connote some kind of baseline feed that emerges from within the network (e.g., poisson or tonic input) that is designed to bring the network to some kind of steady-state mode (even if it does so only transiently).

@cjayb
Copy link
Collaborator Author

cjayb commented Dec 2, 2020

I also think being consistent with the paper, as well as other papers in the field, makes sense---'feeds' don't have a biological connotation.

I personally like the word 'drive', but another one used in the paper is (exogenous) 'input'. So we'd have

  1. evoked input/drive
  2. rhythmic input/drive
  3. noisy input/drive (e.g. Poisson)
  4. tonic input/bias (current clamp)
    where the last one has a very different implementation compared with the others.

A 'drive' makes sense physiologically for 1-3. 4 is more of a 'bias', though one that's implemented as an 'input' directly to the cell soma (never synapses).

I'll try some ideas out in #221

@jasmainak
Copy link
Collaborator

That's fine calling it a "drive". I'm wondering if #221 is the right PR for that though. Because if you try to make it consistent and call it drive everywhere, you end up with a large diff. Let's try to focus on getting it to work in #221. In a follow up PR, we can rename it to "drive" everywhere.

For 3. and 4., do you imagine a separate function or the same function as for 1. and 2.? One complication is that evoked inputs can also be cell-specific, right?

@cjayb
Copy link
Collaborator Author

cjayb commented Dec 2, 2020

Whoops, didn't see this until after my latest push... It's a large diff, yes, but it's kinda integral to the whole cleanup process so I included it. Need to merge this PR before I can get CI results though... Tests are passing locally of course.

For 3. and 4., do you imagine a separate function or the same function as for 1. and 2.? One complication is that evoked inputs can also be cell-specific, right?

In the latest push, 1-3 are all 'drives', and 4 is a 'bias'. It actually cleaned up Network quite nicely, see what you think.
And yes: 1-3 can all be 'cell-specific' or 'common', as far as I can tell. In the 'classic' implementation, 1, 3 and 4 are cell-specific, 2 are 'common'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants