NDA Help Center

Login Dialog

Frequently Asked Questions

Glossary

NDA Help Center

Filter Cart

The Filter Cart provides a powerful way to query and access data for which you may be interested.  

A few points related to the filter cart are important to understand with the NDA Query/Filter implementation: 

First, the filter cart is populated asyncronously.  So, when you run a query, it may take a moment to populate but this will happen in the background so you can define other queries during this time.  

When you are adding your first filter, all data associated with your query will be added to the filter cart (whether it be a collection, a concept, a study, a data structure/elment or subjects). Not all data structures or collections will necessarily be displayed.  For example, if you select the NDA imaging structure image03, and further restrict that query to scan_type fMRI, only fMRI images will appear and only the image03 structure will be shown.  To see other data structures, select "Find All Subject Data" which will query all data for those subjects. When a secord or third filter is applied, an AND condition is used.  A subject must exist in all filters.  If the subject does not appear in any one filter, that subjects data will not be included in your filter cart. If that happens, clear your filter cart, and start over.  

It is best to package more data than you need and access those data using other tools, independent of the NDA (e.g. miNDAR snapshot), to limit the data selected.  If you have any questions on data access, are interested in using avaialble web services, or need help accessing data, please contact us for assistance.  

Frequently Asked Questions

Glossary

Loading...

Login
Reset Password

NDA provides a single access to de-identified autism research data. For permission to download data, you will need an NDA account with approved access to NDA or a connected repository (AGRE, IAN, or the ATP). For NDA access, you need to be a research investigator sponsored by an NIH recognized institution with federal wide assurance. See Request Access for more information.

Warning Notice

This is a U.S. Government computer system, which may be accessed and used only for authorized Government business by authorized personnel. Unauthorized access or use of this computer system may subject violators to criminal, civil, and/or administrative action. All information on this computer system may be intercepted, recorded, read, copied, and disclosed by and to authorized personnel for official purposes, including criminal investigations. Such information includes sensitive data encrypted to comply with confidentiality and privacy requirements. Access or use of this computer system by any person, whether authorized or unauthorized, constitutes consent to these terms. There is no right of privacy in this system.

Update Password

You have logged in with a temporary password. Please update your password. Passwords must contain 8 or more characters and must contain at least 3 of the following types of characters:

  • Uppercase
  • Lowercase
  • Numbers
  • Special Characters limited to: %,_,!,@,#,$,-,%,&,+,=,),(,*,^,:,;

Subscribe to our mailing list

Mailing List(s)
Email Format

You are now leaving the NIMH Data Archive (NDA) web site to go to:

Click on the address above if the page does not change within 10 seconds.

Disclaimer

NDA is not responsible for the content of this external site and does not monitor other web sites for accuracy.

Accept Terms
Filter Cart
No filters selected
Description
Value Range
Notes
Data Structures with shared data
No filters have been selected
Switch User

ERP

erp

01

Guidelines for using human event-related potentials to study cognition: Recording standards and publication criteria. T.W. PICTON, S. BENTIN, P. BERG, E. DONCHIN, S.A. HILLYARD, R. JOHNSON, JR., G.A. MILLER, W. RITTER, D.S. RUCHKIN, M.D. RUGG, and M.J. TAYLOR

