Showing posts with label rocket_launchers. Show all posts
Showing posts with label rocket_launchers. Show all posts

Monday, April 14, 2014

Rocket competition

Wednesday we'll have our rocket competition after we finish going through new material. As I mentioned today, there are 3 targets you'll have to hit.

  1. over level ground
  2. hit a hole (about 0.2m in diameter and 0.5m above the floor)) in a vertically standing board
  3. hit a hole (same hole) in a board lying flat about 0.5m above the floor

You'll have three shots at each, with one practice shot. If you hit on the practice shot but miss on one of your 'real' attempts, we'll take the best 3 out of 4. Overall this will count as 2 lab grades, scaled by how many times you hit the target.

I will specify the distance to each target and its height above the floor when applicable. You'll have a marked line that you can't cross, but you can move further back, prop up your rocket, etc., so long as you don't move closer. You can use a laser pointer to align the launcher horizontally if need be. There will be a small prize for the top 3 teams.


Wednesday, March 12, 2014

Rocket launcher deliverable #2

Just like last week, you are basically free to do what you want during the lab work period, you just have to deliver to me the result I ask for by the end of the week. My impression so far is that you're all making very good progress, so this deliverable should be easy.

This week, I want you to tell me the following:
  • Did you find that you need to use the same rocket and turret for reliable results, or did it not matter too much?
  • Give an estimate of the variability in the launcher's range for at least 3 angles. For instance, if you do 5 launches at a given angle, what are the mean, maximum, and minimum ranges? 
  • Given the variability you find, approximately what size target do you think you could hit reliably? Ballpark answer is fine.
  • How does the actual range of the rocket compare to what you would predict without drag forces, evaluated for at least 2 angles?
  • How much kinetic energy must be lost to drag forces for each of those angles (say, a % of the launch energy)?
  • Using the example code I've given you (below), or code you've written, what drag coefficient makes your simulations match your measured data reasonably well?


Friday, February 28, 2014

Rocket launchers, first deliverables

From now on, our 'labs' will be characterizing the rocket launchers and figuring out how to predict their motion. Each lab session, you'll get your launcher and tell us what sensors or equipment you might need for that session. We will not have written procedures or detailed lists of tasks, just a final goal and a set of deliverables each week.

For example, next week (by Friday), your primary deliverable is to have figured out the muzzle velocity of the launcher as well as some estimate of its uncertainty. A secondary deliverable is to sketch out how you will proceed during the following week. How you choose to proceed is up to you, I will only give advice as to whether your plans are reasonable or not, and how you might alter them if they are not reasonable.

Your deliverables will take the form of a short memo (2 pages maximum), one per group, due by the end of the day Friday March 7. Any reasonable format is accepted (hard or soft copy). This memo should contain, at least, the following key points:
  • What is the launch velocity, with an estimate of its uncertainty. Does it depend on which rocket and which turret you use?
  • How did you determine the velocity, in brief? (E.g., what sensor did you use.) Define your measure of uncertainty, or how you quantified uncertainty.
  • What are the appropriate equations of motion for your projectile, including drag? That is, what does the force depend on? (You do not need to solve the equations yet, just figure out what they are.) 
  • At launch time, you will have the ability to measure the target coordinates. Besides that and the muzzle velocity, what else do you need to know to set up your launch to hit a target?
  • What quantities can be determined experimentally ahead of time, and which will only be known once you know the target coordinates?
  • What are your potential sources of uncertainty, and how could you characterize them? A detailed plan is not necessary, just an idea.
As the week progresses, we'll discuss the finer points of your memos. All you really need is a measure of the velocity, and a rough idea of what things you're going to need to figure out over the next weeks.

Tuesday, February 25, 2014

Tomorrow's lab

Tomorrow, we'll do one more 'regular' lab before starting with the rocket launchers. The main point is to learn how to use photogates for timing, which will be useful for characterizing your launchers. A secondary point is to verify conservation of momentum in 1D collisions.

Also: the rocket launchers just arrived yesterday, so tomorrow I'll show you what they look like and how they work. We'll need a couple of days to install the right software on the lab computers, but either this Friday or next Monday we'll get started with them.

