Software future

[314PiGuy]

What is at least 1 thing you would want to have or get done in the future regarding software?

[Advay17]

I would like to implement unit tests into our code using sim to ensure that our code is at least at some level of stability.

[314PiGuy]

I would like to have better communication with mechanical especially during competition season to prevent issues stemming from hasty planning and subsequent reliance on temporary solutions.

[VMFortress]

Did you have specifics in mind you feel caused issues?

[314PiGuy]

The biggest issue I thought was how the mounting of the pi case seemed too quick of a decision, probably because everyone thought it would not be as important as other things. It turned out to be problematic though with things like the warping and the fan assembly breaking.

[shreshtaparthaje]

I would like to document every major change/implementation so that other members can read and understand what is going on.

[ironon]

I would like to graduate and go to college

I would like to see software consistently do stuff to improve stuff in the long term, not just short term need-to-happen things.

[NadiaAdams]

I would like to create or copy a piece of code for a mechanism, and then comment what each line/block of code does. This would be for new members to learn from, or even as a reference for current-but-still-learning members.

[VMFortress]

Any idea which you might like to start with? For our subsystems we have:

• Arm (the part that actually moves up and down)
• End Effector (more so the rollers on the arm that move the coral in and out + the LaserCANs with them)
• Elevator
• LEDs
• Vision (Maybe a bit of a larger thing)
• Drive (which might be a lot but probably has a few smaller parts)
  • Drive overall
  • Gyro
  • Swerve Modules

[NadiaAdams]

End effector (maybe with laserCANs? i'm not sure how difficult that would be to explain) and arm sound the easiest for now. as I gain more experience and learn more about coding an frc bot, I would like to create more sample pieces of code like this that just explain each block of code, especially to ease new members into this level of coding. for now, I am not at that level, and would most likely need someone to teach me what is going on in one of these mechanism codes.

[Advay17]

If you do need help with anything, I could maybe help sometime before or during a meeting! I also do agree that end effector and arm are a good place to start, because they get you covered on both rev and ctre knowledge. LaserCANs should be easy to set up as well, though I am less knowledgeable about them.

[Advay17]

Also #40 and specifically #76 relate to this!

[ComradeDev]

Store documentation on how the robot works and how the components work in a wiki page or another storage option. This would be nice for newer members to refer back to if they have any issues.

[VMFortress]

A great way to do this is just pick something you want to do, whether you know or not, and start doing it and write down your steps as you go. Then those notes can be cleaned up and/or discussed and then put in the wiki or elsewhere. This goes for anyone that wants to contribute in this way, not specifically you.

[Advay17]

#40 and specifically #76 relate to this!

[Rohit1046]

I would like to ensure that we are able to complete tasks in an organized manner, and on time, and are able to enter competitions prepared and confident in our software, so we don't have to scramble to make last minute changes.

[guineapig25]

I would to work on:

• 3 coral auto
• fixing auto align & other competition essentials
• personally rereviewing the code so I can learn more
• Getting more sleep and studying for AP Exams

[guineapig25]

Everyone please, Schoolwork and AP Exams are a top priority! Don't blow them off!!!

[VMFortress]

Absolutely recommend everyone participating in the code reviews in Pull Requests! Even if you don't understand 99% or what's in there, you may see 1% of "That comment is misspelled" or "that should be greater than, not less than" which is helpful while also getting your eyes on the code to become more familiar!

[VMFortress]

Also, let's get our two coral auto before the three lol

[Nall-s]

Adding documentation on how to code different features of the robot is crucial (like adding comments in files, etc.), and I would also like to take some time and go over software essentials (like how auto, vision, and mechanism code work).

[VMFortress]

Any areas you have interest in starting? Mechanism is probably the simplest (especially once the sim is fully working) and there are a number of options.

And PRs are always welcome to get you accommodated with the process! Even if it's just a single line change with adding a comment on something you don't think is clear. And on top of that, even if you're not sure the comment is 100% right, that's what the code review is for!

[Nall-s]

I'd like to start on mechanism code (since that's what I'm most familiar with) but I'm also very interested in looking into how vision and auto works. I think what you said about reviewing code files and making comments seems like a good start!

[Advay17]

#40 and specifically #76 relate to this!

[InfinityJuice]

I would like asynchronous work to be assigned/made clear (I know we have just started using github issues, which is definitely good) and I know a lot of other people said something about writing comments for the subsystems, and I did this over the break but I haven't finished (I will probably be done tonight or tomorrow night and will upload a branch, but I think a lot of the other new members should also do this in order to learn more independently to see what they can find out).

[VMFortress]

Looking forward to the comments! I definitely agree all new members should contribute to this and hopefully some work up front will help be an example to others.

[EshanNayak]

One thing that I think we should have that I don't I've seen mentioned yet is more so for during competitions. I feel as though there wasn't much communication with what we did regarding software in between matches. Even just a heads up would make sure everyone knows what's going on during a competition.

[VMFortress]

Agreed. It can be a bit nerve-racking when the match is about to start and no one knows what to expect!