Algodoo

If a tic happens within a frame then display the count.

Thanks. I found this linkage very interesting from a mathematical standpoint. The first thing I noticed, is that for a first order approximation (dx = r*(1-cos(a)) ≈ r*a^2/2), dx of the orange link equals the dx of the blue link.

If a = angle, r = radius, r1 = radius of blue link, r2 = radius of orange link, and r2 = 0.25*r1 then:
dx = r1*(0.75+0.25*cos(2*a1)-cos(a1))
If we use the first three terms of a Taylor series approximation for cosine then:
dx ≈< 0.125*r1*a1^4

For r1=4 and a1=0.5:
dx = 0.029972
dx ≈< 0.03125

Q: Would that be true only during the linear portion of the movement?
A: Yes, I was referring only to the vertical almost straight line motion. The cosine approximation is considered a small angle approximation. There are (2) other flat spots on the tracer curve that are most likely just as straight.

Q: Can I use the code for this?
A: Yes.

Q: where can I find the code.
A: In the blue "Rotate Polygon" box._rotatePoly.

Q: How can r1 be greater than r2? (Wouldn't you have to make the bar longer?).
A: Yes.

Thanks.

Jackhammer rescue
Milling Cutter

Impressive. This is the first time I've seen the mouse wheel used as a general adjustment tool. In my mind, the mouse scroll wheel was unavailable.

Thanks. Fixed.

Nice work. You could add a charging circuit and a voltmeter (or scope) and then make the spark dependent on voltage and distance. The spark size could also be dependent on voltage.

As a side note (you know this but others may not), capacitors sometimes don't look like capacitors such as the case of CRT tubes and Helium Neon lasers.

Thanks.

Nice work. I like handy tools like this.

Maybe bendTarget = lerp(-0.075, 1.3, (_input_Data - _meterLo) / (_meterHi - _meterLo)).
or
bendTarget = lerp(-0.075, 1.3, (math.max(math.min(_input_Data,_meterHi),_meterLo) - _meterLo) / (_meterHi - _meterLo))

FYI: bendConstant is limited by motorTorque

Q: Did you take a close look at the screwdriver?
A: Ha! Not until just now. I completely missed that the first time around. You would think that, as somebody who nit picks, I would have picked up on that right away.

I see what you did and I think it's awesome.

I won't make any promises, but I'm assuming that the present adjustment is slow?

Yes, good. I suspect you will be in highlighted scenes shortly.

I like your idea but I'm not going to do it because I don't think I can do it well enough to be effective. I'm going to start by using the mouse click to shift between two step sizes. Working on it...

Thanks.

That's because the volt meter and pot are each connected in parallel with the voltage doubler circuit that's after the flyback transformer.

Well done.

Thanks for the link. I can see where the adjustable stiffness beams could be replaced by Algodoo springs. I would need to understand the algorithms. This is something that Kilinich, UnityDogGaming0, Little, and a few other Algobox users might be able to handle.

I stated "it appears that Algobox has failed to load this scene.". The phunlet loads, but a user may not realize it.

Nice scene. Good presentation. Tight code. Rated 10.

I did the following to get the scene to run at 100% of simulation time:

1. Converted network visualization to an image.
2. Put input box postStep code into onClick.
3. Deleted number display box postStep code.
4. Set simulation frequency to 30.

Rated highly because I like the flip motion.

I concur with your Algodoo Forum post. I chose to put the code in postStep because that allows the user to speed up or slow down time by changing the simulation speed or frequency. If I was more interested in accuracy than entertainment, then I would use system.time. I may still do that in a second version.

Thanks. That must have been due to aliasing between the update rate and system.time. I changed the code to update the time midway thru system.time seconds.

Thanks.

It turns out that Algodoo system.time is not as accurate as I thought. On my PC, the clock lost 64 seconds in 10 hours when compared to the PC time.

376 users that are now running Flip Clock Mod II are going to be disappointed. I could probably write a Python program that could send the PC system time to an Algodoo text input menu by using sendkeys or something like that.

Q: I tried running your script via the command line interpreter. Could that possibly be the problem?
A: Yes, AlgoTime.py needs to be in the C:\Users\Xray\Documents\Algodoo folder. You should be able to run it by double-clicking the file. A command window should then open and stay open. If the command window stays open, then it's probably working OK. If it opens but immediately closes, then Python doesn't like the script. The modules "time" and "datetime" need to be loaded on your system. If you run the file using IDLE, it will probably tell you if it doesn't see a module. Modules are typically loaded by by entering "pip install modulename" in a command window. Python indentation is critical. Any indentation errors will cause the code to fail. If you run the file in IDLE, it will tell you at what line the code fails. If the file runs in IDLE, but double clicking the file doesn't open it, then Python needs to be in your PATH variable. If the code runs correctly and is in the right place, but the clock in the scene doesn't update, then you probably need to set _readPythonTime = true in the time setting box script below the clock. I've updated the Python code in the latest scene edit, but the old code and the new code should both work.

P.S. If I right click on AlgoTime.py and choose "Open with" and select Python then the code doesn't work because it's apparently running somewhere other than the Algodoo folder. That's why Python needs to be in your PATH variable (or you need to put "with open('C:\Users\Xray\Documents\Algodoo\AlgoTime.txt', 'w') as f:" in AlgoTime.py).