You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update README for a few other functions and common activities.
Including the preferred way to locate batons to allow filtering by types of relays (e.g. practice vs competition).
Update LOCKFILE as additional packages were needed for making the RMD file again.
As a workflow grows, it may become more difficult to find where they are in the R environment or on the file system. It is recommended to use `locate_batons()` for this purpose. This also allows the user to define which **relay_type** to search for. This could be important if you have a mix of testing batons mixed in with ones being actively used.
110
+
111
+
```{r, eval = FALSE}
112
+
# Location on file system that has baton objects saved
113
+
work_loc <- '/my/fav/loc'
114
+
115
+
# Get list from location of interest, exclude all test batons
There are several helper functions to make it easier to examine contents of a baton, either within the R session or through the connection to the persistent YAML file.
For functions such as `summary` and `plot`, one may not want to load the baton directly. However, since these functions require a specific class to operate, one can not simply just read the YAML file. Instead, we can use the `preview_baton()` constructor and pass this to the appropriate generics.
0 commit comments