Skip to content

Instantly share code, notes, and snippets.

View Steampunkery's full-sized avatar

Thomas O'Keeffe Steampunkery

View GitHub Profile
#!/usr/bin/env python3
import re
import json
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
import numpy as np
import tensorflow as tf
import sys
#!/usr/bin/python3
import re
import subprocess
import tkinter as tk
from Xlib import display
def lambda_factory(index):
global labels
global buttons
FROM python:2.7
MAINTAINER CloudCV Team <[email protected]>
WORKDIR /app
ENV PYTHONUNBUFFERED 1
COPY . /app
RUN mkdir -p static/
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update
.section {
height: 95vh;
width: 24.78vw;
margin:0px;
padding: 0px;
flex: 1 1 0px;
border: 2px solid black;
}
html, body {
margin:0px;
@Steampunkery
Steampunkery / BlockFamilyContrast.md
Last active December 2, 2017 17:54
A compare & contrast of the new and old BlockFamily systems of Terasology

What is a BlockFamily?

A block family is a group of blocks that are defined together. For example, there is a RomanColumn family which consists of a cap block, a base block and a middle block. These blocks are separate blocks with different textures, and they can also have distinct shapes (although RomanColumns are all cubes), but they share a *.block file. A block family is created with the "rotation" tag in v1 block families and the "family" tag in v2 block families. For more information about v1 block families and v2 block families, look here. This gist aims to compare and contrast the block family versions and add some documentation as well.

Definition

What I'm referring to as old block families are the current block families in the master Terasology repo as of the time of writing (Friday, December 1 2017). [Example of old block families](https://github.com/Terasology/Sample/tree/b1358433e95590c9ce4bdcee333c1d0a002f8ddc/src/main/jav