Notebook review / advice

Hi, can you guys review my teams notebook and give it feedback please? Also, please note that this is a copy of our real notebook, so some slides towards the end are still in progress, and it is missing a few pages that have just been started. Lastly, because some members do not want their face to be shown, there are blank spaces, which are filled with photos, but they had to be removed.

Now, without further adew, Copy of 6546W Engineering Notebook - Google Slides

They are not just looking for material constraints (Page 13). You can also include time and manpower constraints.

1 Like

Here’s a list of all the things I saw (Your notebook is mostly great, just there are a few things I noticed):

  1. Page 17: The 1000 points combined is for autonomous and driver skills combined. The team with 100 scored about 480 in drivers and 520 in autons.
  2. Page 18: If you score a goal, there’s about a 95% chance of the switch being cleared at the end. (Rapid relay’s weird)
  3. Page 20: The hero bot’s catapult does have a variable drawback, but you need to put the catapult almost entirely all the way down to intake the ball. (My team has the hero bot still. :cry:)
  4. Page 22: You mention the H-drive not being able to climb over objects. That is true, but that is not a big problem in rapid relay, because there is nothing that it is legal to climb over. I saw that you said something about that on page 31, but you might want to also put that on page 22.
  5. Page 27: You might want to say something about not copying the Ben Lipper design and just using it as inspiration or a resource, so the judges don’t think you holecounted.
  6. Page 33 and 34: Are there supposed to be pictures there? There’s a gap in the text for them, but I can’t see one, even after reloading the page.
  7. Page 35: Adding an explanation of your code will probably get you some more points.
  8. Everywhere: Replace “I” with “We” to show teamwork.
  9. Page 40: The vex forum discussion is about V5 pneumatics, which are different than IQ ones. You can still use that in your notebook, just make sure to clarify that.
  10. Pages 42 and 43: It mentions that things happening would be “catastrophic”. You might want to mention what would happen if it did break and what you needed to do to fix it.
  11. Page 44: I think there’s a typo. It says “We have it coded out already.”
  12. Page 48: There’s a random “T” at the end. That’s probably a typo.
  13. Page 56: Explain how you tested the robot. The rubric for the notebook says that you need to explain how you tested the robot and what the test results were.
  14. Page 61: There are no problems, I’m just saying that I like your title. :smile:
  15. Page 89: You might want to use rectangles instead of circles for showing the sprockets on the intake. I saw it and I thought “Are those flywheels?”. You might just want to do that to make it a bit more clear to the judges what they are.
  16. Page 94: Clarify that the 02s and 03s are pins, not beams.
  17. Page 122: You might want to think of a better name than “Controller Controllering”. I like the name, but it’s not very descriptive.

That’s my list! Those are the problems I found, but overall, your notebook is great. Good luck at worlds! :smile::smile::smile:

6 Likes