Currently, creating a sortie object requires a tlog, a ulog, and an HDF5 file for the receiver data. However, some users might want to make sorties using single files, or some partial combination of these files. Additionally, users might want to add a bunch of files all at once, but not have proper naming schema for these files or know which files go with which sorties. Sortie objects might be hindering the ability to use files like this.
It might be better to just specify a bunch of files rather than organizing into sorties. This would also allow easier sorting and concatenating of mission and rx data, at the cost of viewing individual flight data during large measurements.
Currently, creating a sortie object requires a tlog, a ulog, and an HDF5 file for the receiver data. However, some users might want to make sorties using single files, or some partial combination of these files. Additionally, users might want to add a bunch of files all at once, but not have proper naming schema for these files or know which files go with which sorties. Sortie objects might be hindering the ability to use files like this.
It might be better to just specify a bunch of files rather than organizing into sorties. This would also allow easier sorting and concatenating of mission and rx data, at the cost of viewing individual flight data during large measurements.