gravitation | n-body-simulation performance test suite | GPU library

I need to perform a ZOH discretization of a continuous LTI state-space model in OpenModelica (OMEdit). I tried two ways of doing this:

1. using matrix exponential (Matrices.exp function) for calculating discretized A matrix (A_d) and subsequent calculation of discretized B matrix (B_d) following equation: B_d = A^-1 (A_d - I) B, where I is identity matrix; This algebraic equation can be solved either by direct calculation of matrix inversion (Matrices.inv function) or, more efficiently, by solving for B_d matrix using Matrices.solve2 function: Bd = Matrices.solve2(A,(Ad-identity(2))), thus avoiding calculation of matrix inversion. However, in both cases A matrix must be invertible, what generally (and very often) doesn't hold.
2. using Matrices.integralExp function which should return both discretized matrices (A_d, B_d) and should work for general matrix A, whether invertible or singular; However, this function does not work for me - it returns error message: "No viable alternative near token: (".

I attach code for both methods for demonstration purpose. The state space model represents a very simple second-order system of linearized pendulum with length 1 m, mass 1 kg and gravitational acceleration 9.81 m/s². Sampling time for discretization is 0.1 s. The first code works fine (A is invertible in this particular case) but the second code doesn't. Does anybody know what am I doing wrong? I'd be grateful for any advice.

method #1:

this is my first post! With that in mind, if I need to add anything more than what is below, please let me know. Thank you!

I am currently working to make a platformer game in Javascript where a player can move using arrow keys. Currently, my left and right movements, as well as my player gravity, works. However, when I jump, I am unable to provide smooth jumping movements. originally, I tried simply moving my player's y value higher.

this is my website that I am developing, and I trying to develop a calculator which depending on the subject and equation your are trying to use, the calculator will give you an answer.

I made two dropdown menus, however, when I hover over the "Physics" menu, for some reason the "Maths" menu is covered. Also, the list for "Physics" is a bit too long and I wanted to make a scroll bar, but I don't know how to.

I tried to look on w3schools and other resources, but I couldn't find a solutions which solved my problem.

I pretty much deleted the last code and started new. I added a new class called Object which is the replacement for the lists called body_1 and body_2. Also all the calculations are now done from within the Object class. Most previous existing issues were resolved through this process but there is still one that presists. I believe its inside the StartVelocity() function which creates the v1/2 needed to start the Leapfrog algorithm. This should give me a geostationary Orbit but as clearly visible the Satelite escapes very quickly after zooming through earth.

Codes are:

Why does my Fortran code execute 5 times faster than my C++ code to solve this second order differential equation (for universal gravitation between a planet and a sun) using RK4? How could I optimize my C++ code, please ?

I have tried changing pow() to x*x with no improvements. Removing the write operations divided execution time by 2 on Fortran, but only made C++ code about 15% faster.

Here are the codes:

C++ (compiled with: c++ -Wall -Wextra equadiff.cpp -o equadiffcpp.x):

I am planning to acquire position in 3D cartesian coordinates from an IMU (Inertial Sensor) containing Accelerometer and Gyroscope. I'm using this to track the objects position and trajectory in 3D.

1- From my limited knowledge I was under the assumption that Accelerometer alone would be enough, resulting in acceleration in xyz axis A(Ax,Ay,Az) and would need to be integrated twice to get velocity and then position, but integrating would add an unknown constant value, this error called drift increases with time. How to remove this error?

2- Furthermore, why is there a need for gyroscope in the first place, cant we just translate the x-y-z axis acceleration to displacement, if accelerometer tells the axis of motion then why check orientation from Gyroscopes. Sorry this is a very basic question, everywhere I checked both Gyro+Accel were used but don't know why.

3- Even when stationary and not in any motion there is earth's gravitation force acting on the sensor which will always give values more than that attributed by the motion of sensor. How do you remove the gravity?

Once this has been done ill apply Kalman Filters to them to fuse them and to smooth the values. How accurate is this method for trajectory estimation of an object for environments where GPS is not an option. I'm getting the Accelerometer and Gyroscope values from arduino and then importing to Python where it will be plotted on a 3D graph updating in real time. Any help would be highly appreciated, especially links to similar codes.

I am currently working through problem sets for java and I am tasked with computing the acceleration of gravity however I am unsure as to get the appropriate result. The question is below:

Compute the acceleration of gravity for a given distance from the earth's center, distCenter, assigning the result to accelGravity. The expression for the acceleration of gravity is: (G * M) / (d2), where G is the gravitational constant 6.673 x 10-11, M is the mass of the earth 5.98 x 1024 (in kg) and d is the distance in meters from the earth's center (stored in variable distCenter).

Here is the code that was given to me:

I am trying to make an n-body solver (a bunch of objects gravitationally attracted to each-other). The problem is that it looks like the gravity1 function does not feed back the return objects, resulting in linear motion of the objects:

The code looks like this:

Here's a little code that I've written to get a ball bouncing in Processing. The ball should change it's color everything it bounces off the "ground" and become slower and slower and lay at the ground at the end. But - and that's the problem I've got - the ball doesn't stops changing it's color at the bottom - and that means it didn't stops bouncing, right?

The question is: How do I tell the ball to stop and not to change it's color anymore?