Since this will be my first real "from the start" publication the goal for me has more to do with the experience of publishing the projects, use of the public hosting site and access tools, particularly git.
The projects that will be published are:
Python based
Qt 6. based
One is a V4L2 device regular frame capture to jpeg file application (I use it ultimately to create daily timelapse videos of the vew from my home)
This application has a view on the main window that shows a simulation of the time-of-day using a graphical model (a sun passing through a ground/sky view with colors that are based on day time and a moon passing through a ground/sky view with colors that are based on night time)
One is a three part audio meter where the parts are all in the same UI window and are:
a) A live self-relative dB meter at a user chosen sample rate and update frequency
b) A moving day-view track of the minimum and maximum signal level
c) A moving day-view track of the audio frequency content via FFT
The current state of both projects is usable, almost fully functional, with the potential for some improvements (e.g. optimizing 5 to reduce it's runtime overhead, which is difficult for an app doing filtered, windowed and FFTed liveaudio sample data)
Both apps make decent example Python Qt6, a v4L2 client and audio capture applications
My interest in 3 is the creation of daily timelapse videos of the view from my home because in snow storms the videos look great but I wanted the frame capture automated and just left to run. My interest in 5 was a matter of exploring audio capture client interfaces with no real purpose, ergo two different signal level meters and an audio spectrum content meter were "things to do".
The audio meter application could be developed by anyone with access to monitor for problems at a location, which is one of the reasons for wanting to publish it for the benefit of others.
Both would be GPL3 licensed.
This project is part of:
Hack Week 23
Activity
Comments
Similar Projects
Improve chore and screen time doc generator script `wochenplaner` by gniebler
Description
I wrote a little Python script to generate PDF docs, which can be used to track daily chore completion and screen time usage for several people, with one page per person/week.
I named this script wochenplaner and have been using it for a few months now.
It needs some improvements and adjustments in how the screen time should be tracked and how chores are displayed.
Goals
- Fix chore field separation lines
- Change screen time tracking logic from "global" (week-long) to daily subtraction and weekly addition of remainders (more intuitive than current "weekly time budget method)
- Add logic to fill in chore fields/lines, ideally with pictures, falling back to text.
Resources
tbd (Gitlab repo)
openQA log viewer by mpagot
Description
*** Warning: Are You at Risk for VOMIT? ***
Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?
You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).
This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."
Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.
No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")
This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.
Goals
Work on the existing POC openqa-log-visualizer and change it to something usable
Resources
Improve/rework household chore tracker `chorazon` by gniebler
Description
I wrote a household chore tracker named chorazon, which is meant to be deployed as a web application in the household's local network.
It features the ability to set up different (so far only weekly) schedules per task and per person, where tasks may span several days.
There are "tokens", which can be collected by users. Tasks can (and usually will) have rewards configured where they yield a certain amount of tokens. The idea is that they can later be redeemed for (surprise) gifts, but this is not implemented yet. (So right now one needs to edit the DB manually to subtract tokens when they're redeemed.)
Days are not rolled over automatically, to allow for task completion control.
We used it in my household for several months, with mixed success. There are many limitations in the system that would warrant a revisit.
It's written using the Pyramid Python framework with URL traversal, ZODB as the data store and Web Components for the frontend.
Goals
- Add admin screens for users, tasks and schedules
- Add models, pages etc. to allow redeeming tokens for gifts/surprises
- …?
Resources
tbd (Gitlab repo)