But how do you make a model of a falling slinky? Remember, you don’t fully understand something until you model it.
Also, with a model you can quickly test different situations. What happens if you put a car on one end of the slinky (or massive spring). What kind of spring constant do you need? What if the two masses are different?
All of these questions can be investigated with a model.
Let’s get to it. Of course, I am building my model with python—because I like python (and so should you). Here is my code. This is what most of it looks like (sorry, I can’t embed here).
Here is a gif of the output.
The balls wait a short time before dropping—just to make it dramatic.
I have calculated the position of the bottom mass so that it starts in equilibrium. If you don’t do that, the bottom mass will just oscillate up and down and ruin the whole thing.
I added two objects—a stick on the side and a free falling ball. That way you can see how the spring thingy falls.
Oh, you should absolutely try changing things up and running the model.
Here is how the model works.
There are two masses (the ball1 and ball2)—just ignore the other objects, they don’t matter.
Once the top mass is let go, there are two forces on the two balls. The downward gravitational force and then the spring force. Whatever the spring force on the bottom ball is, the top ball has the opposite.
The gravitational force is easy to calculate.
For the spring force, you need to know the natural length of the spring and the distance between the masses. The spring force depends on the difference between the distance and the natural length—then just multiply by the spring constant. Yes, I often mess up the sign on this force so that the two objects get pushed away in a weird motion.
After that, you are pretty much done. Use this force to update the momentum and then use the momentum to update the position.
Here are some things for you to try.
What if the top mass is 0.1 times the bottom mass? Does this still work?
What if the bottom mass is 0.1 times the top mass?
See if you can calculate and plot the vertical motion of the center of mass of the two ball system.
What if the spring also has mass? There is a way to model this, but I’m going to make you think about it first.
Suppose I want to do this with a 2000 kg car. What spring constant would I need? What natural length of a spring should I use?
It happens all the time. It even happens to you. There is a new lab you want to try out—or maybe you are just modifying a previous physics lab. You are trying to make things better. But when the class meets—things fall apart (sometimes literally).
Yes. This is what happened to me this week. And yes—it’s OK.
But let’s look at the lab and go over the problems so that I can make it even better for the future.
Finding the electric field due to a point charge
This is a lab for the algebra-based physics course. It’s always tough because many of the first things they cover in the lecture class don’t have lab activities with things you can measure. Oh sure—there is that electrically charged clear tape lab, but it will be a while before they get to circuits.
So, my idea was to have the students use python to calculate the electric field due to a point charge. This would give them a safe and friendly introduction to python so that we could use it later to get the electric field due to other things (line a dipole or a line charge). It would be great.
You can look at that stuff, but basically I give a workshop style presentation and have the students do the following:
Review vectors. Add two vectors on paper (not with python).
Find the displacement vector – given the vector for a point, find the vector from that point to another point (the vector r).
Find the unit vector and the magnitude of a vector (using python).
Next, find the electric field due to a point charge for the simple case with a charge at the origin and the observation point on the x-axis. Do this on paper.
Now do the same calculation with python.
Find the electric field at some location due to a charge not at the origin (in python).
Use python (or whatever) to make a graph of the electric field as a function of distance for a point charge. Graph paper is fine. If they wanted to, they could do the calculations by hand (or use python).
Finally, give a quick overview of the sphere() and arrow() object in glowscript.
So, that was the plan.
Here are the problems students had during this lab.
Computer problems. Yes—whenever using computers, someone is going to have a problem. In this case, it was partly my fault. There was one computer that was broken and some other ones weren’t updated. Honestly, the best option is for students to bring their own.
I can see that there are some students that just sort of “shut down” when they see computer code. They automatically assume it’s too complicated to grok.
Students working in big groups. I hate having 4 students use one computer. That’s just lame.
Too much lecture. The first time I did this, I spent too much time going over vectors with not enough breaks for students to practice. I partially fixed this for the second section of lab.
Some students were just lost on vectors.
Yes, the unit vector is a tough concept.
I’ve learned this before—but I guess I need to relearn. The visualization (sphere and arrow) are just too much for many students. That’s why I moved it to the end in my second section.
So, that’s it. I am going to rewrite the lab stuff on trinket.io. I am also going to change my material for the dipole stuff that they are doing next week. Hopefully it goes well. Let’s just see.
Tonight’s episode (actually there are two episodes tonight) looks at the famous slinky drop problem. Let’s start with the first place I saw this—from Derek Muller (Veritasium) even though he didn’t invent this either.
That’s pretty awesome, right? Of course the first thing I want to do is to make a model of a falling slinky. Here is that first post.
Some important comments.
It’s important that the slinky itself has mass. You can’t use the normal assumption of a massless spring.
The best way to model a spring with mass is to have a bunch of smaller masses connected by massless springs.
When the slinky is dropped, the center of mass falls with a downward acceleration of -9.8 m/s^2.
However, since the slinky is contracting this makes the bottom of the slinky motionless.
Here is an animation of my python model.
Sorry—this code is older and I don’t have it on some online platform (I will try to update that soon). But here is the important plot. What if you look at the vertical position of the top, bottom and center of mass for this “slinky”? Here’s what that looks like.
The red curve is the bottom mass. Notice how it “hangs” there? Awesome.
But can you just put a mass (like a car) on the end of a spring and drop it? Yes, but it won’t look very cool. The key is the center of mass. You want the center of mass to fall such that the bottom mass stays in place. With a car and a spring, there is no top mass moving down faster than the acceleration due to gravity to make the bottom mass (the car) move up relative to the center of mass.
In the end, you need some type of mass at the top of the spring too. So, that could work. Two large masses separated by a spring. When you hang and then drop, the bottom mass will be stationary.
Here’s what that looks like in slow motion. Sorry about the vertical video, when I recorded this I didn’t think I would post it.
But wait! What if you want to make something like the slinky? In that case you can get a bunch of masses and connect them with rubber bands. It will be just like the python animation above, but in real life.
I should have recorded this in slow motion. Oh well.
Just for fun, here are some of my original notes in which I estimate what kind of spring you would need to do this drop thing with two cars.
In order to keep my blogging certification up to date, I am required to post some type of year end review.
OK, here it is. These are my “best” or “favorite” posts from 2018. Maybe these didn’t get the most traffic, but they are ones that I like the best. It’s all about me.
You might think this list is long, but I just counted. I had 106 blog posts for the year of 2018. So, these all “made the cut”. Also, I normally just list the posts but this time I will give a brief description.
Really, this post is all about a TV show – The 100. In one episode, a boy is floating around in a space ship during the re-entry process. This leads to a discussion about how gravity works and what happens during re-entry.
This really isn’t a blog post—at least not like a normal post. This is really just a holder for my WIRED video on how airplanes fly. This short explanation covers flying using the momentum principle instead of Bernoulli’s Principle.
The gravitational constant is needed to find the gravitational force between two objects with mass. The problem with finding this value is that it’s very small and we (humans) didn’t initially know the mass of the Earth.
Here is a method to find the gravitational constant by estimating the mass of a mountain and detecting the change in gravitational field with a pendulum. It’s just so crazy it might work.
Oh, the real tricking part is find the direction of “up” and “down”.
Everyone knows (or should know) how much I love numerical calculations with python. Here is a demo to show the angle of reflection is equal to the angle of incidence using Fermat’s Principle. This says that light takes the path of shortest distance.
First, there is a random walk. Second there is a random self-avoiding walk (SAW). A self avoiding walk doesn’t cross its own path. So, a SAW is like a long protein—which is important for life.
3D works the best for proteins (and not 4D). In 4D, there is no big difference in length vs. step number for SAW and normal walks. In 3D, it’s more likely a walk will cross itself—which is important for protein folding.
Yes, there is lots of python code here. Note: random walks in 4D are tricky since you can’t just use the position of the walk as a built in 3D vector class.
This is one of my blog posts that goes along with an episode of MacGyver (since I’m the technical consultant for the show). The idea was that MacGyver would use some stuff from a car to find out how to get to a base from his location in the desert.
The cool part is that navigation is really just using a compass to measure angles and clock to measure time.
Note: for this particular episode, I did a bunch of calculations to get the exact angle and time measurements they would use in the show. I don’t think they made it in the episode, but I did it. Also, I had to cheat since everything happened at night and MacGyver couldn’t find the time of local noon.
Yes, a Star Wars post. SPOILER ALERT – there is a space battle in Star Wars The Last Jedi. They show this First Order ship firing on the Resistance. In order to make it look like a WWII sea battle, the turbo lasers have an arc to them—that looks cool, but it wouldn’t happen.
So, what do I do? Other than enjoy the movie (which I do), I first do a video analysis to determine the vertical acceleration. Then I make a python model to recreate the arc. Fun.
In Star Wars A New Hope, there is a scene that shows the escape pod leaving the blockade runner (near the beginning of the movie). It turns out that this shot was created by dropping a model and viewing it from above.
Here is my video analysis (with angular size) to show that the model is indeed accelerating as it moves away.
Bonus: one of the guys that made this special effect sent me an email after I posted this. Winning.
I started off writing a book review (How to Invent Everything: A Survival Guide for the Stranded Time Traveler – Ryan North). In the book, he suggests that if you were starting from scratch it would be easier to build a radio transmitter than it would be to build a clock. Of course (from a previous post), a clock is important for navigation. If you had a radio transmitter, you could just broadcast the time.
OK, but how difficult is it to build a transmitter? Not too hard. I did it. Here is my spark gap transmitter.
Why are you still here? Oh, you are waiting for just one more post? Or maybe you think this was too many? No, it’s 16 out of 106. That’s just 15 percent of my posts.
Who is Rhett? Where is he from? What are his super powers? Why do you want to contact Rhett for your project? Let’s answer these questions.
Super Brief History
How about just the highlights? Yes.
Born in the past, not the future.
B.S. in physics from Benedictine University (although it was called I.B.C. back then).
M.S. in physics from the University of Alabama (including work at CERN).
Ph.D. in physics from NC State University.
Some other stuff here.
Associate Professor of Physics at Southeastern Louisiana University.
Stuff I Do: Blogging
Yes, I like to write. Blogging is the best (for me). It’s quick and free form. You can use a variety of tools (video, gif, graph, python). It’s just the best. THE BEST!
I should probably include some of my favorite posts—but there are just too many that I love. If you want a post on a particular topic (like video analysis)—just google “rhett allain video analysis” and that should get you what you need.
Oh, I also blog here—but I guess you already know that.
Stuff I Do: MacGyver
I am currently the technical consultant for the CBS show MacGyver. It’s a super fun and awesome job. But what do I do? Essentially, I help out with the “MacHacks” in the show. I look over the hacks and see if they are at least plausibly based on some real thing. Other times, I make suggestions for hacks. Finally, I offer suggestions for some of the science-type stuff that MacGyver says.
Oh, I also make DIY home-versions of hacks. Here is an example.
As a bonus, here is an interview I did with CBS KPIX out of San Fransisco on my work with MacGyver.
Stuff I Do: MythBusters
I’ve actually been working on MythBusters much longer than I have worked for MacGyver. I worked on about the last 4 seasons of the original MythBusters and then I did the reboot with Jon Lung and Brian Louden. Finally, I worked on MythBusters Jr.
So, what do I do? Really, there are two things. First thing is to do some background check on future myths. For some myths, I do some estimations and calculations to see if there is a chance of a myth working. You don’t want something that is either too easy or too hard, it should be just right.
The second thing I do is the science explanations. When there is a short explanation about how something works, I help with that.
Stuff I Do: Books
Writing books isn’t as much fun as blogging, but there it is. Here are the books I have authored.
I could talk about books more—but I’m just going to leave it at that.
Stuff I Do: Python and Numerical Calculations
It’s not my fault. If you want to blame someone—how about Bruce Sherwood and Ruth Chabay. It is through their textbook, Matter and Interactions (Wiley), that I was introduced to python and numerical calculations. It’s awesome.
Once you start solving problems by coding, it sort of gets addictive. I’ve been creating python programs since about 2003 (just a guess). Later I started putting more and more of it in my classes—and here we are.
I’m not an expert coder, but I am an expert at implementing this stuff in introductory courses. That’s what I do. I have even held workshops for teachers and educators. It’s fun.
If you want to look at the stuff I’ve done, here are three versions (all online).
Physics Python for Mere Mortals. This is an online type book with embedded code. Designed for intro students with zero previous programming experience and some physics. This is what I use in my lecture and lab courses.
Introductory Physics with Python. This is more like a full book. It’s incomplete, but the idea is to teach physics using python. I want to work on this some more.
I like to solve physics problems. Here is one for you (I just made it up).
A 4 meter ladder leans against a frictionless wall at a 30 degree angle. The mass of the ladder is 10 kg. A human stands 1 meter up the ladder and has a mass of 70 kg. What is the minimum coefficient of static friction between the floor and the ladder so that the ladder doesn’t slip?
Here is the solution—in video form.
But wait! There’s more. Let’s do another problem.
Suppose you have the same ladder and the same human. However, in this case the coefficient of static friction between the ladder and the ground is 0.55. How far up can the human move before the ladder slips?
I like this question because I don’t know how the answer will turn out. That makes it fun. So, let’s do it.
But what kind of problem is this? I’ll make this a multiple choice question. Here are your options.
A friction problem.
An equilibrium problem.
A ladder problem.
A work-energy problem.
Your answer? Go ahead and answer. It’s important to think about things like this if you want to become an expert problem solver.
Did you pick? OK, I’ll tell you that there will be quite a few students that will say this is a friction problem because it has a coefficient of friction. That’s not untrue—but it’s not a good way to classify the problem. You could also say this is a “ladder problem”—again, not untrue but not helpful.
This is an equilibrium problem. We are trying to find the point at which the ladder slips—the point it leaves equilibrium, but it’s still sort of in equilibrium.
For an object in equilibrium, there are two main ideas—especially for a rigid object. First, it must have zero net force. Second, it must have zero net torque about any point. In two dimensions, I can write these two conditions as the following three equations.
Let’s talk about the torque stuff. I don’t want to get into a whole thing about torque, so let me just say that torque is like a “rotational force” and it can be calculated as:
In this expression, F is the applied force, r is the distance from the point at which you are calculating torque, and is the angle between r and F. This equation is equivalent to F-perpendicular times r or F times r-perpendicular.
Oh, torques that would make an object rotate clockwise are negative.
One last thing about torques—especially the sum of the torques. If an object is in rotational equilibrium about some point (point “o”) then it is also in rotational equilibrium about any other point. When you set up the torque equation, you can pick whatever point you like to sum the torques—it’s your choice (but choose wisely).
Now we can start setting up some equations for equilibrium. I’ll start with a force diagram for the ladder.
I know that’s a little busy—but it will have to do. Here are some comments.
There are two normal forces. One from the wall (labeled 1) and one from the floor.
There are two gravitational forces—and this is a cheat. There is a gravitational force on the ladder and it is as though it is one force acting at the center of mass for the ladder. If the ladder has a uniform density, the center of mass is the center of the ladder.
The other gravitational force is fake. This force is there to represent the weight of the human. But that gravitational force acts on the human, not the ladder. The ladder pushes UP on the human the same as the weight. Since forces come in pairs, an upward pushing force from the ladder means there is a downward pushing force from the human on the ladder. It’s equal to mg, but not mg.
The friction force is parallel to the floor. The maximum magnitude of this friction force would be: where is the coefficient of static friction.
Now for some equations. First, this is the sum of the forces in the y-direction.
Just a quick reminder. These are not vectors. These are components of vectors in the y-direction. That’s why the two gravitational forces have a negative sign. I guess I can simplify this a little bit.
Next is the sum of forces in the x-direction.
Since we are at the point of maximum friction, I can include the expression for the frictional force in terms of the coefficient.
Notice that I know the value of since it only depends on the mass of stuff—but I don’t know . I’m going to need another equation. That’s where the sum of the torques comes in.
In order to write down the sum of the torques, I need to pick a point about which I calculate the torque. I’m going to go with the bottom of the ladder. At this point, there are two forces applied. Since they are applied at the point about which the torque is calculated, they contribute zero torque and they won’t appear in the equation. Winning.
Here is the sum of the torques about point O (at the bottom of the ladder).
What do I want to solve for here? I want the distance the human goes up the ladder. This is the value “s” in the expression above. Really, I have all the values I need in that expression to solve for s. I just need to set to the maximum frictional force. But that would be boring.
Instead, let me make a plot of the frictional force as a function of human distance up the ladder. That will be more fun, right?
But this isn’t the best system. The problem is that there are two coordinates—the angle for the top bar and the angle for the bottom bar. Sure, it’s cool—but what if you want to plot angle vs. time or something. You have to plot both angles vs. time and that’s a bummer.
OK, how about a model of bounded population growth? That’s just one dimensional, right? Actually, it doesn’t even have to be population, it’s just an equation—something like this.
In this expression, r is some parameter—it really doesn’t matter what. Let’s just model this expression for different values of r. I’ll use a starting x value of 0.1 and r values of 0.7 and 0.9. Here is the code.
Notice that when r = 0.7, the population reaches some stable value—but this is not true for r = 0.9.
Now for another way to look at a chaotic systems—the bifurcation diagram. Honestly, I didn’t really understand these things until I made one. Here’s what we are going to do.
Start with some initial value of x (just pick something—I’m going to use 0.5). Pick a value for r also. Let’s just start at 0.1.
Run the model for 200 iterations and throw out that data. This should allow us to look at the long term behavior for that particular value of r (throws out the transient behavior).
Now run the model for 100 additional iterations and save these.
Create a plot of these final x values vs. r.
Next increase the r value a little bit (I will increase it by 0.001)
Repeat until you get bored.
So if the model is stable after the initial stuff, then it will just keep plotting the same value of x after the first 200 iterations and you will just get a dot. If it’s not stable after the first stuff, then you will get a bunch of dots with different x values.
OK, let’s do it. Here is the code. Oh, I made a function to iterate the model. I probably should put more comments in there.
This is what it looks like.
Up to an r value of about 0.75, you only get one final x value. After that, you get two different values . With r over 0.9, it gets crazy.
OK, that’s enough for now. I just want to make sure future Rhett knows how to make a bifurcation diagram.
Let me be clear—something isn’t working with my program. However, I think the idea is solid. Also, by writing this I might be able to figure out my problem.
Two Forms of Angular Momentum
I’ll just just to the main point. I’m trying to make a connection between the two forms of angular momentum. The first is the point-particle definition. This says that the angular momentum of a point is defined as:
In this expression, L is the angular momentum, r is the position vector, and p is the linear momentum.
The other form of angular momentum is defined as:
Here ω is the angular velocity vector for a rigid object and I is the moment of inertia tensor.
Ok, let’s get started. I’ll begin with a simple case and move to more complicated stuff.
A free particle.
A particle has a mass m and moves with a constant velocity (no external forces). What happens to the angular momentum? Here is a python program for a free particle in which I also calculate the angular momentum. This is just a picture – you need to go here to run it.
Here is a plot of the z-component of the angular momentum in this case.
Notice that it’s constant. Oh, I assume you know about cross products—they are in vpython, so you don’t have to do it manually.
So, yes—angular momentum is conserved. No big surprise there. But what if you change the origin? Is angular momentum still conserved? Try it.
There is very little point looking at the moment of inertia. I’ll do that next.
Single object constrained to circular motion.
I want to get an object moving in a circle—but I don’t want to make some crazy constraint. This sounds like a job for THE SPRING. Yes, I will model an object moving in circular motion by using a spring attached to the object and some stationary thingy.
If you calculate the angular momentum (from the linear momentum), here is what you get.
It doesn’t look constant—but I think that’s just a rounding error. Reminder: this is the angular momentum from . What if I use the moment of inertia and the angular velocity? Do I get the same thing?
I can calculate the angular velocity as:
For objects moving about a fixed axis, the moment of inertia is a scalar value that is calculated as:
Notice that if you put these two definitions together, you get (essentially):
So it should work.
Using a stationary pivot point can cause some problems. Since the pivot point is stationary, there must be some external forces on the system. This means that calculating momentum and angular momentum can be difficult.
What happens if the center of mass of the system is not zero? In this case, I need to redo the angular momentum calculation. First, for the point model, it would be still be r cross p, but I can write it two ways:
In this case, the 1r subscript means the position relative to the center of mass and the momentum relative to the center of mass. The com subscript means center of mass.
For the moment of inertia method, I have:
But this is where I will stop. For some reason, I can’t get a constant angular momentum using the moment of inertia. Here is the plot of the component of momentum for the case when the center of mass is moving.
I feel like I am making some silly mistake. So, here are some notes and comments.
Maybe I am calculating the relative velocity incorrectly.
Maybe it has something to do with my definition of the angular velocity.
Note that the two masses can have slightly different angular velocities since this isn’t actually a rigid object—it’s just mostly rigid (stiff spring).
I feel like I have so many different programs, that I’m losing track of what works (that’s why I wrote this blog post).
What’s the next step? Well, after getting this calculation to work—I have big plans. The ultimate goal is to have a 4 mass rotator (4 masses connected by springs) and calculate the moment of inertia and the angular momentum. I would be very happy if I could show that the angular velocity vector doesn’t have to be in the same direction as the angular momentum vector. That would be cool.
There should be a grave yard for blog posts that start, but never get published. Fortunately, I have this site. Here I can share with you my failed posts. Get ready.
It starts with this epic video from the Soyuz MS-10 failed launch.
That’s pretty awesome. It’s doubly awesome that the astronauts survived.
Ok, so what is the blog post? The idea is to use video analysis to track the angular size of stuff on the ground and from that get the vertical position of the rocket as a function of time. It’s not completely trivial, but it’s fun. Also, it’s a big news event, so I could get a little traffic boost from that.
How do you get the position data? Here are the steps (along with some problems).
The key idea is the relationship between angular size, actual size and distance. If the angular size is measured in radians (as it should be), the following is true where L is the length (actual length), theta is the angular size, and r is the distance.
Problem number 1 – find the actual distance of stuff on the ground. This is sort of fun. You can get snoop around with Google maps until you find stuff. I started by googling the launch site. The first place I found wasn’t it. Then after some more searching, I found Gagarin’s Start. That’s the place. Oh, Google maps lets you measure the size of stuff. Super useful.
Finding the angular size is a little bit more difficult. I can use video analysis to mark the location of stuff (I use Tracker Video Analysis because it’s both free and awesome). However, to get the angular distance between two points I need to know the angular field of view—the angular size of the whole camera view. This usually depends on the camera, which I don’t know.
How do you find the angular field of view for the camera? One option is to start with a known distance and a known object. Suppose I start off with the base of the Soyuz rocket. If I know the size of the bottom thruster and the distance to the thruster, I can calculate the correct angular size and use that value to scale the video. But I don’t the exact location of the camera. I could only guess.
As Yoda says, “there is another”. OK, he was talking about another person that could become a Jedi (Leia)—but it’s the same idea here. The other way to get position time data from some other source and then match that up to the position-time data from the angular size. Oh, I’m in luck. Here is another video.
This video shows the same launch from the side. I can use normal video analysis in this case to get the position as a function of time. I just need to scale the video in terms of size. Assuming this site is legit, I have the dimensions of a Soyuz rocket. Boom, that’s it (oh, I need to correct for the motion of the camera—but that’s not too difficult). Here is the plot of vertical position as a function of time.
Yes, that does indeed look like a parabola—which indicates that it has a constant acceleration (at least for this first part of the flight). The term in front of t2 is 1.73 m/s2 which is half of the acceleration. This puts the launch acceleration at around 2.46 m/s2. Oh, that’s not good. Not nearly good enough. I’m pretty sure a rocket has an acceleration of at least around 3 g’s—this isn’t even 1 g. I’m not sure what went wrong.
OK, one problem won’t stop me. Let’s just go to the other video and see what we can get. Here is what the data looks like for a position of one object on the ground.
You might not see the problem (but it sticks out when you are doing an analysis). Notice the position stays at the same value for multiple time steps? This is because the video was edited and exported to some non-native frame rate. What happens is that you get repeating frames. You can see this if you step through the video frame by frame.
It was at this point that I said “oh, forget it”. Maybe it would turn out ok, but it was going to be a lot of work. Not only would I still have to figure out the angular field of view for the camera, but I need to export the data for two points on the ground to a spreadsheet so that I can find the absolute distance between them (essentially using the magnitude of the vector from point A to point B). Oh, but that’s not all. When the rocket gets high enough, the object I was using is too small to see. I need to switch to a larger object.
Finally, as the rocket turns to enter low Earth orbit, it no longer points straight up. The stuff in the camera is much farther away than the altitude of the rocket.
OK, that’s no excuse. I should have kept calm and carried on. But I bailed. The Soyuz booster failure was quite some time ago and this video analysis wouldn’t really add much to the story. It’s still a cool analysis—I’ve started it here so you can finish it for homework.
Also, you can see what happens when I kill a post (honestly, this doesn’t happen very often).
Actually, there is one other reason to not continue with this analysis. I have another blog post that I’m working that deals with angular size (ok, I haven’t started it—but I promise I will). That post will be much better and I didn’t want two angular size posts close together.