Description
Description
The cFS backend is lacking in features when compared with other backends like ROS and F'. In particular, it doesn't accept a specification as input, which means that the user must take an additional step of extracting the variable names and handlers from the spec before using the cfs command.
The cfs command should accept the same flags as other commands like ros and fprime, use an input spec if provided, and accept selecting the format for the file and the properties, as well as an external pre-filter or pre-processor.
Type
- Feature: Add to cFS backend features available in other backends.
Additional context
None.
Requester
- Ivan Perez.
Method to check presence of bug
Not applicable (not a bug).
Expected result
The cfs command accepts the same flags as other commands like ros and fprime, uses an input spec if provided to determine the variables and handlers to use in the cFS application, accepts selecting the format for the file and the properties, and can filter properties via an external pre-filter.
Desired result
The cfs command accepts the same flags as other commands like ros and fprime, uses an input spec if provided to determine the variables and handlers to use in the cFS application, accepts selecting the format for the file and the properties, and can filter properties via an external pre-filter.
Proposed solution
Modify cFS backend in ogma-core by porting over features from the ROS and FPrime backends to read and process input specifications.
Update README to document the new arguments available.
Further notes
None.