Allow RtsGrp commands to accept non-contiguous ranges
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 46
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Currently the RtsGrp commands accept a range of RTSs from start_index to end_index. Instead, the command could accept a set of bytes where each bit corresponds to the RTS to start. This would allow the group commands to work with a range of RTSs that is non-sequential
Imported from GSFCCFS-1468
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the RtsGrp command implementation and any tests for start_index and end_index handling. Determine how a byte set should select non-contiguous RTSs, then confirm that group commands accept and execute those selections without breaking contiguous ranges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100