Retrieve params after optimization #578
-
|
Hi, After optimization with hnn_core, how can I access the new, optimized, parameters? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
|
The best way would be to access the Now that you bring this up, we should probably add this to the optimization example.... |
Beta Was this translation helpful? Give feedback.
-
|
maybe @carolinafernandezp easy pull request for you if you want to try? It can count towards the 1 pull request requirement if you end up applying to GSoC |
Beta Was this translation helpful? Give feedback.
-
|
Ok I can definitely do that! |
Beta Was this translation helpful? Give feedback.
-
|
let us know if you need help. Here is the contributing guide: https://jonescompneurolab.github.io/hnn-core/dev/contributing.html I'm sure Andy can also help if you're stuck :) |
Beta Was this translation helpful? Give feedback.
-
|
@carolinafernandezp are you still planning to apply for GSoC? We just submitted our application as an organization. After that, it will be time for candidates to start applying. This is the right moment to make a pull request if you are still planning on applying! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
The best way would be to access the
net.external_drivesattribute, which contains the dynamic properties of each drive via e.g.net.external_drives['evprox1']['dynamics']. For synaptic weight parameters, you can inspect thenet.connectivityattribute, which is itself a list of all the connections within and onto the network. Sincenet.connectivityis itself a list of all the connections defined in the network, you can usepick_connectionto find the index associated with the drive of interest.Now that you bring this up, we should probably add this to the optimization example....