geom_trajectory_segments: Plotting individual segments of the trajectory
In dynverse/dynplot2: Grammar of graphics for single-cell data

Plotting individual segments of the trajectory

geom_trajectory_segments(mapping = NULL,
  position_arrow = position_trajectory_arrows_middle(),
  arrow = ggplot2::arrow(length = ggplot2::unit(0.5, "cm"), type =
  "closed"), arrow_size = 1, shadow = if ("colour" %in%
  names(mapping)) {     dynplot::shadow() } else {     FALSE }, ...,
  data = construct_get_segment_info(position_arrow), show.legend = NA)

`mapping`	Set of aesthetic mappings created by `aes()` or `aes_()`. If specified and `inherit.aes = TRUE` (the default), it is combined with the default mapping at the top level of the plot. You must supply `mapping` if there is no plot mapping.
`position_arrow`	Where to place the arrows within the segments. Typically these are functions created by `position_trajectory_arrows_middle()` or `position_trajectory_arrows_boundaries()`.
`arrow`	specification for arrow heads, as created by arrow().
`arrow_size`	The size of the arrow relative to the line size.
`shadow`	Shadow specification as created by `shadow()`
`...`	Other arguments passed on to `layer()`. These are often aesthetics, used to set an aesthetic to a fixed value, like `colour = "red"` or `size = 3`. They may also be parameters to the paired geom/stat.
`data`	A function created by `construct_get_segment_info()`.
`show.legend`	logical. Should this layer be included in the legends? `NA`, the default, includes if any aesthetics are mapped. `FALSE` never includes, and `TRUE` always includes. It can also be a named logical vector to finely select the aesthetics to display.