Setup

Jump to bottomEditNew page
Taddic edited this page Dec 10, 2013 · 57 revisions

NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!

Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R. To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..

Linux dependencies

Run

make install_linux_deps

and it will install:

  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application

R

The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.

Install R

R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.

Setting R_HOME (important!)

Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:

  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!

  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.

We hope this step will become redundant in the future, but doing it is not going to break anything.

Forecast package in R

This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command

R

Inside R, enter the following:

install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with

q()

You do not have to save the workspace, so just press n.

You should now be ready to go.

rErlang

rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run

make install

It does require R to compile, so make sure you have done that first.

Downloading the project

All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.

Downloading dependencies

The following commands will install the needed project dependencies:

make install

Elastic Search (ES)

Configuring ES

NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!

The configuration of ES can be found in the lib/elasticsearch/config folder. The file of interest is elasticsearch.yml

Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:

cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es More info about the options can be found in the file.

Running ES

This will run the elasticsearch server on your computer.

make run_es

Our back-end can be started without it, but the API can not be used unless it is started.

Run the application

This command starts the back-end service, enabling the API.

make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):

make run_all

OR

sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.

make test_setup

OR

sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:

sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.

Running tests

To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.

make test
Add a custom footer
Add a custom sidebar

Clone this wiki locally

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Setup
Jump to bottomEditNew page

Taddic edited this page Dec 10, 2013
·
57 revisions
NOTE: these instructions might only work with the Ubuntu 12.04 LTS 64bit release!
Installation on OSX would most likely lead to a dead-end since libR.so is not available in the OSX version of R.
To run the project, you first need to make sure that you have Erlang and R installed, and for some functionality in R to work you need to manually install a package for it..
Linux dependencies
Run
make install_linux_deps

and it will install:
  • Erlang
  • R
  • NodeJS
  • Misc dependencies used by the application
R
The backend system uses R for statistical computations, such as time series forecasting (a.k.a predictions). It can be used through calls to the API, and uses an internal interface to feed commands from Erlang to R and get back results. In order to compile the project, two of three parts are necessary, and in order to run time series forecasting, an extra step is required.
Install R
R was installed with during the linux dependencies installation. Now there are only a few extra steps needed for it to work properly.
Setting R_HOME (important!)
Unfortunately, R does not set the variable R_HOME to what we need to use it from within our engine. There are two ways to set this variable:
  • For each session, before you start the engine, run
export R_HOME=/usr/lib/R

in the terminal. NO BLANKSPACES AROUND THE = SIGN!
  • In $HOME/.profile, insert the line
export R_HOME="/usr/lib/R"

This will set the variable when you log in to the system (will not take effect until you relog/restart ubuntu). This way you don't have to worry about remembering to set it every time you start a new terminal.
We hope this step will become redundant in the future, but doing it is not going to break anything.
Forecast package in R
This one needs to be done manually, but is only required for actually running predictions. Start R in a terminal with the command
R

Inside R, enter the following:
install.packages("forecast")

choose y twice, then select the mirror you want to use (preferably one close to you). Once the installation is done, you can quit R with
q()

You do not have to save the workspace, so just press n.
You should now be ready to go.
rErlang
rErlang is our internal api for connecting Erlang and R. It is included as a dependency in our project and is automatically downloaded and compile when you run
make install

It does require R to compile, so make sure you have done that first.
Downloading the project
All you need to do is check out our project. We recommend using the develop branch, as it is the latest (most) stable. The demo branch periodically has some newer functionality, but stability is not guaranteed.
Downloading dependencies
The following commands will install the needed project dependencies:
make install

Elastic Search (ES)
Configuring ES
NOTE: Since you change your config file in the lib folder, it will not be saved. If you do a new make install or a make clean_libs then your changes will be removed!
The configuration of ES can be found in the lib/elasticsearch/config folder.
The file of interest is elasticsearch.yml
Most of the fields are commented out and this means that they will use the defaults. Some options that are good to know:
cluster.name: my_cluster_name # Defines the name of the cluster
node.name: "My Unique Node Name" # Defines the unique node name
path.data: /my_path/data #Define where you want the data to be
path.work: /my_path/work #Define where you want the temporary files
path.logs: /my_path/logs #Define where you want the logs

If you want the data to be persistant, you need to specify the data path. This might also cause you to have to run es with sudo sudo make run_es
More info about the options can be found in the file.
Running ES
This will run the elasticsearch server on your computer.
make run_es

Our back-end can be started without it, but the API can not be used unless it is started.
Run the application
This command starts the back-end service, enabling the API.
make run

You can also use the sensec.sh script to start RabbitMQ, ElasticSearch, Node.js rt-script and Sensor-Cloud by using the following command (the commands perform the exact same things):
make run_all

OR
sudo ./sensec.sh start

Alternatively you can use the following command in order to setup all parts that is needed before running 'make test'.
make test_setup

OR
sudo ./sensec.sh test_setup

This will call the service wrappers for RabbitMQ, ElasticSearch, Node.js rt-script and running Sensor-Cloud in erlang, the tasks are running in the background , Sensor-Cloud is running with the -noshell command so that erlang is not terminated if the task is running in the background. To close the services you can use:
sudo ./sensec.sh stop

Note that the script will log output for RabbitMQ, ElasticSearch and Sensor-Cloud in a folder called logs on the root directory of Sensor cloud.
Running tests
To run the test, you should make sure that the service is not already running and that you have an elsticsearch server running. If you did a make run before, make sure to quit it, using q().. Now you can do a make test, make test will start the service, run the tests and then shut the service down.
make test

 Add a custom footer

 Add a custom sidebar

Clone this wiki locally