NDA Help Center

Login Dialog

Frequently Asked Questions


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



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.


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
Value Range
Data Structures with shared data
No filters have been selected
Switch User

Judgment of Line Orientation - Form H



Judgment of Line Orientation - Form H as defined by Dr. Bradley Peterson's group at Columbia University. This is a standardized measure of visuospatial judgment.

Download Definition as
Download Submission Template as
Element NameData TypeSizeRequiredDescriptionValue RangeNotesAliases
subjectkeyGUIDRequiredThe NDAR Global Unique Identifier (GUID) for research subjectNDAR*
chrono_ageIntegerRequiredInterview Chronological Age0 :: 1200
R = Right; L = Left; B = Both
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.
jol_formh_test_practice_1IntegerRecommendedpractice test 11 :: 11
jol_formh_test_pract_1_correctString5Recommendedwas practice test 1 correct?
jol_formh_test_practice_2IntegerRecommendedpractice test 21 :: 11
jol_formh_test_pract_2_correctString5Recommendedwas practice test 2 correct?
jol_formh_test_practice_3IntegerRecommendedpractice test 31 :: 11
jol_formh_test_pract_3_correctString5Recommendedwas practice test 3 correct?
jol_formh_test_practice_4IntegerRecommendedpractice test 41 :: 11
jol_formh_test_pract_4_correctString5Recommendedwas practice test 4 correct?
jol_formh_test_practice_5IntegerRecommendedpractice test 51 :: 11
jol_formh_test_pract_5_correctString5Recommendedwas practice test 5 correct?
jol_formh_test_1IntegerRecommendedtest 11 :: 11
jol_formh_test_1_correctString5Recommendedwas test 1 correct?
jol_formh_test_2IntegerRecommendedtest 21 :: 11
jol_formh_test_2_correctString5Recommendedwas test 2 correct?
jol_formh_test_3IntegerRecommendedtest 31 :: 11
jol_formh_test_3_correctString5Recommendedwas test 3 correct?
jol_formh_test_4IntegerRecommendedtest 41 :: 11
jol_formh_test_4_correctString5Recommendedwas test 4 correct?
jol_formh_test_5IntegerRecommendedtest 51 :: 11
jol_formh_test_5_correctString5Recommendedwas test 5 correct?
jol_formh_test_6IntegerRecommendedtest 61 :: 11
jol_formh_test_6_correctString5Recommendedwas test 6 correct?
jol_formh_test_7IntegerRecommendedtest 71 :: 11
jol_formh_test_7_correctString5Recommendedwas test 7 correct?
jol_formh_test_8IntegerRecommendedtest 81 :: 11
jol_formh_test_8_correctString5Recommendedwas test 8 correct?
jol_formh_test_9IntegerRecommendedtest 91 :: 11
jol_formh_test_9_correctString5Recommendedwas test 9 correct?
jol_formh_test_10IntegerRecommendedtest 101 :: 11
jol_formh_test_10_correctString5Recommendedwas test 10 correct?
jol_formh_test_11IntegerRecommendedtest 111 :: 11
jol_formh_test_11_correctString5Recommendedwas test 11 correct?
jol_formh_test_12IntegerRecommendedtest 291 :: 11
jol_formh_test_12_correctString5Recommendedwas test 29 correct?
jol_formh_test_13IntegerRecommendedtest 131 :: 11
jol_formh_test_13_correctString5Recommendedwas test 13 correct?
jol_formh_test_14IntegerRecommendedtest 141 :: 11
jol_formh_test_14_correctString5Recommendedwas test 14 correct?
jol_formh_test_15IntegerRecommendedtest 151 :: 11
jol_formh_test_15_correctString5Recommendedwas test 15 correct?
jol_formh_test_16IntegerRecommendedtest 161 :: 11
jol_formh_test_16_correctString5Recommendedwas test 16 correct?
jol_formh_test_17IntegerRecommendedtest 171 :: 11
jol_formh_test_17_correctString5Recommendedwas test 17 correct?
jol_formh_test_18IntegerRecommendedtest 181 :: 11
jol_formh_test_18_correctString5Recommendedwas test 18 correct?
jol_formh_test_19IntegerRecommendedtest 191 :: 11
jol_formh_test_19_correctString5Recommendedwas test 19 correct?
jol_formh_test_20IntegerRecommendedtest 201 :: 11
jol_formh_test_20_correctString5Recommendedwas test 20 correct?
jol_formh_test_21IntegerRecommendedtest 211 :: 11
jol_formh_test_21_correctString5Recommendedwas test 21 correct?
jol_formh_test_22IntegerRecommendedtest 221 :: 11JoL_FormH_Test_22a
jol_formh_test_22_correctString5Recommendedwas test 22 correct?
jol_formh_test_23IntegerRecommendedtest 231 :: 11
jol_formh_test_23_correctString5Recommendedwas test 23 correct?
jol_formh_test_24IntegerRecommendedtest 241 :: 11
jol_formh_test_24_correctString5Recommendedwas test 24 correct?
jol_formh_test_25IntegerRecommendedtest 251 :: 11
jol_formh_test_25_correctString5Recommendedwas test 25 correct?
jol_formh_test_26IntegerRecommendedtest 261 :: 11
jol_formh_test_26_correctString5Recommendedwas test 26 correct?
jol_formh_test_27IntegerRecommendedtest 271 :: 11
jol_formh_test_27_correctString5Recommendedwas test 27 correct?
jol_formh_test_28IntegerRecommendedtest 281 :: 11
jol_formh_test_28_correctString5Recommendedwas test 28 correct?
jol_formh_test_29_IntegerRequiredtest 291 :: 11JoL_FormH_Test_29
jol_formh_test_29_correctString5Recommendedwas test 29 correct?
jol_formh_test_30IntegerRecommendedtest 301 :: 11
jol_formh_test_30_correctString5Recommendedwas test 30 correct?
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
comments_miscString4,000RecommendedMiscellaneous comments on study, interview, methodology relevant to this form data
sexString20RequiredSex of the subjectM;FM = Male; F = Femalegender
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: jlot_form_h01 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.