Debug Barkan Valvetrian Dynamics Simulation -- 2

IF YOU ARE NOT FAMILIAR WITH THIS TYPE OF WORK PLEASE DO NO BID ON IT. I WILL ONLY RESPOND TO BIDS THAT EXPLAIN THEIR FAMILIARITY WITH THIS TYPE OF WORK. This project is to debug and make a VB.net program work correctly and return the results shown in the paper it is based on. If you find that VB is not a good language for this project, I would be open to another language C++ or C# I had this project done a few years ago and the freelancer came close to a correct result but it is still not close enough to use. I don't know what the root cause of the problem is, it might be as simple as an incorrect unit conversion or it might be a more complex problem. I am hoping that someone with knowledge of how to code this type of project will take it. If are not familiar dynamic motion in flexible bodies, don't bid on this project. In your bid, explain that you are familiar with dynamic motion or I will assume that you did not read the description and don't understand the project. This program was last saved in VB Express 2010 This program is supposed to compute the reaction of a flexible valve train mechanism. The normal operating speed for an engine would be 4000 RPM. When 4000 RPM is used as an input to the program the computed results are not reasonable. The follower jumps off of the cam. If a much lower RPM is used such as 30, the follower does stay on the cam but this is not useful because an engine cannot run that slow. I have traced the problem as far as I can. 1. The functon F_func computes F1 (the force) which returns a value that is too high. F1 is computed using the function d2Zdt 2. The function d2Zdt returns a value that I think is much too high. 3. The function d2Zdt calls lin_intrp_d2Z(theta), I tried editing the function to return a lower number by multiplying the return by a small value like 0.001, this does make the result stable but it is not right of course. This is as far as I can debug this because I don't know the math or the code in this function. You can also look at [login to view URL] to see how the author wrote the program. The main point of the problem is that Inertia is not proportional to acceleration as I assume it should be. I uploaded the project and the supporting documentation.