Download & Installation

Author

Cox Lab

Published

November 28, 2024

1 Download

Downloading and using the software is free of charge.

Simply download from here and unpack the compressed file MaxQuant.zip.

2 Running

Please choose your operating system to view how to run MaxQuant.

2.1 MaxQuant on Windows

Supported operation system versions (64-bit is required) are Windows 10 or 11 or Windows Server 2016, 2019, 2022.

  • Install .NET Core 8.0 or higher: To find out whether you already have it, you can either open the following path. We recommend using version 8.0.302 at least, as it solves some bugs with the GUI.
C:\Program Files\dotnet\sdk

or run the following command in the terminal (Win+R -> cmd):

dotnet --version

If you need to, you can download the software and get installation instructions e.g. for .NET 8.0 here.

.NET 3.1 and older versions are not supported anymore.

MaxQuant now works with .NET >= 8.0.302

  • Run MaxQuant GUI Double click on MaxQuant.exe in the MaxQuant folder and specify your RAW files, experimental design and fasta files.

  • Start MaxQuant Click on the Start button.

2.2 MaxQuant on Linux

We are supporting MaxQuant on Ubuntu 20.04 or higher, but MaxQuant should also work on other distributions of Linux. You may run MaxQuant using Graphical User Interface. MaxQuant on Linux doesn’t support the use of a GUI at the moment. We’re planning to make it available in future versions, so stay tuned to our newletter, where we’ll inform our users about new updates.

This tutorial is focused on running MaxQuant using the command-line.

  • Install .NET Core 8.0 To find out whether you already have it, type in the command line
dotnet --version

If you see at least version \(8.0.302\), then everything is ready to start MaxQuant.

Otherwise you need to follow the installation instructions at .NET Core SDK 8.0 for your operating system.

2.2.1 Global installation on Ubuntu using sudo permissions

Ubuntu 22.04 (for example)

wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
sudo apt-get update; \
sudo apt-get install -y apt-transport-https && \
sudo apt-get update && \
sudo apt-get install -y dotnet-sdk-8.0

2.2.2 local installation using the conda environment

An alternative installation method, which might work better, if no sudo rights are available for the user would be to use the conda1 environment.

Depending on your architecture, the user must choose between the x86 and the Arm installation scripts. Both can be downloaded from the anaconda repository using the wget command.

# Or use conda to install an environment
## get the installer 
mkdir -p ~/miniconda3
# for 64x-bit 86x architecture
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh
# for 64-bit arm architecture
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-aarch64.sh -O ~/miniconda3/miniconda.sh

### You'll only need one the above two scripts!!!

# Install the conda base env
bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3
rm -rf ~/miniconda3/miniconda.sh

Before one can use the conda environment in your shell, it must be initialized and the session restarted. Another tip would be to install the mamba package, but this is only optional and is not needed, if you’re using conda on a regular basis. (If you do, you probably already installed mamba 😀).

# initialize conda on bash 
~/miniconda3/bin/conda init bash
~/miniconda3/bin/conda init zsh
# logging out and back in again
conda install conda-forge::mamba
mamba init 
#Here again, one must log out and back in again for mamba to be active.

Now, using the mambacommand one can create a new environment for dotnet. One can either choose a specific version for dotnet or by omitting the version number, the latest available version on the anaconda repository will be installed. You can search here for possible versions.

Before you can use the tool, you must activate the environment. Last check to see if the installation was successful, one can check for the available dotnet version.

#Now we create `dotnet` env
# create the dotnet env
mamba create -n dotnet8 conda-forge::dotnet=8.0.302
mamba activate dotnet8
#To test that we do have `dotnet`
dotnet --version

2.2.3 Scripted installation using Microsoft resources.

One can also follows Microsoft’s instruction to install the (optional) latest version of.NET by following the script here.

A manual install has more options to choose from using the dotnet-install script from the .NET page.

wget https://dot.net/v1/dotnet-install.sh -O dotnet-install.sh
chmod +x ./dotnet-install.sh
./dotnet-install.sh --channel 8.0

Possible important options here are:

  • --channel - use this to ask for a specific version and/or subversion
  • --version - install a specific version
  • --install-dir - use this to specify the path to the installation directory.

We also added a script for an automated installation of the .NET which can also be downloaded here. Running the script will ask the user for a download location, where, for now, .NET version 8.0.302 will be installed. This version was needed due to a bug in Perseus.

After downloading the script it needs to be made executable and can be run as such:

chmod -x Install_dotnet.sh
sh Install_dotnet.sh INSTALLATION_PATH/

