Package Creation and MindRun import
License Required
A specific license is required to manage MindRun packages from MindDev.
MindRun is a companion application to MindDev that allows you to run its protocols in a simpler, faster way, with automatic visualization of results once the test is complete. To use MindRun, you need to implement protocols as MindRun packs, which must first be created in MindDev.
Let's go through how to create your own MindRun pack!
Creating a pack requires that you have already created a protocol with the MindDev Research tool and executed it at least once to generate a result file. This file is required for automatic result visualization in MindRun.
Preparing the Reference Protocol
- Launch MindDev and select the protocol you want to import into MindRun. In this guide, we use the Continuous Performance Test (CPT), a simple 2D test, as an example. The steps, however, are valid for any protocol.
- Execute the selected protocol using either “Test Protocol” or “Run Protocol”.
- “Test Protocol” generates a result file automatically saved by MindDev, which you will use to create analysis points (a required step before importing a protocol into MindRun).
- “Run Protocol” can also be used but is intended for actual experiment sessions, as it requires selecting a participant from your subject database. You can, however, create a dummy subject reserved for generating all your MindRun packs.
Modifying a Protocol Used in a Pack
Once this step is complete, do not modify the protocol in MindDev. Doing so may cause errors in future result analyses. The result file used for pack creation must exactly match the executed protocol.
If you notice an error in your protocol at this point, fix it, save it, and rerun it (“Test Protocol” or “Run Protocol”) to generate a new matching result file.
Test Protocol
If you used “Test Protocol”, open the generated result file by clicking “Load Last Test Result” in the top toolbar. This file is always named outputtest.xml. Rename it immediately and save it in MindDev’s “Results” folder.
outputtest.xml File
Remember: this is a temporary file. Each time you use “Test Protocol”, a new outputtest.xml is generated and overwrites the previous one. Only the latest version is kept in memory.
If you used “Run Protocol”, your result file is already saved in the “Results” folder with a unique name. Open this file in MindDev.
Adding Analysis Filters
- Add analysis filters to your result file to extract the relevant test data. Your result file must display a pink “R” indicator showing that data has been collected. This indicator appears on parent nodes and on each trial, helping you locate recorded events.
Opening a trial shows the type of recorded event. In this example, it is a “Reaction Time Recorder,” but it could be any other event depending on what you included in your trial entities when creating the protocol.
A “Data Record” node is thus added to the result file, containing the recorded data.
 |
|
Add analysis filters to the “data records” at the trial level. Right-click and add a new node. All available filters will be shown: choose either generic filters or those designed for the specific test. Here we add filters designed for CPT.
Repeat this step as needed to add multiple filters.
In this example, three filters are added to evaluate overall performance:
- CPT Total Error Filter – shows the total number of errors (both omissions and unexpected reactions).
- CPT Good Reaction Time – shows the average reaction time for correct responses.
- CPT Good Reaction – counts the number of correct responses.
Other filters could be added (e.g., to distinguish between omission and commission errors).
Where to Place Filters
Filters don’t need to be placed on every trial. Adding them to the first trial applies them to all trials automatically.
Previewing Filter Results
You can already preview the result for the trial where the filter is placed. In this example, no error was recorded for trial 1 (Number: 0).
- Add Excel entry points to each filter. This step is crucial: it enables both Excel export and result visualization in MindRun.
- When selecting the Excel entry point, go to the “Properties” panel to rename it (“Object Properties” > “Name”) and assign a unique ID (“Base Excel Entry Point Properties” > “Excel Entry Point Id”). You can also rename the “Array Name.” This name will be shown in the per-trial graphical representation in MindRun. Choose carefully.
Array Name Recommendation
Use a short “Array Name” so that it doesn’t take too much space in the MindRun graph.
You can also add calculations by selecting the appropriate formulas for each entry point.
Adding a Full Extraction Filter
- Add a special filter from the “MindRun Filters” category called MindRun View Filter. This filter allows you to select and display all data from the protocol in MindRun by enabling a specific checkbox.
MindRun View Filter and Excel Entry Points
No Excel entry point is needed for this specific filter.
You can have multiple MindRun View Filters in a trial, which will generate multiple graphs.
Adding Scores
- MindRun displays results as graphs, including a spider chart summarizing overall performance. To display data in this chart, you need to create scores (at least three for the spider chart). Unlike Excel entry points (which display trial-by-trial data), scores generate a single result summarizing all trials.
Add scores by inserting a node at the “Experiment” level of your result protocol.
There are different types of scores: generic scores or scores based on the Excel entry points you created earlier.
- In this example, we use scores based on Excel entry points.
- Choose the type of score depending on your test. In this example, we use:
- “Excel Entry Point Based Sum Score” for error and success counts
- “Excel Entry Point Based Average” for mean reaction time.
- Each score must be linked to an Excel entry point by specifying its “Excel Entry Point Id” in the score properties.
Linking Scores to Excel Entry Points
The software can only link the score to recorded data via the Excel Entry Point Id. Make sure to type it exactly as it appears (including spaces and capitalization).
- Rename each score so you can easily match it with the corresponding Excel entry point. This name will be displayed in the MindRun spider chart.
Score Naming
Use short names to avoid cluttering the chart.
Once filters and scores are set, your result file becomes a Reference Protocol. We recommend saving a copy of the original result file (without filters) and then saving the new one with filters under a new name (for example, prefix with “PR” for “Protocol Reference”) in the “Results” folder.
Verify that everything is set up correctly before proceeding to the pack import phase.
Importing the Pack
To import a package into MindRun, some preparation is required. You can check the “Package Manager for MindRun” section for details on how to properly prepare protocols. Here, we only describe the import steps.
- In MindDev, open the “Lite Database Manager Tool.”
- The next page lets you create your MindRun package.
- Add a new reference protocol.
- Rename the default name “Reference” to your test name in the “Object Properties.” For example:
CPT_Experiment.
- Set the name of your test battery or category. For example:
Tutorials.
- Add the link to your protocol file (without filters) from the “Protocols” folder.
- Add the link to your reference protocol (with data + filters + scores) from the “Results” folder.
- Click the yellow key icon on the left panel to link the pack, protocol, and reference protocol.
- Verify that the links and full file paths are correctly assigned.
-
Save the package with “Save as Database” in the “RegisteredProtocols” folder:
C:\Users\USERNAME\Documents\MindDev\Lite\RegisteredProtocols -
You can name the package as you wish. In this example:
PRM_Tutorials_CPT_Experiment.
- Close the “Lite Protocol Reference Manager,” open MindRun, and check that the pack is available in the “My Protocols” section.
Your protocol is now ready to use!
Editing the Pack
Editing a MindRun Pack
For minor corrections (pack name, test name, etc.), open the pack in MindDev Research and edit it.
- Select the pack file with the “Load Database” button in the left panel.
Make the necessary changes, save, close the “Lite Protocol Reference Manager,” and restart MindRun to apply the updates.