Wednesday, February 19, 2014

Class for Wed 19 Feb / upcoming exam

We'll continue our discussion of momentum a little bit, time permitting, at least as far as figuring out how to handle collisions. A larger portion of the class will be related to homework problems, which are directly relevant for the exam, and another lab on programming.

For the homework, you should be a little bothered by #6, I'll outline 2 methods to solve this one. Number 7 should be quite mysterious, and that is OK - the technique you need to solve it is related to the experimental propagation of uncertainty - if you change one variable a little bit, how do the others change? This is related to how you move along surfaces in 3D, something you are learning or have learned in Cal III.

Number 8 requires some thought - the equilibrium spacing is where U(r) is minimum, or where dU/dr = -F = 0 and the net force is zero. Find this first. The breaking point of molecule is when you exceed the maximum restoring force implied by U(r). If you find F(r) = -dU/dr and look for its maximum, this will occur for a particular r, beyond which the force binding the atoms together is exceeded and the atoms will come apart. Mathematically, that means setting dF/dr = 0 to find the maximum, that's the radius beyond which you break the molecule. Using the result for the equilibrium spacing, you can write it in terms of only n, m, and the equilibrium radius. I might have asked this question before if you are willing to dig a little.

For the exam, the format is exactly like the last time. It will likely consist of 6 problems, of which you have to solve 4. The questions will only be on work, kinetic energy, potential energy, and conservation of energy - 2 chapters in the book. You'll have a formula sheet given like last time, and can bring 1 sheet of paper of your own. I will post HW3 solutions by Thursday morning, hopefully, to help you study.

Finally, the lab: we'll continue with coding. You have two basic tasks.

1) I assert that the sum of the first n cubes of integers (sum of i^3 from i=1 to i=n) is the square of the sum of the first n integers (square of the sum of i from i=1 to i=n). Write a program that can check this for specific values of n. Print out your code and results for n=10 and n=17. Basically: sum the integers, square the sum, and compare to the sum of the cubes of integers.

2) Write and evaluate a program to calculate the range of a projectile under only the influence of gravity (no drag forces). Verify that it gives the correct result (within a few percent numerical error) for a launch speed of 25 m/s and a launch angle of 45 degrees. (You already know how to calculate the range without a drag force ...) Note that links I gave previously, and specific folders here are highly useful. Print out your code and note your results for the conditions noted.

Monday, February 17, 2014

Starting with Python

For tomorrow's "lab", we'll start messing around with python. Nothing fancy, just a few simple examples so you can learn to do basic calculations (like multiply stuff) and display the answer. We'll work our way up to more complicated things. If you are interested enough to mess around on your own, try the excellent tutorial here. Don't feel bad if you haven't programmed before. It will be weird at first, but you'll pick up enough to do what you need to in no time.

Sunday, February 16, 2014

Starting our project

As I mentioned on Friday, from now on we're going to stop with the usual labs and work on a project for the rest of the semester. The basic project is to characterize and simulate USB-controlled foam rocket launchers.

The ultimate goal will for you to be able to calculate numerically the flight of a realistic projectile and use this result to actually hit a target with the launcher. You will have to include drag forces and everything - using measured values of launch velocities, drag coefficients, etc. The experimental end of this will be measuring launch velocities, their variability, and trying to measure drag coefficients using the sensors we have. How to get a good measure of the drag coefficient will require some time and care. By the end, we should be able to specify a target, and you will perform the calculations and then actually hit the target.

The theoretical end of this is figuring out how to calculate things numerically. Projectile motion with drag can't be done analytically, so we'll need to learn how to simulate things. To start with, we can do this in pseudocode, as I did on Friday, just learning the appropriate algorithm for calculating trajectories numerically. Once you've got your head around how the process works, we can start with actual code. For those of you that can program, you're free to use any language you want and any methods you want. What you do has to make sense, and it has to work. For those of you that can't program, I'm going to teach you just enough Python to get the job done. We'll start learning basic python coding tomorrow; see the next post.

Tuesday, May 5, 2009

Final Exam

Your final exam is here, if you want to look back at it ...

Also, moodle is now up to date with everything except the final exam. Labs 9, 10, and 11 were from the rocket competition:

L9 = competition performance
L10 = quality / correctness / cleverness of code
L11 = quality / cleverness of the physical setup and measurement system

FYI, the grading breakdown (weighting, number dropped, etc.) can be found here.

Saturday, May 2, 2009

We made the news ...

Video of the contest on the Tuscaloosa News site.

UA News
writeup.

And, Mr. Cecil is on the front page of the "B" section of Friday's Tuscaloosa News. Very cool. Try to save him a copy of the paper if you can :-)

Friday, May 1, 2009

Reminder: code submission

Each team owes me code ... soon.

Don't worry about dependencies, libraries, etc. I'll figure it out.

Rocket Contest

Well, I was pleased, and had a good time :-) I thought it went well, and you all did a great job. The visitors were pretty impressed with what you were able to come up with, and in particular the variety of solutions presented.

By the way: no one will come out of this with a bad lab grade, I was impressed all around. Even if you didn't get as many 'hits' as you would have liked, it was clear you all had solid approaches and took the task seriously, and that's worth a lot.

Currently, I'm uploading many photos and some video from today, but I'm not quite finished yet ... I'll post some links here when it is finished. Keep your eyes on the Tuscaloosa news, they may run a story based on the video and pics they took today.

Also: I've decided you can keep the launchers, sensors, and laser pointers - your lab fees more than paid for them, and at this point you put a lot of work into the customizations. I do need the voltmeters back if you still have them though ...

In the mean time: here is (1) a UA news bit, (2) a short video of a successful shot, thanks to Marcy Huey's fine camera work, and (3) a listing of several other videos, including team Red Scare's propaganda.

(All videos are AVI straight from my camera; editing and conversion to mpeg should happen this weekend I hope.)

Wednesday, April 29, 2009

Last-minute things for the competition

Last minute preparations and information ....

Things: Tomorrow, I will bring the following items, at least:
  • USB extension cable
  • tape measure (verify ceiling height, etc)
  • camera
  • soldering iron (sensor repairs)
  • stopwatch (elapsed time between shots)
  • target
What to bring: The launcher (duh), position sensor, and the computer running your calculations. If you need a computer for tomorrow, you'd better let me know soon. Like right now.

Press: It is not clear if press will come or not - they won't know themselves until the last minute. They have been invited, so we'll see what happens. If they do show up, it would be nice if a few of you were a bit early to the competition so they can ask you a few questions. Obviously this is optional, but the basic point is, 'show up early, and there is a chance you'll be interviewed.'

Visitors: There are going to be a number of random visitors tomorrow. Pay them no mind, go on about your business :-)

Location
: Shelby L107. This is not the same as 107, a lecture hall you may have had classes in.

Directions
: from the rotunda entrance, go left. Continue down the hallway until you reach the breezway. Go through it and into the next hallway. At the dead end, turn right. L107 is on your right. I will have a few signs up to guide you.

Timing:
We might be done by 12:30, it is hard to predict. We will not go beyond the normal class period.

Grading-related:
Remember that you need to turn in your source for the trajectory calculations. Please try to do this by the end of Friday.

Ok ... that is all I can think of right now. The contest will be pretty relaxed, but we will have to be efficient - with 5 teams and multiple shots, it will take a while.

Tuesday, April 28, 2009

Tuesday's class

Today we'll go over some review questions, and spend an hour or so practicing for the rocket competition on Thursday.

Also, I had completely forgotten about Exam III solutions until one of you reminded me in the comments ... I'll get on that and have something for you by Thursday at the latest, along with solutions to the example problems from last week. The end of the sememster is proving a bit more painful than expected, so I am a bit behind ... apologies.

I have put up some very silly flyers to advertise our little contest. If you feel so inclined, you can do some of your own advertising as well. A number of faculty and staff members have expressed an interest in coming to watch the competition, mainly because they think what you've been up to is very neat. Probably, they are jealous.

(I may have mentioned this to the University Relations office. There might be local press.)

Finally, I'll post directions to L107 Shelby soon. You can find a handy map here. Note that you are going to L107, which is not the same as plain old 107. (Grab the 'emergency evacuation plan' map, it is actually much clearer. And possibly quite relevant, one never knows.)

