Last updated: 2024-10-17
Checks: 2 0
Knit directory: test-3/
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.
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
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 70a7581. 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: .Rproj.user/
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 | 70a7581 | Paloma | 2024-10-17 | about page and index |
| html | 2ed0880 | Paloma | 2024-10-17 | Build site. |
| Rmd | 4594242 | Paloma | 2024-10-17 | about page |
| html | e4cf6f3 | Paloma | 2024-10-16 | initial files |
| Rmd | fd1d59b | Paloma | 2024-10-16 | Start workflowr project. |
The output from the plate reader, as well as all the information to interpret it, are stored in this repository. We used the original output from Myassays as it provides a better fitting curve than one calculated manually.
All samples in this essay were obtained from the same person, and were extracted using the same protocol. The parameters that we want to optimize vary for different samples:
Visualizations were conducted using dataset obtained from Myassays.com, i.e. before calculating final values including weight, buffer vol, and spike. This was because I wanted to look at the general performance of the assay, as well as visualizing the influence of different parameters of interest before controlling for them.