digital filters: fix code blocks
This commit is contained in:
parent
2ea9e2145a
commit
37ced43dd1
|
@ -54,7 +54,7 @@ q_att = startracker(actual);
|
|||
```
|
||||
|
||||
Looking inside `startracker()`, we see that it pretty clearly indicates that we *are* the star tracker; every timestep, the code tells us, the adversary, what the true physical orientation is as a quaternion. We can act as the star tracker and send back a wxyz-format quaternion on stdin, which it will use as the star-tracker output (note that, for some reason, the code they give us uses space-separated floats and the actual challenge uses comma-separated floats):
|
||||
```{.matplotlib}
|
||||
```{.matlab}
|
||||
% Model must have a q_att member
|
||||
|
||||
function [ q ] = startracker(model)
|
||||
|
@ -78,7 +78,7 @@ endfunction
|
|||
```
|
||||
|
||||
Also note that in `challenge.m`, immediately after the star tracker call, checking the return value for consistency with the physical model is _commented out_. We can tell the satellite that it's pointing anywhere we like and it will believe us, although Kalman error might be bad:
|
||||
```
|
||||
```{.matlab}
|
||||
%err = quat2eul(quat_diff(q_att, target.q_att))';
|
||||
%if max(abs(err)) > err_thresh
|
||||
% disp("Error: No way, you are clearly lost, Star Tracker!");
|
||||
|
|
Loading…
Reference in New Issue