evpo

##############################
# In your underground bunker:
##############################

ubuntu@sign-key-owner:~$ gpg2 --list-secret-keys 
/home/ubuntu/.gnupg/pubring.gpg
-------------------------------
sec   rsa2048/26AD9CA6 2018-02-10 [SC] [expires: 2018-02-20]
uid         [ultimate] Shelling Point <nowhere@north.pole>
ssb   rsa2048/4CC51AF4 2018-02-10 [E] [expires: 2018-02-20]

rygorous

why doesn't radfft support AVX on PC?

So there's two separate issues here: using instructions added in AVX and using 256-bit wide vectors. The former turns out to be much easier than the latter for our use case.

Problem number 1 was that you positively need to put AVX code in a separate file with different compiler settings (/arch:AVX for VC++, -mavx for GCC/Clang) that make all SSE code emitted also use VEX encoding, and at the time radfft was written there was no way in CDep to set compiler flags for just one file, just for the overall build.

[There's the GCC "target" annotations on individual funcs, which in principle fix this, but I ran into nasty problems with this for several compiler versions, and VC++ has no equivalent, so we're not currently using that and just sticking with different compilation units.]

The other issue is to do with CPU power management.

dhermes

*.pyc
*.aux
*.log
*.out

yonatan

// Commented version of https://twitter.com/zozuar/status/1441384708441456651
// Google-translated (with some editing) from @gam0022's version

float i, // Ray marching loop counter
e, // Volume density (the smaller the value, the higher the density)
s, // FBM scale (and loop counter)
g, // Ray's distance (also used for tunnel twirl and camera prespective)
k = .01; // Handy constant

// Ray marching loop

bjodah

1. Install msys2 from msys2.org
2. run msys2.exe: pacman -Syu, restart, pacman -Su
3. run mingw64.exe: pamcan -S mingw-w64-x86_64-emacs
4. create C:\msys2_64\runemacs_patched_path.bat:
  cmd /C "set PATH=C:\msys2_64\mingw64\bin;C:\msys2_64\usr\bin;%PATH% && C:\msys2_64\mingw64\bin\runemacs.exe --daemon"
5. Super-R shell:startup [RET]
6. Create shortcut to runemacs_patched_path.bat, call it e.g. "emacs-daemon"
7. Create a short-cut in Start menu:
  C:\msys2_64\mingw64\bin\emacsclientw.exe -c -n -a "C:\msys2_64\mingw64\bin\runemacs.exe"

karlrohe

# PCA on n=6990 images of handwritten 2's, each with d = 784 pixels.

# install.packages("remotes")
# remotes::install_github("jlmelville/snedata")
#  thank you jlmelville for making this data so easy to access!
library(snedata)
library(magrittr)
library(Matrix)
library(rARPACK)

piyushrpt

Setting up a feedstock from scratch

This is a step-by-step tutorial for setting up your own conda feedstock from scratch. I started with the instructions here:

https://medium.com/@lgouarin/conda-smithy-an-easy-way-to-build-and-deploy-your-conda-packages-12216058648f

As a novice, I found that the above tutorial lacked sufficient detail. So, I decided to document the process that I used for my own future reference.

0. Prerequisites

twlz0ne

;;; test-lsp-jdtls-installation.el --- Test lsp jdtls installation -*- lexical-binding: t; -*-
;;; Date: 2020-05-11_09.12.50
;;; Usage:
;; ┌────
;; │ $ emacs -nw -Q -l \
;; │         --eval '(setq with-proxy-http-server "127.0.0.1:XXXX")' \
;; │         /path/to/test-lsp-jdtls-installation.el
;; └────
(toggle-debug-on-error)
(setq user-emacs-directory (format "~/.emacs.d/%s/%s/" (file-name-base load-file-name) emacs-version))

jalavik

# original XML at http://www.w3.org/Math/characters/unicode.xml
# XSL for conversion: https://gist.github.com/798546


unicode_to_latex = {
    u"\u0020": "\\space ",
    u"\u0023": "\\#",
    u"\u0024": "\\textdollar ",
    u"\u0025": "\\%",
    u"\u0026": "\\&",

bjodah

mount_*/
environment_*/
output.log