Fluctuation-driven regime in spinal motor networks

Fluctuation-driven regime in spinal motor networks

When spinal circuits generate rhythmic movements it is important that the neuronal activity remains within stable bounds to avoid saturation and to preserve responsiveness. Here, we simultaneously record from hundreds of neurons in lumbar spinal circuits of turtles and establish the neuronal fraction that operates within either a ‘mean-driven’ or a ‘fluctuation–driven’ regime. Fluctuation-driven neurons have a ‘supralinear’ input-output curve, which enhances sensitivity, whereas the mean-driven regime reduces sensitivity. We find a rich diversity of firing rates across the neuronal population as reflected in a lognormal distribution and demonstrate that half of the neurons spend at least 50 % of the time in the ‘fluctuation–driven’ regime regardless of behavior. Because of the disparity in input–output properties for these two regimes, this fraction may reflect a fine trade–off between stability and sensitivity in order to maintain flexibility across behaviors.

None
None
None

None
       
Help
Projects

Projects serve as an overall way to group subjects, datasets, and collections together. A project can be used to relate experiments for publications, as well as to describe day-to-day experiments or sharing experimental data with collaborators. Projects define the overall permissions level of most other content. See section below on Permissions for further details.

Two-Part Form

The project submission form consists of two parts. In the first part, you fill in the required fields. Once you click "Create and continue," the project entry is created, and you can continue editing it on the second part of the form, which contains all the fields.

Project fields:

  • Name: The project name must be unique across BrainSTEM (required).
  • Authenticated groups: Please assign one or more groups to the project. Assigned groups will have change permissions to the project. You can continue to assign permissions on the "Manage permissions" page of the created project (required).
  • Description: A rich text description of the project.
  • Publications: List of related publication IDs formatted as strings.
  • Extra Fields: Allows you to add additional fields to the project. The values can be strings or numeric values.
  • Public Project: Determines if the project is publicly available or accessible only through the private portal.
  • Name Used in Repository: Use this field if you have another name for your project (maximum length: 200 characters).
  • Tags: Tags for the project. Tags are useful for organizational purposes, allowing you to quickly label a project and use them as filters.

Permissions

Projects define the overall permissions level for subjects, datasets, collections, and module data. You manage permissions through the management tab, where you can assign individual users and groups access levels to a project. Projects have four permission levels: membership (read access), change permissions, managers, and owners. For more information on permissions, please visit the permissions page.

Project API Access

The API allows for programmable access to projects, enabling you to read, edit, and delete projects through the API. For details about the project's fields and data structure, refer to the API Documentation on the Project API endpoint.