This will download the .NET installation script from Microsoft and will install the tool at the given path. no sudo rights are needed.

2.3 Edit mqpar.xml file

Currently we highly recommend to pre-configure the mqpar.xml file in MaxQuant GUI. After transferring the file on Linux machine, do not forget to update file addresses accordingly. You can also use a programmatic way to change that.

If you use on-the fly prediction use this command:

If you use on-the-fly prediction use this command:

dotnet MaxQuant/bin/MaxQuantCmd.dll old_mqpar.xml --changeFolder new_mqpar.xml <new folder with fasta files> <new folder with raw files>

<<<<<<< Updated upstream If you use predicted libraries, you need to also add the path to the saved libraries, so use this command: ======= If you use predicted libraries, you also need to add the path to the saved libraries, so use this command: >>>>>>> Stashed changes

dotnet MaxQuant/bin/MaxQuantCmd.dll old_mqpar.xml --changeFolder new_mqpar.xml <new folder with fasta files> <new folder with raw files> <new folder with libraries>

However if you feel familiar with a structure of mqpar.xml, you may create a template of mqpar.xml and edit it directly.

dotnet MaxQuant/bin/MaxQuantCmd.dll --create new_mqpar.xml

2.4 Run MaxQuant

dotnet MaxQuant/bin/MaxQuantCmd.dll mqpar.xml

3 Hardware requirements

  • 4 GB RAM minimum.
  • 4 GB RAM per thread that is executed in parallel is required.
  • There is no upper limit on the number of cores. Whatever you can fit into a shared memory machine will work as long as the disk performance scales up with it.

Here we list some example hardware configurations that we are using in the lab and that we are quite happy with. These are mere examples and there is no reason to prefer specific vendors or brands.

3.0.1 Dell PowerEdge R820 (Intel)

  • 4x Intel® Xeon® E5-4640 2.40GHz, 20M Cache, 8.0GT/s QPI, Turbo, 8C, 95W
  • 128GB Memory for 4CPU (16x8GB RDIMM, 1600 MHz, Standard Volt, Dual Rank, x4)
  • PERC H710p integrated RAID Controller, 1GB NV Cache
  • 6x 900GB, SAS 6Gbps, 2.5-in, 10K RPM Hard Drive (Hot Plug)
  • RAID-0
  • OS: Microsoft Windows Server 2012 Standard

3.0.2 Standard PC

  • Processor: Intel® Core i7-2600 Processor (8M Cache,3.40 GHz)
  • OS: English original Windows® 7 Professional(64-Bit)
  • RAM: 16GB (4X4GB) 1333 MHz DDR3 Non-ECC 489916 1 [370-20205] 3
  • Primary Hard Drive: 256GB SSD Solid State Drive
  • Additional Hard Drive: 2TB (7.2k rpm) Serial ATA II with NCQ and 16MB Data Burst Cache
  • Graphics card: 512MB AMD Radeon HD 6350
  • USB 3.0: USB 3.0 PCI-Card
  • To improve the processing speed the SSD can also be used exclusively for MaxQuant
  • USB 3.0 convenient for fast file transfer, 500MByte/s (USB 2.0 = 60MByte/s)
  • Hard drives can of course be larger depending on the respective sizes of your projects and wallet.

3.0.3 ‘Monster’ PC

  • Coolermaster HAF 922 Black Tower Case
  • 2 x Front USB 2.0 and Audio ports
  • 750W EPS12V Quiet power supply
  • Additional Red LED 200mm Case Fans
  • Asus Sabertooth P67 Intel i7 Skt1155ATX motherboard With 2 x 16x 2.0 PCI-Express slot, 3 x PCI-e x1 slot, SATAIII 4 x DDR3 memory slots, Audio, 10/100/1000 LAN, SATAII, & USB 3.0/USB 2.0 ports
  • Intel i7 2600K 3.4GHz Quad Core 8MB cache Skt1155 Unlocked processor
  • Corsair Vengeance 32GB (4 x 8GB) DDR3 1866MHz Quad Channel memory
  • Western Digital 500GB Caviar Black SATAIII disk drive
  • 1GB Nvidia Geforce GT430 PCI-e x16 2.0 graphics card
  • Black DVD+/- R RW Dual Layer drive
  • LSI 9260-8i 8port SAS 6Gb/s PCI-Express RAID controller
  • Battery Backup for RAID controller
  • 2 x Crucial 512MB Solid State Disks
  • Thanks to Peter McHardy for assembling this configuration

For questions or problems with the installation we would love to hear from you under Contact.

References

1.
Anaconda software distribution. Anaconda Documentation (2020).