This README.txt file was generated on <20211108> by <Elliot Collins>



#

# General instructions for completing README: 

# For sections that are non-applicable, mark as N/A (do not delete any sections). 

# Please leave all commented sections in README (do not delete any text). 

#



-------------------

GENERAL INFORMATION

-------------------



1. Title of Dataset: ORF_rawData.zip



2. Author Information



First Author Contact Information

    Name: Elliot Collins

    Institution: Carnegie Mellon University

    Email:collinse@uw.edu



Corresponding Author Contact Information

    Name: Marlene Behrmann	

    Institution: Carnegie Mellon University

    Email: behrmann@cmu.edu





---------------------

DATA & FILE OVERVIEW

---------------------



#

# Directory of Files in Dataset: List and define the different 

# files included in the dataset. This serves as its table of 

# contents. 

#



Directory of Files:

   A. Filename:  3##/   (308-311 directories)    

      Short description: There are 13 identical directories. Each contains the raw data output for 1 subject in the experiment. For each subject, there are 26 text files from the experiment. There are 6 "ratings" sessions titled ORFratings_3##_s#.txt and 20 training sessions titled ORFtraining_3##_session.txt. For each text file, one line is one trial, with the parameters of the trials listed in the appropriate column. Both types of files are outputs from scripts in the Learning Experiment Plan zip file also available on Figshare. 





Citations: If you use this data or software for any reason please cite: Collins, E, & Behrmann, M (2020) Exemplar learning reveals the representational origins of expert category perception. Proceeding of the National Academy of Sciences. 117(20), 11167-11177.






#

# File Naming Convention: Define your File Naming Convention 

# (FNC), the framework used for naming your files systematically 

# to describe what they contain, which could be combined with the

# Directory of Files. 

#



File Naming Convention: see as above





#

# Data Description: A data description, dictionary, or codebook

# defines the variables and abbreviations used in a dataset. This

# information can be included in the README file, in a separate 

# file, or as part of the data file. If it is in a separate file

# or in the data file, explain where this information is located

# and ensure that it is accessible without specialized software.

# (We recommend using plain text files or tabular plain text CSV

# files exported from spreadsheet software.) 

#



-----------------------------------------

DATA DESCRIPTION FOR: Training Sessions 'ORFtraining_3##_session#.txt'

-----------------------------------------



1. Number of variables:11





2. Number of cases/rows: 240





4. Variable List: (per trial)
	SubI (subject ID)
	imageTarget (image subject is looking for)
	TragExp (happy or neutral expression of target face)
	disNO1 (face identity 1)
	disNO2 (face identity 2)
	disNO3 (face identity 3)
	disNO4 (face identity 4)
	session trial (numeric trial: 0-239)
	accuracy (1=correct, 0=incorrect)
	RT (reaction time in seconds)


-----------------------------------------

DATA DESCRIPTION FOR: Ratings Sessions 'ORFratings_3##_s#.txt'

-----------------------------------------



1. Number of variables:9





2. Number of cases/rows: 925





4. Variable List: (per trial)
	SubI (subject ID)
	imageCondition (practice, experiment)
	trial (trial number)
	NO_1 (image used in first sample)
	NO_2 (image used in second sample)
	position1 (X position used for first image along horizontal in degrees of visual angle)
	position2 (X position used for second image along horizontal in degrees of visual angle)
	response (similarly score 1-7)
	RT (reaction time)





--------------------------

METHODOLOGICAL INFORMATION

--------------------------



#

# Software: If specialized software(s) generated your data or

# are necessary to interpret it, please provide for each (if

# applicable): software name, version, system requirements,

# and developer. 

#If you developed the software, please provide (if applicable): 

#A copy of the software’s binary executable compatible with the system requirements described above. 

#A source snapshot or distribution if the source code is not stored in a publicly available online repository.

#All software source components, including pointers to source(s) for third-party components (if any)



1. Software-specific information: N/A



Additional Notes(such as, will this software not run on 

certain operating systems?): N/A



#

# Equipment: If specialized equipment generated your data,

# please provide for each (if applicable): equipment name,

# manufacturer, model, and calibration information. Be sure

# to include specialized file format information in the data

# dictionary.

#



2. Equipment-specific information: N/A

<create a new entry for each qualifying piece of equipment>



Manufacturer:

Model:



(if applicable)

Embedded Software / Firmware Name:

Embedded Software / Firmware Version:

Additional Notes:



#

# Dates of Data Collection: List the dates and/or times of

# data collection.

#



3. Date of data collection: 2018-2019