Jump to content
  TPR Home | Parks | Twitter | Facebook | YouTube | Instagram 

TNK

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by TNK

  1. Loefet and I have 20+ measurements of Balder from almost every row and we can approximate where in the train the measurement was recorded with the force-characteristic of the airtime hills. You can see this in almost every coaster.

     

    Do you have data regarding the seat on the row? I feel that an lateral seat really makes a difference compared to a middle seat, not only because of the better view, but also because of the G forces.

     

    What are you trying to do with the data? Are you going to make it public, or publish it?

  2. You can clearly see the two stops on the graphic as then the forward acceleration is negative but throughout the rest of the ride there are smaller variations partially cause by this.

     

    What you are saying is true, but I don't thing that there are any conclusions to be made based on a single graph. I think that the variation is insignificant among all the other forces involved.

     

    It would be very interesting to get data in an consistent way, a few samples from the front seat, a few from the middle and a few from the back, and compare them.

     

    I went on Manta the other day, on the back seat, and it was amazing. Front row is definitely overrated.

  3. I agree with you on the normalization aspect and I would love to be able to normalize and do some noise reduction but it requires quite a load of calculations to get right as far as I know, and I'm no programming whiz to be able to get an automated program for it.

    What programs do you use for normalization and doing the noise reduction, or is that a feature which is built in to the program above?

     

    It is really easy to do the rotation of the measuring device and to do some basic noise reduction. You only need some spreadsheet calculations.

     

    To rotate the coordinates of the measuring device take a look here http://www.mathematics-online.org/inhalt/aussage/aussage444/. That is the rotation in a single plane. Since you have 3 dimensions, you have to apply the transformation 3 times.

     

    I will go step by step explaining how I got the graph for another IOA coaster Dragon Challenge: Hungarian Horntail

     

    Imagine that your measuring device is an cube withe 3 axes: forward, lateral and vertical, and you want to rotate it in the right position

     

    This is my raw data:

    1m.thumb.png.2da698c22f915a0c78f6f57cfc64fa5c.png

    Notice how in some places the vertical acceleration hit a limit at about 40 m/s^2, that is because the sensor in my Nexus 4 has a maximum range of 39.22 m/s^2, that is 4g, with g considered at 9.805

     

    At the beginning of the graph the gravitational acceleration has components on all 3 axis of the sensor, more on the lateral, and less on the forward.

     

    Using the formula here http://www.mathematics-online.org/inhalt/aussage/aussage444/, I rotated the device around it's lateral axis, until the forward axis was on the horizontal plane, so the gravitational component on it would be 0. Because of the noise, I used an average value to find the rotation angle.

     

    The lateral component is unchanged, only the forward and vertical components are changed.

    2.thumb.PNG.692cb9dcf89370f6af18407a38d1c720.PNG

    I did the same exact thing for the the lateral axis, I rotated the device around it's forward axis. This time the forward axis is unchanged, and the lateral axis becomes 0, transferring it's gravitational component to the vertical axis. Notice how the fact that the device clipped at measuring the full acceleration is not evident anymore.

     

    When stationary, the gravitational acceleration is 0 on both lateral and forward axis

    3m.thumb.png.d0656f9d48ecdbd4b3d8974798e73b07.png

    But the device is still not "straight", when the train is going forward, the acceleration is split in two components, between the forward and the lateral, but not on the vertical, we already ensured that the vertical is really "vertical".

     

    On the hill, even at constant speed, the gravitational pull is spitted between the vertical, the forward and the lateral. This is the opportunity to rotate the device one more time, so the gravitational pull has no lateral component. I rotated the device around the vertical axis, at an angle that the lateral acceleration is 0 while the train is climbing the hill.

     

    This time, since the train is moving, there is even more noise, so it is even more important to use an average value when calculating the right angle of rotation.

    4.thumb.PNG.a546aadfe15c1500c49769a9c368bbfd.PNG

    Now I calculated each point as the average of the previous 10 values, noise reduction.

    5.thumb.PNG.7ab0891e27ba644047e3282befc41ae5.PNG

    And as the average of the previous 20 values, a more aggressive noise reduction.

    6.thumb.PNG.55b910370a1ba32237adbe3f5798198f.PNG

    I hope I was clear enough, if you need help, or I haven't explained something properly, please let me know.

  4. Looks like most of the ones we do with our accelerometers. Yours seems to have more noise reduction compared to ours, and we haven't really bothered with normalization as well, so ours still needs work before they look as good as the ones you posted.

    Here is for instance SD2K

     

    I used https://play.google.com/store/apps/details?id=com.lul.accelerometer&hl=en on my Nexus 4. Every point plotted is an average of 10 readings. One reading was taken every 20 ms. Graph was done using google docs.

     

    Are your logs available anywhere? What accelerometer did you use? How is it connected to the ride?

     

    I think normalization is pretty important, and is not hard to do.

  5. Interesting. I assume that, given that there is forward acceleration throughout the ride, you didn't sit in the middle, right?

     

    I don't see how forward acceleration can be influenced greatly by the seat on the ride.

     

    There are 5 distinct changes in the forward acceleration:

     

    1: the train leaves

    2: ascending part (because the inclination changes the gravitational acceleration component is present on the movement direction)

    3: launch

    4: first stop

    5: complete stop

    Hulk1.thumb.png.1fda1d19af4e0d46da0b71e1eea82db3.png

  6. I have recently been to Universal IOA and rode Hulk. I have recorded the acceleration using my phone. After a bit of data processing (normalizing the axes) I got this graph.

     

    I have 10 different readings, this is just one of them. There are lots of error sources, including a few samples that are clipped (acceleration was over the sensor limit). I do have data for the blue track of the Dragon Challenge, Manta and Kraken, but I haven't looked at it yet.

     

    A few observations:

     

    Maximum total acceleration: about 3.5G

    Maximum lateral acceleration: less than 1G

    Maximum forward acceleration: a bit over 1.5G (at launch)

    Actual ride length: about 45 seconds

     

    I am wondering if this was done before

    Hulk.thumb.PNG.480994f1b42ed453ae4f8d110c04a099.PNG

×
×
  • Create New...

Important Information

Terms of Use https://themeparkreview.com/forum/topic/116-terms-of-service-please-read/