Thursday, April 23, 2009

Today's class ... probably

I am mulling over a change of plans. On one hand, we should do more thermodynamics. On the other hand, you will all end up taking it again anyway ...

So here's my thought: if you agree to do a bit of reading on your own and take a short multiple-choice quiz on Ch. 18 on Friday, we'll spend tomorrow doing final exam review instead. Nothing we covered after Exam III is on the final exam, so this is a reasonable gamble for you to take, I think.

Anyway: tomorrow you have a choice - lecture on heat and thermodynamics, or do practice problems for the final. Since our PH125 Deathwatch is in its final stages, here's what the rest of our time looks like:

This week:
Thurs: practice or thermo + concept test + rocket testing
Fri: pending your vote for Thurs, possibly a thermo quiz. Post-mortem on the concept test (i.e., where are you as a whole having the most trouble). After thinking about Crito's comments & link, I'll also point out the ones I thought were tricky and why ... where does intuition seem to fail?

Dead Week:
Tues: final exam review, dry run for rocket competition
Thurs: rocket competition
Fri: no class

Wednesday, April 22, 2009

Thursday's class

Thursday, we'll be doing our requisite post-assessment. Remember that concept test you took at the beginning of the semester? Basically, we'll take it again and see if you learned anything :-)

It should take about 20min, and there will be grade-related incentives for doing well.

We'll also go over a bit more thermodynamics (heat and energy), and leave some time for you to do some 'practice shots' for the rocket competition.

Thursday, April 16, 2009

Rocket launcher code

Linux kernel module to control the launchers. Should be portable ...

Update: code for OS X here. Pretty readable & hackable. You are not by any means required to include rocket launcher control in your code, this is just in case you're interested in trying it for 'fun.'

Thursday, April 9, 2009

Checking your code

In case you want to check that your code is working ...

If you use the drag equation

F_d = \frac{1}{2}\rho C A \vec{v}\cdot\vec{v}
with starting parameters

v_x=31\,\text{m/s} \\
v_y=35\,\text{m/s}\\
m=0.046\,\text{kg}\\
A=0.00143\,\text{m}^2\\
\rho=1.225\,\text{kg}/\text{m}^3\\
C=0.25
then you should get a range of 126 meters over level ground (and 221 meters with C=0, i.e., no drag).

Monday, April 6, 2009

Tomorrow's class

(1) Waves: read chapter 16 (or at least skim it)
(2) Problem-solving: homework for this week, more harmonic motion
(3) More rocket madness

Friday, April 3, 2009

Today's recitation

Today, we'll have one more presentation, if all the group members are around ...

After that, we'll work on homework problems - both the ones from last night, and the ones due tonight.

Monday, March 30, 2009

Talks for Thurs/Fri

Thursday and Friday of this week, I would like each group to give a short oral presentation on their progress with the rocket project so far. A few formal details:

  • It is a group presentation - designate a speaker, or take turns. Either way.
  • Minimum 10 minutes, maximum 15 minutes per group
  • Powerpoint/etc are not required but may be used if you like.
  • We will start on Thurs and finish these on Fri. Pseudo-random numbers will choose your presentation order on Thurs.

As for the content, I would mainly like to see you present your basic approach to the assignment, where you are now, and what you think you still need to do.

  • What is required for the project?
  • What experimental quantities must be determined, and what is your progress?
  • What parameters must be controlled, and what is your approach?
  • What are the relative errors & their sources?
  • How will you determine the trajectory/angle at launch time?
  • What problems are still outstanding?
  • What solutions are you still working on?

I'll discuss this a bit more tomorrow, but hopefully you get the idea. This is really just meant to be a reasonably informal (but not too informal) status report, like an oral version of your memos, updated with all your recent progress.

You can keep the talk fairly general in some respects - I am not asking you to give all your secrets away to the other teams, but I do expect you to give concrete statements about what you have done. For example - quoting your launch velocity and error or discussing the algorithm you are using for your calculations is fairly general. Giving away your trick for highly accurate positioning of the turret or optimizations to basic algorithms is not necessary.

Grade-wise, this will count as a lab.