Help & Documentation

CRCNS Thalamus: th-1

Home › Stem › Projects › CRCNS Thalamus: th-1
CRCNS Thalamus: th-1

Extracellular recordings from multi-site silicon probes in the anterior thalamus and subicular formation of freely moving mice. [about] The data set contains recordings made from multiple anterior thalamic nuclei, mainly the antero-dorsal (AD) nucleus, and subicular areas, mainly the post-subiculum (PoS), in freely moving mice. Thalamic and subicular electrodes yielding high number of the so-called Head-Direction (HD) cells were likely to be located in the AD nucleus and the PoS, respectively. Electrode placement was confirmed by histology. The data was obtained during 42 recording sessions and includes responses of 720 neurons in the thalamus and 357 neurons in the PoS, in seven animals while they foraged for food in an open environment (53- x 46-cm).  Three animals were recorded simultaneously in the thalamus and the PoS (21 sessions). In the four other animals, electrodes were implanted in the anterior thalamus and in the pyramidal layer of the CA1 area of the hippocampus but only to record Local field Potentials (LFPs). The raw (broadband) data was recorded at 20KHz, simultaneously from 64 to 96 channels.  The raw data was processed to extract the LFPs and detect spikes. Included in the data set are the following items:

  • Times and waveforms of detected potential spikes.
  • Results of spike sorting.
  • LFPs.
  • The coordinate and direction of the mice head and video files from which the positions were extracted.
  • Metadata tables giving properties of the neurons and characteristics of the recording sessions.

More information is given in document: crcns_th-1_data_description.pdf and in the following publication which is based on this dataset: Internally organized mechanisms of the head direction sense. Peyrache A, Lacroix MM, Petersen PC, Buzsaki G, Nature Neuroscience. 2015

None
None
None

None
None
       
back
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.