Articles by tag: organization

Articles by tag: organization

    Super Regionals - The First Day

    Super Regionals - The First Day By Ethan, Evan, Tycho, Max, Jayesh, Janavi, Caitlin, Darshan, Omar, Charlotte, and Austin

    Task: Go to super regionals, set up, and present

    Way too early in the morning, on March 22nd, the Iron Reign team gathered in darkness. It was approximately 65 Farenheit and gusts around 12 mph were blowing in from the South. Under this cover of darkness, a bus pulled into our school. As the trees shivered in the wind and the stray dogs around our school howled, we boarded the bus.

    Of course, we were boarding the bus to head down to Athens, GA, to go to the South Super Regional tournament, and we hoped, to advance to Worlds. On our way there, we stopped at Sunset HS to pick up RoboBison Amistad, the other team from our school district. Then, we two teams were on our way.

    No road trip operated by DISD can ever be simple, and this one was no exception. Our coach was driving our chase vehicle AKA our robotics RV, but managed to beat us there by five hours. The team ended up being on the same bus for twenty total hours, stopping three times. Luckily, on our way down there, many of us got to see sights such as the Mississippi River for the first time.

    Finally, we arrived in Athens at 1 in the morning. Some of the team split off to sleep, while others broke off to work on the robot. But, it was late, and we all went to bed soon.

    The next, first real day of the tournament, we woke up bright and early. We were one of the first ones to have pit load-in, and we actually managed to do everything in a timely manner. Our tent that we designed was slightly bigger than we thought, but the teams neighboring us were fine with it, so everything worked out in the end. We did a little bit of preliminary scouting and talked to a few teams. We also got our robot through inspections.

    Finally, we went into judging, and it was the best presentation that we've done this year. We had two new team members added to the presentation, and we pulled it off flawlessly. As well, we added a new visual gag, with Darshan jumping out at the judges from under the cart. We got asked some very good questions that I can't remember, but the judges were generally very impressed.

    Reflections

    See Postmortem.

    South Superregionals Day Two

    South Superregionals Day Two By Max, Tycho, Omar, Jayesh, Darshan, Austin, Charlotte, Caitlin, Evan, Ethan, and Janavi

    Task: Reminisce on our first six Superregionals matches

    After a decent night's rest, we began Day Two at around 7 AM. A lot of our tools and materials were still on our RV, so we first moved them over to our pit. Our match schedule said that we'd have nine matches beginning with Match #1 (just our luck). After the...interesting Pokemon-themed opening ceremonies, we began the day with our first match.

    Match 1: Our alliance partner was Thorn's Army, and we faced Greased Lightning and Guzzoline Robotics. We lost; we didn't earn as many points in autonomous or teleop. It was our first game anyway; just a warmup. No big deal.

    Match 2: Our alliance partner was Saber Robotics, and we faced Aperture Science and The Prototypes. We lost; tied in teleop, but our autonomous didn't score as much as theirs. Warmup game #2, no big deal.

    Match 3: Our alliance partner was 4-H Rohming Robotics, and we faced Team Duct Tape and Twisted Axles. We won; even though neither of us were able to cap, we nailed our autonomous and teleop periods.

    Match 4: Our alliance partner was Static Void, and we faced East Cobb Robotics and Team CHAOS. We won; our autonomous didn't score as much (we missed a beacon and a ball), but our partner was able to cap and our combined teleop scored more.

    Match 5: Our alliance partner was LASA MurPHy, and we faced Diatomic Dingos and Blue Crew, Too. We won; our autonomous worked great and scored well, which made up for our lackluster teleop period.

    Match 6: Our alliance partner was Technical Difficulties, and we faced the Rockettes and LASA Ultra Violet. We won; once again, our autonomous worked great (we missed a ball though), we scored more particles in teleop, and our partner was able to cap. Four in a row!

    We felt pretty good about this day, since we came off of a four win streak. However, we still worked as long as we could on improving the reliability of our autonomous. Once the pits were closed, we were directed to the team social, where there was Super Smash Bros. and DJ Mickey Nightrain. It seemed like a fun time (Tycho tried his best at professional Smash), but roboticists usually aren't the type to be out on a dance floor. Jayesh is an exception because he's weird.

    As well, we were interviewed by a few groups of judges, and performed well in the interviews. We froze up a few times, but it worked out. Also, we invited some of the judges onto our RV.

    Reflections

    Even though we were able to do a lot of work this day, we're slightly disappointed in our tiredness. Even though the RoboBisons had brought an entire field with them, we didn't really think about asking them to let us use it to practice. We were very exhausted, and with a half-still-sick Mr. Virani, we think we just weren't enthused enough to stay up late and do some more work. If we had, we might've had the small bit of reliability we needed to win more matches with just our autonomous. ;-; Either way, we're proud of the work we did. Tycho did a great job driving for all the matches. Note for next year - we neeeeeeeed more than one driver. On to Day Three!

    South Superregional - Day Three

    South Superregional - Day Three By Jayesh, Tycho, Omar, Max, Darshan, Austin, Charlotte, Caitlin, Evan, Ethan, and Janavi

    Task: Reminisce on our last three Superregionals matches

    Our final competition day began with the driver team rushing to the pits because of a warning given by the game officials for the first match's teams to reach the pits earlier than expected. We reached in time, in fact about an hour before the match actually began. This mild inconvenience did give us time to formulate a strategy against our opponents, the high-scoring mechromancers.

    Match 1: Our alliance partner was Neutrinos, and we faced Mechromancers Redfish. We lost; The Neutrinos disconnected early and we had made a strategy of denying the scoring of the Mechromancers. We were relatively succesful, halving their usual scoring output, but without the expected scoring of the Neutrinos, we lost.

    Match 2: Our alliance partner was Guzzoline Robotics, and we faced Mouse Spit and Browncoats. We won a very close game, where a blocking penalty by Mouspit helped us win our closest game of the tournament.

    Match 3: Our alliance partner was KNO3, and we faced The League of Legendary Scientists and Tundrabots. We lost a 15 point game, where a miscue in our autonomous positioning proved fatal and cost us the winning points of the match.

    The match schedule we had today would be our toughest sleight of games for the entire tournament. Despite the unfortunate circumstances of the Neutrinos disconnecting early into our first match, we played decently well and had close games against our toughest competition.

    Reflections

    Our last loss ended up proving worse than anyone could've expected. In the award ceremony we figured out we were one spot on the leaderboard from advancing. Due to our aquisition of the Judge's award and our position on the leaderboard, we were named first alternate for Worlds. Unfortunate for us, we hope to do better next year.

    So, You're Writing a Blog Post

    So, You're Writing a Blog Post By Ethan

    Frontmatter

    layout: Do not touch.
    title: Title of your article (you can't use hyphens or colons.) tags: Enter as comma seperated list, case insensitive. Try to use one award and one normal tag

    • Tips - tips and tricks for other teams.
    • Journal - working on the journal, blog, and posts like this one.
    • Outreach - volunteering and special events. Ex. Moonday, NSTA
    • Mechanical - work on the robot, parts, building, ect.
    • Software - programming.
    • Business - grants, funding, ect.
    • Organization - organizing, cleaning physical things.
    • Video - if you have a video, nothing else.
    • Private - will NOT show up on the blog page
    • Pinned - pins post as first on the homepage until the tag is removed.
    • Inspire - (award) all around good posts, important things for judges like NSTA, or a post going over our robot in detail
    • Connect - business award
    • Innovate - design process and uniqueness award
    • Design - award about how well documented and designed your robot is
    • Motivate - recruitment, representing STEM/FIRST
    • Control - coding award

    section: Choose team, engineering, or business.
    personhours: Calculate using # of people * hours worked. One number.
    rolecall: People who participated in the post, comma seperated. Author of post goes first.

    REMEMBER: keep the space between the colon and the information, and dont touch the "---"s.

    Rules

    Task: Used for succinctly describing what you did
    Body of Post: Describe what you did, how you did, ect..
    Reflections: Used to say how something worked out, your creative process, expectations, ect.
    Images: Must be 600px wide. Use as many as you'd like. Save in images.
    Videos: Use the default YouTube embed.
    Embedded Insta/Twitter Posts: DON'T put in the first paragraph. You will break the blog.
    Filenames: Save as YYYY-MM-DD-NAME.html in _posts. If unfinished, Draft-YYYY-MM-DD-NAME.html

    Meeting Log

    Meeting Log September 09, 2017 By Ethan, Evan, Abhi, Tycho, Austin, Karina, and Kenna

    Meeting Log September 09, 2017

    Today was the first meeting of the Relic Recovery season. Our main focus today was strategy, then organization and getting the robot ready for this year's challenges

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Write blog post for Kickoff
    • Fix dates for indexPrintable
    • Blog post catchup
    • Strategy review

    Software

    • Glyph recognition OpenCV
    • Aspiring programmer's code review

    Build / Modelling

    • Teardown old robot
    • Design Competition - glyph grabber

    Service / Outreach

    • Kickoff

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanKickoff post2:002
    EthanFix dates4:002
    EvanDesign Competition2:004
    AustinTeardown robot2:002
    AustinDesign Competion4:002
    TychoCode review2:004
    KennaBlog review2:004
    KarinaStrategy review2:004
    AbhiStrategy review2:004
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001
    PeopleTask2:001

    Meeting Log

    Meeting Log September 16, 2017 By Ethan, Evan, Karina, Tycho, Austin, Charlotte, and Kenna

    Meeting Log September 16, 2017

    Today we had a major outreach event at Conrad HS in DISD which served around 450 people. We also planned on continuing our building competition, working on strategy, the blog, and the robot teardown.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Conrad post
    • About page - new members
    • Strategy

    Software

    • Code review

    Build / Modelling

    • Complete robot teardown
    • Finish design competition
    • Install REV hubs

    Service / Outreach

    • Conrad HS volunteering

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanConrad post2:002
    EthanAbout page4:002
    EvanDesign competition2:004
    AustinRobot teardown2:001
    AustinREV hubs3:001
    AustinDesign competition4:002
    KarinaAbout page2:002
    KarinaStrategy4:002
    TychoCode review2:004
    CharlotteConrad post2:004

    Meeting Log

    Meeting Log September 23, 2017 By Charlotte, Kenna, Tycho, Austin, and Evan

    Meeting Log September 23, 2017

    We started the day by volunteering at LV Stockard MS, another DISD event. During our practice, we planned to work on robot design, blog updates, and code testing.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • About page updates
    • Stockard blog post

    Software

    • Controller mapping

    Build / Modelling

    • Cryptobox grabber - competition judging
    • Install chosen grabber
    • Reposition robot hubs

    Service / Outreach

    • Stockard MS DISD

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    CharlotteStockard post2:002
    CharlotteCompetition judging4:002
    KennaAbout page2:002
    KennaCompetition judging4:002
    TychoController mapping2:004
    AustinCompetition judging2:002
    AustinInstall grabber4:002
    EvanCompetition judging2:002
    EvanMove hubs4:002

    Meeting Log

    Meeting Log September 30, 2017 By Ethan, Evan, Tycho, Austin, Kenna, Karina, Austin, and Abhi

    Meeting Log September 30, 2017

    Today was based around prepping for our meeting with DISD adminmistrators, getting our robots in working order, and organizing parts for the season.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Fix stats page
    • Strategy

    Software

    • Program lift
    • Program grabber

    Build / Modelling

    • Fix lift string system
    • Add lift supports

    Service / Outreach

    • DISD prep

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanFix stats page2:002
    EthanDISD Prep4:002
    EvanLift supports2:004
    AustinLift string2:004
    TychoProgram lift2:002
    TychoProgram grabber4:002
    KennaLift supports2:004
    KarinaStrategy2:004
    AbhiStrategy2:004

    Meeting Log

    Meeting Log October 07, 2017 By Ethan, Evan, Austin, Tycho, and Charlotte

    Meeting Log October 07, 2017

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • DISD post
    • Fix old post formatting
    • Stockard MS

    Software

    • Begin autonomous

    Build / Modelling

    • Fix robot - was dropped
    • REV hub relign 2
    • Realign square base

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanDISD post2:002
    EthanFix formatting4:002
    EvanFix robot2:002
    EvanRealign4:002
    AustinFix robot2:002
    AustinREV realign4:002
    TychoAutonomous2:004
    CharlotteStockard post2:002
    CharlotteJournal review4:002

    Meeting Log

    Meeting Log October 14, 2017 By Ethan, Kenna, Abhi, Austin, Janavi, Evan, Charlotte, and Tycho

    Meeting Log October 14, 2017

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Learn to blog
    • UTA post
    • Teach how to blog
    • Strategy post

    Software

    • IMU testing
    • Autonomous

    Build / Modelling

    • Install wheel mounts
    • Test string for lift

    Service / Outreach

    • UTA volunteering

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanTeach how to blog2:002
    EthanFix formatting of posts4:002
    KennaLearn to post2:002
    KennaUTA post4:002
    AbhiStrategy post2:004
    AustinWheel mounts2:004
    EvanString test2:004
    CharlotteLearn to blog2:004
    TychoIMU2:002
    TychoAutonomous4:002

    Meeting Log

    Meeting Log October 21, 2017 By Ethan, Tycho, Evan, Abhi, Charlotte, and Karina

    Meeting Log October 21, 2017

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Travis blog post
    • Work on presentation

    Software

    • Work on openCV integration
    • Test out RoboRealm

    Build / Modelling

    • Robot drive practice
    • Learn PTC
    • Jewel thief mockup

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanWork on presentation2:004
    TychoTravis blog post2:001
    TychoOpenCV3:002
    TychoRobotRealm4:002
    CharlottePTC2:004
    AbhiPTC2:004
    KarinaDrive practice2:004
    EvanJewel thief mockup2:004

    Meeting Log

    Meeting Log November 03, 2017 By Ethan, Evan, Tycho. Austin, Charlotte, Karina, Janavi, Kenna, and Abhi

    Meeting Log November 03, 2017

    Today is one of the last full meetings until our tournament, so we need to get everything ready for judging. This post also includes the objectives for the next week.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • 3 posts from each member
    • DISD Scrimmage post
    • Field build post
    • Strategy\Business plan
    • Print notebook
    • Finish presentation
    • Presention practice

    Software

    • Autonomous
    • Drive practice

    Build / Modelling

    • Respool string
    • Robot tuneup

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    Ethan3 posts2:002
    EthanFinish presentation4:002
    EvanTuneup2:004
    TychoAutonomous2:002
    TychoDrive practice4:002
    EvanDrive practice2:004
    AustinDrive practice2:004
    AustinTuneup2:004
    JanaviWork on presentation2:004
    KennaPrint notebook2:004

    Spring Cleaning in the RoboDojo

    Spring Cleaning in the RoboDojo By Janavi, Evan, Ethan, Austin, Tycho, Karina, Charlotte, Kenna, and Abhi

    Task:

    A few weeks leaving for our Oklahoma competition we assembled a large garage tent upon the pool deck and moved our field inside the tent to shield it from the weather. The night before the competition we moved in a projector so we could project see the code on the wall and left it there when we went to Oklahoma. We were very surprised when we came back to Dallas around midnight and found the canvas that was supposed to be covering the tent crumpled in the corner of the backyard and the frame of the tent on its side resting again the tree as you can see in the photo below

    But what surprised us the most was that nothing that we let upon that table was disturbed at all, the projector lay in the same spot and even a glass of water we had left hadn't moved an inch.The next day we came back, well rested and finally wrestled the RoboDojo back from the grasps of the tree and bolted it down to the pool deck to prevent any future mishaps.

    After that we started to move robotics stuff outside and Max placed a board hole onto the wall with hooks so we can hang up the tools for easy access.

    We moved out all shelves that overflowed with boxes upon of boxes of robotics parts to the RoboDojo. Our plan is to move all of the robotics building out to Dojo that way we have easy access to the field and don't have to constantly move in and out to test. To start the move we labelled shoe boxes with bright orange tape to organize all of the tools and parts ,

    after that we started sorting through the shelves someone exclaiming almost every five minutes " I was looking for that last time! ". Eventually after getting most of the big items sorted we worked on organising the smaller items like hex keys and nuts into grid containers.

    Reflections

    Making this big move has really helped us not only with organization but it has allowed us to do a deep clean of all the robotics parts, we sorted thorough all of our old motors and battery and found some that either didn't work any more or were outdated. This is very important to do periodically because it allows us to make more space and it eliminates the chance of us bringing broken battery to competitions. Moving all of the items outside has taken us a while and we are still currently still moving items outside but so far it has had an immediate effect, our two teams have been able to do more testing and we are able to spend less time searching for stuff ever since we organized. Since this has been so helpful to our teams we might plan to make this a yearly occurrence, during summer or after our season ends we can spend two weekends completely reorganizing the Dojo.

    Meeting Log

    Meeting Log December 09, 2017 By Ethan, Evan, Tycho, Austin, Janavi, Charlotte, and Abhi

    Meeting Log December 09, 2017

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Write post-mortem
    • Update past MeetLogs

    Build / Modelling

    • 3D-model
    • Work on robot flipper

    Service / Outreach

    • Build 2nd field

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EvanFlipper2:004
    AustinFlipper2:004
    Abhi3D Model2:004
    EthanPost Mortem2:002
    EthanField4:002
    JanaviField2:004
    CharlotteField2:004
    TychoField2:004
    KarinaField2:004

    Qualifier Preparation

    Qualifier Preparation By Kenna, Abhi, Karina, Charlotte, Tycho, Janavi, Ethan, Austin, and Jayesh

    Townview Prep Pic

    We have been preparing to host our own qualifier since November when we hosted a DISD Scrimmage. Now we have to prepare our school for 26 teams to compete tomorrow. Most of our team was there to help construct the fields. The highlight of my Friday night was dragging assorted metal chairs across the cafeteria, only to be told we only wanted to use the black chairs and spending 2x longer than needed to make our audience seating. However, we were lucky enough get lots of help from our friends in DISD, Townview, and FTC Team 7172, which eased my chair-sorting pain. Our team has made several fields together and should have been more efficient in communicating and managing our time. But that is something to learn and improve on next time. In the end, however, it went smoothly because there was lots of teamwork between 6832 and Townview volunteers once everyone had time to figure out how to best assemble the field.

    The main point we'd like to drive home is that you *really* have to consider logistics when setting up a tournament. While you'll consider all the big things before the final day, such as making maps, printing flyers, and placing fields; some of the smaller items can be ignored. A prime example is that we put off figuring out the judging room locations and had to figure that out; another example that we forgot to do is have a pit organization. It would have majorly helped had we organized the pit by team number or some other order for queueing, or at least had made a map of teams beforehand.

    Alumni Meeting

    Alumni Meeting By Ethan, Abhi, Karina, Austin, Tycho, Kenna, Charlotte, Janavi, Darshan, Jayesh, and Omar

    Task: Talk with our former members

    Since we're in the last weeks of December, our schools are legally obligated to let us out. And, while colleges aren't legally mandated to let their students out, they tend to do so, as not doing that would rather enrage their students and families. So, due to this fortuitous coincidence, us simple FTC students were able to work with their dearly departed alumni to fix various problems with our team, mainly the blog.

    Besides it just being nice to see all our former members come back home, we were also able to gain knowledge from their experiences in college. As well, several of our members became judges for FTC tournaments, so they were able to provide valuable insights into the judging process, which we highly appreciate. Also, as you see in the above photo, you can see we got p-r-e-t-t-y l-i-t.

    Blog Fixes

    post problem
    PID & balance everything
    rev robot reveal write more
    PID further everything
    zygote write more & picture
    makeshift glyph why tag and task
    Birth connect --> more posts
    stockard meet folkloricos people
    childhood see birth
    rail test elaborate on wear & tear
    testing materials reflective
    designing the grabber fix frontmatter & emphasis
    oh no! dying glyphs everything
    v2 hexifier everything
    7-Oct fix pic
    chassis upgrade remove extra paragraph
    pick and place talk about code not just place
    machine vision goals more reflective & how to implement
    wheel protection after photo talk about engineering & link related
    garage WE, usefulness
    ptc creo tutorial reason for making video
    intake WE, reflection
    OK qualifier fix rick roll
    grabber v3 fix drawing & reflection
    *Pinned Posts* change + shorter posts
    working auto more than code
    how to RV 10 --> 6
    DISD sponsorship GRAMMAR, why we received
    gripper construction more words --> strategy, hyperlink
    *make new post, talking to alumn jayesh pic @ competition
    designing jewel arm WE, new pic
    building field GRAMMAR, head + free + DISD
    adding code fixes 2 robot more than code
    greenhill FTC positive spin & analysis
    driving struggles WE, reflect
    gripper p2 more words, WE
    make code readable more writing, explain process
    business plan ethan upload
    all evan posts
    evan need 2 add, connect posts to each other, more img
    all abhi "fixes" Someone pls review these "fixes"
    all code post tycho add

    Our blog is one of our most important parts for competition, as it allows us to communicate our ideas, designs, and engineering process to judges. Through the help given by our former alums, we hope to improve our chances at Wylie East.

    Meeting Log

    Meeting Log December 23, 2017 By Abhi, Karina, Austin, Tycho, Kenna, Ethan, Charlotte, Janavi, Darshan, Jayesh, and Omar

    Meeting Log December 23, 2017

    Our team alumni visited practice today. They imparted their knowledge to us in terms of the blog and our build plans.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Use alumni reccomendations with number and content of blog posts.

    Software

    • Investigate ways to pick up glyphs during autonomous
    • Review OpenCV viewing of cryptobox

    Build / Modelling

    • Complete frame of gripper arms v3
    • Assemble new gripper arms

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:00pm.25
    AllRecap Townview Qualifier2:15.5
    AustinAssemble Gripper arms2:453
    AbhiComplete frame v32:452
    KarinaComplete frame v32:452
    OmarHelp build ideas2:452
    DarshanHelp build ideas2:452
    KennaFix Blog2:452
    JanaviFix Blog2:452
    CharlotteFix Blog2:452
    JayeshIdentify fixes in blog2:452
    Karina3-D Model4:451
    Abhi3-D Model4:451
    PeopleTask2:001

    Meeting Log

    Meeting Log January 06, 2018 By Ethan, Evan, Charlotte, Kenna, Tycho, Austin, Abhi, Karina, and Janavi

    Meeting Log January 06, 2018

    So, today's the last Saturday before the Wylie Qualifier, and we're pretty unprepared. We're a little behind on our blog posts by about a week, we still haven't added our octopucker attachment, and we need to finish our 3D model of our robot.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Spring Cleaning Post
    • Code Improvement
    • SEM Tournament Post
    • Flipper Post
    • Octopucker Post
    • 3D Model Post
    • Proofread
    • Fix presentation

    Software

    • Fix autonomous jewel code

    Build / Modelling

    • Finish 3D model
    • Attach octopucker grabber
    • Work on flipper

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanReview Posts2:004
    EveryonePresention2:001
    EvanWork on octopuckers2:004
    AustinFix wiring issues2:004
    CharlotteFix Presentation2:004
    EthanFix presentation2:002
    KennaProofread posts2:004
    TychoWork on auto code2:004
    Abhi3D model2:004
    Karina3D model2:004

    Prepping for Wiley

    Prepping for Wiley By Janavi, Karina, Ethan, Charlotte, Kenna, Abhi, Austin, Tycho, and Evan

    Task:

    It was countdown time before the competition, we had to practice driving our robot, pack the MXP, and practice our presentation. So we decided to split up into smaller groups to accomplish more. Tycho, Charlotte, and Evan drove together to practice communicating quickly and effectively. They also played against our sister team so both teams could get practice with other robots in a competition-like setting before the real thing.

    Inside, Ethan and I worked on putting the final touches on our team's journal. We hole-punched papers, decorated tabs, and double-checked the whole journal. Austin, Tycho, Abhi and Kenna were helping out our guest team with their phones and their robot(click here to read more about that!).

    Every 30 minutes we all met up as a team in the tent and practiced our presentation. This really helped all of us work out any kinks or problems we had in our presentation. After each dry run we gave and received constructive criticism as well as new ideas, which really helped to improve our overall presentation.

    Reflections

    This method of splitting up into sub-teams really helped us organize and coordinate our time. In the past this has worked well for us, so applying this to our competition prep was a good move. By splitting up we could divide tasks more evenly and have a clear understanding of what we had to do. Another really beneficial thing we did were the practice runs every 30 minutes. By doing this we were able to practice our presentation and give each other feedback. Leaving 30 minutes between each run gave everybody time to review their slides and incorporate any new ideas into their presentation.

    Meeting Log

    Meeting Log January 27, 2018 By Ethan, Karina, Charlotte, Abhi, Tycho, Austin, Kenna, Evan, and Janavi

    Meeting Log January 27, 2018

    We are very behind on updating our engineering journal and discussing our performance in Wylie. This was the main focus of the day.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • STEM Expo Post
    • Chassis Post
    • Driving Post
    • Wylie Postmortem
    • Create poster

    Build / Modelling

    • Work on new chassis
    • Attempt to update gripper

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    EthanWork on poster2:004
    CharlotteDriving2:004
    JanaviWork on chassis2:004
    KarinaDriving2:004
    TychoDriving2:004
    EvanGripper update2:004
    KennaWork on chassis2:004
    Abhi3D Model2:004
    AustinGripper update2:004

    Building a new chassis

    Building a new chassis By Karina and Janavi

    Task:

    Janavi and I have started to build a new chassis for Kraken 2.0., modelled after Kraken’s current chassis.

    First, we had to measure the chassis of Kraken, then cut REV rails to these measurements. Lastly, we assembled the pieces to look as it does above.

    With this being the first build project Janavi and I have taken the lead on, we had to have some help from the more experienced builders on our team: Evan and Austin. The most difficult task we came across was having to figure out at which angle to cut the REV rails to fit diagonally on the main frame of our new chassis. After we found this measurement, it was easy cutting the pieces using the miter saw and safety equipment and then we assemble all the REV rails with handy-dandy brackets.

    Our current plan is to use this chassis as a base for our fifth generation grabber system. Going forward, we have to figure out how we are going to mount our conveyor belt onto our chassis, and then how to mount grabber arms onto the conveyor belt. We also have a new set of mecanum wheels which we are going to attach to the chassis. However, it came to our attention that they are thicker, so we will have to adjust the rails that run parallel to one another so that the wheels can fit in between.

    Normally during the season the build team, the programming team and the drive team all need the robot and this can be difficult. Often times this can hinder our performance since the drive team doesn't get the practice it needs. Therefore the team decided to build a new chassis because having a second base will enable us to dedicate more time to drive practice with Kraken while simultaneously testing out new designs on what will be our second robot. Additionally, having two robots will allow to choose which robot we will take to competition based on performance.

    Meeting Log

    Meeting Log February 03, 2018 By Ethan, Kenna, Charlotte, Karina, Janavi, Evan, Tycho, Abhi, and Austin

    Meeting Log February 03, 2018

    This is the last Saturday meeting before the tournament. We have to finish bringing the engineering journal up to date, as well as work on the presentation.

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Update blog posts
    • Finish poster

    Build / Modelling

    • Update 3D Model

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AllPlanning Meeting2:10pm.25
    AllFinish past-due blog posts2:004

    OK Regional Keychains

    OK Regional Keychains By Kenna, Ethan, Charlotte, Austin, and Evan

    Task:

    We came to the Oklahoma Regional woefully unprepared for the amount of stuff other teams would give out. As soon as we arrived, we received every trinket imaginable. There were keychains, pins, 3D-printed symbols, business cards, patches, and tons of other creative designs. Luckily, the MXP was there and had 4 3D printers on board. Normally, we use them to print out keychains for kids during our outreach in Dallas, but this time it was for our own use. We whipped up a quick design on SketchUP and started printing. The design wasn't especially memorable (something we want to improve on for Supers), but it was nice to have something to give out to passing teams.

    Tycho also enjoyed our efforts (the red things are all keychains). We printed throughout the entire day since we hadn't come with any. It added a bit of stress to the whole day, which we could have done without.

    For Superregionals, our goal is to come prepared with a creative keychain or card. Janavi and Kenna have already started working on a few designs to use to connect with other teams. We're very excited to see what all the other teams have at Supers.

    Preparing for South Super Regionals

    Preparing for South Super Regionals By Ethan

    Task: Prepare for the South Super Regionals in Athens, Georgia

    We currently have a bit over two weeks to get ready for the South Super Regionals, and we're not quite ready. Actually, if we want to get competition-ready, we've got a long way to go. From prior experience, we're currently 55% on awards and 45% on robot game for advancement, but we want to get both to 60-70+%. So, we created a list so that we could break our workload down into discrete tasks.

    Engineering Journal

    • North Texas Regionals PostMortem
    • OK Regionals Play-by-Play
    • OK Regionals PostMortem
    • Meta-PostMortem
    • Reindex Journal
    • Super Regionals Packing List

    Business

    • Talk to AWC for Sponsorship

    Build

    Relic Arm
    • 3D Model
    • Code
    • Improve Gripper
    • Posts
    Octopuckers
    • Print Latest Design
    • Next Design\Post
    • Print Old Versions
    Gripper
    • Space Attachment Links
    • Test Code
    • Phone Mount
    • Posts for Above
    • Mount Pulley Clips
    • Star Intake/Post
    • Update to V5
    • Extend Internal Lift
    • Bottom-Mounted Jewel Thief
    • Posts

    Code

    • Automate Balancing
    • Auto-Column w/ Vuforia
    • Cryptobox Alignment w/ Vuforia
    • Posts

    Organizational

    • Clean RoboDojo
    • Clean MXP
    • Design Pit
    • Make List of Pit Items
    • Design Posters

    Next Steps:

    As you can see, we've got a lot to do, but I'm confident we'll finish a majority of these items.

    Iron Reign's Meta-Post Mortem

    Iron Reign's Meta-Post Mortem By Ethan

    Task: Evaluate how well Iron Reign has stuck to its priorities

    As Super Regionals approaches, we'd like to evaluate our past performance on post mortems, to see how well we've done, to modify our future post mortems, and to find new approaches towards solving our problems.

    Past posts are:

    Mustang Qualifier at Oklahoma

    ISSUE: Time Management
    We've definitely gotten better at time management in tournaments since this one, and haven't had any issues since.
    ISSUE: Referring to Coach
    Again, we've gotten much better on this. We've all grown more familiar with the information about our team. I think this was mostly a one-time issue.
    ISSUE: Preparedness
    We have gotten much more prepared for each tournament than the last. We made the 3D model we needed of our robot. We have our robot inspection-ready before the tournament now. We do still have issues with packing however, especially when we travel out-of-state.
    ISSUE: Presentation
    We've done a lot of practice for our presentation and eliminated a lot of stuttering and pauses. As well, our robot is much more functional than it was, so we're good there too.
    ISSUE: Robot Stability
    We switched to the LG 4 phones and eliminated all shutoff issues, so theres no problem there anymore.

    Wylie East Qualifier

    ISSUE: Packing
    We haven't gotten much better at this, we even forgot our engineering journal in Dallas when we went to the Oklahoma Regional.
    ISSUE: Judging
    See above.
    ISSUE: Robot fixes
    • More 3D parts to combat wear and tear - fixed
    • Vuforia fixes - not fixed
    • Strain relief - fixed
    • Lack of driver experience - fixed
    ISSUE: Scouting Gaps
    We have gotten much better at scouting, with more accurate spreadsheets, some of which we've already included in other posts.

    North Texas Regional

    ISSUE: Last minute robot changes
    We did this at both this tournament and the next tournament, so we haven't done much to combat doing this. At the time, it always feels needed, but in retrospect, it doesn't. Here, these last minute changes helped, but ideally we should have finished them the week before and not the night before. At the next tournament, we made a system a week before, but ended up reverting to the old version the night before.
    ISSUE: Lethargy
    One of Iron Reign's trademark moves is being apathetic as possible, and this doesn't always shine well on us in tournament. We really haven't improved much on this, and we really should.
    ISSUE: Robot Weakness
    All of these issues were tournament-specific and won't come up again.

    Oklahoma Regional

    ISSUE: Preparation
    WE FORGOT OUR ENGINEERING JOURNAL IN DALLAS. We really really need to work on packing for Georgia, and make a definite list and plan with people responsible for it.
    ISSUE: Design Keychains
    We want to have a trinket to hand out to teams. We started this in Oklahoma, but we should mass-produce items before the tournament.
    ISSUE: Speed
    We have designed a new gripper-flipepr system to increase our speed and have already built a new chassis around it.
    ISSUE: No Relic Arm
    We've designed a new Relic Arm that'll work, we just need to attach it to the robot and program it.

    South Super Regionals Day One, 2018

    South Super Regionals Day One, 2018 By Ethan, Evan, Kenna, Charlotte, Austin, Karina, Janavi, Abhi, Tycho, Justin, and Christian

    Task: Set up and present at SSR 2018

    A placid stillness hung over the dark, cold room. The early sun flashed through the pale window curtains, ineffective against the onslaught of light. Outside, birds started to chirp and sing, starting off the new day. All over the city, teams were waking up, walking to the Classic Center (the Thunderdome of Robotics), to see their fate, either as champions of the last ever Super Regionals, or to go home defeated and never again see the light of Dean Kamen and his vision. However, through all of this movement and energy, this hotel room stayed quiet. Slowly, a beeping slowly grew more loud, blaring its morning call throughout the room until no one could deny its existence. In spite of the warm and soft Holiday Inn™ beds calling their users back to slumber, the team members had to wake, under the threat of death by coach. Thus started the journey of Iron Reign's 2018 Supers.

    The Pits (Setup and presence)

    This day marked the first official day of the 2018 South Super Regionals, the last one ever being held. With FIRST moving to the Qualifier-Reigional-Worlds system, we wanted to make a good impression and show off, and thats exactly what we did. First, we overdesigned a robot that impressed judges and looked nice to other teams, as well as making sure we had little goodies to hand out. But, we really worked on our pit presence, to make ourselves really known to other teams. We made posters detailing Iron Reign's season and hung them up; we brought LEDs and lights to give our tent that good old rustic Roman Feeling™; we had business cards to hand out; we went around and talked to other teams and took pictures of their robots. All of this served to make it feel as if Iron Reign was really *there*. While this eventually proved ineffectual to get picked, this still was a good strategy - it got us noticed - and we will feel its effects at Worlds. We still could've done more with the pit setup though, it would've helped to find a place for posters and the like beforehand, and we ran into some placement issues of our robot and award carts that irritated the safety officials. But, overall, 9/10 would do again. (We will)

    Judging

    Our judging didn't go that well. Our presentation was fine, we still had breaks and pauses like usual, and we got the majority of information across, but we didn't deliver on important information correctly. Our energy was a little low, we had a power outage while going over our outreach which distracted the judges, and on top of that, the judges' paradigms were a little closer to the engineering side of things. Now, this isn't necessarily a bad thing - having a skewed mindset makes a judge more likely to defend for some awards - but for an outreach-heavy team like ours, we were at a disadvantage for the Connect and Motivate awards. In the questioning, we only had one connect-related question, with the rest on Innovate and Design, so we knew we probably wouldn't be up for our usual awards from the get-go, which is a shame as we've gotten the Connect Award at every level of competition this year.

    That was the end of the night, so like all Good and Responsible Teams™, we went to bed early and got enough sleep to be rested for the next day /s.

    South Super Regionals Day Two, 2018

    South Super Regionals Day Two, 2018 By Ethan, Evan, Kenna, Charlotte, Austin, Karina, Janavi, Abhi, Tycho, Justin, and Christian

    Task: Complete the first day of competition at SSR

    After finishing judging and setup, all we had left to do was the entire robot game. Knowing this, we stayed until 12, tattooing pictures of Minions™ on each other. Thus, we were perfectly prepared for the tournament the next day.

    Match 5
    We won this match, 207-256. We mainly won due to the autonomous, our partner and ourselves scored 170 points and the other side couldn't catch up.
    Match 16
    We lost this match, 236-297. We suffered as a result of having a broken relic arm and not focusing on the end game. We really need a relic arm for Worlds.
    Match 23
    We lost this game, 412-105. We were up against two of the top ten teams in the tournament and we couldn't compete on any level. We didn't even get the balancing stone point because our robot turned off on the field.
    Match 29
    We won this game, 285-351. While we were outclassed in TeleOp, our combined autonomii were able to overcome that and give us a win.
    Match 38
    We lost this game, 109-286. We were outclassed on every level, and it didn't help that our robot was unresponsive. This was a wake up call for our team to improve.
    Match 49
    We lost this match, 572-221. This wasn't even close and was a huge disappointment.
    Match 56
    We lost this match, 196-374. Again, we underperformed in every aspect of the game and ended our day with a 2-5 record.

    Besides our subpar performance in the robot game, we were also interviewed by a team of judges that we guessed were responsible for the Innovate or Design awards. They asked a little more in-depth questions than what we were used to, but we were able to answer them effectively and demonstrate our engineering process. The judges were reasonably impressed by our robot - our design was fairly uncommon - and it made us canidates for the Innovate award by our estimation.

    Janavi, Karina, Abhi, and Tycho stayed up to work on driving and autonomous to prepare for the final day while the rest of us slept so that we would be restful and awake for the next day.

    South Super Regionals Day Three, 2018

    South Super Regionals Day Three, 2018 By Ethan, Evan, Kenna, Charlotte, Austin, Karina, Janavi, Abhi, Tycho, Justin, and Christian

    Task: Finish SSR and attend awards ceremony

    It was the final day. Tumbleweeds drifted over the land, rolling and turning through the abandoned Athens streets. Over the horizon, a dust cloud rose, brown and shifting and twisting, speckled with the detritus of an abandoned city, flashing and siezing, lighting up the city through its inky blackness, devoid of all light. Under these auspices, with the flashing lights of the looming cloud highlighting every crack, every pore of our grim, stone-cold faces, we trekked through these dark streets, against the cold, whipping winds blowing in, through the debris and detritus of the lost, fallen FTC teams that succumbed to the biting winds and the shooting lightning. Through these harrowing conditions, we perservered and arrived at the fabled Classic Center, the home of all southern FTC teams' dreams, and their doom.

    We started out with our 2-5-0 record, so we didn't have a great outlook on alliance selection or for the tournament in general. However, through our discussion the night before, we decided to give our newer team members a shot at driving and working on the robot. So, Justin and Karina became the main drivers for the day, since we didn't have much to lose.

    Match 70
    We lost this match, 379-267. Even though we lost, we did way better than expected, so this is still a win in our hearts. Had we executed our autonomous correctly, we could've won this match, or at least gotten closer and impressed more people.
    Match 78
    We won this match, 388-348. It definitely helped that we were partnered with the top team in our division, but it was certainly a morale booster overall. This ended the SSR with a 3-6 record.

    With the fresh feeling of defeat in our hearts, as we didn't stand a chance of actually getting picked, we went to a nice italian restruant and talked about potential plans while eating good food. If you ever have the chance, eat at Depalmas Italian Cafe.

    We walked back to the tournament, bellies full of prosciutto and cheese, reasonably not confident for our chances to advance to worlds. So, we sat in the stands, waiting, hoping that our names would be called (except for the Promote Award, ours is kind of embarrassing). As we slowly slipped into deep slumber, we heard a but a whisper from the announcer, "And the 2nd place Innovate Award goes to............Team 6832 Iron Reign!". And so, we advanced to Worlds, and rode off into the sunset.

    Meeting Log

    Meeting Log March 17, 2018 By Abhi, Tycho, Ethan, Janavi, Austin, Karina, and Kenna

    Meeting Log March 17, 2018

    Today we focused on changes we planned from Supers. Also, we decided to have a mini discussion about good and bad things from Supers (not a post mortem).

    Today's Meet Objectives

    Organization / Documentation / Competition Prep

    • Review Journal
    • Post Mortem
    • Assigning Blog Posts

    Software

    • Implement Field Oriented Drive
    • Open CV Progress
    • Fix Viewforia demo mode
    • Driver Practice Modifications

    Build / Modeling

    • Build Sparring Bots
    • Make flag holder
    • Learn how to 3-D print
    • Build Relic Arm

    Service / Outreach

    • Promote video redesign
    • Reveal Video footage

    Today's Work Log

    Team MembersTaskStart TimeDuration
    AbhiFlagHolder11:003
    Abhi,KennaLearn to 3-D print12:00.10
    AustinPromote1:001
    AllPlanning Meeting+Assign Blog Posts2:00pm.5
    AbhiCode changes2:301
    TychoOpenCV+Demo Changes3:002
    Kenna, JanaviSparring Bots3:003
    KarinaRelic Arm3:001
    EthanPost Mortem3:001
    Karina,AbhiDriver Practice4:002
    Austin, AbhiReveal Video4:001
    EthanReview Journal4:002

    Importance of Documentation

    Importance of Documentation By Abhi and Tycho

    Task: Explain commits

    As explained in a previous post, we were having many issues with git commits and fixing our errors in it. After a lot of the merging conflicts, we had to fix all the commits without exactly knowing what was being changed in the code. Part of the reason this was so hard was our lack of good naming conventions. Though we always try to make a title and good description for all posts, this doesn't always happen. This is precisely why it is important to check in all changes at every session with good descriptions. Someone had to spend their time mechanically trying to do merge conflicts without understanding the intent behind the code. So it took them longer, they may have made mistakes, an issue fixed by good documentation in the first place.

    This post is dedicated to explaining some of the errors and what the commits true intentions were.

    Stuff:

    That one is mostly about code for the 3rd servo in the gripper open/close methods. It created the servo in pose and added code for it in GlyphSystem2.

    4a6b7dbfff573a72bfee2f7e481654cb6c26b6b2:

    This was for tuning the field oriented code to work. There were some errors with arrays in the way power was fed to the motors (null pointer exception) so I (Abhi) had to fix that. Also, I made some touch up edits with formatting in the methods. After all this, Tycho made (may have edited existing) a method in Pose for Viewforia demo. Minor changes were made to account for this.

    c8ffc8592cd1583e3b71c39ba5106d48da887c66:

    First part was all Argos edits at the museum to make it functional and fine tune some measurements. Second part involved the conveyor belt flipper. Tycho made changes to the dpad up and down to return to the home position rather than carry out complete motion (not sure if this carried over in all the commit mess but it was done theoretically). Driver practice will have to confirm changes.

    Next Steps

    Don't name things badly so this doesn't happen.