Download Definition as
Download Submission Template as
Files
PDF file iconpicton_tw_00_127.pdf
Element NameData TypeSizeRequiredDescriptionValue RangeNotesAliases
subjectkeyGUIDRequiredThe NDAR Global Unique Identifier (GUID) for research subjectNDAR*
src_subject_idString20RequiredSubject ID how it's defined in lab/project
interview_dateDateRequiredDate on which the interview/genetic test/sampling/imaging/biospecimen was completed. MM/DD/YYYYRequired field
interview_ageIntegerRequiredAge in months at the time of the interview/test/sampling/imaging.0 :: 1260Age is rounded to chronological month. If the research participant is 15-days-old at time of interview, the appropriate value would be 0 months. If the participant is 16-days-old, the value would be 1 month.
sexString20RequiredSex of the subjectM;FM = Male; F = Femalegender
taskString4,000RequiredCognitive process being studied
behavioral_responses_typeString100RequiredDescription of monitored behevioral responses
behavioral_responses_fileFileRequiredBehavioral responses file
physiological_responses_typeString100RequiredDescription of monitored physiological responses
physiological_responses_fileFileRequiredPhysiological responses file
exp_block_nubmerIntegerRequirednumber of experimental blocks
exp_block_1String100RequiredDescription of block 1 design
exp_block_time_1IntegerRequiredBlock 1 time
exp_block_2String100RequiredDescription of block 2 design
exp_block_time_2IntegerRequiredBlock 2 time
subj_sensory_abilityString100Requiredsubject's sensory ability
subj_motor_abilityString100Requiredsubject's motor ability
subj_sensory_responseString100Requiredsubject's sensory response
subj_motor_responseString100Requiredsubject's motor response
stimuli_typeString50Requiredtype of stimulii.e. visual, sound, etc.
subj_cognitive_abilityString100Requiredsubject's cognitiveability
subj_cognitive_responseString100Requiredsubject's cognitive response
medication_list_fileFileRequiredmedication list
cllinical_diagnosisString100Requiredclinical diagnosisAutism; PDD-NOS; Asperger's; ADHD; Language Disorder; Other; None
stimuli_detailString100Requiredstimuli description
stimuli_detail_fileFileRecommendedstimuli detail in file
stimuli_responseString100Requiredresponse to stimuli
stimuli_response_fileFileRequiredresponse to stimuli file
stimuli_timingString100Requiredstimuli timing
electrode_typeString100RequiredType of used electrodes
electrode_impedanceIntegerRequiredelectrode impedance in kOhm
electrode_locationString100RequiredDescription of electrode position coordinate information
electrode_location_fileFileRequiredFile containing electrode position coordinate information
electrode_fix_methodString100Requireddescription of how electrode are affixed to subject' head
artifact_cleaningString100Requiredthe way in which artifact-contaminated single channels are treated
referenceString100Requireddescription of reference recording
gain_resolutionIntegerRequiredgain or resolution of recording system
filterString100Requireddescription of filtering charachteristics
convertion_rateIntegerRequiredrate of A/D convertion
response_averageIntegerRequirednumber of responses for averaging
erp_time_lockString100Requiredthe way of ERP time locked to stimuli
compensation_procedString100Requiredlatency-compensation procedures
filter_algorithmString100Requiredfiltering algorithm
artifact_noncerebralString100Requirednoncerebral artifacts
artifact_rejectString100Requiredcriteria for rejecting artifact-contaminated trials
artifact_compensatString100Requiredartifact compencation procedure
erp_waveformsFileRequiredERP waveforms file
erp_temporalFileRequiredERP temporal
erp_spatialFileRequiredERP spatial
erp_voltageFileRequiredERP voltage
erp_time_calibrationFileRequiredtime calibration
erp_polarityFileRequiredERP polarity
electrode_waveform_locationFileRequiredelectrode location on waveforms
electrode_mapFileRequiredelectrode map
viewpoint_scalp_mapFileRequiredviewpoint for scalp-distribution map
vendorString100RecommendedVendor
equipmentString100Recommendedname of used equipment
Data Structure

This page displays the data structure defined for the measure identified in the title and structure short name. The table below displays a list of data elements in this structure (also called variables) and the following information:

  • Element Name: This is the standard element name
  • Data Type: Which type of data this element is, e.g. String, Float, File location.
  • Size: If applicable, the character limit of this element
  • Required: This column displays whether the element is Required for valid submissions, Recommended for valid submissions, Conditional on other elements, or Optional
  • Description: A basic description
  • Value Range: Which values can appear validly in this element (case sensitive for strings)
  • Notes: Expanded description or notes on coding of values
  • Aliases: A list of currently supported Aliases (alternate element names)
  • For valid elements with shared data, on the far left is a Filter button you can use to view a summary of shared data for that element and apply a query filter to your Cart based on selected value ranges

At the top of this page you can also:

  • Use the search bar to filter the elements displayed. This will not filter on the Size of Required columns
  • Download a copy of this definition in CSV format
  • Download a blank CSV submission template prepopulated with the correct structure header rows ready to fill with subject records and upload

Please email the The NDA Help Desk with any questions.

Distribution for DataStructure: erp01 and Element:
Chart Help

Filters enable researchers to view the data shared in NDA before applying for access or for selecting specific data for download or NDA Study assignment. For those with access to NDA shared data, you may select specific values to be included by selecting an individual bar chart item or by selecting a range of values (e.g. interview_age) using the "Add Range" button. Note that not all elements have appropriately distinct values like comments and subjectkey and are not available for filtering. Additionally, item level detail is not always provided by the research community as indicated by the number of null values given.

Filters for multiple data elements within a structure are supported. Selections across multiple data structures will be supported in a future version of NDA.