Mavo 🇺🇦
Open Source Optimization Framework Developer
- Posts
- 769
- Followers
- 33
- Following
- 49
-
I have also decided, to create a mini test framework for configs, that tracks changes in configs and requires the developer to explicitly confirm any changes via a verification file in version control. This is important when configs of multiple evolving modules are merged into one.
-
Today I fixed my production configuration, which was destroyed by migrating to the new Cell API for the configuration. It failed because the existing config code was/is spaghetti and untangling the mess is partially only possible via trial and error. Fortunately, the certificate update via let's encrypt and ACME4j is working again.
Oh, will I be happy, when the migration to the Cell API is done :)
-
So, I created a very simple solver for problems composed of interconnected optimization problems. I tried it on the first simple example and it returned a none empty solution with zero cost? Suspicious 🤨
-
The 10 Thousandth commit 🍻
-
Now the constraint tree representation is compacted 😗
You can think of it as a debugging tool for constraints generated based on the problem definition.
-
So the test data generation for sport courses seems to be working 🥸
-
The price of round brackets is exploding! 💰
Therefore I finalized my modifier syntax. This way nested function calls can sometimes avoid brackets.
Save your money today!
-
Working on an alternative modifier syntax for nested function calls 🏢
-
Example loading is now fully working 🏇
-
Now I've drafted a simple example loading mechanism 🛞
-
The first dynamic example loading worked! 💃
-
Introducing sub menus to the constraint editor
-
Defining one rater at a time for the sport course planning.
-
I have now set up CPU profiling on my live server 🌌
-
Starting to work on a new optimization problem 🤩
-
The generated function call documentation is starting to take shape 🥤
-
Now there is a minimal number of days between exams!
-
Adding concrete values to the argumentation of selectors 🧉
-
Working on arguments for ratings
-
mhhhh, I am having to write less error messages than expected for my editor
🤔💭
My previous editor did the ANTLR based parsing and interpretation at once,
which required a lot more error checking.
So, splitting up the parsing and interpretation reduced the need for error handling... but still .. 🤔💭 ... by that much ... -
Starting error handling and reporting
-
Today I deleted the code editor, in order to replace it with the Geal editor ✅
-
So, I have migrated major parts of the editor's GUI to the new Geal programming language 😊
🚧 Now user facing errors need to be done 🚧
-
Parsing the start and end of projects for the notification queue
-
Fun fact: everything except for strings and integers is now a function call, as it simplifies the language and its interpreter. This also applies for references. 😂
-
Working on a GUI launcher for my server program.
-
Today I found out, that certain grammar rules in ANLTR4 can lead to unusable error messages.
-
The next spam account from LinkedIn: [email protected]
-
-
Using the monospace font family for the code editor, so one can make the source code formatting extra nice.
-
Now the accomplishments of the day are deployed 🎇
https://live.splitcells.net/net/splitcells/gel/ui/editor.html
-
Indicating the currently selected tab seems to be a good idea as well 💐
-
...and an error indicator is included as well 🎁
-
Now there is a result update indicator as well 💝
-
Now there are also tables 💘
-
So, I think the decision was made: I'll first do a test run with git-bug and see if it works. If this is the case, it will be my permanent solution:
https://todo.sr.ht/~splitcells-net/net.splitcells.network/122