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

Implement component Mission Protection System (MPS) #11

Open
2 of 5 tasks
podhrmic opened this issue Apr 4, 2024 · 7 comments · May be fixed by #116
Open
2 of 5 tasks

Implement component Mission Protection System (MPS) #11

podhrmic opened this issue Apr 4, 2024 · 7 comments · May be fixed by #116
Assignees
Labels
application software application software components SoW TA2.1.1.A Develop the Open SUT primarily using existing components and specifications. SoW TA2.1.1.C Develop CN specifications for components with rich code-level specifications.
Milestone

Comments

@podhrmic
Copy link
Collaborator

podhrmic commented Apr 4, 2024

Summary

MPS is an engine protection system. Redundant, measures engine temperature and pressure, and shuts down the engine if unsafe values are detected.

Acceptance Criteria

MPS conforms to the architecture specifications, component requirements and can be run in the OpenSUT infrastructure. Split into multiple tasks if needed.

Do

@podhrmic podhrmic added the application software application software components label Apr 4, 2024
@podhrmic podhrmic added this to the MVP 1 milestone Apr 4, 2024
@podhrmic podhrmic changed the title Implement Component Mission Protection System (MPS) Implement component Mission Protection System (MPS) Apr 4, 2024
@thatplguy
Copy link
Contributor

Update 4/26

Roughly halfway done, hitting more CN issues as porting more. Working with UCam to understand/resolve. Making extra content for the tutorial in the form of personal notes, to be added to the tutorial in the future.

CN workflow is currently:

  • something doesn't work
  • look hard at the HTML output
  • magic happens (needs very expert insight)
  • thing is fixed

Would be very helpful to surface more insights – not necessarily more detail, but more helpful information.

Notes:

  • Santiago: Useful debug technique is finding a minimal example that reproduces the bug. Drop these in the CN MM channel!
  • Iavor: Would be great to note down what the tool could/should have done to help in these tricky/stuck cases.
  • Mike: Try making an error diary – write down the mistake/annoyance/friction.

@podhrmic
Copy link
Collaborator Author

podhrmic commented May 3, 2024

@peterohanley can you open a draft PR with the code you have so far?

@podhrmic
Copy link
Collaborator Author

To clarify - an appropriate span of a commit is a single file with ported specs.

@podhrmic podhrmic added SoW TA2.1.1.A Develop the Open SUT primarily using existing components and specifications. SoW TA2.1.1.C Develop CN specifications for components with rich code-level specifications. labels May 29, 2024
@podhrmic podhrmic modified the milestones: MVP 1, MVP 2 Jun 19, 2024
@podhrmic podhrmic modified the milestones: MVP 2, MVP 3 Jul 15, 2024
@podhrmic
Copy link
Collaborator Author

@peterohanley are the issues listed above resolved now?

@podhrmic podhrmic linked a pull request Sep 26, 2024 that will close this issue
@podhrmic
Copy link
Collaborator Author

Blocked on GaloisInc/VERSE-Toolchain#124

@podhrmic
Copy link
Collaborator Author

Due date 12/4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application software application software components SoW TA2.1.1.A Develop the Open SUT primarily using existing components and specifications. SoW TA2.1.1.C Develop CN specifications for components with rich code-level specifications.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants