Milab 6958 no msa for peptides - #13
Merged
Merged
Conversation
Comment on lines
+104
to
+115
| .output("isPeptide", (ctx): boolean => { | ||
| const ref = ctx.data.datasetRef; | ||
| if (ref === undefined) return false; | ||
| const keyAxis = ctx.resultPool.getPColumnSpecByRef(ref)?.axesSpec[1]; | ||
| if (keyAxis?.name !== "pl7.app/variantKey") return false; | ||
| const domain = keyAxis.domain ?? {}; | ||
| const declared = domain["pl7.app/modality"]; | ||
| if (declared === "vdj" || declared === "amplicon") return false; | ||
| if (domain["pl7.app/peptide/extractionRunId"] !== undefined) return true; | ||
| if (domain["pl7.app/repertoire/extractionRunId"] !== undefined) return false; | ||
| if (domain["pl7.app/vdj/clonotypingRunId"] !== undefined) return false; | ||
| return true; |
There was a problem hiding this comment.
Peptide Classification Lacks Tests
The new classifier branches on the key axis, modality, three run identifiers, and a default true result. This output directly controls whether the table shows the MSA button, but no focused model test covers the peptide, repertoire, V(D)J, or unknown-domain cases. A later metadata or classification regression could therefore expose MSA for unsupported datasets or hide it for supported ones. Please add focused tests for each branch and the fallback behavior.
Prompt To Fix With AI
This is a comment left during a code review.
Path: model/src/index.ts
Line: 104-115
Comment:
**Peptide Classification Lacks Tests**
The new classifier branches on the key axis, modality, three run identifiers, and a default `true` result. This output directly controls whether the table shows the MSA button, but no focused model test covers the peptide, repertoire, V(D)J, or unknown-domain cases. A later metadata or classification regression could therefore expose MSA for unsupported datasets or hide it for supported ones. Please add focused tests for each branch and the fallback behavior.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
PaulNewling
approved these changes
Sep 24, 2026
PaulNewling
approved these changes
Sep 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The PR appears safe to merge, with the non-blocking concern that its new metadata-sensitive peptide classifier lacks focused regression tests.
Fix with agent prompt
Summary
This PR classifies selected datasets as peptide or non-peptide and uses that result to suppress the table's multiple-sequence-alignment entry point for peptide datasets. It also updates the repository's SDK tooling and workflow validation command.
isPeptidemodel output based on the selected dataset's key-axis metadata.@platforma-sdk/tengo-builderto 4.1.1 and@platforma-sdk/block-toolsto 2.16.1.pl-tengo importsbefore workflow checking.Important touched terms
isPeptide— A new boolean model output identifying peptide datasets. It now examines the selected dataset's key axis and its modality/run metadata.pl7.app/variantKey— The key-axis type used by variant-oriented datasets. It is now the prerequisite axis name for peptide classification.PlAgDataTableV2cell button — The cluster-table control that emitscell-button-clicked. Its axis configuration is now conditional onisPeptide..structuremetadata format used by repository tooling. Its version marker changes from 2 to 3.Diagram
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Selected dataset] --> B{Key axis is variantKey?} B -- No --> N[isPeptide = false] B -- Yes --> C{Declared VDJ or amplicon?} C -- Yes --> N C -- No --> D{Peptide extraction ID exists?} D -- Yes --> P[isPeptide = true] D -- No --> E{Repertoire or VDJ run ID exists?} E -- Yes --> N E -- No --> P P --> H[Hide MSA cell button] N --> S[Show MSA cell button]Reviews (1) · Last reviewed commit: "MILAB-6958: bump tengo-builder and block..."