From d0dfa96e24ec6b8818ad168292c74cb2c59d798d Mon Sep 17 00:00:00 2001 From: Barrett Ruth Date: Thu, 5 Jun 2025 18:07:01 -0500 Subject: [PATCH] fix: image addresses --- src/content/posts/autonomous-racing/multithreading-a-gui.mdx | 4 ++-- .../posts/autonomous-racing/refactoring-a-state-machine.mdx | 2 +- src/content/posts/software/from-github-pages-to-aws.mdx | 2 +- src/content/posts/software/my-cp-setup.mdx | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/posts/autonomous-racing/multithreading-a-gui.mdx b/src/content/posts/autonomous-racing/multithreading-a-gui.mdx index 7b1ebb8..48eacef 100644 --- a/src/content/posts/autonomous-racing/multithreading-a-gui.mdx +++ b/src/content/posts/autonomous-racing/multithreading-a-gui.mdx @@ -47,7 +47,7 @@ The Qt Framework is quite complex and beyond the scope of this post. Big picture How do we optimize this? It is necessary to take a step back and observe the structure of the entire application: -![single-threaded-design](/public/posts/multithreading-a-gui/single-threaded-design.webp) +![single-threaded-design](/posts/multithreading-a-gui/single-threaded-design.webp) Many flaws are now clear: @@ -68,7 +68,7 @@ First, let's pin down what exactly can be parallelized. This lead me to the follow structure: -![multi-threaded-design](/public/posts/multithreading-a-gui/multi-threaded-implementation.webp) +![multi-threaded-design](/posts/multithreading-a-gui/multi-threaded-implementation.webp) - Three callback groups are triggered at differing intervals according to their urgency on the GUI node - A thread-safe queue[^2] processes all ingested data for each callback group diff --git a/src/content/posts/autonomous-racing/refactoring-a-state-machine.mdx b/src/content/posts/autonomous-racing/refactoring-a-state-machine.mdx index 276642c..44d74d2 100644 --- a/src/content/posts/autonomous-racing/refactoring-a-state-machine.mdx +++ b/src/content/posts/autonomous-racing/refactoring-a-state-machine.mdx @@ -101,7 +101,7 @@ Considering each element of the state machine, I simplified it into the followin Since we only have $N\ll 32$ vehicle flags and $M\ll 32$ track flags, all of this information (all of the state flags) can be encoded in a `uint32_t`: -![state-encoding](/public/posts/refactoring-a-state-machine/state-encoding.webp) +![state-encoding](/posts/refactoring-a-state-machine/state-encoding.webp) The state must also store a few other relevant details: diff --git a/src/content/posts/software/from-github-pages-to-aws.mdx b/src/content/posts/software/from-github-pages-to-aws.mdx index 1c899fd..ca0bb11 100644 --- a/src/content/posts/software/from-github-pages-to-aws.mdx +++ b/src/content/posts/software/from-github-pages-to-aws.mdx @@ -44,7 +44,7 @@ A user request can be modelled as follows: 4. CloudFront checks its edge caches for the requested content. If the content is stale or not cached, CloudFront fetches the content from S3. Otherwise, it uses the cached content from an edge server. 5. CloudFront returns the content to the user's browser. -![system design of my portfolio website](/public/posts/from-github-pages-to-aws/website-design.webp) +![system design of my portfolio website](/posts/from-github-pages-to-aws/website-design.webp) # difficulties diff --git a/src/content/posts/software/my-cp-setup.mdx b/src/content/posts/software/my-cp-setup.mdx index ccb7465..c428b2c 100644 --- a/src/content/posts/software/my-cp-setup.mdx +++ b/src/content/posts/software/my-cp-setup.mdx @@ -26,7 +26,7 @@ That's it. The `makefile` relies on some scripts that compile code and run the c # neovim integration -![screenshot of my neovim competitive programming setup](/public/posts/my-cp-setup/cp-setup.webp) +![screenshot of my neovim competitive programming setup](/posts/my-cp-setup/cp-setup.webp) Leveraging [LuaSnip](https://github.com/L3MON4D3/LuaSnip), a custom `CP` user command, and some scripting for window management and asynchronous jobs, I'm able to: