$ git clone https://github.com/cockpit-project/cockpit.git
$ cd cockpit
$ curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
$ sudo apt-get install -y nodejs
#!/usr/bin/env bash | |
# A basic Self Signed SSL Certificate utility | |
# by Andrea Giammarchi @WebReflection | |
# https://www.webreflection.co.uk/blog/2015/08/08/bringing-ssl-to-your-private-network | |
# # to make it executable and use it | |
# $ chmod +x certificate | |
# $ ./certificate # to read the how-to |
#include <stdio.h> | |
int main() | |
{ | |
int a = 42; | |
printf("%d\n", a); | |
return 0; | |
} | |
int main() | |
{ | |
int a = 42; | |
printf("%d\n", a); | |
} |
... | |
BL calc ; Jump to calc | |
... ; Execute here after return | |
... | |
calc: ; function body | |
ADD r0, r1, r2 ; do some calculate here | |
MOV pc, r14 ; PC = R14 to return | |
After implementing Sugar & James jump method and applying it straightforwardly to a few data sets, we're ready to throw it a few curveballs. This will demonstrate both its robustness and some necessary aspects of setting it up for success.
Again we need some functions we built in part one and part two. Feel free to skip this part if you don't need the review and you're not following along with a REPL. If you are following along in the REPL, here's the full Clojure source.
(def iris (i/to-matrix (incd/get-dataset :iris)))
/* | |
____ _____ | |
/\__ \ /\ ___\ | |
\/__/\ \ \ \ \__/_ | |
\ \ \ \ \____ \ | |
_\_\ \ \/__/_\ \ | |
/\ _____\ /\ _____\ | |
\/______/ \/______/ | |
Copyright (C) 2011 Joerg Seebohn |
After implementing Sugar & James' jump method and exploring its application to Fisher's iris data in Part One of this series, we're now ready to apply the jumps-in-distortions test to some other sample data sets. Pure Clojure source here.
Remember these functions from earlier? We'll be using them again.
(defn assoc-distortions
"Given a number `transformation-power-y` and a seq of maps
Kafka acts as a kind of write-ahead log (WAL) that records messages to a persistent store (disk) and allows subscribers to read and apply these changes to their own stores in a system appropriate time-frame.
Terminology: