This article applies to:
E-Prime 3.0
E-Prime 2.0
E-Prime 1.x
Detail
The following table contains the file formats used by E-Prime, an image of the file type, and a brief description of the file:
| E-Prime Version | Extension | Icon | Type | Description |
| 3.0 | .es3 |  |
E-Studio File | The .es3 file holds the E-Studio experiment design data for E-Prime 3.0 experiment files. |
| 3.0 | .ebs3 |  |
E-Basic Script File | The .ebs3 file is used to run an E-Prime 3.0 experiment. Double clicking it automatically runs the experiment file. Opening E-Run and loading in the .ebs3 file allows users to see details (e.g., Experiment Author) about the experiment. To protect the Intellectual Property of Industrial Partners and Institutions amongst other reasons, E-Run 3.0 does not provide a mechanism to directly edit the contents of the script generated by E-Studio. E-Prime 3.0 offers StartupInfo options to load data that can override the values of the generated file from E-Studio. This permits for changing subject number, device settings, etc. without the need of modifying the original .es3 file. |
| 3.0 | .edat3 |  |
E-DataAid File | The .edat3 files are used to store experiment data that can be analyzed in E-DataAid. |
| 3.0 | .emrg3 |  |
E-Merge File | The .emrg3 files are comprised of merged data from multiple .edat3 files. These files can be opened and analyzed in E-DataAid just like .edat3 files. |
| 3.0 | .epk3 |  |
E-Prime PackageFile | The .epk3 file format is used in E-Studio to merge PackageFile script and routines into an experiment via PackageCall objects. The .epk3 file format is viewed and edited in the PackageFile Editor. These user created .epk3 files can be accessed only in E-Studio. Certified PackageFiles with the .epk3 extension (primarily from Industrial Partners) are authored in a special version of the PackageFile Editor. These files can be accessed in E-Prime 3.0 at the discretion of the Certified PackageFile author. At generation time, the script and routine contents are merged into an .ebs3 file. |
| 3.0 | .startupinfo3 |  |
Startup Info File | A .StartupInfo3 file is used for loading name/value pairs into the Context object for use during an experiment. It can be edited in the Experiment Object's Startup Info tab, an InLine object, the StartupInfo Editor, or any other external XML editor. The StartupInfo Editor features standard interface characteristics including menus and toolbars. A Global.startupInfo file is used to load parameters that apply to all experiments running on a particular machine. It should be located in the My Experiments > 3.0 folder. For example, it could set the same Display device resolution for all experiments. Local StartupInfo files load name/value pairs into only the experiment that they are associated with and must be saved in the same folder as the .es3 or .ebs3 files that use them. For example, it could be used to increment the Subject number used for a particular experiment each time it is run. |
| 3.0 | .cd3 |  |
Column Definition File | A .cd3 file contains column defintions that are used in E-DataAid analysis. E-DataAid provides methods of limiting the display of columns to those desired (i.e., through arranging, hiding/unhiding columns). Once the desired layout is achieved, E-DataAid provides a mechanism on the main interface toolbar to save a “Column Definition” that may be reapplied when loading the data file at a later time. The Column Definition feature serves as a quick method to return to the desired display/arrangement of attributes within an experiment file. See E-DATAAID: Saving and Loading Column Arrangement (.cd3) [23602] for more information. |
| 2.0 | .es2 |  |
E-Studio File | The .es2 file format holds the E-Studio experiment design data for both E-Prime 2.0 Standard and Professional experiment files. For the differences between E-Prime 2.0 Standard and Professional, please refer to RELEASE INFO: Differences between E-Prime 2.0 Standard and E-Prime 2.0 Professional [18082] and RELEASE INFO: FAQ about E-Prime Editions [27746]. |
| 2.0 | .ebs2 |  |
E-Basic Script File | The .ebs2 file is used to run an E-Prime 2.0 experiment. Double clicking it automatically runs the experiment file. Opening E-Run and loading in the .ebs2 file allows users to see details (e.g., Experiment Author) about the experiment. To protect the Intellectual Property of Industrial Partners and Institutions amongst other reasons, E-Run 2.0 does not provide a mechanism to directly edit the contents of the script generated by E-Studio. E-Prime 2.0 Professional offers StartupInfo options to load data that can override the values of the generated file from E-Studio. This permits for changing subject number, device settings, etc. without the need of modifying the original .es2 file. |
| 2.0 | .edat2 |  |
E-DataAid File | The .edat2 files are used to store experiment data that can be analyzed in E-DataAid. |
| 2.0 | .emrg2 |  |
E-Merge File | The .emrg2 files are comprised of merged data from multiple .edat2 files. These files can be opened and analyzed in E-DataAid just like .edat2 files. |
| 2.0 | .epk2 |  |
E-Prime PackageFile | The .epk2 file format is used in E-Studio to merge PackageFile script and routines into an experiment via PackageCall objects. The .epk2 file format is viewed and edited in the PackageFile Editor. These user created .epk2 files can be accessed only in E-Studio for E-Prime 2.0 Professional. Certified PackageFiles with the .epk2 extension (primarily from Industrial Partners) are authored in a special version of the PackageFile Editor. These files can be accessed in E-Prime 2.0 and/or E-Prime 2.0 Professional at the discretion of the Certified PackageFile author. At generation time, the script and routine contents are merged into an .ebs2 file. NOTE: .epk2 files cannot be used in E-Prime 1.x. |
| 2.0 | .startupinfo |  |
Startup Info File | A .StartupInfo file is an XML-based document used for loading name/value pairs into the Context object for use during an experiment. It can be edited in the Experiment Object's Startup Info tab, an InLine object, the StartupInfo Editor, or any other external XML editor. The StartupInfo Editor features standard interface characteristics including menus and toolbars. The StartupInfo Editor is available in E-Prime 2.0 Professional only. A Global.startupInfo file is used to load parameters that are applied to all experiments running on a particular machine. It is located in the My Experiments folder. For example, it could set the same Display device resolution for all experiments. Local StartupInfo files load name/value pairs into only the experiment that they are associated with and must be saved in the same folder as the .es2 or .ebs2 files that use them. For example, it could be used to increment the Subject number used for a particular experiment each time it is run. |
| 1.0 | .es |  |
E-Studio File | The .es file holds the E-Studio experiment design data for E-Prime 1.x experiment files. A E-Prime 1.x .es file can be upgraded to E-Prime 3.0 or 2.0 by choosing "E-Prime 1.x Files" in the file type drop down when opening experiment files in E-Studio. Once a file has been upgraded to the .es3 or .es2 file format, it cannot be viewed in E-Prime 1.x. The E-Prime 1.x .es file is not altered during the conversion process. |
| 1.0 | .ebs |  |
E-Basic Script File | The .ebs file is used to run an E-Prime 1.x experiment. |
| 1.0 | .edat |  |
E-DataAid File | The .edat files are used to store experiment data that can be analyzed in E-DataAid. Files of any extension that contain UNICODE characters will appear as | characters in E-Prime 1.x. |
| 1.0 | .emrg |  |
E-Merge File | The .emrg files are comprised of merged data from multiple .edat2 files. These files can be opened and analyzed in E-DataAid just like .edat files. Files of any extension that contain UNICODE characters will appear as | characters in E-Prime 1.x. |
| 3.0, 2.0, 1.0 | .anl |  |
Analysis File | E-Prime Analysis files (.anl) can be generated to aid in data analysis. They are used within E-DataAid and can be loaded in an analysis to show predetermined Columns, Rows, and Data. See DATA ANALYSIS: Data Analysis [22839] for more information. |
| 3.0, 2.0, 1.0 | .txt |  |
Text File | A plain text file (.txt) is generated to hold ontodata during the experiments. After the experiment is completed, an .edat, .edat2, or .edat3 is generated from the .txt file. In the event an E-DataAid file is not produced at the end of a study (e.g., Ctrl+Alt+Shift, etc.), E-Recovery may be used to generate the data file with help from the .txt file. |
| 3.0, 2.0, 1.0 | .wndpos | |
Windows Position File | A .wndpos file stores the state (e.g., open windows & positions) of an E-Studio session. When an new session is opened with an existing experiment file, it will open to the same state as the experiment was left in. |
| 3.0, 2.0, 1.0 | .xml | NOTE: The image of a .xml file is specific with the default applicaton for opening .xml files (e.g., Internet Explorer). | XML File | An .xml file is a generic file formats used by E-Prime to generate various reports. |
End User Legacy Comments:
| David McFarlane 2/22/2012 2:31:00 PM |
Can EP2 use .epk files from EP1? Is there a way to convert EP1 .epk files for use with EP2, or do we just lose that work? |
| Brandon Cernicky 9/10/2012 8:18:00 PM |
epk from 1.x do not convert to epk2. While you do not necessarily lose your work, it does require some manual copy and paste to get your routines into the GUI. |
Comments
2 comments
A good start. You left out .txt, .wndpos, .xsl, & .xml (and possibly .bin):
- txt: E-Prime generates a plain text file to hold data during the experiment, and upon successful completion generates the .edat* file from this. In the event of an aborted run, E-Recovery may be used to to generate an .edat* file with partial data from the .txt file.
- wndpos: This file stores the state (e.g., open windows & positions) of your E-Studio session. When you open an new session with an existing .es* file, it will open to the same state that you left it in.
- xsl, xml: These are not E-Prime-specific files, but generic formats used for various report files generated by E-Prime.
Note also that .es2, .ebs2, and .startupInfo files, under the hood, are just plain text xml files.
On a fussy grammatical note, "These files are comprised of ..." should read either "These files comprise ..." or "These files are composed of ..." (see Strunk & White's "The Elements of Style").
Please sign in to leave a comment.