Opening the book…
Resetting and Restarting
If you ask someone who works at an IT help desk, they’ll tell you that a huge proportion of computer problems can be solved by restarting the computer. Computers are insanely complicated, and there are millions of idiosyncratic problems that can accumulate as the computer carries out more and more operations. A simple restart returns everything to its default status. A restart is an especially good strategy if you start having "weird" problems (e.g., when things that worked fine a few minutes ago are no longer working).
However, restarting your computer can take some time, so when I run into a weird problem when analyzing ERP data, my first step is just to quit and relaunch eStudio. In fact, I try to prevent those problems by quitting and restarting eStudio whenever I’m about to start something new. I also like to type clear all in the Matlab command window prior to restarting eStudio, which clears out any variables that have been set (and I also sometimes type close all to close any windows that might have been opened previously).
It's also possible that some option has been set that you've forgotten about, which causes eStudio to do something unexpected. You can reset all the options to their defaults by clicking the Reset button (in the lower right corner of the plotting region).
If that doesn’t work, I try resetting ERPLAB’s working memory. This is a file that ERPLAB uses to store your current settings. The problem you’re having might be a side effect of one of your settings, or the settings may have become corrupted, so clearing the settings sometimes helps. To do this, go to the Settings menu in the top left corner of the eStudio GUI and select Memory Settings > Reset Working Memory. If resetting the working memory doesn’t work, I try restarting Matlab. Again, this is especially useful when I’m encountering a weird problem.
If none of the above steps solve the problem, and the problem is really odd, I try restarting my computer. But that’s very rare. And just like I restart eStudio on a regular basis to prevent problems, I recommend restarting your computer once a week or so. If the weird problem persists, you might try moving to a different computer to see if that solves the problem.
Finally, you can try uninstalling and reinstalling EEGLAB and ERPLAB. Although rare, it is possible that the code has been corrupted. I once encountered a case of a user who reported that one of the ERPLAB windows was missing some buttons, and she found that reinstalling ERPLAB solved the problem.
Missing Channel Locations or Data Quality Metrics in Datasets or ERPsets
Are your channel locations or data quality metrics missing from an EEGset or ERPset? The most common reason for this is that you have applied Channel Operations or Bin Operations to your data.
When you apply Channel Operations, ERPLAB may not be able to figure out the location information for your new channel. For example, when you create a new channel by averaging together a set of existing channels, how can ERPLAB know the 3-D location of this new channel? Indeed, this average across channels doesn’t really have a location. There is a box you can check in the GUI labeled Try to preserve location information, and it can preserve the channel locations in many cases (e.g., when you re-reference your data). But it uses a fairly simple algorithm, and it may strip out your previous channel location information if the algorithm can’t figure out a sensible set of locations.
A similar issue arises for the data quality metrics that are computed during averaging. If you modify the channels using Channel Operations or modify the bins using Bin Operations to your data, ERPLAB has no way of knowing whether the data quality metrics are still valid. For example, if you create a new bin with a difference wave or an average of two prior bins, what is the data quality for this new bin? There may be analytic solutions for some cases, but these solutions would require many assumptions. As a result, ERPLAB strips out the data quality information from the ERPset that is created when you run Channel Operations or Bin Operations. Our logic in stripping out the channel location information or data quality metrics in these situations is that we’d rather eliminate the information than provide you with incorrect or misleading information.
Solutions to Miscellaneous Common Problems
- Make sure the MATLAB PATH is set correctly (especially if you’re having problems right after installing a new version). See the section describing the Matlab PATH near the end of Chapter 1 for more details.
- If you can't get eStudio to launch, make sure that ERPLAB is installed inside the plugins folder within the EEGLAB folder (e.g., eeglab2024.0 > plugins >erplab). You should see a folder named studio_functions inside that folder.
- Make sure you’re using the right version of Matlab, EEGLAB, and ERPLAB.
- Some ERPLAB functions (e.g., filtering) require the Matlab Signal Processing Toolbox. You may need to install this toolbox. If you purchased Matlab yourself, you may need to buy this toolbox from The Mathworks. If you obtained Matlab through your institution, ask your IT group how to get this toolbox.
- If eStudio or Matlab doesn’t seem to respond to the mouse or keyboard, you may have a window hidden somewhere that’s waiting for input. For example, if you are performing manual artifact detection in one window, and then you look at another window, the artifact detection GUI may be waiting for input, and nothing else will work right until you close that GUI.
- If you load an EEGset but some or all of the channels appear to be missing in the plot region, the DC offset of the EEG signal is probably shifting the EEG outside of the range that is visible in the plotting window. To solve this, select Remove DC in the Plot Settings panel.
- EEGLAB has its own routine for extracting epochs from the continuous EEG (EEGLAB > Tools > Extract epochs), but do not use it!!! Instead, use the Extract bin-based epochs panel.
- EEGLAB and ERPLAB often print information in the command window that can help you figure out why things aren’t working properly.
- Don’t forget to read the Frequently Asked Questions (FAQ) pages for both EEGLAB and ERPLAB.
This page titled 14.3: A2.2 Some Basic Solutions was last modified on Thu, 01 Oct 2026 18:52:45 GMT and is shared under a CC BY-NC 4.0 license and was authored, remixed, and/or curated by Steven J Luck directly on the LibreTexts platform.
The book could not be loaded just now.