Skip to content

MaxQuant v2.7.0 provides unreliable TMT reporter ion intensities from Astral analyser data #163

@mgraham4

Description

@mgraham4

The TMT reporter ion intensity values from MaxQuant v2.7.0 have many zero values and intensity values that are very different to when the same data is run on a previous version 2.6.3. Although v2.6.3 has no specific support for the Astral, the reporter ion values make more sense and are more typical.

Here are zero values in the reporter ion columns from using v2.7.0 for a TMT 12 plex, run with detection in the Astral analyser, which identified 7,314 protein groups:

Image

Here are the zero values in the reporter ion columns from using v2.6.3 for the same 12 plex, run with detection in the Astral analyser (orbitrap chosen as instrument in MaxQuant), which identified 7,236 protein groups:

Image

The v2.7.0 reporter ion data is also unreliable when no data is missing.
Here are the intensities of the four most intense proteins after using v2.7.0:

Image

Here is the same data using v2.6.3, which makes more sense:

Image

Things I have tried:
Searching data acquired from on a QEPlus with detection in the orbitrap - issue does not occur - issue may be specific to data acquired in the Astral analyser.
Changing to instrument "orbitrap" in v2.7.0 - issue still occurs.

I am using a Windows system.
You should see this same issue if you take TMT data acquired on an Astral analyser and search with v2.7.0.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions