3D View and Some Calculations Start

And here we have the NEW layout. (Again.) But I'm not changing it anymore. Promise. I've already started doing some calculations (which are beneath the picture), and even though they don't quite add up (for reasons explained below), I'm really happy with this very generic-inspired yet unique design. I really kept it close to the drawn layout as in the previous post, though I had to change a number of heights as we wouldn't want any track to hit other track because, well, it wouldn't be good.

3d view of the layout, taken from the previous post's sketched layout. And yes, there WILL be supports, just haven't put them in yet in case I need to alter anything as they make it so painful.

So, beginning calculations.
What's the first thing people ask about a roller coaster? "How fast does it go!?" And in order to find the velocity, we need to know a number of other things.

I'm looking at the entire train as a particle for right now, which could cause a number of errors as it's much larger than a particle. (The other way to look at something is a "rigid body". A particle has negligible size, which...this does not.) But just to sort of get a feel, this is how I'm doing it for right now. Assuming an average weight of 1400 [lb] per 2-across car (estimated from Philadelphia Toboggan Coasters, Inc website), at 6-cars per train, the weight of one train is approximately 8400 [lb].

Since velocity is the integral of acceleration, and we know the acceleration (GRAVITY!) we can find an equation for velocity. Now, this acceleration does not take into account the 5 [mph] lift speed, simply because the acceleration is 0 once the train reaches its 5 [mph]. If it were accelerating, it would be increasing speed all the way up the lift. So the acceleration is 31.17 [ft/s^2]. The equation (v = v0 - a*t) becomes v = 7.33 - 32.17t. The 7.33 is simply the 5 [mph] lift speed converted to [ft/s].

After getting the position equation (y = y0 + v0*t - a*t^2), we know that the coaster's hill bottoms out at 9.5 feet above ground. We can then solve for t in the position equation, plug that into the velocity equation and get a velocity of the train at the bottom of the first hill. After doing this, we get t = 1.907 [s] and v = 54.018 [ft/s] which converts to just over 79 [mph]. This does NOT seem right for a coaster only 112 feet tall. So what could have gone wrong?

Well, for one, there's no friction accounted for, and as I stated before, I've considered this as a particle, which it clearly isn't, and I should likely get something more accurate when I consider the train as a rigid body.

Until the next update!

So I've decided to scrap that other layout because it was giving me far too much of a headache trying to deal with scales and accurate heights and radii and things. The new much simplified, much condensed, much smaller, much more model-centric layout:

Now I'm working on the side-profile, then I'll be doing calculations on potential & kinetic energy, speed/velocity, acceleration, g-forces on the rider, and I suppose I'll have to do some support stresses.

When I chose this project I just sort of pictured that I'd make a NoLimits coaster, and boom it'd basically be done. NOPE. I WAS VERY WRONG.

Anyway, this is the latest update for all zero of you following along!

Layout

Here is the picture of the layout in an editor view. Quite a simple out-and-back style. The "out" part is basically just hills, whereas the "back" part is more about disorientation and transitions and bits of airtime. And lots of crossovers/unders.

Nitrogen:

Update

I completely forgot I even had a blog for this, hahahaha. Anyway, the virtual model is done for the ride, which I've renamed "Nitrogen" to keep it sort of generic and useless.

