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

Latex reports folder #25

Open
JMoore5353 opened this issue Dec 9, 2024 · 1 comment
Open

Latex reports folder #25

JMoore5353 opened this issue Dec 9, 2024 · 1 comment

Comments

@JMoore5353
Copy link
Contributor

JMoore5353 commented Dec 9, 2024

There is a folder named "latex_reports" that has some useful information.

Should we generate the pdf version of the latex reports and put them somewhere, or just leave them as latex reports? Some of them contain useful information (somewhat outdated), and I reference the mixer report in the mixer change documentation.

I don't think they are super useful just staying there since they have low visibility. We should change how we do it if we want the reports to be useful.

@iandareid @bsutherland333 @gabesnow99

@bsutherland333
Copy link
Contributor

These originally were reports that were found in the rosflight_firmware repository, since that is also where the website documentation used to reside. I left them in there because I thought they could be useful, but wasn't sure what to do with them. If we want to use them we should make them more visible, otherwise we could remove them.

There use to be an algorithms tab in the documentation that had a pretty long report on the estimation scheme. I removed it since I thought it was overkill for what we wanted on the documentation, but if we want to still keep extensive academic type reports on the documentation, we could carve out a place for both the page I removed and any relevant reports. https://docs.rosflight.org/v1.3/algorithms/estimator/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants