-
Notifications
You must be signed in to change notification settings - Fork 2
Fix build #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tonywu1999
wants to merge
2
commits into
devel
Choose a base branch
from
fix-build
base: devel
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix build #46
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
git ls-files | head -20Repository: Vitek-Lab/MSstatsLiP
Length of output: 518
🏁 Script executed:
cat -n DESCRIPTION | head -40Repository: Vitek-Lab/MSstatsLiP
Length of output: 2352
🏁 Script executed:
fd -t f "groupComparisonLiP" -x cat -n {}Repository: Vitek-Lab/MSstatsLiP
Length of output: 13499
🌐 Web query:
MSstatsPTM groupComparisonPTM function parameters ptm_label_type protein_label_type version history💡 Result:
groupComparisonPTM()parameters:ptm_label_type,protein_label_typeptm_label_type: labeling type for the PTM dataset; must be"LF"or"TMT"(default"LF"). [1,2]protein_label_type: labeling type for the PROTEIN (global proteome) dataset; must be"LF"or"TMT"(default"LF"). [1,2]These parameters let MSstatsPTM run group comparisons even when the PTM and global-protein datasets use different labeling types (e.g., PTM is TMT but the proteome is label-free). [3]
Version / history (what changed, and when)
groupComparisonPTM()useddata.type(noptm_label_type/protein_label_type). [4]groupComparisonPTM()includesptm_label_typeandprotein_label_type, and notes thatdata.type“will be deprecated” in favor of the two new parameters. [1]data.typewould be replaced byptm_label_type+protein_label_type, and advising for backward compatibility to set both new parameters to the olddata.typevalue. [3]Practical migration rule: if you previously did
data.type = "LF"(or"TMT"), now doptm_label_type="LF", protein_label_type="LF"(or both"TMT"), unless you intentionally want them to differ. [1,3]References:
[1] Bioconductor MSstatsPTM 2.13.0 PDF manual (Bioc 3.23; published 2026-03-03). (bioconductor.posit.co)
[2] MSstatsPTM reference manual (HTML) documenting allowed values for
ptm_label_type/protein_label_type. (bioc.r-universe.dev)[3] MSstats Google Group announcement (2025-03-19) describing the parameter change and rationale. (groups.google.com)
[4] Bioconductor MSstatsPTM 2.0.3 PDF manual (Bioc 3.16; published 2023-04-10). (bioconductor.statistik.uni-dortmund.de)
Citations:
🏁 Script executed:
Repository: Vitek-Lab/MSstatsLiP
Length of output: 46
🏁 Script executed:
# Check NAMESPACE file for any hints about MSstatsPTM cat NAMESPACERepository: Vitek-Lab/MSstatsLiP
Length of output: 2530
🏁 Script executed:
Repository: Vitek-Lab/MSstatsLiP
Length of output: 46
🌐 Web query:
MSstatsPTM version 2.1 2.2 2.3 ptm_label_type protein_label_type introduced when release date💡 Result:
When were
ptm_label_type/protein_label_typeintroduced?They replaced the old single
data.typeparameter forgroupComparisonPTM()as part of the Bioconductor 3.21 cycle; MSstatsPTM 2.10.0 (Date/Publication: 2025-04-15) is documented in Bioconductor materials for that release series. [1] (The change was announced ahead of time for the “upcoming MSstats 3.21 bioconductor release”.) [2]You can see the old interface (
data.type) in MSstatsPTM 2.0.3 examples. [2]You can see the new interface (
ptm_label_type,protein_label_type) in current manuals (e.g.,dataProcessPTM()andgroupComparisonPTM()). [3]Release dates for MSstatsPTM 2.1 / 2.2 / 2.3 (Bioconductor evidence)
From the Bioconductor package archives I could access:
If you want, tell me whether you mean Bioconductor releases specifically (recommended for “release date”), or GitHub tags/releases—and I can look up whether 2.1.x / 2.3.x exist as GitHub-only versions.
🌐 Web query:
MSstatsPTM changelog release notes ptm_label_type protein_label_type💡 Result:
Where this change is documented (release notes / changelog context):
groupComparisonPTM()’sdata.typeparameter is being replaced by two new parameters:ptm_label_typeandprotein_label_type, to support cases where PTM and proteome data use different label types (e.g., PTM=TMT, protein=LF). Back-compat guidance: set both new parameters to the olddata.typevalue. [1]What the current MSstatsPTM docs say:
groupComparisonPTM()still listsdata.typebut states it “will be deprecated in favor ofptm_label_typeandprotein_label_type”, and documents both new args as acceptingLForTMT. [2]dataProcessPTM()as takingptm_label_typeandprotein_label_typeexplicitly (same allowed values:LF/TMT). [2]Sources:
[1] MSstats Google Group announcement (Mar 19, 2025): “Upcoming Backwards-Incompatible Changes in MSstats 3.21 – Action Required”
[2] Bioconductor MSstatsPTM manual (PDF), sections for
groupComparisonPTManddataProcessPTMAdd
MSstatsPTM (>= 2.10.0)version constraint in Imports before releasing.groupComparisonLiP()callsgroupComparisonPTM()withptm_label_typeandprotein_label_typeparameters, which were introduced in MSstatsPTM 2.10.0 (Bioconductor 3.21, released ~April 2025). Without a version bound, installations with older MSstatsPTM versions will fail at runtime.🤖 Prompt for AI Agents