This repository contains extensions, plugins, for the Imaris (Oxford Instruments) microscopy image analysis program. They either provide additional image analysis capabilities via the open source SimpleITK image analysis library, or are utilities that allow the user to easily modify meta-data associated with images stored in the Imaris file format (e.g. channel names, colors).
The extensions are designed so that they can be run either as independent programs or via the Imaris extension mechanism. When run as independent programs they can be used on any of the standard operating systems (Windows/OSX/Linux).
Software development notes:
- We use the black code formatter to ensure uniform code style.
- The code is tested on Linux/OSX/Windows with Python versions 3.7 and 3.10.
- As the testing data is rather large, we use git-lfs. To obtain the data using standard git commands you will have to install git-lfs on your system.
- Details on how to contribute can be found here.
- Using zip file:
Download the zip file for a specific release or the latest code's zip file. Replace older versions with the contents of the zip file (don't forget to keep the
run_extensions.bat,run_extensions.shfiles which you previously modified for your setup). - Using git:
Initially, clone repository using git (with GitHub account).
Update to latest code:
git clone https://github.com/niaid/imaris_extensions.gitgit pull - If updating, you will want to remove or rename the existing Python environment:
or
conda remove -n imaris --allconda rename -n imaris old_imaris
Then, recreate the imaris environment, step 2 in the setup instructions below.
If you find these extensions useful in your research, support our efforts by citing it as:
Z. Yaniv, B. Lowekamp, "SimpleITK Imaris Extensions", doi: 10.5281/zenodo.7854019.
⚠ WARNINGS
Avoid converting files into imaris format using a network or external drive, this has the potential to produce corrupt files that are hard to identify as such (unless you enjoy hours of debugging). This issue is not specific to the work found here. For more details see the XTRegisterSameChannel documentation.
Corrupt files will cause the extensions to fail with an error message "...OSError: Can't read data (inflate() failed)". In some cases imaris is able to read such files while the extensions fail to do so. A solution, that often works, is to read the file into imaris and then "Save as" to a new file which can then be read by the extensions.
Out of memory errors will cause the extensions to fail with an error message along the lines of "...Failed to allocate memory for image.". The minimal RAM size required to run an extension depends on the image sizes and the specific extension in use. For common image sizes, 16GB of RAM is often sufficient, 64GB or more is desirable. If memory size is not sufficient, consider increasing the size of the machine's virtual memory. Experience has shown us that some extensions, e.g. XTChannelArithmetic, do work on systems with only 8GB of RAM when configured appropriately (using a memory efficient slice-by-slice processing at the cost of longer runtimes).
- XTRegisterSameChannel - Registration of 2D or 3D images that share a common channel (correlation based affine alignment). Sample datasets are freely available on zenodo
. A video illustrating the usage of the extension is available on YouTube.
- XTChannelArithmetic - Perform channel arithmetic, and more advanced channel manipulations via short SimpleITK expressions (short SimpleITK programs).
- XTVirtualHEStain - Create a virtual H&E stain from a fluoresence image and add the RGB image as three new channels to the original image.
- More to come.
- XTConfigureChannelSettings - Configure channel settings, name, description and visualization configuration specified via a csv file or an Imaris file.
- XTExportChannelSettings - Export channel settings, name, description and visualization configuration to a csv file. The resulting csv file can be easily edited and then applied to other imaris files using the XTConfigureChannelSettings extension.
- More to come.
- Install a Python version. The specific Python version you need depends on your version of Imaris (for us this is Python 3.7.0). Running the extensions as independent programs is less restrictive, requiring the use of Python version 3.6 or above.[Miniconda download].
- Configure and install the required Python packages.
- On Windows: open the Anaconda Prompt (found under the Anaconda3 start menu).
- On Linux/OSX: on the command line
source path_to_your_anaconda3/bin/activate base
cd path_to_your_extensions_directory
conda env create -f environment.yml
-
Configure Imaris to point to your Python executable and to the directory containing the extensions (see Imaris manual).
Note: this is an optional step, if you don't have the Imaris software on the specific machine you can still run the extensions. -
Edit one of these files, set the path to your Python executable:
Windows:run_extensions.bat
OSX/Linux:run_extensions.sh -
Run the relevant script:
Windows: double click the
run_extensions.bat.OSX/Linux: from a terminal, make the script executable
chmod +x run_extensions.shand run it./run_extensions.sh.Bonus: On OSX, you can configure things so that double clicking the script in Finder will run it. In Finder,
- Right-click the run_extensions.sh file and select "Open with" and then "Other..."
- Change the "Enable" dropdown menu from "Recommended Applications" to "All Applications".
- Search for "Terminal" and select it (check the "Always Open With" if you want all shell scripts to be run via terminal, otherwise leave it unchecked).
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent