Fix up missing images
@ -8,7 +8,7 @@ tags: frc
|
||||
|
||||
I was scrolling through reddit the other day, and came across [this great post](https://www.reddit.com/r/FRC/comments/byzv5q/i_know_what_im_doing/) by u/[MasterQuacks](https://www.reddit.com/user/MasterQuacks/).
|
||||
|
||||
|
||||
|
||||
|
||||
I thought to myself "ha. Thats funny", and moved on. But that thought had stuck with me.
|
||||
|
||||
@ -59,4 +59,4 @@ with plt.xkcd():
|
||||
## The result
|
||||
Here is the resulting image. From left, to right: 5024, 254, 1114, 5406, 2056
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ While working on an assignment with [Coggle](https://coggle.it) today, I noticed
|
||||
## What is a .mm file?
|
||||
It turns out, a `.mm` file is just some XML describing the mind map. Here is a simple mind map:
|
||||
|
||||
|
||||
|
||||
|
||||
And again as a `.mm` file:
|
||||
|
||||
|
||||
@ -25,12 +25,12 @@ I am currently running a stock Ubuntu [18.04](https://releases.ubuntu.com/18.04.
|
||||
env XDG_CURRENT_DESKTOP=GNOME gnome-control-center
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
Next, go to *Settings > Language and Region > Input Sources*, and click on *Manage Installed Languages*.
|
||||
This will bring up a window where you can select a new language to install. From here, I clicked on *Install / Remove Language*.
|
||||
|
||||
|
||||
|
||||
|
||||
In this list, I just selected the languages I wanted (English and Japanese), and applied my changes. You may be asked to enter your password while installing the new languages. Once installation is complete, log out, and in again.
|
||||
|
||||
@ -54,12 +54,12 @@ Now that `ibus` is installed, run the setup script:
|
||||
ibus-setup
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
From here, set your shortcut to something not used by I3 (I chose `CTRL+Shift+Space`, but most people prefer `Alt+Space`), and enable the system tray icon.
|
||||
Now, go to the *Input Method* settings.
|
||||
|
||||
|
||||
|
||||
|
||||
From here, press the `+`, and add your language(s).
|
||||
|
||||
|
||||
@ -48,9 +48,9 @@ I also looked at other file types. Binaries are very interesting because they fo
|
||||
|
||||
Back to executable data, these are small segments of a `dll` file:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Check out the script
|
||||
This script is hosted [on my GitHub account](https://github.com/Ewpratten/binmap) as a standalone file. Any version of python3 should work, but the following libraries are needed:
|
||||
|
||||
@ -41,7 +41,7 @@ After task allocation, I took on the job of handling sounds and sound loading fo
|
||||
|
||||
Day 1 started with @exvacuum developing a heartrate monitor system for the game:
|
||||
|
||||
|
||||
|
||||
|
||||
*Demo image showing off his algorithm*
|
||||
|
||||
@ -63,19 +63,19 @@ soundAssets.debug_ding.play();
|
||||
|
||||
This rewrite also added integration with the volume control sliders in the game settings menu:
|
||||
|
||||
|
||||
|
||||
|
||||
*Audio Settings screen*
|
||||
|
||||
Later on in the day, a basic HUD was designed to incorporate the game elements. A bug was also discovered that causes Firefox-based clients to not render the background fill. We decided to replace the background fill with an image later.
|
||||
|
||||
|
||||
|
||||
|
||||
*V1 of the game HUD*
|
||||
|
||||
While developing the sound backend, and tweaking UI, I added sound assets for heartbeats, and footsteps. World assets were also added, and the walking system was improved.
|
||||
|
||||
|
||||
|
||||
|
||||
*The game with basic world assets loaded*
|
||||
|
||||
@ -90,11 +90,11 @@ While developing the sound backend, and tweaking UI, I added sound assets for he
|
||||
|
||||
Day 2 started with a new background asset, and a new HUD design:
|
||||
|
||||
|
||||
|
||||
|
||||
*The game's new background*
|
||||
|
||||
|
||||
|
||||
|
||||
*The game's new HUD*
|
||||
|
||||
@ -112,6 +112,6 @@ From then on, development time was just spent tweaking things such as:
|
||||
|
||||
Micromanaged Mike is free to play on [@rsninj722's website](https://rsninja.dev/LudumDare46/).
|
||||
|
||||
|
||||
|
||||
|
||||
*Final game screenshot*
|
||||
@ -35,7 +35,7 @@ In terms of workflow, I write all my notes as markdown files with [embedded LaTe
|
||||
|
||||
<script src="https://gist.github.com/Ewpratten/163aa9c9cb4e8c20e732e3713c95c915.js" ></script>
|
||||
|
||||
|
||||
|
||||
*A screenshot of my workspace*
|
||||
|
||||
Now, the question came up of *"how do you easily distribute notes and assignments to classmates and professors?"*. That question got me stuck for a while, but here is the system I have come up with:
|
||||
|
||||
@ -93,11 +93,11 @@ Notice the line `"image":"ewpratten/frc_devcontainer:2020.3.2",`. This is tellin
|
||||
|
||||
With a minimal amount of work, I got everything needed to develop and test FRC robotics code running in the browser via Codespaces.
|
||||
|
||||
|
||||
|
||||
|
||||
*Launching Codespaces from a GitHub repository*
|
||||
|
||||
|
||||
|
||||
|
||||
*Editing code in the browser*
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ That being said, since the keyboard has so many shortcuts and combinations to ge
|
||||
|
||||
The keyboard's baseplate is made of aluminum, and is CNC-cut, so it both looks and feels very nice. For a keyboard that I can wrap my (admittedly large) hand around, it is fairly heavy too (I seem to remember the FedEx shipment coming in at around 3lbs). In this case, heavy is not at all a bad thing. The weight of this keyboard makes it feel... expensive. Also, it never feels like the board is sliding away when I'm typing.
|
||||
|
||||
|
||||
|
||||
|
||||
One downside though, in terms of connectivity, the keyboard unfortunately uses USB micro connector instead of the newer (and nicer) USB type C connector. As someone who connects his life with USB-C, I am not the biggest fan of this choice, but at least I had a right-angle USB-micro cable lying around that I can use with it. Alongside the USB-micro connection, removing the backplate will reveal a [JTAG](https://en.wikipedia.org/wiki/JTAG) connector that allows you to flash custom firmware to the keyboard if you want. @ChaoticEnigma has forked the popular [QMK](https://github.com/qmk/qmk_firmware) keyboard firmware as [`qmk_pok3r`](https://github.com/pok3r-custom/qmk_pok3r), and added support for many Vortex boards including the Core, if you are looking to load something more custom.
|
||||
|
||||
@ -51,13 +51,13 @@ The first could be done simply by performing a firmware upgrade to the latest ve
|
||||
|
||||
This process unfortunately requires access to a computer that runs Windows (or VirtualBox). On windows, the setup process is really quite easy. You go to [this link](http://www.vortexgear.tw/db/upload/webdata4/6vortex_201861271445393.exe), which will download the firmware upgrade tool. Running the tool, and plugging in the keyboard will provide you with some options.
|
||||
|
||||
|
||||
|
||||
|
||||
The "bin group" selection provides two options. Selecting `Core by MPC` will flash the re-programmable firmware to the keyboard, and the other option will restore the keyboard to factory firmware.
|
||||
|
||||
Vortex provides a programming tool, but I am not a huge fan of it. I plan to write a Java app that can program the keyboard (and load saved profiles from it), but for now, I am using a great tool made by @tsfreddie called [Much Programming Core](https://tsfreddie.github.io/much-programming-core/). This tool allows you to configure keybindings and remap keys through his website, and there are easy-to-follow instructions on how to download the correct file, and flash your keyboard.
|
||||
|
||||
|
||||
|
||||
|
||||
Speaking of flashing the board, with the MPC firmware, the process for loading custom keybindings (which works on any OS) is really easy and simple. Just unplug the keyboard, then plug it back in while holding <kbd>fn</kbd>+<kbd>D</kbd>. This will cause the keyboard to mount as a USB drive, and you can drop configuration files on to it.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ This can also be set up on the client instead of the server, allowing a single c
|
||||
On the rendering side of the game, I run a few specialized mods to improve or replace various functions of Minectaft's built-in game renderer. Starting with the largest change, I use the [Sodium](https://github.com/jellysquid3/sodium-fabric) renderer, which includes a large number of rendering improvements, and opens up some extra customizability to the user.
|
||||
|
||||
<div class="center" markdown="1">
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
The developer of Sodium, @jellysquid3, has a few other rendering or rendering-related projects I use. Mainly: [Phosphor](https://github.com/jellysquid3/phosphor-fabric), which makes large improvements to the game lighting engine, and [Lithium](https://github.com/jellysquid3/lithium-fabric) which makes all-around improvements to the game.
|
||||
@ -63,7 +63,7 @@ In my inventory, I use [Roughly Enough Items](https://github.com/shedaniel/Rough
|
||||
|
||||
|
||||
<div class="center" markdown="1">
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
In terms of HUD "extras", I use [Here's What You're Looking At](https://www.curseforge.com/minecraft/mc-mods/hwyla) to show basic information about the block I am looking at. This is very helpful for me, as I am still learning what all the new `1.9+` blocks are. I also extend HWYLA with [Hwyla Addon Horse Info](https://www.curseforge.com/minecraft/mc-mods/hwyla-addon-horse-info) to show me the stats of any horse I look at, and [cAn i MiNe thIS bLOCk?](https://www.curseforge.com/minecraft/mc-mods/can-i-mine-this-block) to tell me the needed tool to harvest a specific block. I also use [Game Info](https://www.curseforge.com/minecraft/mc-mods/gameinfo) to tell me the world time in the upper left of my screen.
|
||||
@ -79,7 +79,7 @@ There are a few small mods that I have installed to provide some nice-to-have in
|
||||
I hate writing down coordinates of various things, so I use Xaero's [Minimap](https://www.curseforge.com/minecraft/mc-mods/xaeros-minimap) and [World Map](https://www.curseforge.com/minecraft/mc-mods/xaeros-world-map) mods. These both provide in-world waypoints, and generate a map of everywhere you travel in the world.
|
||||
|
||||
<div class="center" markdown="1">
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
## Building utilities
|
||||
|
||||
@ -40,10 +40,7 @@ On the software side of this machine, [I pushed to switch the core development l
|
||||
|
||||
We were able to design a fully autonomous shooting system using high-speed computer vision, real-time path planning, and ball trajectory models to allow our operators to make the robot score game pieces by pressing and holding a single button. On top of this scoring system, *Darth Raider* featured fully autonomous and real-time-error-correcting spatial navigation, allowing us to input a list of goal coordinates for the robot to navigate to efficiently. The final large autonomously controlled system of this robot was known as the "hopper"; a long tunnel for storing and stacking balls. This system was 100% software controlled, and made use of an amazing predictive sorting system developed by @rsninja722 that would perfectly align balls as they were fed in to the robot. Below is a clip taken from semi-finals where we wrote an experimental system that allowed us to essentially use two completely separate robots as one, effectively doubling our gamepiece storage capacity from our max 4 balls to 7. (Big thanks to the [Falcons](https://www.thebluealliance.com/team/5032) for letting us subject them to this experiment.)
|
||||
|
||||
<div class="center" markdown="1">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
For a few months after we finished competing, I went on to publish my largest open source project to date: [Lib5K](https://github.com/frc5024/Lib5k).
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ This step will void your device's warranty. Chromebooks are able to handle anyth
|
||||
|
||||
Luckily, on the Acer R11, this process is very simple. Firstly, unscrew the laptop's bottom plate to expose the motherboard (some screws are hidden under rubber feet). With the backplate off, you will find a screw that looks like this:
|
||||
|
||||
|
||||
|
||||
|
||||
The screw is hard to miss, it is beside the WIFI card, an has an arrow pointing to it. Simply remove it, and put the laptop back together. You now have a fully unlocked device.
|
||||
|
||||
@ -45,7 +45,7 @@ sudo firmware-util.sh
|
||||
|
||||
This will open up the `firmware-util` settings screen.
|
||||
|
||||
|
||||
|
||||
|
||||
You will want to select the `RW_LEGACY` option to load the `RW_LEGACY` / SEABIOS payload. The `UEFI` option is technically the better choice, but it will completely remove the device's ability to run ChromeOS again in the future.
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 15 MiB After Width: | Height: | Size: 15 MiB |
|
Before Width: | Height: | Size: 9.4 KiB After Width: | Height: | Size: 9.4 KiB |
|
Before Width: | Height: | Size: 5.7 KiB After Width: | Height: | Size: 5.7 KiB |
|
Before Width: | Height: | Size: 231 KiB After Width: | Height: | Size: 231 KiB |
|
Before Width: | Height: | Size: 116 KiB After Width: | Height: | Size: 116 KiB |
|
Before Width: | Height: | Size: 1019 KiB After Width: | Height: | Size: 1019 KiB |
|
Before Width: | Height: | Size: 53 KiB After Width: | Height: | Size: 53 KiB |
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 55 KiB After Width: | Height: | Size: 55 KiB |
|
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 46 KiB |
|
Before Width: | Height: | Size: 276 KiB After Width: | Height: | Size: 276 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 7.1 KiB After Width: | Height: | Size: 7.1 KiB |
|
Before Width: | Height: | Size: 480 B After Width: | Height: | Size: 480 B |
|
Before Width: | Height: | Size: 1005 B After Width: | Height: | Size: 1005 B |
|
Before Width: | Height: | Size: 176 KiB After Width: | Height: | Size: 176 KiB |
|
Before Width: | Height: | Size: 514 B After Width: | Height: | Size: 514 B |
|
Before Width: | Height: | Size: 8.4 KiB After Width: | Height: | Size: 8.4 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 785 KiB After Width: | Height: | Size: 785 KiB |
|
Before Width: | Height: | Size: 180 KiB After Width: | Height: | Size: 180 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 108 KiB After Width: | Height: | Size: 108 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
|
Before Width: | Height: | Size: 83 KiB After Width: | Height: | Size: 83 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 35 KiB |