You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reading the different tutorials proposed here, notably Chapter 4 about PointNet. It is said in the "Building the recurrent (l4 --> l4) network" cell, that for the different type of connections you rely on ExctoExc.json, InhtoInh.json, ExctoInh.json and InhtoExc.json files for the dynamics params argument in add_edge call. These files each contain a dictionary specifying the receptor types (1,2,3 or 4), and this parameters refers to the synapse location in NEST (see section Receptor type).
My question is about the InhtoInh.json (receptor type: 4) and ExctoInh.json (receptor type:3) files which refer in NEST to proximal dendrite synapses location. Can you explain me why in PointNet (which uses point neuron models with no dimension right?) we use receptor type targeting proximal dendrites?
Thank you for your help!
Best,
Julien
The text was updated successfully, but these errors were encountered:
Hi,
I am reading the different tutorials proposed here, notably Chapter 4 about PointNet. It is said in the "Building the recurrent (l4 --> l4) network" cell, that for the different type of connections you rely on ExctoExc.json, InhtoInh.json, ExctoInh.json and InhtoExc.json files for the dynamics params argument in add_edge call. These files each contain a dictionary specifying the receptor types (1,2,3 or 4), and this parameters refers to the synapse location in NEST (see section Receptor type).
My question is about the InhtoInh.json (receptor type: 4) and ExctoInh.json (receptor type:3) files which refer in NEST to proximal dendrite synapses location. Can you explain me why in PointNet (which uses point neuron models with no dimension right?) we use receptor type targeting proximal dendrites?
Thank you for your help!
Best,
Julien
The text was updated successfully, but these errors were encountered: