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

Record GLIF model after spike current PointNet #365

Open
Jballbe opened this issue May 1, 2024 · 2 comments
Open

Record GLIF model after spike current PointNet #365

Jballbe opened this issue May 1, 2024 · 2 comments

Comments

@Jballbe
Copy link

Jballbe commented May 1, 2024

Hi,

I am currently using a GLIF3 model glif_psc – Current-based generalized leaky integrate-and-fire (GLIF) models (from the Allen Institute), and I was wondering if there was a way to record the after spike currents during the simulation?

Thank you for any help you can give me!
Best,

Julien Ballbé

@kaeldai
Copy link
Collaborator

kaeldai commented May 8, 2024

Hi @Jballbe

I was able to look into it and it looks like for the glif_psc models there is a variable called "ASCurrents_sum" that can be recorded at each step in the simulation. It looks like it is just the sum of both "asc_amps" in pA. (The individual "asc_amps" are stored in a vector of size 2 and I don't think NEST allows multimeter recordings of vectors).

To record the "ASCurrents_sum" variable in BMTK you can add a "multimeter_report" to the reports section of the config.simualation.json file. For instance to record in the point_450glifs example I'd add the following to record from the Scnn1a cells:

"reports": {
    "ascurrents_recordings": {
      "module": "multimeter_report"
      "variable_name": "ASCurrents_sum",
      "cells": {
        "population": "v1",
        "model_template": "nest:glif_psc",
        "model_name": "Scnn1a"
      },
    }
  },

You can modify the cell attributes filter to record for a different population (or even all glif_psc cells). After the simulation runs it will create a file output/ascurrents_recordings.h5 with a Timestamps x Cells "data" table.

Just a Warning: The multi-meter recordings files can get really big and also slow down the simulation significantly. Especially if you're not running on an HPC it may be good to either filter the cells, or to reduce the tstop or dt parameters in the config before you know how big these files can get!

@Jballbe
Copy link
Author

Jballbe commented May 17, 2024

Hi @kaeldai ,

Thank you very much for your response, that's very helpful. And thank you for the warning

Best,
Julien

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

2 participants