Per-gene and per-histology summary views - #18
Merged
Conversation
rjcorb
approved these changes
May 12, 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.
Purpose/implementation Section
What scientific question is your analysis addressing?
Summarising the exisiting tables to create a summary view for TAPESTRY front end, instead of large, slow queries from the API.
What was your approach?
Add two PostgreSQL materialized views to TAPESTRY-data-preprocessing:
Add a
refresh_views.pypipeline script that issues REFRESH MATERIALIZED VIEW for both views and can be run after any pipeline that updates the underlying tej, sample_tej, tej_recurrence, or tej_domain tables.What GitHub issue does your pull request address?
Closes #17
Directions for reviewers. Tell potential reviewers what kind of feedback you are soliciting.
This worked for me when rebuilding after an edit, but not sure if it'll work from scratch. If the container is already running, this may allow you to not have to rebuild all the tables. Just check to see if the results say
Refreshed materialized views.If above doesn't work
You may have to get rid of the previous version for this to work, so I'll include both commands. May take ~10 mins (thanks CPM data):
Results (just check the final rows have
pipeline-1 | Refreshed materialized views.):Which areas should receive a particularly close look?
View heads for review
tej_gene_summary:
tej_histology_summary
Is there anything that you want to discuss further?
Is the analysis in a mature enough form that the resulting figure(s) and/or table(s) are ready for review?
Results
What types of results are included (e.g., table, figure)?
What is your summary of the results?
Reproducibility Checklist
Documentation Checklist
READMEand it is up to date.