Last updated: 2025-03-28
Checks: 1 1
Knit directory: hruban_wflow/
This reproducible R Markdown analysis was created with workflowr (version 1.7.1). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
The R Markdown file has unstaged changes. To know which version of
the R Markdown file created these results, you’ll want to first commit
it to the Git repo. If you’re still working on the analysis, you can
ignore this warning. When you’re finished, you can run
wflow_publish
to commit the R Markdown file and build the
HTML.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version 9b107c0. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
Note that you need to be careful to ensure that all relevant files for
the analysis have been committed to Git prior to generating the results
(you can use wflow_publish
or
wflow_git_commit
). workflowr only checks the R Markdown
file, but you know if there are other scripts or data files that it
depends on. Below is the status of the Git repository when the results
were generated:
Ignored files:
Ignored: .DS_Store
Ignored: code/rlucas/.DS_Store
Ignored: data/estimates/.Rapp.history
Untracked files:
Untracked: code/pivot_wider_pacto.R
Untracked: data/allfeatures_pacto.5mb.hg19.csv
Untracked: extdata/
Unstaged changes:
Modified: analysis/about.Rmd
Modified: analysis/index.Rmd
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the repository in which changes were
made to the R Markdown (analysis/about.Rmd
) and HTML
(docs/about.html
) files. If you’ve configured a remote Git
repository (see ?wflow_git_remote
), click on the hyperlinks
in the table below to view the files as they were in that past version.
File | Version | Author | Date | Message |
---|---|---|---|---|
Rmd | 9bbcb47 | Shashikant Koul | 2025-03-27 | Initial commit |
html | 9bbcb47 | Shashikant Koul | 2025-03-27 | Initial commit |
Rmd | 6dc79eb | Shashikant Koul | 2025-03-19 | Start workflowr project. |
Carolyn Hruban, Daniel C. Bruhm, Inna M. Chen, Shashikant Koul, Akshaya V. Annapragada, Nicholas A. Vulpescu, Sarah Short, Susann Theile, Kavya Boyapati, Bahar Alipanahi, Zachary L Skidmore, Alessandro Leal, Stephen Cristiano, Vilmos Adleff, Julia S. Johannsen, Robert B. Scharpf, Zachariah H. Foda, Jillian Phallen, and Victor E. Velculescu
Determining response to therapy for patients with pancreatic cancer can be challenging. We evaluated methods for assessing therapeutic response using cell-free DNA (cfDNA) in plasma samples from 40 patients with metastatic pancreatic cancer as part of the CheckPAC trial (NCT02866383). Patients were evaluated before and after initiation of therapy using tumor-informed plasma whole-genome sequencing (WGMAF), and genome-wide cfDNA fragmentation profiles and repeat landscapes (ARTEMIS-DELFI). Of those assessed with WGMAF, molecular responders had a median overall survival (OS) of 319 days compared to 126 days for non-responders (HR=0.29, 95% CI=0.11–0.79, p=0.011). For ARTEMIS-DELFI, patients with low scores after therapy initiation had a longer median OS than patients with high scores (233 days versus 172 days, HR=0.12, 95% CI=0.046-0.31, p<0.0001). We validated ARTEMIS-DELFI in a separate cohort of 40 patients with pancreatic cancer who were part of the PACTO trial (NCT02767557). These analyses suggest that non-invasive mutation and fragmentation-based cfDNA approaches can identify therapeutic response of individuals with pancreatic cancer.