You can demo the Open Ephys GUI on any computer using the File Reader to read in data that’s already been saved. But if you are planning to run experiments, you’ll need to make sure your system is capable enough to keep up with data acquisition. In general, the minimum requirements will depend on how many channels you’d like to acquire simultaneously, and whether you need low-latency closed-loop feedback. Below, we provide some guidelines for configuring your data acquisition machine.
The most important thing you can do to improve performance is use a solid-state drive (ideally NVMe) for writing data. And if you need to record ≥128 channels simultaneously, an SSD is required.
For the Open Ephys acquisition board#
More than 800 Open Ephys acquisition boards have been produced and shipped to labs on every continent. This cost-effective, open-source device can easily scale from 16 channels to 512 channels just by adding more headstages and cables. It’s a very flexible way to acquire data from a wide variety of electrodes, including tungsten wires, tetrodes, and silicon probes.
The following hardware is recommended for experiments that use the acquisition board:
Operating system - the acquisition board works equally well on macOS, Windows, and Linux (all distros).
Processor - A 4-core, 3.0+ GHz processor is fine for 32-channel recordings, but you’ll want more cores and more speed as you scale up. Having a faster processor will allow you to build more complex signal chains without worrying about CPU overload. The GUI uses multithreading for data acquisition and recording, so having more cores is also helpful.
Memory - at least 1 GB of memory per 32 channels.
Data storage - a solid state drive for writing data is strongly recommended for all configurations, and required for any recordings involving at least 128 channels.
Graphics card - the GUI doesn’t rely much on the GPU for processing, so a good graphics card is not critical for data acquisition. However, consider upgrading your graphics card to speed up offline analysis steps (such as spike sorting).
Connections - At least one USB 3.0 port
These are the minimum requirements for getting up and running. You will likely need additional hardware for the full experiment (e.g. reward ports, mazes, commutators, light for optogenetic stimulation).
Acquisition board (available from the Open Ephys Store)
I/O boards for interfacing with auxiliary analog and digital signals (available from the Open Ephys Store)
Headstages and cables (available as part of the Open Ephys Starter Kit or from Intan Technologies; there is also a low-profile headstage available from the Open Ephys Store)
Electrodes - there is lots of flexibility here, as long as you have some way to interface between your electrodes and a compatible headstage. For tetrodes, we recommend the shuttleDrive.
For Neuropixels probes#
Operating system - Windows 7 or 10 (Linux support is coming soon)
Processor - minimum of 6 cores, 3.5 GHz; an Intel processor is recommended for optimum driver compatibility, but many users have AMD processors that work without issues.
Memory - at least 2 GB per simultaneously recorded probe; 16 GB is recommended.
Data storage - a solid state drive is essential (at least 500 MB/s write speed); an NVMe drive is strongly recommended.
Graphics card - the GUI doesn’t rely on the GPU for processing, but GPUs are essential for offline analysis. An NVIDIA GPU is likely required (for CUDA compatibility); we recommend buying a GTX 1660 or better.
Connections - the motherboard should have at least one x8- or x16-compatible PCIe slot, in addition to the one used by the GPU.
The following summarizes the additional hardware you’ll need to buy to run Neuropixels experiments. Full details can be found on the Neuropixels PXI plugin page.
From IMEC: Neuropixels basestations, cables, headstages, and probes
One PXI chassis (so far we’ve tested National Instruments PXIe-1071, PXIe-1082, and PXIe-1083 and ADLINK PXES-2301)
(optional) One PXI-based analog and digital I/O module (see the NI-DAQmx page for a list of hardware we’ve tested)
For chassis without a built-in controller (e.g. PXIe-1071, PXIe-1082), you’ll need:
One PXI remote control module (we’ve tested NI PXIe-8381 and PXIe-8398) – requires NIDAQmx driver
One PCIe interface card (we’ve tested NI PCIe-8381 and PCIe-8398)
MXI-Express Cables to connect the remote control module to the PCIe card
For chassis with a built-in Thunderbolt controller (e.g. PXIe-1083):
One Thunderbolt interface card that’s compatible with your motherboard
One sufficiently long Thunderbolt cable