haiwan
/
sledge
0
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
sledge/runtime/experiments/applications/ekf/one_iteration
History
Sean McBride 6dc172952c
refactor: assorted bash cleanup 		4 years ago
..
.gitignore feat: edf_one_iter framework 4 years ago
README.md chore: Move one_iteration test 4 years ago
edf_nopreemption.env feat: edf_one_iter framework 4 years ago
edf_preemption.env feat: edf_one_iter framework 4 years ago
ekf_raw.dat chore: Move one_iteration test 4 years ago
expected_result.dat chore: Move one_iteration test 4 years ago
fifo_nopreemption.env feat: edf_one_iter framework 4 years ago
fifo_preemption.env feat: edf_one_iter framework 4 years ago
initial_state.dat feat: edf_one_iter framework 4 years ago
run.sh refactor: assorted bash cleanup 4 years ago
spec.json chore: update tests to handle stricter validation 4 years ago

README.md

EKF

Executes TinyEKF as shows by You Chong's GPS example

In order to be compatible with the stdin/stdout model of serverless, the input and output files are binary concatenations of various C structs.

See main() in runtime/tests/TinyEKF/extras/c/gps_ekf_fn.c for specifics.

This test executes multiple iterations, comparing the binary result against a known memoized result stored at expected_result.dat.