Last updated: 2021-06-22
Checks: 1 1
Knit directory:
VSA_altitude_hold/
This reproducible R Markdown analysis was created with workflowr (version 1.6.2). 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 456a363. 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: .Rhistory
Ignored: .Rproj.user/
Ignored: renv/library/
Ignored: renv/staging/
Untracked files:
Untracked: analysis/characterise_data.Rmd
Unstaged changes:
Modified: analysis/design_notes.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/index.Rmd
) and HTML (docs/index.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 |
---|---|---|---|---|
html | 456a363 | Ross Gayler | 2021-06-21 | Add automatic rendering of DFDs |
html | d8b9d53 | Ross Gayler | 2021-06-18 | Add DFD for Design 01 |
Rmd | 0b7e1d4 | Ross Gayler | 2021-06-17 | Publish initial docs |
html | 0b7e1d4 | Ross Gayler | 2021-06-17 | Publish initial docs |
Rmd | 87c00d2 | Ross Gayler | 2021-06-17 | Start workflowr project. |
This is the website for the research project “VSA Altitude Hold”.
If you have cloned the project to a local computer this website is
rendered in the docs
subdirectory of the project directory.
If you are using workflowr
to publish the research website it will
also be rendered online to GitHub Pages.
This page acts as a table of contents for the website. There are links to the web pages generated from the analysis notebooks and to the rendered versions of any manuscripts/documents/presentations.
This notebook is for keeping notes about potential approaches for implementing altitude hold in VSA.
Links to rendered manuscripts and presentations will go here.
This project repository deals with the conceptual issues of using VSA for altitude hold. Actual implementation occurs in the gym-copter repository So the empirical work in this repository is limited to exploration of VSA-specific issues.
This notebook characterises data generated by the simulation of the classically implemented altitude hold controller. We need to understand the properties of the signals in order to design VSA implementations of them.