calibre-web:
image: lscr.io/linuxserver/calibre-web:amd64-latest
container_name: calibre-web
environment:
- PUID=1000
- PGID=1000
# most of the code is refactored colmap parsing from LLFF, a GPLv3 project. | |
# this is meant to be comparable to instant-ngp's colmap2nerf.py, and uses the | |
# same arguments, with additional functions for masking and LLFF format poses. | |
# LLFF format .npy files will always be made, remove if you ONLY want NeRF format | |
#~~~provide a dataset folder path with another "image" subfolder with the pics~~~ | |
# ~~~colmap can be installed to PATH or linked as an argument (--colmap_path)~~~ | |
# usage: (for LLFF format, nvdiffrec) | |
# colmap2poses.py --mask "/path/to/dataset/" |
Please check this repository for ExampleAgent.
function OnEvent(event, arg) | |
if (event == "MOUSE_BUTTON_PRESSED" and arg == 3) then | |
distance = 512 | |
Sleep(200) | |
MoveMouseRelative(-distance, 0) | |
Sleep(500) | |
MoveMouseRelative(distance, 0) | |
PressAndReleaseMouseButton(1) | |
MoveMouseRelative(distance, 0) | |
Sleep(500) |
If you, like me, resent every dollar spent on commercial PDF tools,
you might want to know how to change the text content of a PDF without
having to pay for Adobe Acrobat or another PDF tool. I didn't see an
obvious open-source tool that lets you dig into PDF internals, but I
did discover a few useful facts about how PDFs are structured that
I think may prove useful to others (or myself) in the future. They
are recorded here. They are surely not universally applicable --
the PDF standard is truly Byzantine -- but they worked for my case.
#!/usr/bin/env bash | |
# Assuming yay is run by user with UID 1000 | |
admin="$(id -nu 1000)" | |
cachedir="/home/$admin/.cache/yay" | |
removed="$(comm -23 <(basename -a $(find $cachedir -mindepth 1 -maxdepth 1 -type d) | sort) <(pacman -Qqm) | xargs -r printf "$cachedir/%s\n")" | |
# Remove yay cache for foreign packages that are not installed anymore | |
rm -rf $removed |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.
Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct