Sample "real-life" implementation of a cFS mission build.

Open
#150 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, docker
Domain
documentation

Research direction

Review the current cFS bundle, the cFS-101 training VM, and the OpenSatKit alternative described in the issue. Define whether the deliverable is a how-to guide, a complete Docker image, or both; done would be a publicly available mission-like example that demonstrates the intended purpose of cFS features.

Written by the indexing model from the issue text.

Description

docs

Is your feature request related to a problem? Please describe.
From the cFS Mailing list:

it would be nice to see a fully completed project to decipher why certain features are used. The how is easy to digest from the documentation but a real-world example would help clarify each feature’s intended purpose.

I know a lot of this code may be internal to NASA / other organizations but it would be really helpful to have a completed demo to reference from time to time.

Describe the solution you'd like
A how-to guide or a complete docker image with a mission-like cFS implementation.

Describe alternatives you've considered
The current bundle, partnering with open-sat kit

Additional context
Also from the mailing list

I have also been pulling apart the training VM provided by the cFS-101 repo. It would be incredibly helpful if anyone had any open source projects that I could see, it just always seems that looking through an already completed project is the best way to learn new things and their intricacies.

Requester Info
@astrogeco

Dominant language
C
Stars
1.5k
Forks
391
Avg merge
1d 11h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nasa/cFS

All issues in nasa/cFS

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.