DevKiD

Today using another framework. RP HAL. And receiving the delivery of 4 picos. Not much done today. And reprogramming the code and the firmware about a million times.

Creating for CANSAT a financial report and update the firmware. Taking another Approach.

Creating the first step

Fixing github problems and trying again the firmware in rust. Having hopes for rust.

Fixing and reformating code and adding prime fac

Making the second rev. Now 3 Microcontroller are on board: Pico, Zero and Esp32

Making Schematics

Having problems with the ssd. It doesn't want to work with me. (Firmware still doesn't work)

Building Firmware and getting results that are somehow wrong. Why do I get 3.3V at Pin 21 and not GPIO 21.

Gathering about 600€ and building the first firmware. - Having trouble with the normal OS - always the Network Error Not Reachable.

In 5 days, I will come back with a new update.

Today is the last day. This project will be stopped for 1 month. I will now develop a firmware for the raspberry PI.

Adding inverse hyperbolic functions.

Adding hyperbolic functions.

Adding more trigonometry and PI. Also Building a satellite.

Today: remove intervals - make the project easier and more cross-platform compactible.
Adding trigonometry and having a bad day. Create a pull request and haven't sleep. So today I've done only a bit.

Testing new features from yesterday. Getting error because musl isn't on 2 os. Everything other works just as fine as before.

Programming today the planned intervals. Intervals are there to execute function in loops from a to b in x steps. But C++ cannot run as example a python function because it is out of scope. So I develope a system where function names etc. can be passed down and the API read the list of passed down function and execute them. Then it returns the value and the interval function gets satisfied. Note that the C++ version differs to the C shared version. It sounds easy but I implemented so that somehow only half of it works.

Adding more features and trying fixing the CI/CD problem while testing the shared object by some unix based systems.

After 100 Test I got the others to work. Now I can test not only with dll but also with .so and .dylib. They are ready for release but they still have too few features.

Getting destroyed by CI/CD again. Why does only one of the two in the matrix run? Anyway, I got the windows compilation running. Wasn't as hard as Lua. It's now the fifth day and I got already 18h.

Hating Lua. CI/CD for Lua is horror. It is not worth it.

I'm adding a method to handle intervals. That means when I run calculations, the results come out as intervals instead of exact values. This helps when values might vary a bit or aren't 100% known—like when dealing with measurements or approximations. It's useful for checking how results change over a range. https://github.com/DevKiDCosmo/TheMathLib/blob/main/docs/basics_notes.md#drafts-to-variable-and-calculation-with-formulas

Today I integrated support for several language APIs: Java, Rust, Go, .NET, and Lua. To streamline development and reduce redundancy, I'm planning to create a universal definitions file. This file will serve as a single source of truth across all APIs—allowing the core logic to dynamically load definitions and generate the appropriate language-specific function interfaces. Next step: refactor the current implementation to auto-generate language bindings based on these shared definitions.

Fixing the class and linking problem. Now files can use function from other class. Before due to restriction redefinition errors appear.

Updating API for PY. Using C++ and C to create dll can be handy. Now creating API for Java, Kotlin, Go, Rust... Yeah, a lot of work to do.

Adding more mathematical formular to the current collection.

Now adding API for different languages. Finally getting permutation to work and updating docs. It was painful.

Enhanced the basics.md documentation to include clearer organization and more details on math functions available in Moo.
Breaking my head of something like type errors.

• Creating a docs for everything that will be featured. Beginning from the basics
• Struggling with C and C++