Give every project into own file
This commit is contained in:
8
projects/2d-fluid-sim.md
Normal file
8
projects/2d-fluid-sim.md
Normal file
@@ -0,0 +1,8 @@
|
||||
# 2D Fluid Sim
|
||||
A simple 2D fluid simulation that would allow me to get a basic analysis of a cross-section of a wing or similar structures.
|
||||
|
||||
## References
|
||||
- [PDF by 10 Minute Physics](https://matthias-research.github.io/pages/tenMinutePhysics/17-fluidSim.pdf)
|
||||
|
||||
## implementations
|
||||
- [Rust Fluidsim](https://gitea.lol3r.com/leon/fluidsim)
|
||||
5
projects/calorie-tracker.md
Normal file
5
projects/calorie-tracker.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Calorie Tracker
|
||||
A simple calorie tracker
|
||||
|
||||
## implementations
|
||||
- [CalFlow](https://gitea.lol3r.com/leon/calflow)
|
||||
2
projects/camera-tracker.md
Normal file
2
projects/camera-tracker.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Camera tracker
|
||||
Software that can "lock" onto something on the screen and try to track it
|
||||
5
projects/combine-exchange-locks.md
Normal file
5
projects/combine-exchange-locks.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Implement Combine-and-Exchange locks
|
||||
A different type of lock for async contexts
|
||||
|
||||
## References
|
||||
- [Paper proposing the idea](https://arxiv.org/abs/2511.09194)
|
||||
3
projects/crystalline-memory-reclaimation.md
Normal file
3
projects/crystalline-memory-reclaimation.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# Crystalline memory reclaimation
|
||||
A lock-free/wait-free (depending on configuration used) memory reclaimation scheme for concurrent data structures.
|
||||
I want to implement this as a Rust crate, with a safe interface that should basically make it impossible to misuse (as little unsafe as possible in public API)
|
||||
3
projects/cs-demos.md
Normal file
3
projects/cs-demos.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# Parse CS Demos
|
||||
I already worked a bit on analysing cs demos in the past and would love to have a solid implementation for this in rust.
|
||||
It should be flexible enough to allow one to build different tools using it.
|
||||
3
projects/custom-drone-software.md
Normal file
3
projects/custom-drone-software.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# Custom drone software
|
||||
I would love to have my own implementation for drone control software.
|
||||
This should involve all the bells and whistles, like parts for receiving input commands, autonomous operation etc.
|
||||
2
projects/custom-minecraft-proxy.md
Normal file
2
projects/custom-minecraft-proxy.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Custom Minecraft Proxy
|
||||
This would require the [protocol implementation](#sans-io-rust-implementation-of-minecraft-protocol) to be done first or at least developed alongside.
|
||||
2
projects/custom-rust-async-runtime.md
Normal file
2
projects/custom-rust-async-runtime.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Custom Rust async runtime
|
||||
A custom async runtime for rust to try out my own ideas for a runtime.
|
||||
2
projects/custom-visualisations-for-firefly-iii.md
Normal file
2
projects/custom-visualisations-for-firefly-iii.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Custom Visualisations for Firefly III
|
||||
I am already tracking basically all of my finances in my personal Firefly III instance, but I feel like there could be more interesting insights hidden in the data that is not being shown by default.
|
||||
1
projects/e-graph-implementation.md
Normal file
1
projects/e-graph-implementation.md
Normal file
@@ -0,0 +1 @@
|
||||
# E-Graph implementation
|
||||
1
projects/epaxos-implementation.md
Normal file
1
projects/epaxos-implementation.md
Normal file
@@ -0,0 +1 @@
|
||||
# EPaxos implementation
|
||||
1
projects/fourier-transform.md
Normal file
1
projects/fourier-transform.md
Normal file
@@ -0,0 +1 @@
|
||||
# (Fast) Fourier Transform
|
||||
1
projects/graph-layout-engine.md
Normal file
1
projects/graph-layout-engine.md
Normal file
@@ -0,0 +1 @@
|
||||
# Graph Layout Engine
|
||||
1
projects/image-processing-in-rust.md
Normal file
1
projects/image-processing-in-rust.md
Normal file
@@ -0,0 +1 @@
|
||||
# Image Processing in Rust
|
||||
2
projects/jiffy-queue.md
Normal file
2
projects/jiffy-queue.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Implement jiffy Queue
|
||||
A lock free queue
|
||||
1
projects/memory-ssa.md
Normal file
1
projects/memory-ssa.md
Normal file
@@ -0,0 +1 @@
|
||||
# Memory SSA
|
||||
6
projects/minecraft-items.md
Normal file
6
projects/minecraft-items.md
Normal file
@@ -0,0 +1,6 @@
|
||||
# Visualise minecraft items and their relations
|
||||
Ingest the information about minecraft items and entities and their relations somehow and then generate different (interactive) graphs that show the relations between items.
|
||||
Possible relations:
|
||||
- Used in crafting recipe
|
||||
- Dropped by
|
||||
|
||||
2
projects/nomad-gitlab-runner.md
Normal file
2
projects/nomad-gitlab-runner.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Nomad Gitlab Runner
|
||||
A Gitlab Runner that will spawn the given jobs on a Nomad cluster for easier scaling
|
||||
1
projects/pid-in-rust.md
Normal file
1
projects/pid-in-rust.md
Normal file
@@ -0,0 +1 @@
|
||||
# PID in Rust
|
||||
1
projects/postgres-protocol-implementation.md
Normal file
1
projects/postgres-protocol-implementation.md
Normal file
@@ -0,0 +1 @@
|
||||
# Postgres protocol implementation
|
||||
1
projects/rust-crate-to-receive-obs-stream.md
Normal file
1
projects/rust-crate-to-receive-obs-stream.md
Normal file
@@ -0,0 +1 @@
|
||||
# Rust crate to receive stream from OBS
|
||||
@@ -0,0 +1 @@
|
||||
# Sans-IO Rust implementation of minecraft protocol
|
||||
2
projects/sensor-fusion.md
Normal file
2
projects/sensor-fusion.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Sensor Fusion
|
||||
Things like Kalman-Filters etc.
|
||||
1
projects/signal-processing.md
Normal file
1
projects/signal-processing.md
Normal file
@@ -0,0 +1 @@
|
||||
# Signal Processing
|
||||
3
projects/state-machine-crate.md
Normal file
3
projects/state-machine-crate.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# Rust crate for state machines
|
||||
I would like to have a rust crate to dynamically or statically create state machines in rust without any macros.
|
||||
The state machines should allow for synchronous and asynchronous transitions and ideally be serializable as well.
|
||||
2
projects/vault-secret-engine-ceph-s3.md
Normal file
2
projects/vault-secret-engine-ceph-s3.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Vault secret engine for ceph s3
|
||||
A custom vault secret engine to dynamically generate and handle s3 credentials for ceph.
|
||||
1
projects/vault-secret-engine-ceph-users.md
Normal file
1
projects/vault-secret-engine-ceph-users.md
Normal file
@@ -0,0 +1 @@
|
||||
# Vault secret engine for ceph users
|
||||
2
projects/vault-secret-engine-gitlab-tokens.md
Normal file
2
projects/vault-secret-engine-gitlab-tokens.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Vault secret engine for gitlab tokens
|
||||
A custom vault secret engine to dynamically generate and handle gitlab access tokens with different scopes.
|
||||
1
projects/wait-free-memory-allocator.md
Normal file
1
projects/wait-free-memory-allocator.md
Normal file
@@ -0,0 +1 @@
|
||||
# Wait-Free memory allocator
|
||||
6
projects/werewolf-bot.md
Normal file
6
projects/werewolf-bot.md
Normal file
@@ -0,0 +1,6 @@
|
||||
# Implement new werewolf bot
|
||||
I would love to have a more flexible werewolf bot implementation.
|
||||
The goals would be relatively ambitious:
|
||||
- Allow for custom role implementations (likely using custom programming language)
|
||||
- All role behaviour should be modeled using state machines and be deterministic for a single playthrough
|
||||
- The state of a playthrough should be saved somehow to tolerate failures or restarts of the bot
|
||||
2
projects/wordle-solver.md
Normal file
2
projects/wordle-solver.md
Normal file
@@ -0,0 +1,2 @@
|
||||
# Wordle Solver
|
||||
A simple program to help in solving wordle.
|
||||
Reference in New Issue
Block a user