At this point the concept of a data source is only really used by hydrobot as a way to construct the full measurement name for the server call, and to parse the info from the server response.
In batch processing, this means that each measurement is treated as a different processing operation. In cases where a data source have multiple measurements this causes some silly things to happen.
It would be useful if we could group all these together somehow. Sam suggested we call them "Data Source Types", so that "Water Temperature" contains all of the related measurements under it.
Since we still have unique processors per data source type, we could specify an additional parameter that separates the measurements, e.g. "altitude" for AT or "depth" for DO and WT. This could simply be specified in the .yaml file along with the data source type.
At this point the concept of a data source is only really used by hydrobot as a way to construct the full measurement name for the server call, and to parse the info from the server response.
In batch processing, this means that each measurement is treated as a different processing operation. In cases where a data source have multiple measurements this causes some silly things to happen.
It would be useful if we could group all these together somehow. Sam suggested we call them "Data Source Types", so that "Water Temperature" contains all of the related measurements under it.
Since we still have unique processors per data source type, we could specify an additional parameter that separates the measurements, e.g. "altitude" for AT or "depth" for DO and WT. This could simply be specified in the .yaml file along with the data source type.