Next-generation multiplexed targeted proteomics quantifies post-translational modifications in disease and compound-protein interactions with high throughput.
Paper
Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
C++ · 212 lines · 7.3 KB · MIT
- // Copyright(c) 2011 - 2018 Thermo Fisher Scientific - LSMS
- //
- // Permission is hereby granted, free of charge, to any person obtaining a copy
- // of this software and associated documentation files (the "Software"), to deal
- // in the Software without restriction, including without limitation the rights
- // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
- // copies of the Software, and to permit persons to whom the Software is
- // furnished to do so, subject to the following conditions:
- //
- // The above copyright notice and this permission notice shall be included in all
- // copies or substantial portions of the Software.
- //
- // THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- // IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- // FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- // AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
- // OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- // SOFTWARE.
- #include "StdAfx.h"
- #include "ApiUsageTest.h"
- #include "HandlerToResetEvent.h"
- using namespace System::Reflection;
- using namespace Microsoft::Win32;
- using namespace Thermo::Interfaces::InstrumentAccess_V1;
- using namespace Thermo::Interfaces::InstrumentAccess_V1::Control::Acquisition;
- using namespace Thermo::Interfaces::ExactiveAccess_V1::Control::Acquisition;
- namespace ManagedCppLoad
- {
- ApiUsageTest::ApiUsageTest()
- {
- }
- ApiUsageTest::!ApiUsageTest()
- {
- m_instrument = nullptr; // no active destruction here
- }
- ApiUsageTest::~ApiUsageTest()
- {
- this->!ApiUsageTest();
- }
- // Return true if loading the API has been successful
- bool ApiUsageTest::Load()
- {
- Console::Write(L"Loading Exactive Series API...");
- try
- {
- Object^ o = LoadDirect();
- IInstrumentAccessContainer^ iac = safe_cast<IInstrumentAccessContainer^>(o);
- m_instrument = safe_cast<IExactiveInstrumentAccess^>(iac->Get(1));
- }
- catch (Exception^ e)
- {
- Console::WriteLine(L" failed to load API");
- Console::WriteLine();
- Console::WriteLine(e->ToString());
- return false;
- }
- Console::WriteLine(L" API Loaded");
- return true;
- }
- // Return true if the instrument is accessible within 10 seconds
- bool ApiUsageTest::WaitForInstrument()
- {
- Console::Write(L"Waiting for instrument to become connected within 10 seconds...");
- try
- {
- IExactiveAcquisition^ ea = m_instrument->Control->Acquisition;
- if (!ea->WaitFor(TimeSpan::FromSeconds(10), SystemMode::Off, SystemMode::On, SystemMode::Standby))
- {
- Console::WriteLine(L" Sorry, system mode remained at {0}", ea->State->SystemMode);
- return false;
- }
- // I cheated, we wait a maximum of 20 secs.
- if (!ea->WaitFor(TimeSpan::FromSeconds(10), InstrumentState::Off, InstrumentState::StandBy, InstrumentState::ReadyToDownload))
- {
- Console::WriteLine(L" Sorry, instrument state remained at {0}", ea->State->SystemState);
- return false;
- }
- }
- catch (Exception^ e)
- {
- Console::WriteLine(L" failed to use the API");
- Console::WriteLine();
- Console::WriteLine(e->ToString());
- return false;
- }
- Console::WriteLine(L" Instrument connected");
- return true;
- }
- // Return the scans interface in a way that it is suitable to receive commands
- IScans^ ApiUsageTest::GetWorkingScansInterface()
- {
- Console::Write(L"Placing custom scans and waiting for it to accept commands...");
- IScans^ s = nullptr;
- try
- {
- s = m_instrument->Control->GetScans(false);
- // The interface is not usable until parameters are available, create a waiting mutex and wait on it.
- AutoResetEvent^ waiter = gcnew AutoResetEvent((s->PossibleParameters != nullptr) && (s->PossibleParameters->Length > 0)); // auto-dispose
- HandlerToResetEvent^ handler = gcnew HandlerToResetEvent(waiter); // auto-dispose
- s->PossibleParametersChanged += gcnew System::EventHandler(handler, &HandlerToResetEvent::Handler);
- waiter->WaitOne(1000); // 1 second should really be sufficient because we are already connected. Expect few ms to get this happen
- s->PossibleParametersChanged -= gcnew System::EventHandler(handler, &HandlerToResetEvent::Handler);
- if ((s->PossibleParameters == nullptr) || (s->PossibleParameters->Length == 0))
- {
- Console::WriteLine(L" Sorry, IScans interface node doesn't supply parameters for unknown reason");
- return nullptr;
- }
- }
- catch (System::Security::AccessControl::PrivilegeNotHeldException^ priv)
- {
- Console::WriteLine(L" cannot get IScans interface, missing privilege '{0}'", priv->PrivilegeName);
- return nullptr;
- }
- catch (Exception^ e)
- {
- Console::WriteLine(L" cannot get IScans interface");
- Console::WriteLine();
- Console::WriteLine(e->ToString());
- return nullptr;
- }
- // assume "Set" is part of the commands
- Console::WriteLine(L"Available");
- return s;
- }
- // Place two consecutive scans, one on positive, one in negative mode
- void ApiUsageTest::PlaceScans(IScans^ scans)
- {
- Console::Write(L"Placing custom scans with different polarity...");
- try
- {
- ICustomScan^ cs;
- for (int i = 0; i < 5; i++)
- {
- cs = scans->CreateCustomScan();
- cs->RunningNumber = 2001;
- // assume we have one possible values "0" and "1" for polarity
- cs->Values["Polarity"] = "0";
- if (!scans->SetCustomScan(cs))
- {
- Console::WriteLine(L" cannot place custom scan for unknown reason");
- return;
- }
- cs = scans->CreateCustomScan();
- cs->RunningNumber = 2002;
- // assume we have one possible values "0" and "1" for polarity
- cs->Values["Polarity"] = "1";
- if (!scans->SetCustomScan(cs))
- {
- Console::WriteLine(L" cannot place custom scan for unknown reason");
- return;
- }
- }
- }
- catch (Exception^ e)
- {
- Console::WriteLine(L" cannot place custom scans");
- Console::WriteLine();
- Console::WriteLine(e->ToString());
- }
- Console::WriteLine(L" OK");
- }
- // New way of linking the API requires knowledge about class/namespace and the implementing API.
- // Exactive's standard values can be found in the standard Xcalibur registry at
- // HKLM\Software[\Wow6432Node]\Finnigan\Xcalibur\Devices\Thermo Exactive
- // under the string values ApiFileName_Clr2_32_V1 and ApiClassName_Clr2_32_V1
- Object^ ApiUsageTest::LoadDirect()
- {
- String^ asmName = nullptr;
- String^ typeName = nullptr;
- String^ baseName = String::Format(L"SOFTWARE{0}\\Finnigan\\Xcalibur\\Devices\\Thermo Exactive", (IntPtr::Size > 4) ? L"" : L"\\Wow6432Node");
- RegistryKey^ key = Registry::LocalMachine->OpenSubKey(baseName);
- if (key != nullptr)
- {
- asmName = safe_cast<String^>(key->GetValue(L"ApiFileName_Clr2_32_V1", nullptr));
- typeName = safe_cast<String^>(key->GetValue(L"ApiClassName_Clr2_32_V1", nullptr));
- key->Close();
- }
- if (String::IsNullOrEmpty(asmName) || String::IsNullOrEmpty(typeName))
- {
- Console::Error->WriteLine("Exactive is not registered or service hasn't been started one time.");
- Environment::Exit(3);
- }
- Assembly^ assm = Assembly::LoadFrom(asmName);
- Object^ o = assm->CreateInstance(typeName);
- return o;
- }
- // Old way of linking to the API using COM. Disadvantages are strange error messages, late detection
- // of bitness or CLR errors and too much .NET-magic
- Object^ ApiUsageTest::LoadPerCom()
- {
- Type ^t = Type::GetTypeFromProgID("Thermo Exactive.API_Clr2_32_V1", true);
- Object ^o = Activator::CreateInstance(t);
- return o;
- }
- }
ApiUsageTest.cpp at commit c246dcc, under MIT · at the source
Overview
- Department of Cell Biology, Harvard Medical School, Boston, MA USA
- Mental Illness Research Education and Clinical Center (MIRECC), Veterans Affairs Palo Alto Health Care System, Palo Alto, CA USA
- Department of Psychiatry and Behavioral Sciences, Stanford University School of Medicine, Stanford, CA USA
- Thermo Fisher Scientific, San Jose, CA USA
- Department of Chemistry and Biochemistry, Brigham Young University, Provo, UT USA
- Department of Biochemistry and Molecular Biotechnology, University of Massachusetts Chan Medical School, Worcester, MA USA
Abstract
The abstract is not reproduced here: the paper's license (CC BY-NC-ND) does not allow it. Read it in the paper, at the publisher or on Europe PMC.
Repositories
Its files are read in the Code ↔ Paper reader above.
thermofisherlsms/iapi
c246dcc8772d03c9c32e9b2fde486e97572c8fbf, 11 May 2026Availability: 1 check, the latest on 27 September 2026: the link answers
- 27 September 2026: the link answers
13 files
- examples/
exactive/ , C++, 212 linesManagedCppLoad/ ApiUsageTest.cpp - examples/
exactive/ , C/C++, 30 linesManagedCppLoad/ ApiUsageTest.h - examples/
exactive/ , C++, 40 linesManagedCppLoad/ AssemblyInfo.cpp - examples/
exactive/ , C++, 33 linesManagedCppLoad/ ClientValidation.cpp - examples/
exactive/ , C++, 50 linesManagedCppLoad/ HandlerToResetEvent.cpp - examples/
exactive/ , C/C++, 24 linesManagedCppLoad/ HandlerToResetEvent.h - examples/
exactive/ , C++, 52 linesManagedCppLoad/ main.cpp - examples/
exactive/ , C/C++, 3 linesManagedCppLoad/ resource.h - examples/
exactive/ , C++, 7 linesManagedCppLoad/ stdafx.cpp - examples/
exactive/ , C/C++, 8 linesManagedCppLoad/ stdafx.h - examples/
exactive/ , MATLAB, 95 linesScripts/ Matlab/ AcquisitionByCount.m - LICENSE, License, 21 lines
- README.md, Text, 75 lines
uwpr.github.io/comet
Availability: 1 check, the latest on 27 September 2026: the link answers (HTTP 200)
- 27 September 2026: the link answers (HTTP 200)
Code availability statement
The paper has a code availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- it points to the authors' code: thermofisherlsms/
iapi , uwpr.github.io/comet
Read it in the paper: doi.org/10.1038/s41467-026-76929-y.
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 2 repositories of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 11 scripts, each with its path and the digest of its content;
- no match between paragraphs and code yet;
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
No dataset and no data link were found in the paper.
Data availability statement
The paper has a data availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- no repository, dataset or request procedure was recognized in it
Read it in the paper: doi.org/10.1038/s41467-026-76929-y.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 27 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 13 authors, 2 keywords, 9 MeSH terms, 4 funders, 34 references.
Cite
This paper
Shuken, S. R., Frere, G. A., Beard, C. R., McGann, C. D., Canterbury, J. D., Zuniga, N. R., Gassaway, B. M., Dawson, S. L., Ooi, K. H., Paulo, J. A., McNerney, M. W., Gygi, S. P., & Yu, Q. (2026). Next-generation multiplexed targeted proteomics quantifies post-translational modifications in disease and compound-protein interactions with high throughput. Nature communications, 17(1), 9048. https://
BibTeX
@article{shuken2026next,
author = {Shuken, Steven R and Frere, Geordon A and Beard, Charlotte R and McGann, Christopher D and Canterbury, Jesse D and Zuniga, Nathan R and Gassaway, Brandon M and Dawson, Shane L and Ooi, Kean Hean and Paulo, João A and McNerney, M Windy and Gygi, Steven P and Yu, Qing},
title = {{Next-generation multiplexed targeted proteomics quantifies post-translational modifications in disease and compound-protein interactions with high throughput}},
journal = {Nature communications},
year = {2026},
month = aug,
volume = {17},
number = {1},
pages = {9048},
publisher = {Nature Portfolio},
issn = {2041-1723},
doi = {10.1038/
url = {https://
pmid = {42649221},
pmcid = {PMC13518854}
}
RIS
TY - JOUR
AU - Shuken, Steven R
AU - Frere, Geordon A
AU - Beard, Charlotte R
AU - McGann, Christopher D
AU - Canterbury, Jesse D
AU - Zuniga, Nathan R
AU - Gassaway, Brandon M
AU - Dawson, Shane L
AU - Ooi, Kean Hean
AU - Paulo, João A
AU - McNerney, M Windy
AU - Gygi, Steven P
AU - Yu, Qing
TI - Next-generation multiplexed targeted proteomics quantifies post-translational modifications in disease and compound-protein interactions with high throughput
T2 - Nature communications
J2 - Nat Commun
PY - 2026
DA - 2026/
VL - 17
IS - 1
SP - 9048
SN - 2041-1723
PB - Nature Portfolio
DO - 10.1038/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1038/
"type": "article-journal",
"title": "Next-generation multiplexed targeted proteomics quantifies post-translational modifications in disease and compound-protein interactions with high throughput",
"container-title": "Nature communications",
"author": [
{
"family": "Shuken",
"given": "Steven R"
},
{
"family": "Frere",
"given": "Geordon A"
},
{
"family": "Beard",
"given": "Charlotte R"
},
{
"family": "McGann",
"given": "Christopher D"
},
{
"family": "Canterbury",
"given": "Jesse D"
},
{
"family": "Zuniga",
"given": "Nathan R"
},
{
"family": "Gassaway",
"given": "Brandon M"
},
{
"family": "Dawson",
"given": "Shane L"
},
{
"family": "Ooi",
"given": "Kean Hean"
},
{
"family": "Paulo",
"given": "João A"
},
{
"family": "McNerney",
"given": "M Windy"
},
{
"family": "Gygi",
"given": "Steven P"
},
{
"family": "Yu",
"given": "Qing"
}
],
"container-title-short":
"volume": "17",
"issue": "1",
"page": "9048",
"DOI": "10.1038/
"PMID": "42649221",
"PMCID": "PMC13518854",
"ISSN": "2041-1723",
"publisher": "Nature Portfolio",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
8,
25
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.1038/s41556-025-01623-y
- Proteostasis and lysosomal repair deficits in transdifferentiated neurons of Alzheimer's disease.Journal: Nature cell biologyIn common: Alzheimer's / dementia, 3 references, 2 authors
- [2] doi:10.1038/s41467-025-60022-x [code]
- Expanding the landscape of aging via orbitrap astral mass spectrometry and tandem mass tag integration.Journal: Nature communicationsIn common: other, genetics / omics, 1 reference, 2 authors
- [3] doi:10.1073/pnas.2609132123 [code]
- A human lysosomal storage disorder toolkit for decoding proteome landscapes in cortical-like and dopaminergic-like induced neurons.Journal: Proceedings of the National Academy of Sciences of the United States of AmericaIn common: genetics / omics, 1 reference, 2 authors
- [4] doi:10.15252/embr.202256399 [code]
- PARK15/
FBXO7 is dispensable for PINK1/ Parkin mitophagy in iNeurons and HeLa cell systems. Journal: EMBO reportsIn common: genetics / omics, 3 references, author João A Paulo - [5] doi:10.1186/s13024-025-00874-5
- Proteomic landscape of Alzheimer's disease: emerging technologies, advances and insights (2021 - 2025).Journal: Molecular neurodegenerationIn common: other, Alzheimer's / dementia, genetics / omics, 4 references
- [6] doi:10.1038/s41586-025-09059-y [code]
- EndoMAP.v1 charts the structural landscape of human early endosome complexes.Journal: NatureIn common: genetics / omics, 1 reference, author João A Paulo
- [7] doi:10.1038/s41556-024-01356-4 [code]
- Combinatorial selective ER-phagy remodels the ER during neurogenesis.Journal: Nature cell biologyIn common: genetics / omics, 1 reference, author João A Paulo
- [8] doi:10.1172/jci.insight.164178
- MKRN3 inhibits puberty onset via interaction with IGF2BP1 and regulation of hypothalamic plasticity.Journal: JCI insightIn common: author Brandon M Gassaway
- [9] doi:10.1073/pnas.2419079121 [code]
- Endo-IP and lyso-IP toolkit for endolysosomal profiling of human-induced neurons.Journal: Proceedings of the National Academy of Sciences of the United States of AmericaIn common: genetics / omics, author João A Paulo
- [10] doi:10.1038/s41467-024-44732-2 [code]
- Disruption of lysosomal proteolysis in astrocytes facilitates midbrain organoid proteostasis failure in an early-onset Parkinson's disease model.Journal: Nature communicationsIn common: 3 references
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 2 repositories of the authors' code, each at its verified commit and with its license, 11 scripts, and 0 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:528ded1b2387078d…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1038/s41467-026-76929-y)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41467-026-76929-y.svg
:target: https://openscicode.org/badge/doi/10.1038/s41467-026-76929-y
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41467-026-76929-y"><img src="https://openscicode.org/badge/doi/10.1038/s41467-026-76929-y.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".
If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
