 For the Circuit Python Parsec today, I wanted to look at how you can time an event in Circuit Python to figure out how long it took. So what you can see here is a little demo I have. It's a Feather RP2040 with a sharp memory display connected to it. And I'm running here a modified version of some particle code that our good friend Todd Bott wrote. And you can see here I'm listing the number of particles that are in the simulation or in the screen right now. And I'm also listing the frames per second, the frame rate that this is running at. What's important is that we've imported the time library. Once you have the time library imported, you can do things like this. I can set a variable called start time to equal time monotonic, which is the exact moment when you ask it. You get a unique time that's essentially a ticker that's been counting up since this board came online. New variable called elapsed time equals time monotonic minus that start time. So this is going to tell me how much time has gone by. Then I'm doing a little bit of math to convert this to frames per second. This FPS is an integer based on one divided by the elapsed time. And then I'm just printing that into the serial port. You can see here these are taking about 0.1 to 0.2 seconds, which equates to about six or seven frames per second. And what we can do now is we can, for fun, go in here and adjust the number of squares in the simulation. So I'm going to change this number of squares. Let's save this. It's going to restart. When this starts up, you can see it's running about one, two frames a second. It's actually slower when those are all clumped together. I am not sure why. Now it's getting up to maybe four frames a second. So you can see the difference when we had 100. We're going quite a bit faster. So that is one way that you can time how long an event takes inside of CircuitPython. And that is your CircuitPython Parsec.