Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export Faults to a Config file #109

Open
dyldonahue opened this issue Jul 9, 2024 · 0 comments
Open

Export Faults to a Config file #109

dyldonahue opened this issue Jul 9, 2024 · 0 comments
Labels
architecture Re-imagining existing code & techdebt

Comments

@dyldonahue
Copy link
Contributor

Current Features

Right now, our fault table is written in c in statemachine.c, and its overwhelming.

Desired Additional Features

To improve the sophistication of our code, we should look to improve this by moving it to a better location. I would like this ticket to investigate and possibly implement some sort of config file (JSON, YAML) or scripting language (Python) or even something like Calypso to store our faults. The c code would then pull the data from this source.

One thing I would like to avoid however is introducing massive overhead. I don't really know what the time and space considerations of any of the above would entail, so lets make sure were not handicapping ourselves with this.

If for whatever reason, this is deemed not viable, lets atleast move our fault table to its own file; faults are a big enough module that they justify their own file instead of being buried in statemachine

Screenshots (as needed)

No response

@dyldonahue dyldonahue added the architecture Re-imagining existing code & techdebt label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Re-imagining existing code & techdebt
Projects
None yet
Development

No branches or pull requests

1 participant