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

Port IR@Home Guides #1599

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Kevin-OConnor
Copy link
Contributor

Port of the guides from 2021 IR@Home guides. Still have to look at the vision one, not sure if that is going to make sense as it's own new doc or a revision/merger with "What is Vision?" and/or "Strategies for Vision Programming". The other two guides about selecting drivers and practice don't seem to fit FRC Docs and will find another home.

Port of the autonomous guide from 2021 IR@Home guides
@jasondaming
Copy link
Member

We should probably pull the "Simple Autonomous Example" out of step 4 if we have this.

@Kevin-OConnor
Copy link
Contributor Author

We should probably pull the "Simple Autonomous Example" out of step 4 if we have this.

Not sure I agree with that. That section is a short description of code that is in the example project and helps them understand what it does.

This article provides a more (very) high level overview of autonomous movement in general and how to program your own.

@jasondaming
Copy link
Member

I think the nested bullets don't format well here and would use (sub)headings. Under those I think bullets will be fine but IMO multiple layers of bullets aren't very readable.

I would split up the external sensor between cameras and other. Similar to internal.

Seems like the bullets under choose an approach could just be integrated into their sections. I would at least remove the word approach on both of the approaches.

Use tabs to separate LV vs text based. It is hard to combine them. Not a big fan or sequence structures in LV. Teams use them as a crutch and abuse them. Just use dataflow, adds another reason to connect error wires.

@jasondaming
Copy link
Member

Additional things I think it would be helpful to discuss:

  • Placing the robot on the field. Many teams don't realize how important this is for Auto repeatability. Placing in relation to field elements to add repeatability. A note about using a measuring device (need to fight so many thinking this is illegal, assuming the rules hold) in relation to nearby field elements to make placement quicker. Use feet or some some other known quantity to measure if a tape measure becomes illegal again (please don't do this).

  • Auto Strategy - Encourage teams to think about where their partners will want to place their robot and to consider having a backup routine for when their ideal spot is taken. Can show/link Sendable Chooser and the LV auto selector here.

  • Setting your robot up to play the rest of the match- I am a big fan of teams trying to do something to try and get in a better position for the rest of the match. It can save precious seconds. This could possibly go into other potential improvements.

Copy link
Member

@Daltz333 Daltz333 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the smartquotes to regular quotes? They mess things up somewhere (I don't remember why).

@Daltz333
Copy link
Member

@Kevin-OConnor should this be closed?

@Kevin-OConnor
Copy link
Contributor Author

I don't think so, I think we still want this content, not sure why I never took it off Draft. Looks like it probably needs an update or two now (I saw at least Ramsete at a quick glance)

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

Successfully merging this pull request may close these issues.

3 participants