I'm having difficulty with the scale I want to use as I was originally thinking a 1":5' scale (That's one inch on the model equals five feet in real life) but as the ride's footprint is about 1350 feet long, it would make the model about 22 and a half feet long; which is ridiculous. So I thought a 1:8' scale would be ok, but then the numbers seem all weird and it's still quite long. Then I thought a 1:10' scale would work, as that'd make the model 11 feet long, but the ride is only 120' tall, so that means the model would only be one foot tall and 11 feet long; which makes it look odd.

Not to mention that if I decide to use wood to create the model then that means I'd have to find appropriately scaled wood for supports and track and very tiny coaster cars.

So there's one dilemma. Another is what I'm making the model out of. I'm leaning towards wood just because it'd be cool to see it fully realized, but it would be incredibly time-consuming, expensive, and would create a big hassle to try and figure out how the trains should stay on the track. (Though I was thinking of notching out and laminating/plastic coating the track and have slots that ball bearings attached to the cars are inserted into? Like this: |_| only sideways with a fin and ball bearing in there. But that'd have to be a lot of notching.)

Another option I've been thinking about is K'nex? However tacky and ridiculous that may sound, it makes the physics physically visible (rather than simulated on a computer screen) simply and fairly cheap. Though, looks and an accurate scale are the downfalls to this choice of model building.

Similarly, something called "spacerails" would not be accurate or visually pleasing but would get the point across.

I think I need to just contact my professor and see what he says about the material. Once I get more time I'll look into model-train scales (something called H0 or HO scale) and see what that's about. I think if worse comes to worst, I'll have to do with creating a non-working model, but if at all possible, I'd really like to get a working one just to say I did it. This is literally the biggest commitment and project I've ever done.

Looking forward to seeing this thing take shape!

Random Ideas

I'm only going to upload one picture, as It may be kind of large, but just know I've had multiple ideas before this. What follows is what I'm thinking about as my general layout. (Yes it's on notebook paper. Yes it's rediculous. No it's not accurate to any scale.) It's merely an idea, and as such is just a rough sketch. But this is the product of not paying attention in class! I rather like the idea of having a sprawling section towards the beginning and then as the momentum decreases getting more compact to increase the feeling of speed, if that makes any sense. That last sentence seems like a run-on, but I don't think it is; but it could be.

Anyway, the long straight bit at the right of the sketch is going to be the lift hill, first drop (which I'm thinking of making a double-down: a sort of half-drop, level out, then the rest of the drop; e.g. lots of airtime), that sort of hammer-head turn around (which isn't really used on wooden coasters I don't think), then some more airtime goodness.

Slow Going

Having been overrun by other school work and things, I've not had much time to do a lot with this, but as a quick update, I'll say: I'm kind of excited.

As there are many many functions and ideas and departments that have input on something as grand as a roller coaster, this ride will not be a complete, all-encompassing project. Rather it will focus on dynamics such as speed/velocity, gravity, potential and kenetic energy, and on stresses with respect to the wheels and possibly some supports. And of course the child in me getting to put a working model together! (What kind of child likes to do tedious work like this? Oh yeah, the one obsessed with jigsaw puzzles! #Nerd)

I'm not sure if I've said it before, but I'll say it now just in case: Manticore will be a terrain-based wooden rollercoaster, similar in nature to rides like Boulder Dash at Lake Compounce, Voyage at Holiday World, and Ravine Flyer II at Waldameer. That's about as far as I've gotten in this, so obviously I've got a long ways to go. I will say that I plan to have a virtual semi-model (thank you NoLimits) done within the next two or three weeks.

It's Official!

I got the OK on the preliminary project proposal! Literally. (It was a one-word message. Is OK even a word? I digress...)

Below I've copied my preliminary proposal, it's about a page long in word.

SENIOR DESIGN PROJECT PRELIMINARY PROPOSAL

PROBLEM: A theme park is looking at expanding their attractions with the addition of a roller coaster. A budget will be given, as will a plot of land with limitations.

PURPOSE: Roller coasters are one of those things that most everyone loves, but most don’t really wonder or care how these scream machines are created. I hope to clarify this and prove that it’s really not just as simple as connecting some pieces of track.

PROCEDURE: After deciding on a theme, limits such as budget and size will be investigated and will factor into the original design sketches. After a general concept is developed, a virtual model will be created and tested before continuing with a physical model. Terrain will also factor into the virtual model. Calculations will then be made to determine the safety and appropriateness of the ride. Once everything checks out well, a physical working scalar model will be created and displayed.

OUTCOMES: This project will hopefully enlighten both myself and others on the topic of roller coaster design. The field is greatly under the radar and only a small number of engineers go into the amusement industry, so I hope to introduce that field to those who may not have realized what it’s like.

ROUGH SCHEDULE:

            Weeks 1-2: deciding on a park, area, type, size, and budget; logistics of how roller coasters work; research.

            Weeks 3-4: estimate budget for materials and construction, designing and manufacturing

            Weeks 5-6: create virtual model/simulation

            Weeks 7-8: adjust design as needed. Order or pick up supplies needed for physical model

            Weeks 9-10: begin building model

            Weeks 11-12: finish building model, test, adjustments if needed, present project

OTHER:

            I’m thinking about keeping a blog to update as I go rather than have a ton of files just hanging around on the computer. This helps organize the process and will provide a wonderful reference for the final report. It also helps keep things simple, concise and clean. I will still be making a presentation and report, however. The blog is solely for my personal organization.

I've obviously decided to go ahead with the blog idea, but copy and paste makes life easier.

I'm really excited to start working on this and see this idea take shape!