This excercise is intended for candidates for PhD students in COeXISTENCE
Please send the solution reports to coexistence@uj.edu.pl
Discover gists
# First, we need to find our device. BEFORE inserting your USB drive, run the | |
# following: | |
diskutil list | |
# This will output a bunch of info about all of the disk drives connected to | |
# your Mac. Each entry will have a header in the form "/dev/diskX", where X is | |
# some number starting at 0. Now, insert your USB drive and run the command | |
# again. You should see a new entry. Make note of the name (ie, /dev/diskX). | |
diskutil list |
# Just a quick update for GPT and to use `rsync` instead of `cp`! | |
# That means this applies to UEFI boot, though for legacy BIOD boot, feel free to swap | |
# GPT to MBR below. | |
# Requires https://homebrew.sh to split the install.wim file | |
brew install wimlib | |
# First, we need to find our device. BEFORE inserting your USB drive, run the | |
# following: | |
diskutil list |
Get-ChildItem -Directory -Force -Recurse *.git | ForEach-Object { cd $_.Parent.FullName; Write-Host $_.Parent.FullName; git pull } |
Here is a way to do a robust install of Ubuntu (+ optional Windows 11 dual boot and LUKS encryption) on an Asus laptop, with minimal usable hardware support, without a significant amount of tinkering that may break in future or require frequent technical attention.
- AMD R7 5800 8 core 16 thread (onboard Radeon graphics)
- NVIDIA RTX 3050 4GB (60W +15W boost)
- 40GB RAM (8GB soldered + 32GB stick)
- 2TB SSD
- 14inch 1920x1080 Display @144Hz
sudo kill `ps -ax | grep 'coreaudiod'| grep 'sbin' | awk '{print $1}'` |
Manim provides out of the box the possibility of marking parts of your scene as separate sections, by using self.next_section()
. This will cause a separate video to be rendered for each section, and then all of them will be stitched together for the final result. The final result will be the same as if you hadn't used sections at all.
But the use of sections allows you to mark some of them with the parameter skip_animations=True
, and in that case, that section will not be rendered. The code of the section will be run anyway (because it may be defining objects or variables needed in following sections), but for every self.play()
, only the final frame will be computed (and not rendered). This ensures that, at the end of the section, all objects are at the same positions as if the animations were played, but skipping the actual rendering significantly reduces the time required to run the code.
In addition, the resulting video when skip_animations=True
is used will be s
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?