This super issue will track the progress of YAMCS integration at a high level. The idea is to make Hermes a "processor"/"plugin" of YAMCS which does the following:
- Handles events in the JPL style
- DP processing on top of file downlink
- (main addition) Adds a plugin to export the Hermes gRPC protocol to the frontend
To do the main part of this task (3) some changes will need to be made to the Hermes model:
- Expand the gRPC API to fully encompass the backend API
- More deeply integrate dictionary with "connection" (i.e. FSW, we should rename that to instance to match YAMCS, it's a good name)
- Redesign of the gRPC:
- We should follow YAMCS style of static load-type configuration, it makes everything simpler...
- Pull out more of the processing into the configuration:
- Possible to make generic data processors, we should do it through stdio like LSPs
- These can be reusable and wrapped to make YAMCS plugins which will be lower performance...
Eventually I'd like to bring Hermes up to par with YAMCS but in the near term full integration is probably best.
This super issue will track the progress of YAMCS integration at a high level. The idea is to make Hermes a "processor"/"plugin" of YAMCS which does the following:
To do the main part of this task (3) some changes will need to be made to the Hermes model:
Eventually I'd like to bring Hermes up to par with YAMCS but in the near term full integration is probably best.