The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
FROM ubuntu:17.04 | |
WORKDIR /root | |
ARG CONDA_VERSION=Anaconda3-4.4.0-Linux-x86_64.sh | |
ARG CONDA_PATH=/opt/conda | |
ARG USER=vizdoom | |
# Install standard dev packages | |
RUN apt-get update && apt-get install -y \ | |
build-essential \ | |
bzip2 \ |
#cloud-config | |
# Set the hostname for this machine (takes precedence over hostname assigned by DHCP lease). | |
hostname: myhost | |
# Authorize SSH keys for the `rancher` sudoer user | |
ssh_authorized_keys: | |
- ssh-rsa AAA...ZZZ example1@rancher | |
; | |
; the "monitor ROM" of an apple 1 fit in one page (256 bytes). | |
; | |
; this is my attempt to take the disassembled code, give names to the | |
; variables and routines, and try to document how it worked. | |
; | |
; | |
; an apple 1 had 8KB of RAM (more, if you hacked on the motherboard), and a | |
; peripheral chip that drove the keyboard and video. the video was run by a | |
; side processor that could treat the display as an append-only terminal that |
Edit 04/11/2021: This gist is quite old now. The current version of PyTorch is 1.8.1, which is miles ahead of version 1.0.1 that I was trying to install when I wrote this gist. Therefore some of the instructions may not apply, or some dependencies may have changed or bugs taken care of. I do not currently have a Raspberry Pi to verify unfortunately. Please proceed with caution. Further, there are may others who have shared their fixes, and direct links to their wheels down in the comments. Cheers !
sudo apt install libopenblas-dev libblas-dev m4 cmake cython python3-yaml libatlas-base-dev
- Stop the swap :
sudo dphys-swapfile swapoff
- Modify the size of the swap by editing as
root
the following file :/etc/dphys-swapfile
. Modify the valiableCONF_SWAPSIZE
and change its value toCONF_SWAPSIZE=2048
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
import numpy as np | |
import gym | |
def sigmoid(x): | |
return 1.0 / (1.0 + np.exp(-x)) | |
env = gym.make('CartPole-v1') | |
desired_state = np.array([0, 0, 0, 0]) | |
desired_mask = np.array([0, 0, 1, 0]) |
# 2020-11-9: Solved in recent Ubuntu updates, not needed anymore, only for historical purposes available. | |
# | |
# Script to disable USB-C PD controller with nuc10 | |
# See: https://community.intel.com/t5/Intel-NUCs/NUC10i3-IRQ-problem/td-p/669863?profile.language=it | |
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511 | |
processActive=$(pgrep -l irq/65-i2c-INT3 | wc -l) | |
if [ "$processActive" -gt "0" ]; then | |
echo "stopping USB-C PD controller" |
This is an initiative to create an overview of the issues found with the Creality CR-6 SE.
As of this writing (2020-09-19) the large number of the motherboard issues have not been publicly acknowledged. Hopefully this overview forces Creality to acknowledge the issues with the Creality CR-6 SE leveling free 3d printer.
According to Creality all issues should be resolved in the newer models:
Here are the improvements we did as below: