This article describes how to modify the configuration file for ProteinPilot™ software to decrease the time needed when using the LSMS Reconstruct algorithm, especially when performing large protein ID searches on data sets from a TripleTOF® 6600 LC-MS/MS System.
X500 series instruments generate wiff2 file formats, but with the newest version of SCIEX OS Software 2.1, they can also generate a .wiff1 file. Only .wiff1 files can be used to perform a ProteinPilot™ software search.
Yes, ProteinPilot™ software 5.0.2 can be run on a Windows 2019 Server. This was not officially tested or mentioned in the release notes, but many users have installed the Windows 10-compatible ProteinPilot software 5.0.2 on the Windows Server 2019 operating system and have run the software successfully in this environment.
This article summarizes the issues with ProteinPilot version 5.0 and mzIdentML created files. Submission of mzIdentML files is still not automated with later versions of ProteinPilot™ software, including version 5.0.x. Complete submissions from ProteinPilot software to PRIDE are not possible, but partial submissions of the mzIdentML are, and this partial submission process is described below.
The version of ProteinPilot™ Software in the SCIEX Cloud is version 5.0.3; therefore, group files created in the SCIEX Cloud cannot be downloaded to a desktop and opened in ProteinPilot Software 5.0.2. To download and read a group file on a desktop installation of ProteinPilot Software, the desktop version must be upgraded to version 5.0.3.
During a search with ProteinPilot™ Software 5.0, 5.0.1 and 5.0.3, the error "Unhandled Exception: Out Of Memory Exception" appears. This issue is due to the LC/MS reconstruct crashing within the ProteinPilot Software when data sets with a high MS1 scan speed are being processed.
For software users who need to view the older group files, maintaining a separate computer with ProteinPilot™ software 4.0 installed is the recommended best approach. Alternatively, both versions, 5.0.x and an older version, can be installed on the same computer, but this is an unsupported configuration.
The taglet.exe error in ProteinPilot™ software is due to a wide range of issues including incorrect language settings, installation of the software on the incorrect operating system, and the incorrect addition of modifications — to name a few.
The software package, PeakView® 2.2, CloudConnect 1.2 beta and SWATH® 2.0.1 software. is needed to perform the OneOmics workflow and/or SWATH protein data processing and is Windows 7 and Windows 10, 64-bit compatible.
The rapid search and a thorough search settings in ProteinPilot™ software determine which parts of the search algorithm will be invoked and effectively how deep the sample will be searched to find the right answers.
If a user installs ProteinPilot™ 5.0 software with Skyline, old and new group files will not be able to be opened because the converter has changed. An error message will be displayed when building peptide libraries while importing a ProteinPilot group file.
ProteinPilot™ software uses the incorrect mass spectrometer name in its group file output file. When a TripleTOF® 5600 system was selected, the group file contains the name QSTAR® Elite instead for system information. This causes the wrong results to be output; if the incorrect instrument name is used, then the incorrect tolerance settings are applied.
Searching for ProteinPilot software files using Windows Explorer cannot be done because there are two files acquired under the same file name. This is a long known issue for all ProteinPilot versions that only one file per file name can be searched using ProteinPilot software.
This is a known issue, and the TrEMBL database is not recommended for use with ProteinPilot software. The TrEMBL database is automatically annotated and not reviewed and could contain redundancies in terms of protein sequences, protein ascension numbers, etc.