text:
# hls-nix

A nix-buildable derivation for [haskell-language-server](https://github.com/haskell/haskell-language-server)

I've written this derivation just to test it out myself. Any suggestions are welcome!

## Installation

This build has a cachix cache already available, and it can be setup with the
commands below:

```
$ nix-env -iA cachix -f https://cachix.org/api/v1/install
$ cachix use korayal-hls
```

Install with the command below:

```
nix-env -iA hpkgs.haskell-language-server -f https://github.com/korayal/hls-nix/tarball/master
```

repository: parenthetical/hls-nix

repo_name: parenthetical/hls-nix


text:
# firebase_remote_config_hybrid_platform_interface

A common platform interface for the [`firebase_remote_config_hybrid`](https://github.com/JohnMusleh/firebase_remote_config_hybrid/tree/master/firebase_remote_config_hybrid) plugin.

This interface allows platform-specific implementations of the `firebase_remote_config_hybrid`
plugin, as well as the plugin itself, to ensure they are supporting the
same interface.

# Usage

To implement a new platform-specific implementation of `firebase_remote_config_hybrid`, extend
[`FirebaseRemoteConfigPlatformInterface`](https://github.com/JohnMusleh/firebase_remote_config_hybrid/tree/master/firebase_remote_config_hybrid_platform_interface) with an implementation that performs the
platform-specific behavior, and when you register your plugin, set the default
`FirebaseRemoteConfigPlatformInterface` by calling
`FirebaseRemoteConfigPlatformInterface.instance = MyFirebaseRemoteConfig()`.

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# geo.okapi

geo.okapi is a JavaScript library that encapsulates features for creating interactive maps. It is based on OpenLayers
and adds some useful features to this library. geo.okapi is open source and it is published under the
[MIT License](https://raw.githubusercontent.com/de-bkg/geo.okapi/master/LICENSE).

## Create a simple map
```javascript
var map = new okapi.MapBuilder()
  .setTarget('mapDiv') // ID of map div
        .setLayers({
            baseLayers: [
                {
                    type: 'BKG',
                    name: 'WebAtlasDE',
                    ref: 'webatlasde_light'
                }
            ]
        }) // Use layer VG2500
  .create(); // Create map
```

**NOTE:** The geo.okapi version with all libraries bundled uses a custom version of OpenLayers with only the necessary
classes included. If you would like to use more OpenLayers classes in your code, you should do the following:

1. Find OpenLayer Version used in geo.okapi:
	- Add geo.okapi with all libraries included in a HTML file.
	- Open file with browser and start the console.
	- Type: *okapi.OPENLAYERS_VERSION*
2. Download the same version of OpenLayers: https://github.com/openlayers/openlayers/releases/
3. At your website use a geo.okapi version without any libraries and add OpenLayers before geo.okapi.
4. Add also the following libraries before geo.okapi:
	- Proj4js 2.5.0 (https://github.com/proj4js/proj4js/releases/tag/2.5.0)
	- FileSaver 1.3.8 (https://github.com/eligrey/FileSaver.js/releases/tag/1.3.8)
	- SheetJS js-xlsx 0.12.13 (https://github.com/SheetJS/js-xlsx/releases/tag/v0.12.13)

license: MIT


text:
# Exploring Neural Networks: Neilsen's Book and MNIST

This repository is a fork of [code samples](https://github.com/mnielsen/neural-networks-and-deep-learning)
accompanying Michael Nielsen's online book [*Neural Networks
and Deep Learning*](http://neuralnetworksanddeeplearning.com).
The intent is to demonstrate my curiosity and impetus to hack around
with other people's code to understand how something like NN really works.
I have read through chapter 2 and am working on chapter 3 of the book, so the questions involved
in my "experiments" reflect where I am, in the middle of the book.
Because I learn best through an iterative, hands-on approach, there's value to documenting my
curiosity and trying to address it on my own, whether or not these questions are addressed later on..

## Running from scratch

First do the standard `pip install -r requirements.txt` as needed (recommended: in a virtual
environment) to install dependencies.

Then run ```python main.py``` from the src directory to execute the main functionality.

## The two experiments
Two questions have emerged as I've worked through this book,
leading me to do further experimentation:

1. If we think of the neural network metaphor, we can quantify the probabilities of a "pulse" making it through
all layers of neurons as a set of 28 x 28 maps of probabilities for each pixel in the images. **Does this map should produce something humans can identify as looking somewhat like
the numerals 0, 1, 2, etc.?**

2. **If I tweak the initial weights to match intuition about, for example, "What an eight
looks like," does that improve predictive power?**

It seems like it should, because the initial
weights have less learning to do, but it's not that simple. As in (1) I'm really interested in
the cross product of all the matrices for all the different levels. As a first approximation, can
I seed the weights in just one layer? Does this encourage the other layers to end up with something
like an identity matrix?

## Inputs and outputs

I'm presently cleaning this up--the outputs to "research question" 1 above are mostly in
archive-of-images,
named my0 through my9.
The "heatmaps" subdir is less useful stuff, my attempts to trace the evolution of one example epoch by epoch.

Meanwhile, the inputs to RQ 2 are my attempts to simulate the heatmap I might expect for the each
numeral--sort of a theoretical counterpart to output from RQ 1. These are in
`experiments/starting-weights`, but I'm in the process of improving/simplifying them. See the
`accompanying .xlsx.

## Next steps
- Set up the experiment to emphasize the comparison at hand rather than
- Cleaner inputs and outputs
- More parametrization.

And that should be enough to make this "decent." I'd also like to:

- Work on later chapters of Nielsen's ebook. (I got a bit sidetracked on the
    exploration reflected here.)
- Stray warnings:
  - `/home/philip/code/neural-networks-and-deep-learning/src/network.py:182: RuntimeWarning: overflow encountered in exp
  return 1.0/(1.0+np.exp(-z))` \[But note! I'm getting this running the original NN structure too, assuming I haven't accidentally broken something there.]

## Neilsen's original README notes

The code is written for Python 2.6 or 2.7. Michal Daniel Dobrzanski
has a repository for Python 3
[here](https://github.com/MichalDanielDobrzanski/DeepLearningPython35). I
will not be updating the current repository for Python 3
compatibility.

The program `src/network3.py` uses version 0.6 or 0.7 of the Theano
library.  It needs modification for compatibility with later versions
of the library.  I will not be making such modifications.

As the code is written to accompany the book, I don't intend to add
new features. However, bug reports are welcome, and you should feel
free to fork and modify the code.

## License

MIT License

Copyright (c) 2012-2015 Michael Nielsen

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


text:
Reverse Relations plugin for Craft CMS
=================

Plugin that allows you to show and save reverse relations in both the CP and the Site.

Features:
- Able to output the relation in the CP and in the site (no other plugin has this feature)
- Only supports entries and users at the moment

Todo:
- Support more element types

Important:
The plugin's folder should be named "reverserelations"

Changelog
=================
###0.4.0###
- Added a read-only setting (thanks to @timkelty)
- Fixed Matrix errors (thanks to @timkelty)

###0.3.1###
- Make sure we have targets before trying to save any

###0.3###
- Added the ability to save both ways
- Added Craft 2.4 support
- Added MIT license

###0.2###
- Only find reverse relations in given source

###0.1###
- Initial push to GitHub

repository: dreamseeker/reverserelations

repo_name: dreamseeker/reverserelations


text:
# Covertype Data Set

This dataset is based on **Covertype Data Set** from UCI Machine Learning Repository

https://archive.ics.uci.edu/ml/datasets/covertype

## Schema

The original dataset has been modified to conform to the following schema:

Column Name | Data Type | Feature Type | Data Domain | Description
------------|-----------|--------------|-------------|------------
Elevation | Integer | Quantitative | meters |  Elevation in meters
Aspect | Integer  | Quantitative | azimuth |  Aspect in degrees azimuth
Slope | Integer | Quantitative | degress | Slop in degress
Horizontal_Distance_To_Hydrology | Integer  | Quantitative | meters | Horizontal distance to nearest surface water features
Vertical_Distance_To_Hydrology | Integer  | Quantitative | meters | Vertical distance to nearest surface water features
Horizontal_Distance_To_Roadways | Integer  | Quantitative | meters | Horizontal distance to nearest roadway
Hillshade_9am | Integer  | Quantitative | 0 to 255 index |  Hillshade index at 9am, summer solstice
Hillshade_Noon | Integer  | Quantitative | 0 to 255 index |  Hillshade index at noon, summer soltice
Hillshade_3pm | Integer  | Quantitative | 0 to 255 index |  Hillshade index at 3pm, summer solstice
Horizontal_Distance_To_Fire_Points | Integer  | Quantitative | meters | Horizontal distance to nearest wildfire ignition points
Wilderness_Area | String | Categorical | Text codes |  Wilderness area designation - refer to the below table for code designations
Soil_Type | Integer | Categorical | Integer codes | Soil Type designation - refer to the below table for code designations
Cover_Type | Integer | Categorical | Integer codes | Forest Cover Type designation - refer to the below table for code designations

### Wilderness Area Code designations

Code | Wilderness Area
----------------|-----
Rawah | Rawah Wilderness Area
Neota | Neota Wilderness Area
Comanche | Comanche Peak Wilderness Area
Cache | Cache la Poudre Wilderness Area

### Soil Type Code designations

 ELU Code | Description
----------|------------
 2702|Cathedral family - Rock outcrop complex, extremely stony.
 2703|Vanet - Ratake families complex, very stony.
 2704|Haploborolis - Rock outcrop complex, rubbly.
 2705|Ratake family - Rock outcrop complex, rubbly.
 2706|Vanet family - Rock outcrop complex complex, rubbly.
 2717|Vanet - Wetmore families - Rock outcrop complex, stony.
 3501|Gothic family.
 3502|Supervisor - Limber families complex.
 4201|Troutville family, very stony.
 4703|Bullwark - Catamount families - Rock outcrop complex, rubbly.
 4704|Bullwark - Catamount families - Rock land complex, rubbly.
 4744|Legault family - Rock land complex, stony.
 4758|Catamount family - Rock land - Bullwark family complex, rubbly.
 5101|Pachic Argiborolis - Aquolis complex.
 5151|unspecified in the USFS Soil and ELU Survey.
 6101|Cryaquolis - Cryoborolis complex.
 6102|Gateview family - Cryaquolis complex.
 6731|Rogert family, very stony.
 7101|Typic Cryaquolis - Borohemists complex.
 7102|Typic Cryaquepts - Typic Cryaquolls complex.
 7103|Typic Cryaquolls - Leighcan family, till substratum complex.
 7201|Leighcan family, till substratum, extremely bouldery.
 7202|Leighcan family, till substratum - Typic Cryaquolls complex.
 7700|Leighcan family, extremely stony.
 7701|Leighcan family, warm, extremely stony.
 7702|Granile - Catamount families complex, very stony.
 7709|Leighcan family, warm - Rock outcrop complex, extremely stony.
 7710|Leighcan family - Rock outcrop complex, extremely stony.
 7745|Como - Legault families complex, extremely stony.
 7746|Como family - Rock land - Legault family complex, extremely stony.
 7755|Leighcan - Catamount families complex, extremely stony.
 7756|Catamount family - Rock outcrop - Leighcan family complex, extremely stony.
 7757|Leighcan - Catamount families - Rock outcrop complex, extremely stony.
 7790|Cryorthents - Rock land complex, extremely stony.
 8703|Cryumbrepts - Rock outcrop - Cryaquepts complex.
 8707|Bross family - Rock land - Cryumbrepts complex, extremely stony.
 8708|Rock outcrop - Cryumbrepts - Cryorthents complex, extremely stony.
 8771|Leighcan - Moran families - Cryaquolls complex, extremely stony.
 8772|Moran family - Cryorthents - Leighcan family complex, extremely stony.
 8776|Moran family - Cryorthents - Rock land complex, extremely stony.

### Forest Cover Code designations (type classes)

Code | Description
-----|------------
0 | Spruce/Fir
1 | Lodgepole Pine
2 | Ponderosa Pine
3 | Cottonwood/Willow
4 | Aspen
5 | Douglas-fir
6 | Krummholz

## Data Splits

In addition to the full data split that contains all records from the original UCI file, the training, evaluation, testing and serving splits have been created.

All data set splits have been uploaded to the `gs://workshop-datasets/covertype` public GCS location.

gha_language: Jupyter Notebook


text:
# redux-promise

[![build status](https://img.shields.io/travis/redux-utilities/redux-promise/master.svg)](https://travis-ci.org/redux-utilities/redux-promise)
[![codecov](https://codecov.io/gh/redux-utilities/redux-promise/branch/master/graph/badge.svg)](https://codecov.io/gh/redux-utilities/redux-promise)
[![npm version](https://img.shields.io/npm/v/redux-promise.svg)](https://www.npmjs.com/package/redux-promise)
[![npm monthly downloads](https://img.shields.io/npm/dm/redux-promise.svg)](https://www.npmjs.com/package/redux-promise)

[FSA](https://github.com/redux-utilities/flux-standard-action)-compliant promise [middleware](https://redux.js.org/advanced/middleware) for Redux.

```js
npm install --save redux-promise
```

## Usage

```js
import promiseMiddleware from 'redux-promise';
```

The default export is a middleware function. If it receives a promise, it will dispatch the resolved value of the promise. It will not dispatch anything if the promise rejects.

If it receives an Flux Standard Action whose `payload` is a promise, it will either

* dispatch a copy of the action with the resolved value of the promise, and set `status` to `success`.
* dispatch a copy of the action with the rejected value of the promise, and set `status` to `error`.

The middleware returns a promise to the caller so that it can wait for the operation to finish before continuing. This is especially useful for server-side rendering. If you find that a promise is not being returned, ensure that all middleware before it in the chain is also returning its `next()` call to the caller.

## Using in combination with redux-actions

Because it supports FSA actions, you can use redux-promise in combination with [redux-actions](https://github.com/redux-utilities/redux-actions).

### Example: Async action creators

This works just like in Flummox:

```js
createAction('FETCH_THING', async id => {
  const result = await somePromise;
  return result.someValue;
});
```

Unlike Flummox, it will not perform a dispatch at the beginning of the operation, only at the end. We're still looking into the [best way to deal with optimistic updates](https://github.com/redux-utilities/flux-standard-action/issues/7). If you have a suggestion, let me know.

### Example: Integrating with a web API module

Say you have an API module that sends requests to a server. This is a common pattern in Flux apps. Assuming your module supports promises, it's really easy to create action creators that wrap around your API:

```js
import { WebAPI } from '../utils/WebAPI';

export const getThing = createAction('GET_THING', WebAPI.getThing);
export const createThing = createAction('POST_THING', WebAPI.createThing);
export const updateThing = createAction('UPDATE_THING', WebAPI.updateThing);
export const deleteThing = createAction('DELETE_THING', WebAPI.deleteThing);
```

(You'll probably notice how this could be simplified even further using something like lodash's `mapValues()`.)

repository: redux-utilities/redux-promise

gha_language: JavaScript

gha_license_id: MIT

repo_name: redux-utilities/redux-promise


text:
---
layout: page
title: Orleans Blog
---

## [Solving a Transactions Performance Mystery](solving-a-transactions-performance-mystery.md)
[Reuben Bond](https://github.com/ReubenBond)
12/7/2018 10:08:58 AM

* * * * *

After arriving in Redmond and completing the mandatory New Employee Orientation, my first task on the Orleans team has been to assist with some ongoing performance investigations in order to ensure that Orleans' Transactions support is ready for internal users and hence release.

We were seeing significant performance issues and a large number of transaction failures in the stress/load tests against our test cluster.
A large fraction of transactions were stalling until timeout.

## [Dmitry Vakulenko](dmitry-vakulenko.md)
[Sergey Bykov](https://github.com/sergeybykov) 11/19/2018 1:57:59 PM

* * * * *

Dmitry Vakulenko joined the Orleans open source community three years ago, and started submitting pull requests that focused on improving performance of the Orleans codebase.
He became the most prolific contributor outside of the current and former members of the core team.

Dmitry also contributed other improvements, but his passion continued to be performance.
Because of the compound nature of incremental optimizations, over time these improvements added up to a staggering aggregate factor. Our conservative estimate is that Dmitry's contributions combined increased performance of Orleans by about 2.6 times.

## [Announcing Orleans 2.1](announcing-orleans-2.1.md)

[Reuben Bond](https://github.com/ReubenBond) 10/1/2018 7:17:59 PM

* * * * *

Today, we announced Orleans 2.1.
This release includes significant performance improvements over 2.0, a major refresh of distributed transaction support, a new code generator, and new functionality for co-hosting scenarios as well as smaller fixes & improvements.
Read the [release notes here](https://github.com/dotnet/orleans/releases/tag/v2.1.0).

branch_name: refs/heads/main


text:
---
title: IR Camera with Trinket M0 and CircuitPython
date: 11 Aug 2019
image: "https://cdn-learn.adafruit.com/assets/assets/000/043/014/medium800/temperature_AMG8833.jpg?1498492692"
---

Install the needed libraries in your `library` folder:

- adafruit_amg88xx.mpy
- adafruit_bus_device

Hook up the camera. *Note:* the `INT` pi is an interrupt that will trigger when the scene has changed

![](https://cdn-learn.adafruit.com/assets/assets/000/059/229/medium640/temperature___humidity_FeatherM0_AMG8833_bb.jpg?1534369163)

```python
import time
import busio
import board
import adafruit_amg88xx

i2c = busio.I2C(board.SCL, board.SDA)
amg = adafruit_amg88xx.AMG88XX(i2c)

while True:
    for row in amg.pixels:
        # Pad to 1 decimal place
        print(['{0:.1f}'.format(temp) for temp in row])
        print("")
    print("\n")
    time.sleep(1)
```

## Linux

To see if the camera is hooked up, do:

```
sudo i2cdetect -y 1
```

# References

- Adafruit AMG8833 8x8 Thermal Camera [Tutorial](https://learn.adafruit.com/adafruit-amg8833-8x8-thermal-camera-sensor?view=all)

repository: walchko/github-blog

repo_name: walchko/github-blog


text:
# Friesian server deploying with Helm Chart

This example demonstrates how to deploy a Friesian recommender server with Helm Chart on a
Kubernetes cluster.

## Prepare environments

* AVX512 instruction support on nodes that deploy the recall server
* [Preparation steps](./preparation) or a PV contains resource files
* [Helm](https://helm.sh) 3.2.0+
* Kubernetes 1.19+

## Deploy Friesian server

You can get the full installation document from [here](./friesian-helm/README.md).

## TL;DR

```bash
git clone https://github.com/intel-analytics/BigDL.git
cd BigDL/apps/friesian-server-helm

# create a namespace
kubectl create ns friesian

# create a PVC to store resources and a pod to copy resources
kubectl apply -f './preparation/create-pvc.yaml' -n friesian
kubectl apply -f './preparation/create-volume-pod.yaml' -n friesian

# copy resources to PVC
kubectl cp /path/to/your/resources friesian/volume-pod:/resources

# delete pod no longer used
kubectl delete -f '2. create-volume-pod.yaml' -n friesian

# install friesian server in namespace 'friesian' with name 'my-release'
helm upgrade --install -n friesian my-release ./friesian-helm

```

After installation, you can follow the printed information to check whether the servers are running
properly.

repository: intel-analytics/BigDL

repo_name: intel-analytics/BigDL


text:
# Redis With Configmap

Based on [Configuring Redis using a ConfigMap](https://kubernetes.io/docs/tutorials/configuration/configure-redis-using-configmap/#real-world-example-configuring-redis-using-a-configmap).

Configuration has been augmented with templating of a ConfigMap so that when it changes redis Pod is recreated (note in this example, redis is not configured to persistent data between Pod recreates).

```bash
kubectl exec -it redis redis-cli
<IP_ADDRESS>:6379> CONFIG GET maxmemory
1) "maxmemory"
2) "2097152"
```

repository: rochacon/kapp

repo_name: rochacon/kapp


text:
# GoCD Agent with Node 15 Docker Image

[![dockeri.co](https://dockeri.co/image/smartassist/gocd-agent-node15)](https://hub.docker.com/r/smartassist/gocd-agent-node15)

[![Docker Hub Automated](https://img.shields.io/docker/cloud/automated/smartassist/gocd-agent-node15.svg?style=flat-square&logo=docker "GitHub issues")](https://hub.docker.com/r/smartassist/gocd-agent-node15)
[![Docker Hub Build Status](https://img.shields.io/docker/cloud/build/smartassist/gocd-agent-node15.svg?style=flat-square&logo=docker "GitHub stars")](https://hub.docker.com/r/smartassist/gocd-agent-node15)

[GoCD Agent on Alpine](https://hub.docker.com/r/gocd/gocd-agent-alpine-3.13) with the latest version of Node 15 added to
it.

## Usage

- To use in your docker-compose.yml:

```yaml
version: "3.8"

services:
  gocd-agent-node15:
    image: smartassist/gocd-agent-node15:v21.2.0
    restart: unless-stopped
    env_file: .env
```

- To modify further, reference in your Dockerfile:

```dockerfile
FROM smartassist/gocd-agent-node15:v21.2.0
```

## Contents

- [GoCD's official Alpine agent's Dockerfile](https://hub.docker.com/r/gocd/gocd-agent-alpine-3.13)
- [Node's official Dockerfile](https://github.com/nodejs/docker-node/raw/main/15/alpine3.13/Dockerfile)

## Versions

| Runtime    | Version |
|------------|---------|
| OS      | Alpine 3.13  |
| GoCD agent | v21.2.0 |
| Node       | 15.14.0  |

## Building

- Update versions in `generate.sh`
- Run `bash generate.sh`


text:
# karma-script-launcher

> Launcher for custom shell scripts.

For more information on Karma see the [homepage].

[homepage]: http://karma-runner.github.com

repository: roblayton/roblayton-portfolio

repo_name: roblayton/roblayton-portfolio


text:
# Proteogenomics

## Files

Workflow: [`proteogenomics.ga`](proteogenomics.ga)

History file: [`PSM_Report.tabular`](PSM_Report.tabular)

## Required Galaxy Tools

If you wish to run the proteogenomics workflow on your own Galaxy instance you will need to install the following, versioned, tools:

| Tool Name                | Owner   | Version |
|--------------------------|---------|---------|
| `column_maker`           | devteam | [626658afe4cb](https://toolshed.g2.bx.psu.edu/repos/devteam/column_maker/rev/626658afe4cb) |
| `fasta_filter_by_length` | devteam | [2fd6033d0e9c](https://toolshed.g2.bx.psu.edu/repos/devteam/fasta_filter_by_length/rev/2fd6033d0e9c) |
| `ncbi_blast_plus`        | devteam | [d724d9af93ee](https://testtoolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/rev/d724d9af93ee) |
| `query_tabular`          | iuc     | [1ea4e668bf73](https://toolshed.g2.bx.psu.edu/repos/iuc/query_tabular/rev/1ea4e668bf73) |
| `tabular_to_fasta`       | devteam | [0b4e36026794](https://toolshed.g2.bx.psu.edu/repos/devteam/tabular_to_fasta/rev/0b4e36026794) |

## Workflow Instructions

We have set-up a publically accessible Galaxy instance on the Jetstream cloud-based cyberinfrastructure resource. Here we provide instructions on accessing this public instance.

1. Go to [https://z.umn.edu/proteogenomicsgateway](https://z.umn.edu/proteogenomicsgateway)

2. Register to use the Galaxy instance. Galaxy requires that all users input an email address to use tools and build workflows etc. To register do the following:
    - Click on the `User` tab and then click on `Register`
    - Enter an email address, password and public name of your choosing

> NOTE: Users who want to remain anonymous can enter an email in the form of<EMAIL_ADDRESS>(where X is any number of your choosing), along with a password and public name of your choosing. Please note that if the email entered is not valid, the administrators of this instance will not be able to contact the user regarding any issues related to the instance. If the desire it to use this instance for long-term research use, we suggest using a valid email address.

3. Once registered, workflows and sample input data can be accessed within the Shared Data tab.
    - To run the workflow, first appropriate input data must be loaded into your active History. Clickon `Shared data` and select `Histories`. From the list of shared Histories, select `Input for Query Tabular F1000 Workflow`. In the page that appears, select `Import History` and click on `Import` when the window appears.
    - Next click on `Shared Data`, select `Workflows`
    - When the shared Published Workflows page appears, type `Query` in the search field
    - The workflow titled `Query Tabular F1000: PSM Report ---> Novel Peptides` will come up. Click on the drop down arrow on the right of the workflow button, and select `Import`
    - In the green box that appears, click on `Start using this workflow`.
    - This will now show up in `Your workflows`. Click on the dropdown arrow and select `Run`.
    - The next window will show the steps in the workflow. The first item shows the input data that you just imported into your History that will be processed by the workflow (`PSM_report.tabular`)
    - Click on `Run workflow` and the analysis will proceed.


text:
[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.1172264.svg)](https://doi.org/10.5281/zenodo.1172264)

# brainvr-unity-framework
This Unity framework was programmed with navigation/cognitive scientists in mind. It provides base start for experiment delivery,
helpful assets for controlling various useful aspects of the scene, such as player controller, sounds, objects, navigation helpers (mapping, gps) etc. It provides ways to parsing json data, logging participant information.

It also comes bundled with R scripts for parsing logged data [here](https://github.com/BrainVR/brainvr-reader)

# How to cite
Please cite if you use it in your work or at least spread the word :) https://doi.org/10.5281/zenodo.1172264

Documentation is available [here](https://brainvr.github.io/brainvr-unity-framework-documentation/)

repository: BrainVR/brainvr-unity-framework

gha_language: C#

gha_license_id: NOASSERTION

repo_name: BrainVR/brainvr-unity-framework


text:
# Change Log

## [Unreleased]

## v2.1.0 - 2023-02-10

### Added

- Feature detection for WebKit ([#50](https://github.com/marp-team/marpit-svg-polyfill/pull/50))
  - A WebKit polyfill will not apply if enabled [Layer-based SVG engine](https://blogs.igalia.com/nzimmermann/posts/2021-10-29-layer-based-svg-engine/)

### Changed

- The `polyfills()` function now returns a [thenable](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise#thenables) array, for getting the correct result of feature detection when calling together with `await` expression ([#50](https://github.com/marp-team/marpit-svg-polyfill/pull/50))
- Upgrade development Node and dependent packages to the latest version ([#51](https://github.com/marp-team/marpit-svg-polyfill/pull/51))

## v2.0.0 - 2022-04-12

### Breaking

- Required Node 10 and later to install (but recommend to use Node 14 and later) ([#45](https://github.com/marp-team/marpit-svg-polyfill/pull/45))

### Fixed

- Make robust from element injection to `<foreignObject>` ([#46](https://github.com/marp-team/marpit-svg-polyfill/pull/46))

### Changed

- Upgrade development Node and dependent packages to the latest version ([#45](https://github.com/marp-team/marpit-svg-polyfill/pull/45))

## v1.7.1 - 2021-02-07

### Fixed

- Fix Marpit's `<section>` detection to use `firstElementChild` instead of `firstChild` ([#33](https://github.com/marp-team/marpit-svg-polyfill/pull/33))

### Changed

- Upgrade development Node LTS and dependent packages to the latest version ([#34](https://github.com/marp-team/marpit-svg-polyfill/pull/34))
- Rename `master` branch to `main` ([#35](https://github.com/marp-team/marpit-svg-polyfill/pull/35))

## v1.7.0 - 2020-08-18

### Changed

- Use transformation matrix generated from `getScreenCTM()` ([#30](https://github.com/marp-team/marpit-svg-polyfill/pull/30))

## v1.6.0 - 2020-08-16

### Added

- Allow to change the target of observer ([#28](https://github.com/marp-team/marpit-svg-polyfill/pull/28))
- Return clean-up function from `observe()` ([#28](https://github.com/marp-team/marpit-svg-polyfill/pull/28))

### Changed

- Upgrade dependent packages to the latest version ([#29](https://github.com/marp-team/marpit-svg-polyfill/pull/29))

## v1.5.0 - 2020-07-16

### Changed

- Propagate zoom factor in the top window into `<iframe>` through `postMessage` ([#24](https://github.com/marp-team/marpit-svg-polyfill/pull/24))
- Migrate from TSLint to ESlint ([#25](https://github.com/marp-team/marpit-svg-polyfill/pull/25))
- Upgrade dependent packages to the latest version ([#26](https://github.com/marp-team/marpit-svg-polyfill/pull/26))

## v1.4.0 - 2020-07-09

### Fixed

- Follow zoom factor of the parent window in `<iframe>` ([#21](https://github.com/marp-team/marpit-svg-polyfill/pull/21))

### Changed

- Upgrade development Node LTS and dependent packages to the latest version ([#22](https://github.com/marp-team/marpit-svg-polyfill/pull/22))
- Test against Node 14 ([#23](https://github.com/marp-team/marpit-svg-polyfill/pull/23))

## v1.3.0 - 2020-06-07

### Fixed

- Fix visually shift depending on zoom level ([#18](https://github.com/marp-team/marpit-svg-polyfill/issues/18), [#19](https://github.com/marp-team/marpit-svg-polyfill/pull/19))

### Changed

- Simplify transformation ([#19](https://github.com/marp-team/marpit-svg-polyfill/pull/19))
- Upgrade dependent packages to the latest version ([#20](https://github.com/marp-team/marpit-svg-polyfill/pull/20))

## v1.2.1 - 2020-04-18

### Changed

- Upgrade dependent packages to the latest version ([#17](https://github.com/marp-team/marpit-svg-polyfill/pull/17))

## v1.2.0 - 2020-01-12

### Changed

- Upgrade dependent packages to the latest version ([#14](https://github.com/marp-team/marpit-svg-polyfill/pull/14))

### Removed

- CI test against EOL Node 8 ([#14](https://github.com/marp-team/marpit-svg-polyfill/pull/14))

## v1.1.1 - 2019-07-13

### Changed

- Upgrade dependent packages to the latest version ([#12](https://github.com/marp-team/marpit-svg-polyfill/pull/12))

## v1.1.0 - 2019-06-20

### Changed

- Simplify WebKit detection (JS build for browser become about 5x smaller) ([#9](https://github.com/marp-team/marpit-svg-polyfill/pull/9))
- Upgrade dependent packages to the latest version ([#10](https://github.com/marp-team/marpit-svg-polyfill/pull/10))

## v1.0.0 - 2019-06-05

### Breaking

- Drop support of Node 6.

### Changed

- Upgrade dependent packages to the latest version ([#7](https://github.com/marp-team/marpit-svg-polyfill/pull/7))
- Automate GitHub release ([#8](https://github.com/marp-team/marpit-svg-polyfill/pull/8))

## v0.3.0 - 2019-03-20

### Fixed

- Incorrect scaling with custom zoom level ([#3](https://github.com/marp-team/marpit-svg-polyfill/issues/3), [#4](https://github.com/marp-team/marpit-svg-polyfill/pull/4))

### Changed

- Upgrade dependent packages to the latest ([#5](https://github.com/marp-team/marpit-svg-polyfill/pull/5))

## v0.2.0 - 2018-12-31

### Fixed

- Fix incorrect scaling in split background ([#2](https://github.com/marp-team/marpit-svg-polyfill/pull/2))

## v0.1.0 - 2018-12-29

### Changed

- Split picking out logics into `polyfills()` function ([#1](https://github.com/marp-team/marpit-svg-polyfill/pull/1))

## v0.0.1 - 2018-12-29

- Initial release.

repository: marp-team/marpit-svg-polyfill

gha_language: TypeScript

repo_name: marp-team/marpit-svg-polyfill


text:
# Rust bindings for the [AAudio](https://developer.android.com/ndk/guides/audio/aaudio/aaudio) library

[![Crates.io](https://img.shields.io/crates/v/aaudio.svg)](https://crates.io/crates/aaudio) [![docs.rs](https://docs.rs/aaudio/badge.svg)](https://docs.rs/aaudio/)

## License

This project is licensed under the MIT license. Read [LICENSE](LICENSE) file for details.

repository: endragor/aaudio-rs

repo_name: endragor/aaudio-rs


text:
# Specifications for the Rails Assessment

Specs:
- [x] Using Ruby on Rails for the project
- [x] Include at least one has_many relationship (x has_many y; e.g. User has_many Recipes)
* **BusinessOwner:** has many clients, has many dogwalkers, has many services
* **Client:** has many dogs
* **Dogwalker:** has many appointments
* **Dog:** has many appointments
* ~~Appointment:~~
* **Service:** has many appointments

- [x] Include at least one belongs_to relationship (x belongs_to y; e.g. Post belongs_to User)
* ~~BusinessOwner:~~
* **Client:** belongs to BusinessOwner
* **Dogwalker:** belongs to BusinessOwner
* **Dog:** belongs to Client
* **Appointment:** belongs to Dog, belongs to Dogwalker, belongs to service
* **Service:** belongs to BusinessOwner

- [x] Include at least two has_many through relationships (x has_many y through z; e.g. Recipe has_many Items through Ingredients)
* **BusinessOwner:** has many appointments through Services
* **Client:** has many appointments through Dogs
* ~~Dogwalker:~~
* ~~Dog:~~
* ~~Appointment:~~
* **Service:** belongs to BusinessOwner

- [x] Include at least one many-to-many relationship (x has_many y through z, y has_many x through z; e.g. Recipe has_many Items through Ingredients, Item has_many Recipes through Ingredients)
* **BusinessOwner:** has many appointments through Services
* **Client:** has many appointments through Dogs
* ~~Dogwalker:~~
* *Dog:*
* **Appointment:** belongs to BusinessOwner, belongs to Client
* *Service:*

- [x] The "through" part of the has_many through includes at least one user submittable attribute, that is to say, some attribute other than its foreign keys that can be submitted by the app's user (attribute_name e.g. ingredients.quantity)<br>
* **Appointments is the join table**
  * **User submittable attributes:**
    * Service
    * date and time of the appointment
    * cost of the appointment = Service.price + Appointment.tip

- [x] Include reasonable validations for simple model objects (list of model objects with validations e.g. User, Recipe, Ingredient, Item)
**Validations:**
* BusinessOwner: unique username, presence of password
* Client: unique phonenumber with 9 digits, presence of name and address
* ~~Dogwalker~~
* ~~Dog~~
* Appointment: presence of service_id, dog_id, and datetime
* Service: presence of description and price

- [x] Include a class level ActiveRecord scope method (model object & class method name and URL to see the working feature e.g. User.most_recipes URL: /users/most_recipes)
**Active Services**
```
scope :active, -> {where("status = ?", true)}
```
Then this is called in the new appointments form to only show active services to choose from.

**Revenue**
in the businessowner model:
```
def revenue
  r = 0
  prices = appointments.collect {|a| a.service.price }
  rev = prices.inject(0){|r,x| r + x }
  "$#{sprintf('%.2f',rev)}"
end
```
this is then shown on the BusinessOwner#show view

**Total Tips**
in the dogwalker model:
```
def tipped
  t = 0
  tips = appointments.collect {|a| a.tip }
  tip_total = tips.inject(0){|t,x| t + x }
  "$#{sprintf('%.2f',tips)}"
end
```
this is then shown on the Dogwalkers#show view for Tips Earned

- [x] Include signup
- [x] Include login
- [x] Include logout
- [x] Include third party signup/login (how e.g. Devise/OmniAuth)

- [x] Include nested resource show or index (URL e.g. users/2/recipes)
**'/clients/:id/appointments'**
nested show page for a particular client's appointments

- [x] Include nested resource "new" form (URL e.g. recipes/1/ingredients/new)
**'/dogs/:dog_id/appointments/new'**
on the client show page there is a list of the cliet's dogs. I want a button next to each dog to add a new appointment for that dog.

- [x] Include form display of validation errors (form URL e.g. /recipes/new)

Confirm:
- [x] The application is pretty DRY
- [x] Limited logic in controllers
- [x] Views use helper methods if appropriate
  - helper methods include dollar_display, logged_in?, current_business_owner
- [x] Views use partials if appropriate
  - using partials to display form error messages.

repository: rosh-agahi/Walk-N-Roll

repo_name: rosh-agahi/Walk-N-Roll


text:
## Windows

1) In the Command Prompt window, get the first exercise...

```
C:\Users\johndoe> exercism fetch kotlin

New:
Kotlin (Etl)      C:\Users\johndoe\exercism\kotlin\etl

unchanged: 0, updated: 0, new: 1
```

2) In the "Welcome to IntelliJ IDEA" window, click the "Open" option.

3) Navigate to the "C:\Users\johndoe\exercism\kotlin\etl" folder.  Make sure you've selected the "etl" folder. Click "OK".

4) In the "Import Project from Gradle" dialog, check the "auto-import" and "create directories" checkboxes and select "Use customizable gradle wrapper".

```
Gradle project:    [C:\Users\johndoe\exercism\kotlin\etl\build.gradle   ](...)

[X] Use auto-import
[X] Create directories for empty content roots automatically

( ) Use default gradle wrapper (not configured for the current project)
(o) Use customizable gradle wrapper
( ) Use local gradle distribution

...
```

5) Click "OK".  IntelliJ will automatically create its project artifacts based on the Gradle project file.

* After the project has loaded and you've dismissed the "Tip of the Day" dialog, you may see a notice (in the top-right-hand corner), saying, "Unindex remote maven repositories found." you can safely dismiss this notice.

6) Open the `README.md` file and carefully read the background for the assignment.

7) Start by running the test suite: In the "Project" view, right-click on the test file (`etl\src\test\kotlin\EtlTest`), select "Run", then pick the "EtlTest" that has a JUnit icon to the left of it (red and green arrows), NOT the Gradle icon (circular green).

* When you first start an exercise, you should expect compilation errors because the test is setting expectations on a class that you need to write.  By trying to run the tests, you get a nice list of what needs to be fixed in the "Messages Make" view.

... and away you go!!!

## Mac OS X

### Get started with the first exercise

1. In the terminal window, get the first exercise...

        $ exercism fetch kotlin

        Not Submitted:       1 problem
        Kotlin (Etl) /Users/johndoe/exercism/kotlin/etl

        New:                 1 problem
        Kotlin (Etl) /Users/johndoe/exercism/kotlin/etl

        unchanged: 0, updated: 0, new: 1

2. In the "Welcome to IntelliJ IDEA" window, click the "Open" option.

3. Navigate to the `/Users/johndoe/exercism/kotlin/etl` folder.  Make sure you've selected the
   "etl" folder. Click "OK".

4. In the "Import Project from Gradle" dialog, check the "auto-import" and "create directories"
   checkboxes and select "Use customizable gradle wrapper".

    ![IntelliJ 14 CE -- Gradle import dialog](http://x.exercism.io/v3/tracks/kotlin/docs/img/mac-osx--idea-ce-gradle-import-dialog.png)

5. Click "OK".  IntelliJ will automatically create its project artifacts based on the Gradle project file.

 * After the project has loaded and you've dismissed the "Tip of the Day" dialog, you may see a
   notice (in the top-right-hand corner), saying, "Unindex remote maven repositories found." you can
   safely dismiss this notice.

6. Open the `README.md` file and carefully read the background for the assignment.

7. Start by running the test suite: In the "Project" view, right-click on the test file
   (`etl\src\test\kotlin\EtlTest`), select "Run", then pick the "EtlTest" that has a JUnit icon to the
   left of it (red and green arrows), NOT the Gradle icon (circular green).
   ![Run tests through IDEA JUnit Runner, NOT Gradle](http://x.exercism.io/v3/tracks/kotlin/docs/img/mac-osx--idea-ce-run-unit-tests.png)

 * If these menu options don't appear at first, wait for a few seconds and try again; IntelliJ is still
   configuring the project with a Kotlin nature.

 * When you first start an exercise, you should expect compilation errors because the test is
   setting expectations on a class that you need to write.  By trying to run the tests, you get a
   nice list of what needs to be fixed in the "Messages Make" view.

... and away you go!!!

repository: cgrayson/xkotlin

repo_name: cgrayson/xkotlin


text:
# Dynamic Proxies Samples

## Benchmarks

To exercise the benchmarks, run the following in a terminal:

 1. mvn clean install
 2. mvn verify -DskipTests -Prun-benchmarks

The first command will install the JAR for the core project in your local Maven
 repository. The second command will use the core JAR to run the benchmarks.

The forking required by JMH does not work when running the benchmarks using the
 Maven plugin in IntelliJ IDEA 2019.2.4.

A note about creating a JPMS (Java) module for the benchmarks.
 This does not work because there is a package clash between jmh-core and
 jmh-generator-annprocess which prevents them being loaded as automatic modules
 at the same time.  jmh-core has a package `org.openjdk.jmh.generators.core`
 which clashes with `org.openjdk.jmh.generators` in jmh-generator-annprocess.

## Releasing

To create a new release, run the following in a terminal:

 1. mvn release:prepare
 2. mvn release:clean

Step 1 creates a git tag after committing a change to the POMs with a release
 version number. The user is prompted for the release version number and the
 next snapshot number. Numbering follows
 [semantic versioning](https://semver.org/).

Two commits will be added similar to:

* [maven-release-plugin] prepare release dynamic-proxies-samples-1.0.0
* [maven-release-plugin] prepare for next development

Step 2 deletes support files that would be used for `mvn release:perform`. We
 are not running that step which is for publishing to a remote maven
 repository. Such publication is highly discouraged when using automatic modules
 such as spark.core. The warning during the Maven compile step is:
```
********************************************************************************************************************************************
* Required filename-based automodules detected: [spark-core-2.8.0.jar]. Please don't publish this project to a public artifact repository! *
********************************************************************************************************************************************
```

The release jar and sources jar can be found in the target directory  and can be
 rebuilt at any time by checking out the tag and running `mvn package`.

The release is done by the
 [Maven Release Plugin](https://maven.apache.org/maven-release/maven-release-plugin/).

repository: sbordet/dynamic-proxies-samples

repo_name: sbordet/dynamic-proxies-samples


text:
---
layout: post
published: true
title: How to Have Comfortable Meditations Using These 7 Items
---
![](https://miro.medium.com/max/2800/1*rX_NuLB5XA__6h3AuxmP5Q.png)

### My (common and uncommon) meditation essentials

*“Are the 10 minutes over yet?” *I thought to myself, sitting on the floor in a small, high hotel room in Bangkok, with closed eyes waiting for something to happen.

I’d resolved to meditate every day for at least 10 minutes. Yet, needless to say, I wasn’t getting anywhere.

With the lack of any meditation equipment, I’d placed a soft pillow on a thorny mat, imagining myself to be some kind of a yogi perhaps.

Within seconds my legs started paining and I couldn’t hold myself still. My posture was one of the biggest hurdles to establishing a consistent meditation practice at that time.

Moreover, I didn’t realize how important the posture was to have a comfortable meditation.

The mind and the body are more connected than we all can imagine. They constantly influence each other.

In a general sense, Amy Cuddy's [TED Talk](https://www.ted.com/talks/amy_cuddy_your_body_language_may_shape_who_you_are?language=en), tells us all we need to know. Different kinds of postures induce different states of mind — confidence or cowardness depending on which pose you choose. For instance, assuming a power pose before an interview can instantly improve your confidence as well as the interviewer's perception of your ability.

Applying the [same concept to mediation](https://medium.com/the-ascent/the-complete-guide-to-meditation-postures-everything-you-need-to-know-e60e60c51666), it’s important to sit in a certain manner for your practice. For one, it makes a psychological connection between the mind and body.

If you always sit on a cushion to meditate for example, then the mind will know it’s time to meditate. Thus, a seemingly small change can have a big impact.

Your posture can thus make or break your meditation. If you take too much back support, it will make you fall asleep but if you try to assume the lotus pose from day one, it will distract you.

To make sure I’m able to sit for long periods of time without disturbances and distractions, here are the meditation essentials I use.

## Mat

![Photo by author](https://cdn-images-1.medium.com/max/4000/1*IP0P4QdxFz5IXQTttfLSRQ.jpeg)*Photo by author*

It’s commonplace knowledge amongst yogis that sitting on the bare floor is not the ideal position for meditation.

This is why many yogis in the past used tiger skin or deer skin as their mats. (It’s important to note that no killing was actually involved. The skin was taken when animals died their natural death).

Swami Sivananda writes in [May I Answer That](https://www.goodreads.com/book/show/40231366-may-i-answer-that):
> **From the spiritual point of view, the sages found that doing Sadhana seated on a deer-skin was highly conducive to Siddhi. The power generated in the body through Sadhana was preserved by the skin.**

The subtle reason is that animal skin creates insulation between the energy of the body and the magnetic pull of the earth.

But since obtaining animal skin is difficult and even illegal, it’s [safe to use](https://supremeswan.com/blogs/supreme-swan/meditation-starts-with-sitting) a mat made with a combination of wool and silk. Silk repels certain earth currents better than cotton.

Nevertheless, the differences are subtle. You may or may not notice these. Don’t make or break your practice on this matter. What’s important is you meditate.

Being born and brought up in a Hindu family, we have several such mats. If you don’t you can find one on Amazon.

## Cushions

Every one should find a spot that helps them sit without legs going numb or to sleep. It’s a major distraction during meditation.

For me two cushions work best — one to sit on and another below my right thigh.

Sitting on a cushion gives an elevation to the buttocks which makes it easier to keep the spine straight during mediation. A straight spine helps energy to flow freely to the brain.

## Shawl

![Photo by author](https://cdn-images-1.medium.com/max/9248/1*ivoYbTxeKScGWqDxyNYRcA.jpeg)*Photo by author*

A shawl is better than a jacket, sweater, or other extra layers of clothing. Removing clothes is difficult during meditation, adjusting the shawl is easier.

Plus, the way a shawl wraps your whole body makes it easier to stay still. It wraps the positive energy that you accumulate while you meditate.

Also, while meditating, you start to withdraw attention from the body. As a result of being still, it cools down. And the shawl provides extra warmth.

As a side note, blankets and shawls almost always induce a psychological sense of comfort and relaxation.

As for the material, I use a silk shawl since it’s not too hot, unlike a woolen shawl.

## Earmuffs

![Photo by author](https://cdn-images-1.medium.com/max/6936/1*8bFOUi3l7mMYg6rTXzTI-Q.jpeg)*Photo by author*

I use the [3M industrial earmuffs](https://www.amazon.com/3M-Peltor-X5A-Over-Earmuffs/dp/B00CPCHBCQ/ref=sr_1_3?crid=24T9KY61IMFZF&dchild=1&keywords=3m+industrial+headphones&qid=1611985866&sprefix=3m+indus%2Caps%2C355&sr=8-3). They are magic.

They block outside noises completely but still let you hear the noises near you — meditation timer, the phone ringing, and so on.

I live with my family and it isn’t always easy to tell them to be quiet when I meditate. Further, I meditate for an hour at a time so they can’t possibly be silent for that long!

If your meditation place has a lot of disturbances that you can’t avoid, then these earmuffs are great.

They can seem heavy to some people while meditating, but I’d much rather prefer a little heaviness than constant distractions.

As an alternative, you can also try using silicon/foam earplugs though I’ve found them to mostly be of the use-and-throw variety and not as effective.

## Beads

![Photo by author](https://cdn-images-1.medium.com/max/6936/1*7PVFHm-GtS0Ob7Sn_WiAWA.jpeg)*Photo by author*

At the most basic level, meditation malas or beads help you focus during your meditation.

Concentrating during meditation is not always easy. Many people find it hard to focus on the breath or some body part for example. This is where beads can help you.

The repetitive movement of touching the beads helps to ground you. Plus, when you chant a mantra every time you take your fingers through the beads, it’s easier to keep count of how many times you’ve chanted.

Beads don’t have to be composed of fancy stones. Normal ones just work fine.

I use the beads for a specific technique of chanting but apart from that, I rarely use them. They come in handy throughout the day if I want to have a quick mindfulness session if I feel I’m losing some of the calmness and peace I experience.

## Harmonium

![](https://cdn-images-1.medium.com/max/9248/1*yEJezqSclbfsLCLPpsOd2Q.jpeg)

![Photo by author](https://cdn-images-1.medium.com/max/9248/1*2klp7HSl41b_IW1h3zPObg.jpeg)*Photo by author*

A harmonium is a keyed instrument that originated in India. It’s a modified version of the reed organ, with keys like the piano and bellows to pump air into the instrument.

I use the harmonium to chant mantras and other devotional chants.

Chanting at its core is about expressing your love and devotion to God.

More than anything, chanting helps to concentrate the forces of your mind on meditation and divine qualities. Often the mind is scattered throughout the day and chanting is a powerful way to bring it back at one point before meditation.

Even if I’ve had a distracted day, five minutes of chanting is all I need to get in the right state of mind. It’s the number one tool to prepare my mind for longer meditations.

## A T-Shaped Board

![Photo by author](https://cdn-images-1.medium.com/max/6936/1*NiUK5jd7quO_ege_vWnwsQ.jpeg)*Photo by author*

Yogis of yore used to carry a similar tool which is commonly known in Hindi as a “Danda” literally meaning stick. Prevalent knowledge tells us that this stick was used by yogis to do [Japa](https://en.wikipedia.org/wiki/Japa) meditation

This T-shaped board is also called an Aum Board. It’s also used to practice the AUM technique of meditation.

AUM is the Holy Ghost or the great Comforter referred to in the Bible as God’s manifestation of creation through vibration. It is the vibration of all life– all creation. Thus, it can be heard within us *and* all around us.

The Aum technique gives people a scientific technique for contacting Spirit through deep concentration on the inner Cosmic sounds and vibration of AUM. It is a tremendously powerful tool for self-realization by bridging our individual consciousness with Cosmic consciousness.

[Learn more about why we meditate on Aum](https://www.ananda.org/meditation/meditation-support/meditation-techniques/aum-technique/).

## To Sum Up

Here are all the mediation essentials I use daily that help me

* A mat

* 2 cushions — one to sit on and one below my right thigh

* A shawl to maintain the right temperature while meditating

* Earmuffs to block noise

* Beads for concentration or Japa meditation

* Harmonium for devotional chanting

* T-shaped board (or Aum board)

Feel free to experiment with one or more of these to have better meditations yourself. And if something helps you, do let me know!

-----------
*Struggling to meditate? Get your free 7 Day email course — [Meditation 101: How to Start Meditating](http://bit.ly/meditation101-course)*


text:
#RepEx: Replica Exchange Molecular Dynamics simulations Package

RepEx is a novel Replica Exchange Molecular Dynamics (REMD)
simulations package for HPC clusters. The primary aim for the design of RepEx
is to decouple the implementation of the Replica Exchange (RE) algorithm from
the Molecular Dynamics (MD) simulation engine. Current version of RepEx supports Amber [1] and NAMD [2] simulation engines, and can be easily modified to support
any other MD engine.

RepEx supports multi-dimensional REMD simulations with arbitrary number and
ordering of dimensions. Currently RepEx supports three exchange types: salt
concentration, temperature and umbrella exchange. RepEx explicitly decouples the
number of replicas, from the computational resources (CPUs, GPUs, etc.). RepEx
can be used as a testing platform for new or unexplored REMD methods.

To execute its workloads, RepEx relies on the concept of task-level parallelism, which is enabled by the use of the RADICAL-Pilot API [Radical Pilot](http://radicalpilot.readthedocs.org/en/latest/).

RepEx supports synchronous and asynchronous RE patterns. Asynchronous RE
Pattern does not have a global synchronization barrier between simulation and
exchange phase. While some replicas are in the simulation phase, others might
be in the exchange phase. Based on some criterion, a subset of replicas
transition into the exchange phase, while other replicas continue in the
simulation phase. Selection of replicas that will transition may be based on a
FIFO principle, e.g. first N replicas transition into an exchange
phase. Alternatively, only replicas which have finished a predefined number of
simulation time-steps (2 ps) during some real time interval (1 minute)
transition into exchange phase.

[1] - [Amber](http://ambermd.org/)

[2] - [NAMD](http://www.ks.uiuc.edu/Research/namd/)

###User guide

RepEx user guide can be found at: [repex.readthedocs.org](http://repex.readthedocs.org/en/master/)

###Website

RepEx website can be found at: [repex.io](http://radical-cybertools.github.io/radical.repex/)

###ICPP-2016 paper

Paper in pdf format: [paper.pdf](https://github.com/radical-cybertools/radical.repex/blob/devel/documents/icpp16/paper.pdf)

Presentation in pdf format: [slides-icpp16.pdf](https://github.com/radical-cybertools/radical.repex/blob/devel/documents/icpp16/slides-icpp16.pdf)

###Presentations

A. Treikalis thesis: [at-thesis-slides.pdf](https://github.com/radical-cybertools/radical.repex/blob/devel/documents/presentations/at-thesis-slides.pdf)

Performance optimization slides: [repex-performance-optimization.pdf](https://github.com/radical-cybertools/radical.repex/blob/devel/documents/presentations/repex-performance-optimization.pdf)


text:
# Scrapy Statsd Middleware

## Usage

```
pip install scrapy-statsd-middleware
```

```
DOWNLOADER_MIDDLEWARES = {
  'statsd_middleware.StatsdMiddleware': 543,
}

SPIDER_MIDDLEWARES = {
  'statsd_middleware.StatsdMiddleware': 543,
}
```

There's also a few settings that you can use:

-   `STATSD_HOSTNAME` - Defaults to the current machine's hostname
-   `STATSD_PREFIX` - Defaults to "hostname.spider-name."
-   `STATSD_HOST_IP` - Defaults to "<IP_ADDRESS>"

This will increment `statsd` with the following:
- requests (`spider_reqs_issued`)
- response (`spider_resps_received`)
- errors (`error_KeyError`, where KeyError is whatever the error name is)
- items processed (`processed_product`, where Product is whatever the item class name is)

## Example Implementation

An example implementation of this middleware is in /example.
It includes a docker-compose file that describes how to use this middleware with statsd & graphite

## Example Installation & Usage

-   Build the docker images: `docker-compose build`
-   Start the statsd container: `docker-compose up -d`
-   Run the example spider: `docker-compose -f ./example/docker-compose.yml run spider bash -c "cd ./opt/scrapy/dirbot/ && scrapy crawl dmoz"`

You can see a live graphite dashboard at <http://<IP_ADDRESS>/dashboard> You should see stats show up under something like "stats.Z-MacBook-Pro.local.dmoz.spider_reqs_issued"

## Development
You can run the tests via make test

repository: expired-brain/scrapy-statsd

repo_name: expired-brain/scrapy-statsd


text:
---
layout: page
title: About
---

ImageLab is a standalone tool which supports anyone to get started with image processing related concepts and techniques in an interactive, less logical way. So, this tool enables and also motivates the fresh users to understand how image processing concepts work by interacting with ImageLab. Moreover, for the users who are already comfortable with image processing tasks ImageLab offers a test environment before they move ahead with actual implementation or development.

[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)

## Sample Overview
![demo_giff](./../assets/Demov2.gif)

## Supported Image Processing Operations

- Basic Read/Write operation
- Image Conversion
- Image Smoothing
- Geometric Transformation operation
- Drawing operation
- Filtering operation
- Thresholding operation
- Transformation operations
- Contour operation
- Miscellaneous operation
- Histogram operation

## Communication channels
[![Gitter](https://badges.gitter.im/scorelab/ImageLab.svg)](https://gitter.im/scorelab/ImageLab?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)

## Technologies used

Following technologies has been used to develop and maintain this project.

| Technology   | Version              |
|--------------|----------------------|
|              |                      |
| Java         | 1.8                  |
| JavaFX       | 1.8 JDK (inbuilt)    |
| OpenCV       | 3.2.0                |
| Apache Maven | 3.6.3                |
| Ruby         | 3.6.3                |
| Jekyll       | 4.1.1                |

## Mentors
- [Namal Jayasuriya]()
- [Oshan Mudannayake](https://github.com/ivantha)
- [Deniz Karakay](https://github.com/dkarakay)
- [Tuan Amith]()
- [Sumedha Dissanayaka](https://github.com/sumedhe)

## Contributors
- [Dilum De Silva](https://github.com/dilum1995)
- [Sahan Dissanayaka](https://github.com/SahanDisa)

repository: polahano/imagelab

gha_language: Java

repo_name: polahano/imagelab


text:
# ClassicCraft
*A WoW Classic simulation tool*

### How to use :
- Download and extract the content of the .zip file anywhere on your computer
- Modify `sim.json` to setup the simulation
	- As of 0.3.1, you can use the [ClassicCraft Addon on Curse](https://www.curseforge.com/wow/addons/classiccraft) to speed up the process (but at the moment some stats like Crit or Hit rating aren't supported by the addon, so you need to fill them by hand afterwards)
	- You can use the examples in the folder `sim.json examples` if needed
- Execute `ClassicCraft.exe`
	- A console should appear and the simulations start
	- Depending on the desired accuracy (`TargerErrorPct` or `NbSim`) and if `StatsWeights` is activated, the process might take some time
- A new .txt file with the logs of the simulation is created in the `Logs` folder, press any key in the console window to close it

### Current features :
- DPS Simulation
	- Character setup
		- Class, Race
		- Talents (use Addon export or classic.wowhead.com/talent-calc/*your_class*/*copy-paste_that_part*)
		- Gear (some special sets like Rogue's T0 6P and T1 5P)
		- Enchantements (Crusader)
		- Consumables
		- CDs to use (Racial, Recklessness, etc.)
		- Raid buffs (Windfury, etc.)
	- Encounter setup
		- Boss Level/Armor
		- Length (+ boss low life length)
	- Statistics output as raw text
		- Overall DPS
		- DPS and Hit stats by spell (Hit, Miss, Crit, Glancing, etc.)
		- Stats weights (1 AP = X DPS, 1 STR = X DPS or X AP, etc.)
- Classes supported
	- Warrior
		- Fury BT (1H or 2H)
	- Druid
		- Feral (Powershifting)
	- Rogue
		- Combat (SS or BS)

### JSON Attributes List
- `Sta` : Stamina
- `Str` : Strength
- `Agi` : Agility
- `Int` : Intellect
- `Spi` : Spirit
- `HP` : Health
- `Mana` : Mana
- `Armor` : Armor
- `ArmorPen` : Armor Penetration
- `Haste` : Haste(Attack Speed) %
- `AP` : Attack Power
- `RAP` : Ranged Attack Power
- `SP` : Spell Power
- `HSP` : Healing Spell Power
- `Hit` : Hit Chance %
- `SpellHit` : Spell Hit Chance %
- `Crit` : Crit Chance %
- `SpellCrit` : Spell Crit Chance %
- `MP5` : MP5
- `Sword` : Sword Weapon Skill
- `Axe` : Axe Weapon Skill
- `Mace` : Mace Weapon Skill
- `Polearm` : Polearm Weapon Skill
- `Staff` : Staff Weapon Skill
- `Dagger` : Dagger Weapon Skill
- `Fist` : Fist Weapon Skill
- `WDmg` : Weapons Additionnal Damage

### FAQ
- When will X class be implemented ?
	- Not a class order but here is a rough roadmap : Popular DPS Melee Specs -> Popular DPS Caster Specs -> GUI -> Alternative DPS Melee and Caster Specs -> Multiple Targets -> Bonus features (multiple players, tanking/healing sim, ...)
- Is X item implemented yet ?
	- Try it yourself and you'll see if it works! The program detects special effects by their item's name, so check for typos if it doesn't. A complete list of supported items will be written, one day.
- Is X set implemented yet ?
	- For now, sets providing stats boost have to be added manually in the `sim.json` file (either along with one of the items or as a Buff). Special set effects are detected by checking pieces names, so write them carefuly. A complete list of supported special sets will be written, one day.

Please report any issue or suggestion either here on [GitHub](https://github.com/Zwyk/ClassicCraft/issues) or on the [Discord](https://discord.gg/tG4q7HE)

You can also PM me on Discord : Zwyk#5555

repository: stweily/ClassicCraft

repo_name: stweily/ClassicCraft


text:
Don't use the Android Studio (IntelliJ) emulator as that makes my system hang and crash and makes it so that I have to reboot, so try using [Androidx86](http://www.android-x86.org/) with virtualbox to test on Oreo.
Note: disable mouse integration in the virtualbox menu when the vm is running to get the mouse to work.
-- to get the virtualbox emulator to show up as a device when you click run in IntelliJ, first on the commandline, type `adb connect <IP_ADDRESS>:5555` and change the IP to whatever the ip is of the virtualbox vm.
 `adb -s <IP_ADDRESS>:5555 install app-debug.apk`
 `adb -s <IP_ADDRESS>:5555 shell`
 https://stackoverflow.com/questions/14654718/how-to-use-adb-shell-when-multiple-devices-are-connected-fails-with-error-mor

Remember to first enable USB debugging on the phone you are testing on: https://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android.htm

We are targeting Android 5.0 Lollipop (SDK 21) and higher.

For setting up IntelliJ, you may need to set the Gradle settings like the "Gradle JVM" set it to Use JAVA_HOME (https://stackoverflow.com/a/36539783/2785644) and also to "Use local gradle distribution"

Then go to Settings->Appearance & Behaviour->System Settings->Android SDK and check if anything needs to be installed or removed there.

Also if you are using the built in Intellij android emulator & you are running on a PC that supports Intel Virtualization Technology, you should also make sure to install the Intel x86 Emulator Accelerator in the SDK Tools tab there as that will make the Emulator run faster.

Then set up the SDK:
 - If the yellow bar up top is showing, click on the Setup SDK in the yellow bar top right, then if Android API 21 Platform isnt there, you will need to add it manually, click on the plus icon and select Android SDK and add C:\Users\Coop\AppData\Local\Android\Sdk to the folder selector window path and then click ok and then select version 21.
- If not, go to Build menu, then Edit Libraries & Dependancies and go to app and click the Properties tab and set Compile SDK version to 21.

If you get an issue with building with gradle that the sdk version is wrong, you may need to add something like:
```
configurations.all {
    resolutionStrategy {
        force 'com.android.support:support-annotations:26.1.0'
    }
}
```
to the build.gradle file

If intellij is really slow, you may want to try some of these: https://stackoverflow.com/questions/30817871/android-studio-is-slow-how-to-speed-up/32366177

Note: when you're testing the app, it seems to stay broadcasting even when you close the app, so you may need to disable then re-enable blueloss everytime you reload the app on the phone in dev.

To view logcat via the terminal, you can run `adb shell`, then type in `logcat` and press enter and that will show you the full log.

To uninstall your apk via the terminal, run `adb uninstall your.package.name`

To install your apk via the terminal, tun `adb install /path/to/apk-debug.apk`

 Also, remember that by default my phone uses the pihole dns, which will interfere when testing analytics in the android app, so either switch to using google dns on the phone or use the Androidx86 VM to test.

repository: Darkle/BlueLoss-Android-App

repo_name: Darkle/BlueLoss-Android-App


text:
# buffinator
Stack based, remote buffer overflow python script template.

```
    ____        _________             __
   / __ )__  __/ __/ __(_)___  ____ _/ /_____  _____
  / __  / / / / /_/ /_/ / __ \/ __ `/ __/ __ \/ ___/
 / /_/ / /_/ / __/ __/ / / / / /_/ / /_/ /_/ / /
/_____/\__,_/_/ /_/ /_/_/ /_/\__,_/\__/\____/_/

	Author :Steve Mcilwain
	GitHub : https://github.com/stevemcilwain
```

## Purpose
I created this script to help me study for the OSCP exam and write remote, stack buffer overflows from scratch.

## Usage
I have the script broken out into phases, so the intent is you do one phase, like fuzzing, then you come back and add the result into a variable and move on to the next step.

As you go along, you comment out methods except the one you're on and save results from your work into variables used by the next phase.

## What This Isn't
The script isn't intended to be fully automated or anything, just to save time in developing a custom script. You need basic understanding of stack-based buffer overflows to use it. This isn't a tutorial or learning tool, more of a time-saver and mental guide.

## Roadmap
I'll add more "protocol" methods as I practice, just point to the one you need in send_with().  The current stuff in the script was from my practice on SLMail 5.5.

Enjoy and contribute!

repository: stevemcilwain/buffinator

repo_name: stevemcilwain/buffinator


text:
# repack

A CLI for repacking your cbr and cbz archives in case they seem to be corrupted
or can't be read from your favorite manga reader!

# Usage

```bash
$ repack -h

A CLI tool for repacking cbr and cbz archives

Usage:
  repack [flags] INPUT_DIR [OUTPUT_DIR]

Flags:
      --dry-run           If set, no archives will be repacked
      --force             Forcefully create the archive by deleting and overwriting any existing files and archives
  -f, --formats strings   The input formats. Multiple formats are supported - comma separated. (default [cbr])
  -h, --help              help for repack
      --no-color          If set, no colors are used for the log message
      --verbosity int     verbosity level (0-3). 0 = error, 1 = info, 2 = debug (default 1)
  -v, --version           version for repack
```

# License

repack is licensed under the MIT License.


text:
# Wagtail-speech

Turn Wagtail pages into lifelike speech using Amazon Polly.

[![Build Status](https://travis-ci.org/moorinteractive/wagtail-speech.svg?branch=master)](https://travis-ci.org/moorinteractive/wagtail-speech)
[![Coverage Status](https://coveralls.io/repos/github/moorinteractive/wagtail-speech/badge.svg?branch=master)](https://coveralls.io/github/moorinteractive/wagtail-speech?branch=master)

* Issues: [https://github.com/moorinteractive/wagtail-speech/issues](https://github.com/moorinteractive/wagtail-speech/issues)
* Testing: [https://travis-ci.org/moorinteractive/wagtail-speech](https://travis-ci.org/moorinteractive/wagtail-speech)
* Coverage: [https://coveralls.io/github/moorinteractive/wagtail-speech](https://coveralls.io/github/moorinteractive/wagtail-speech)

## Installation

Install the package

```
pip install wagtail-speech
```

Add `wagtailspeech` to your `INSTALLED_APPS`

```python
INSTALLED_APPS = [
    # ...
    'wagtailspeech',
]
```

Now make and run your migrations

```
manage.py makemigrations
manage.py migrate
```

We assume you already have setup credentials for [boto3](http://boto3.readthedocs.io/en/latest/guide/configuration.html).

## Usage

Use the ``SynthesizeSpeechMixin`` on pages you want to be rendered as audio streams.
These pages triggers the ``synthesize_speech_from_page`` method when they are edited via the Wagtail admin interface.
You can find your saved audio stream on the ``page.audio_stream`` property (by default a low bitrate .mp3 file).

```python
from wagtail.core.models import Page
from wagtailspeech.models import SynthesizeSpeechMixin

class HomePage(SynthesizeSpeechMixin, Page):
    def get_speech_text(self):
        return self.title
```

You are completely free how to provide the text to be renderend.
In most cases you probably also want to provide values from a ``StreamField``.
For this use case we provided a ``get_speech_text_from_stream_field`` method which calls ``get_speech_text`` (if present) on your blocks and concats the content of it with breaks between them.

```python
class ExampleBlock(blocks.StructBlock):
    text = blocks.TextBlock()
    button_label = blocks.CharBlock(max_length=255)
    button_link = blocks.TextBlock()

    class Meta:
        template = 'blocks/cta.html'

    def get_speech_text(self, value):
        return "%s<break strength=\"x-strong\"/>%s" % (
            force_text(value.get('text')),
            force_text(value.get('button_label')))

class ExamplePage(SynthesizeSpeechMixin, Page):
    content = StreamField([
        ('example', ExampleBlock()),
    ])

    content_panels = Page.content_panels + [
        StreamFieldPanel('content'),
    ]

    def get_speech_text(self, request):
        from wagtailspeech.utils import get_speech_text_from_stream_field
        return get_speech_text_from_stream_field(request, self.main_content)
```

## Settings

Available settings:

```python
WAGTAIL_SPEECH_OUTPUT_FORMAT = 'mp3'
WAGTAIL_SPEECH_SAMPLE_RATE = '8000'
WAGTAIL_SPEECH_VOICE_ID = 'Joey'
```

For other values please read the [documentation](http://boto3.readthedocs.io/en/latest/reference/services/polly.html#synthesize_speech).

## Tips

For proper pronunciations of your text and have more control over breaks, etc. we strongly advice you to read more about the supported tags of the [Speech Synthesis Markup Language](http://docs.aws.amazon.com/polly/latest/dg/ssml.html) in Polly.

## Roadmap

* [ ] Solution for limitations (max. 1500 chars / 5 min audio cut-off.)
* [ ] Add real-time streaming
* [ ] Celery support

repository: djch/wagtail-speech

repo_name: djch/wagtail-speech


text:
Courses Info Portlet
====================

This project is my seminar work for course MI-LIF at CTU in Prague. It’s very simple Liferay portlet which one can use to search and to view information about our courses.

The main aim of this project is:

1. satisfy project targets with regard to used technologies and features,
2. provide reference example how to easily retrieve data from RESTful service (specifically [KOSapi](https://kosapi.fit.cvut.cz)) secured with OAuth2 protocol or HTTP Basic,
3. try out new template engine [Thymeleaf](http://www.thymeleaf.org/) in portlet environment.

I didn’t deal with styling and AJAX at all so it doesn’t look cool, but this project is more about code. ;-) Also it may seem weird that I divided such simple functionality into two portlets, but I just wanted to try out Inter Portlet Communication.

Chosen points of work’s targets
-------------------------------

* Spring Portlet MVC
* Inter Portlet Communication
* Portlet Preferencies
* Portlet modes VIEW, HELP, EDIT
* Liferay Friendly URL mapping
* RESTful client (instead of database)

Used frameworks and libraries
-----------------------------

* [Spring Framework](http://www.springframework.org/) (Core, Portlet MVC, Web, OXM, Security OAuth2)
* [Thymeleaf](http://www.thymeleaf.org/) + [liferay-url-addon](https://github.com/jirutka/thymeleaf-liferay) (XML/XHTML/HTML5 template engine)
* [Hibernate Validator](http://www.hibernate.org/subprojects/validator.html) (JSR-303 Bean Validation)
* [Atom JAXB](https://github.com/jirutka/atom-jaxb) (custom JAXB mapping for Atom Syndication Format)

License
-------

This project is licensed under [MIT license](http://opensource.org/licenses/MIT).


text:
[![Build Status](https://travis-ci.org/Project-Owl/owl.svg?branch=master)](https://travis-ci.org/Project-Owl/owl)
# Project Owl
## Software - OWL 🦉

Website:  http://www.project-owl.com

Manage large and small disasters with the Owl incident management system.  Owl
is designed to offer a fast, simple incident management experience --- just by
talking to it.

Project Owl is a Ruby on Rails web application hosted on IBM Cloud leveraging
the IBM Watson Studio, IBM Watson Cloud APIs, Weather Company APIs, Google Maps
API, and public data sets.

## Hardware - ClusterDuck 🐥
Deploy Owl incident management to geographies without active communications or
infrastructure through the `ClusterDuck` Mobile Network.  This network is made
of portable IoT WiFi devices - called `Ducks` - that provide an ad-hoc network
solution.

![overview](https://user-images.githubusercontent.com/13107225/46240475-263eb080-c376-11e8-9d17-ffe05a4c6527.png)

`ClusterDuck` is prototyped over **Arduino, with a WiFi/LoRa solution** and
levarages IBM's IoT Platform, Node-RED, Cloudant DB, and Cloud Foundry.

Learn more @ [ClusterDuck](https://github.com/Project-Owl/duck)

## Open Source Software

As a developer you can build experiences for Owl Software.  These experiences
are accessible from the conversational interface.  Examples of experiences to
create for Owl are:  a weather forecasting app, and leadership and management
structure app, messaging app, a translation app, or a predictive data analytics
app.

We are looking for passionate developers who would like to contribute to this
software ecosystem.  While the app development environment is under construction
for Owl please reach out to<EMAIL_ADDRESS>if you are interested
in contributing and we will provide more information about the technology and
how to build with it. You can see [general guidelines here](CONTRIBUTING.md).

Apps for Owl are created simply using HTML, CSS, and JS.  If you have built a
web site before, you can build an app for Owl.

## Open Source Hardware
#### ClusterDuck + QuackPack
The `ClusterDuck` hardware solution would also allow passionate developers and
OEMs to build on top of our hardware, via lego-like modules called
**QuackPacks**. In addition to relaying civilian data, additional `Quacks` would
allow `Ducks` to send additional useful and crucial data via sensors such as,
**temperature**, **water-pressure**, **smoke**, **gas**, and a lot more!

**QuackHackers** will be provided with boilerplate libraries in order for your
`QuackPacks` to work with our `Ducks`.

Learn more and contribute to our open source hardware @
[ClusterDuck + QuackPack](https://github.com/Project-Owl/duck#quackpack)

## Project Roadmap

The Owl is currently a cloud software prototype and is being tested in simulated
incidents.  The ClusterDuck hardware also has been manufactured as a prototype
and is being tested to prepare for field experiments.

![roadmap](https://github.com/Project-OWL/owl/blob/master/app/assets/images/projectowl_roadmap.jpg?raw=true)


text:
# 🦕 tyrannosaurus.rest 🦖
[![Build Status](https://travis-ci.com/rakhadjo/tyrannosaurus.rest.svg?branch=master)](https://travis-ci.com/rakhadjo/tyrannosaurus.rest)

The Dinosaur Rest API, because why the hell not?

The word 'dinosaur' originates from the Greek words deinos meaning 'terrible' and sauros meaning 'lizard'.
Hence the word 'dinosaur' actually means 'terrible lizard'. That said, there are a lot of misconceptions today regarding the actual creatures that the
general public mislabel as 'dinosaur' (e.g. ichthyosaurs, mosasaurs, pterosaurs etc. are not actually 'dinosaurs' at all.)

I hope by categorizing information in this API through endpoints, a clearer picture can be painted regarding their mislabeling.

## Usage & Deploying

Assuming you've got `npm` and `Node` installed on your machine:

1. `git clone https://github.com/rakhadjo/tyrannosaurus.rest.git`
2. `cd tyrannosaurus.rest`
3. `npm install`
4. `npm start`

By default I set the app to run on `localhost` port `1212`

## Endpoints

tyrannosaurus.rest only accepts `GET` requests.
No authentication has been planned yet for this project.
Simply perform an HTTP `GET` request on the following endpoints to receive your content requests.
Data will be returned in the `json` format. More on this later.

### Dinosaur Information

There are two ways of getting the dinosaur information.

#### Unordered, uncategorized

The first way is to simply substitute the dinosaur name:
`GET (host)/dinosaur/{dino-name}`

Currently supported endpoints to substitute `{dino-name}` can be found in `static_content/endpoints.js`

#### Categorized by Era

...needs work...

#### Return Type

In most cases, the return type will be as follows:

```json
{
   "name": "",
   "is_dino": "",
   "diet": "",
   "era": "",
   "found": "",
   "avg_weight_kg": "",
   "avg_length_m": "",
   "movement": ""
}
```
Data is retrieved from `dinosaurs.js` supposedly located in the root directory.
### Developer

#### `/about`

Some meta-information of the API, developer, etc.

#### `/endpoints`

Returns the endpoints, and their descriptions.

### Random

#### `/movies`

List of Movies containing the general public understanding of what dinosaurs are 😒

#### `/random`

Returns some random dinosaur entry

#### `/dinobots`

Transformers Reference, they're essentially Autobots that can transform to prehistoric creatures.

#### `/sounds/{identifier}`

Me trying my best to represent each of their sounds with what I can do with my keyboard.
Will return `404` if empty


text:
# tiniest-analytics
Tiniest Analytics is a *very* simple to use, cross-platform (tested on win/osx/linux/ios/android) and basically *very tiny* analytics system written in C++ (about 100 lines of code), made specifically for games. It uses libcurl to post events to your Google Analytics account.

Usage: include TAnalytics.h, call Init("UA-12345678-1", uniqueId) before using and Shutdown() when closing your app, and Update() each frame. You also need libcurl in your project (no ssl needed).

There's only one function to use when posting an event, e.g.

TAnalytics::Event("GameStart", "linux");

TAnalytics::Event("WeaponClicked", "RocketLauncher");

TAnalytics::Event("MapStarted", "SinglePlayer", "MapName.map");

![alt text](https://user-images.githubusercontent.com/292486/33986723-206b0bc8-e0c7-11e7-9ac9-8f4f841385ed.jpg)

![alt text](https://user-images.githubusercontent.com/292486/33986724-20895b32-e0c7-11e7-8114-b203803867e4.jpg)

![alt text](https://user-images.githubusercontent.com/292486/33986722-204d395e-e0c7-11e7-8d1d-4f73cfcb577a.jpg)

Original authors:

Mihai Dragomir -<EMAIL_ADDRESS>/>
Mihai Gosa -<EMAIL_ADDRESS>or @gosamihai on twitter

Initially developed for the 'Door Kickers' games.

License: MIT

repository: thedmd/tiniest-analytics

repo_name: thedmd/tiniest-analytics


text:
# metalsmith-build-info

[![npm](https://img.shields.io/npm/v/metalsmith-build-info.svg)](https://www.npmjs.com/package/metalsmith-build-info)
[![Build Status](https://travis-ci.org/chkal/metalsmith-build-info.svg?branch=master)](https://travis-ci.org/chkal/metalsmith-build-info)

Metalsmith plugin to add various build infos to the metadata.

## Installation

```bash
npm install metalsmith-build-info --save-dev
```

## Usage

```js
var buildinfo = require("metalsmith-build-info");

Metalsmith(__dirname)
  /* ... */
  .use(buildinfo())
  /* ... */
```

The plugin will set the following metadata:

  * `buildinfo.date`: The date at which the site was generated.
  * `buildinfo.user`: The user who generated the site (i.e. `travis`).
  * `buildinfo.nodejs`: The version of Node.js used to generate the site (i.e. `v6.9.2`).
  * `buildinfo.arch`: String identifying the processor architecture that the Node.js
    is currently running on (i.e. `x64`).
  * `buildinfo.platform`: String  identifying the operating system platform on which the
    Node.js process is running on (i.e. `linux`).
  * `buildinfo.version`: The version of Metalsmith used to generate the site (i.e. `2.3.0`)

## License

MIT

repository: chkal/metalsmith-build-info

repo_name: chkal/metalsmith-build-info


text:
# Cluster Autoscaler Helm Chart

###### Instructions to upload Cluster Autoscaler Docker image to AWS ECR

Step1: Get the latest docker image from this link

        https://github.com/kubernetes/autoscaler

Step2: Download the docker image to your local Mac/Laptop. The image address listed on the [releases page](https://github.com/kubernetes/autoscaler/releases)
       Please note that image version should match with Kubernetes version.

        $ docker pull k8s.gcr.io/autoscaling/cluster-autoscaler:v1.19.1

Step3: Retrieve an authentication token and authenticate your Docker client to your registry. Use the AWS CLI:

        $ aws ecr get-login-password --region eu-west-1 | docker login --username AWS --password-stdin <account id>.dkr.ecr.eu-west-1.amazonaws.com

Step4: Create an ECR repo for Metrics Server if you don't have one

        $ aws ecr create-repository --repository-name k8s.gcr.io/autoscaling/cluster-autoscaler --image-scanning-configuration scanOnPush=true

Step5: After the build completes, tag your image so, you can push the image to this repository:

        $ docker tag k8s.gcr.io/autoscaling/cluster-autoscaler:v1.19.1 <account id>.dkr.ecr.eu-west-1.amazonaws.com/k8s.gcr.io/autoscaling/cluster-autoscaler:v1.19.1

Step6: Run the following command to push this image to your newly created AWS repository:

        $ docker push <account id>.dkr.ecr.eu-west-1.amazonaws.com/k8s.gcr.io/autoscaling/cluster-autoscaler:v1.19.1

### Instructions to download Helm Charts

#### Helm Chart

    hthttps://artifacthub.io/packages/helm/cluster-autoscaler/cluster-autoscaler

    https://github.com/kubernetes/autoscaler/tree/cluster-autoscaler-chart-9.9.2/cluster-autoscaler

#### Helm Repo Maintainers

    helm repo add autoscaler https://kubernetes.github.io/autoscaler

#### Helm Chart values.yaml

Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
SPDX-License-Identifier: MIT-0

Permission is hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the "Software"), to deal in the Software
without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so.

 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

## Requirements

No requirements.

## Providers

| Name | Version |
|------|---------|
|  [helm](#provider\_helm) | n/a |

## Modules

No modules.

## Resources

| Name | Type |
|------|------|
| [helm_release.autoscaler](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release) | resource |

## Inputs

| Name | Description | Type | Default | Required |
|------|-------------|------|---------|:--------:|
|  [eks\_cluster\_id](#input\_eks\_cluster\_id) | EKS\_Cluster\_ID | `any` | n/a | yes |
|  [image\_repo\_name](#input\_image\_repo\_name) | n/a | `string` | `"k8s.gcr.io/autoscaling/cluster-autoscaler"` | no |
|  [image\_repo\_url](#input\_image\_repo\_url) | n/a | `any` | n/a | yes |
|  [image\_tag](#input\_image\_tag) | n/a | `string` | `"v1.19.1"` | no |
|  [public\_docker\_repo](#input\_public\_docker\_repo) | n/a | `any` | n/a | yes |

## Outputs

No outputs.

```yaml
    ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
    # affinity -- Affinity for pod assignment
    affinity: {}

    autoDiscovery:
      # cloudProviders `aws`, `gce` and `magnum` are supported by auto-discovery at this time
      # AWS: Set tags as described in https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#auto-discovery-setup

      # autoDiscovery.clusterName -- Enable autodiscovery for `cloudProvider=aws`, for groups matching `autoDiscovery.tags`.
      # Enable autodiscovery for `cloudProvider=gce`, but no MIG tagging required.
      # Enable autodiscovery for `cloudProvider=magnum`, for groups matching `autoDiscovery.roles`.
      clusterName:  # cluster.local

      # autoDiscovery.tags -- ASG tags to match, run through `tpl`.
      tags:
      - k8s.io/cluster-autoscaler/enabled
      - k8s.io/cluster-autoscaler/{{ .Values.autoDiscovery.clusterName }}
      # - kubernetes.io/cluster/{{ .Values.autoDiscovery.clusterName }}

      # autoDiscovery.roles -- Magnum node group roles to match.
      roles:
      - worker

    # autoscalingGroups -- For AWS, Azure AKS or Magnum. At least one element is required if not using `autoDiscovery`. For example:
    # <pre>
    # - name: asg1<br />
    #   maxSize: 2<br />
    #   minSize: 1
    # </pre>
    autoscalingGroups: []
    # - name: asg1
    #   maxSize: 2
    #   minSize: 1
    # - name: asg2
    #   maxSize: 2
    #   minSize: 1

    # autoscalingGroupsnamePrefix -- For GCE. At least one element is required if not using `autoDiscovery`. For example:
    # <pre>
    # - name: ig01<br />
    #   maxSize: 10<br />
    #   minSize: 0
    # </pre>
    autoscalingGroupsnamePrefix: []
    # - name: ig01
    #   maxSize: 10
    #   minSize: 0
    # - name: ig02
    #   maxSize: 10
    #   minSize: 0

    # awsAccessKeyID -- AWS access key ID ([if AWS user keys used](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#using-aws-credentials))
    awsAccessKeyID: ""

    # awsRegion -- AWS region (required if `cloudProvider=aws`)
    awsRegion: us-east-1

    # awsSecretAccessKey -- AWS access secret key ([if AWS user keys used](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md#using-aws-credentials))
    awsSecretAccessKey: ""

    # azureClientID -- Service Principal ClientID with contributor permission to Cluster and Node ResourceGroup.
    # Required if `cloudProvider=azure`
    azureClientID: ""

    # azureClientSecret -- Service Principal ClientSecret with contributor permission to Cluster and Node ResourceGroup.
    # Required if `cloudProvider=azure`
    azureClientSecret: ""

    # azureResourceGroup -- Azure resource group that the cluster is located.
    # Required if `cloudProvider=azure`
    azureResourceGroup: ""

    # azureSubscriptionID -- Azure subscription where the resources are located.
    # Required if `cloudProvider=azure`
    azureSubscriptionID: ""

    # azureTenantID -- Azure tenant where the resources are located.
    # Required if `cloudProvider=azure`
    azureTenantID: ""

    # azureVMType -- Azure VM type.
    azureVMType: "AKS"

    # azureClusterName -- Azure AKS cluster name.
    # Required if `cloudProvider=azure`
    azureClusterName: ""

    # azureNodeResourceGroup -- Azure resource group where the cluster's nodes are located, typically set as `MC_<cluster-resource-group-name>_<cluster-name>_<location>`.
    # Required if `cloudProvider=azure`
    azureNodeResourceGroup: ""

    # azureUseManagedIdentityExtension -- Whether to use Azure's managed identity extension for credentials. If using MSI, ensure subscription ID and resource group are set.
    azureUseManagedIdentityExtension: false

    # magnumClusterName -- Cluster name or ID in Magnum.
    # Required if `cloudProvider=magnum` and not setting `autoDiscovery.clusterName`.
    magnumClusterName: ""

    # magnumCABundlePath -- Path to the host's CA bundle, from `ca-file` in the cloud-config file.
    magnumCABundlePath: "/etc/kubernetes/ca-bundle.crt"

    # cloudConfigPath -- Configuration file for cloud provider.
    cloudConfigPath: /etc/gce.conf

    # cloudProvider -- The cloud provider where the autoscaler runs.
    # Currently only `gce`, `aws`, `azure` and `magnum` are supported.
    # `aws` supported for AWS. `gce` for GCE. `azure` for Azure AKS.
    # `magnum` for OpenStack Magnum.
    cloudProvider: aws

    # containerSecurityContext -- [Security context for container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)
    containerSecurityContext: {}
      # capabilities:
      #   drop:
      #   - ALL

    # dnsPolicy -- Defaults to `ClusterFirst`. Valid values are:
    # `ClusterFirstWithHostNet`, `ClusterFirst`, `Default` or `None`.
    # If autoscaler does not depend on cluster DNS, recommended to set this to `Default`.
    dnsPolicy: ClusterFirst

    ## Priorities Expander
    # expanderPriorities -- The expanderPriorities is used if `extraArgs.expander` is set to `priority` and expanderPriorities is also set with the priorities.
    # If `extraArgs.expander` is set to `priority`, then expanderPriorities is used to define cluster-autoscaler-priority-expander priorities.
    # See: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/expander/priority/readme.md
    expanderPriorities: {}

    # extraArgs -- Additional container arguments.
    # Refer to https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca for the full list of cluster autoscaler
    # parameters and their default values.
    extraArgs:
      logtostderr: true
      stderrthreshold: info
      v: 4
      # write-status-configmap: true
      # status-config-map-name: cluster-autoscaler-status
      # leader-elect: true
      # skip-nodes-with-local-storage: true
      # expander: random
      # scale-down-enabled: true
      # balance-similar-node-groups: true
      # min-replica-count: 0
      # scale-down-utilization-threshold: 0.5
      # scale-down-non-empty-candidates-count: 30
      # max-node-provision-time: 15m0s
      # scan-interval: 10s
      # scale-down-delay-after-add: 10m
      # scale-down-delay-after-delete: 0s
      # scale-down-delay-after-failure: 3m
      # scale-down-unneeded-time: 10m
      # skip-nodes-with-system-pods: true

    # extraEnv -- Additional container environment variables.
    extraEnv: {}

    # extraEnvConfigMaps -- Additional container environment variables from ConfigMaps.
    extraEnvConfigMaps: {}

    # extraEnvSecrets -- Additional container environment variables from Secrets.
    extraEnvSecrets: {}

    # envFromConfigMap -- ConfigMap name to use as envFrom.
    envFromConfigMap: ""

    # envFromSecret -- Secret name to use as envFrom.
    envFromSecret: ""

    # extraVolumeSecrets -- Additional volumes to mount from Secrets.
    extraVolumeSecrets: {}
      # autoscaler-vol:
      #   mountPath: /data/autoscaler/
      # custom-vol:
      #   name: custom-secret
      #   mountPath: /data/custom/
      #   items:
      #     - key: subkey
      #       path: mypath

    # extraVolumes -- Additional volumes.
    extraVolumes: []
      # - name: ssl-certs
      #   hostPath:
      #     path: /etc/ssl/certs/ca-bundle.crt

    # extraVolumeMounts -- Additional volumes to mount.
    extraVolumeMounts: []
      # - name: ssl-certs
      #   mountPath: /etc/ssl/certs/ca-certificates.crt
      #   readOnly: true

    # fullnameOverride -- String to fully override `cluster-autoscaler.fullname` template.
    fullnameOverride: ""

    image:
      # image.repository -- Image repository
      repository: k8s.gcr.io/autoscaling/cluster-autoscaler
      # image.tag -- Image tag
      tag: v1.19.1
      # image.pullPolicy -- Image pull policy
      pullPolicy: IfNotPresent
      ## Optionally specify an array of imagePullSecrets.
      ## Secrets must be manually created in the namespace.
      ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
      ##
      # image.pullSecrets -- Image pull secrets
      pullSecrets: []
      # - myRegistrKeySecretName

    # kubeTargetVersionOverride -- Allow overriding the `.Capabilities.KubeVersion.GitVersion` check. Useful for `helm template` commands.
    kubeTargetVersionOverride: ""

    # nameOverride -- String to partially override `cluster-autoscaler.fullname` template (will maintain the release name)
    nameOverride: ""

    # nodeSelector -- Node labels for pod assignment. Ref: https://kubernetes.io/docs/user-guide/node-selection/.
    nodeSelector: {}

    # podAnnotations -- Annotations to add to each pod.
    podAnnotations: {}

    # podDisruptionBudget -- Pod disruption budget.
    podDisruptionBudget:
      maxUnavailable: 1
      # minAvailable: 2

    # podLabels -- Labels to add to each pod.
    podLabels: {}

    # additionalLabels -- Labels to add to each object of the chart.
    additionalLabels: {}

    # priorityClassName -- priorityClassName
    priorityClassName: ""

    rbac:
      # rbac.create -- If `true`, create and use RBAC resources.
      create: true
      # rbac.pspEnabled -- If `true`, creates and uses RBAC resources required in the cluster with [Pod Security Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) enabled.
      # Must be used with `rbac.create` set to `true`.
      pspEnabled: false
      serviceAccount:
        # rbac.serviceAccount.annotations -- Additional Service Account annotations.
        annotations: {}
        # rbac.serviceAccount.create -- If `true` and `rbac.create` is also true, a Service Account will be created.
        create: true
        # rbac.serviceAccount.name -- The name of the ServiceAccount to use. If not set and create is `true`, a name is generated using the fullname template.
        name: ""
        # rbac.serviceAccount.automountServiceAccountToken -- Automount API credentials for a Service Account.
        automountServiceAccountToken: true

    # replicaCount -- Desired number of pods
    replicaCount: 1

    # resources -- Pod resource requests and limits.
    resources: {}
      # limits:
      #   cpu: 100m
      #   memory: 300Mi
      # requests:
      #   cpu: 100m
      #   memory: 300Mi

    # securityContext -- [Security context for pod](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)
    securityContext: {}
      # runAsNonRoot: true
      # runAsUser: 1001
      # runAsGroup: 1001

    service:
      # service.annotations -- Annotations to add to service
      annotations: {}
      # service.labels -- Labels to add to service
      labels: {}
      # service.externalIPs -- List of IP addresses at which the service is available. Ref: https://kubernetes.io/docs/user-guide/services/#external-ips.
      externalIPs: []

      # service.loadBalancerIP -- IP address to assign to load balancer (if supported).
      loadBalancerIP: ""
      # service.loadBalancerSourceRanges -- List of IP CIDRs allowed access to load balancer (if supported).
      loadBalancerSourceRanges: []
      # service.servicePort -- Service port to expose.
      servicePort: 8085
      # service.portName -- Name for service port.
      portName: http
      # service.type -- Type of service to create.
      type: ClusterIP

    ## Are you using Prometheus Operator?
    serviceMonitor:
      # serviceMonitor.enabled -- If true, creates a Prometheus Operator ServiceMonitor.
      enabled: false
      # serviceMonitor.interval -- Interval that Prometheus scrapes Cluster Autoscaler metrics.
      interval: 10s
      # serviceMonitor.namespace -- Namespace which Prometheus is running in.
      namespace: monitoring
      ## [Prometheus Selector Label](https://github.com/helm/charts/tree/master/stable/prometheus-operator#prometheus-operator-1)
      ## [Kube Prometheus Selector Label](https://github.com/helm/charts/tree/master/stable/prometheus-operator#exporters)
      # serviceMonitor.selector -- Default to kube-prometheus install (CoreOS recommended), but should be set according to Prometheus install.
      selector:
        release: prometheus-operator
      # serviceMonitor.path -- The path to scrape for metrics; autoscaler exposes `/metrics` (this is standard)
      path: /metrics

    ## Custom PrometheusRule to be defined
    ## The value is evaluated as a template, so, for example, the value can depend on .Release or .Chart
    ## ref: https://github.com/coreos/prometheus-operator#customresourcedefinitions
    prometheusRule:
      # prometheusRule.enabled -- If true, creates a Prometheus Operator PrometheusRule.
      enabled: false
      # prometheusRule.additionalLabels -- Additional labels to be set in metadata.
      additionalLabels: {}
      # prometheusRule.namespace -- Namespace which Prometheus is running in.
      namespace: monitoring
      # prometheusRule.interval -- How often rules in the group are evaluated (falls back to `global.evaluation_interval` if not set).
      interval: null
      # prometheusRule.rules -- Rules spec template (see https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#rule).
      rules: []

    # tolerations -- List of node taints to tolerate (requires Kubernetes >= 1.6).
    tolerations: []

    # updateStrategy -- [Deployment update strategy](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy)
    updateStrategy: {}
      # rollingUpdate:
      #   maxSurge: 1
      #   maxUnavailable: 0
      # type: RollingUpdate

```