Students, Time put into start of build - end of season?

[notmattlythgoe]

We usually have a student or 2 pushing 170 for the build season. But I don't think we had a single one over 120 this season. We only meet 4 days a week throughout the build season and we built the best robot we've ever built this season. We stress to our students that your grades must come first and that robotics comes second. More hours does not always equal a better product.

[pntbll1313]

Originally Posted by rkbot

I know this year i was at robotics from usually 3-8,9,10 weeknights and later of Fridays, along with 11am until the early ams the next morning ( we pulled 1 all nighter on week 2 or 3 that was a 22 hour shift). and usually from 11 or 12 until 5, 6 or 7pm on Sundays. I know it is a stretch for 500 hours during build season but i think its possible because i know last year, i didn't even go home on weekends usually it was Friday until 3-5 in the morning and back the next morning sometimes before 11, same with the Saturday night and Sunday morning.

And btw u cant look at an average because you are not going to work the same number of hours on a weekday as a weekend. I know my longest shift this season was 22 hours. Whatever work you do on the weekend will push your average up greatly especially if you spend all your time at robotics when you are not at school.

I'm still a little skeptical of people around the 500 mark. I understand it is possible and that you can't really use an average to prove or disprove it but...

46 day build season, 14 of which are weekend, 32 are weekdays.

if every single weekday looks like this:
[(6 hours sleep)+(45 min time from wake up to dress and get to school and before bell rings)+(7 hours school)] * 32 days
=440 hours

if every single weekend looks like this:
[(5.5 hours sleep)+(30 min commute each day)] * 14 days
=84 hours

There are 1104 hours in 46 days so there are only possibly 580 hours available left to work. I know that many people feel like there schedules looked like this but I doubt many actually were. I also didn't include any time to get homework done. Quite a few students chimed in that their grades dropped which is a little troubling. That is definitely something my team doesn't believe in. We tell them that school is always the most important.

[DampRobot]

Originally Posted by ttldomination

This comes out to 11.9 - 14.3 hours a day if you worked every day this build season.



This comes out to 9.5-11.9 hours a day if you worked every day this build season.



Now, this. 700 is roughly 16.6 hours a day if you worked every day this build season. Even if you meant the entire season, let's take a 12 week period, that comes out to 8.3 hours a day.

Now, I'm not one to deny the time we give to the program, but I don't believe any of you.

Personally, I'm staring down the barrel at around 114 hours spent in the shop during build season.

- Sunny G.

I'm sure all of these people were including time between the "end" of build season and competition. 8.3 hours per day is working from just before 3 (when I assume school ends) till 11 at night. This isn't factoring in that many people work a lot more on the weekends, which would reduce the time worked on weekdays.

It's a lot for sure, but knowing the commitment of some of these people personally, I don't think they're lying. Once you factor in time after build season, and time at home doing CAD (which sometimes took me far into the wee hours of the morning), your time "at" robotics during "build season" can add up pretty fast. I assume if you asked for time physically in the shop during the six week build season, you'd get different answers.

[Connerd]

I'm asking forgiveness here people. I'm sorry I included transport times in that count. Now, if you don't believe me, you're probably right, and I miscounted some times. I might have counted all the hours at school, or something like that. I just made many many many mistakes on this, and it shows.
Sorry guys.

[rkbot]

Originally Posted by pntbll1313

I'm still a little skeptical of people around the 500 mark. I understand it is possible and that you can't really use an average to prove or disprove it but...

46 day build season, 14 of which are weekend, 32 are weekdays.

if every single weekday looks like this:
[(6 hours sleep)+(45 min time from wake up to dress and get to school and before bell rings)+(7 hours school)] * 32 days
=440 hours

if every single weekend looks like this:
[(5.5 hours sleep)+(30 min commute each day)] * 14 days
=84 hours

There are 1104 hours in 46 days so there are only possibly 580 hours available left to work. I know that many people feel like there schedules looked like this but I doubt many actually were. I also didn't include any time to get homework done. Quite a few students chimed in that their grades dropped which is a little troubling. That is definitely something my team doesn't believe in. We tell them that school is always the most important.

I completely, agree with you, Our team says "School comes first" but doesn't always work out that way , I have to make a compromise between school and robotics or else the others will not pick up the slack on my end (which is a lot). My grades are not where I want them to be because of this, but they are good enough for me to be going to school next year ( maybe not the one i wanted, but still). I constantly hear that doing robotics will teach you more than you will ever learn in school (this cant always be used as a broad statement) and i think this is a very true statement but, i hope that doing robotics wont keep anyone from having the education they are hoping to get post-secondary.

[joelg236]

Originally Posted by ttldomination

This comes out to 9.5-11.9 hours a day if you worked every day this build season.

I see why you'd be skeptical. My teammates would vouch for me when I say that I really did come in 12-9 almost every single day. And as others have noted, long nights add on to that number.

[T^2]

Originally Posted by ttldomination

I don't believe any of you.

As others have explained, the time quoted is not just in 6 weeks. I counted shop time and personal time from January 4th to about now.

[Musikman]

Based on the attendance information and rough estimates, my entire team put in just over 3500 hours during build season. I don't want to even imagine how many extra thousands of hours went in outside the six weeks of build season.

[Whippet]

Quick calculation puts me at just over 175 hours, not including countless CAD, programming, and grant-applying hours. You all make me feel incompetent.

[DDSLoan96]

I had the most student hours with 130, we had less than 150 hours of access time this year. Why does everyone seem to have double to triple that?

[rkbot]

Originally Posted by DDSLoan96

I had the most student hours with 130, we had less than 150 hours of access time this year. Why does everyone seem to have double to triple that?

Some teams such as mine have shops outside of the schools, this means we have unlimited access as long as whoever owns the shop or garage consents. We build our robot in a snowmobile repair shop which is owned by our lead mentor who would probably let us build nearly 24/7 if we wanted ( as long as we have supervision). This gives us the ability to put the hours in we do. (we are also a community team meaning no school involvement)

[Oblarg]

Probably somewhere between 250 and 300 hours during build season, plus a fair bit of time after (say another 100 hours, all told).

A bit more time than was prudent, I think. I should scale it back to where I was in 2013 to avoid compromising my performance in class.