Add DeltaSignal pathway perturbation UI - #155
Draft
Chryseisliu wants to merge 2 commits into
Draft
Conversation
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.
What changed
/api/pathways,/api/parse, and/api/solveendpointsWhy
This is a bounded, demonstrable vertical slice for pathway perturbation prediction in the Reactome UI. It keeps the DeltaSignal engine in its own repository and uses the documented HTTP API as the integration boundary.
The first supported demo is Cell Cycle Checkpoints: selecting activated ATM (
R-HSA-5693527) maps to 29 logic-network nodes and can be run as a knockout to visualize the predicted downstream response.User impact
Users can go from a molecule selected in a Reactome pathway to a solver-backed predicted pathway response without leaving the Pathway Browser. Loading, unsupported-network, convergence, and API-error states are shown explicitly.
Validation
npm test: 69 tests passednpm run build: production build passedDeliberate follow-up scope
This draft does not yet include multi-pathway joining, ReacFoam-wide overlays, temporal ordering, backend deployment configuration, or the benchmark report. The largest local network currently has noticeable parse/solve request latency, so backend caching/deployment should be reviewed before production rollout.