text:
# Infowall

## Overview
Infowall is a Dashboard application, which displays a team's status on a wall
mounted display. A team status is broken down into single items of information. Each item is
displayed on its own and the dashboard cycles through all of them, displaying a single item for
distinct period of time.

Infowall maintains different "Dashboards", each keeping an seperate list of items to cycle through.

### Dashboard Items

Dashboard Items represent a unit of information displayed on the dashboard. They could be retrieved
from various resources and are stored as JSON in a database. There are different View types requiring
a certain format of the stored JSON item.

Currently there are the following types of Views:

#### Single Value View
Displays single value in a huge colored box. A Threshold could be configured for the value,
if the current value is better than the threshold, the background is green, otherwise red. The relation,
which determines "being better" could be configured (either "less than" or "greater than"). Optionally
a unit (like "%") could be shown.

Furthermore the View shows the amount of difference to the last update of the item, colored green if it has improved,
red otherwise and the duration, how long item has the current value.

This View should be used for distinct quantifiable, trackable pieces of the team's status, like:

- Code Coverage
- Known Issues
- Code Violations

An item is stored as

{
    "value" : "10"
}

#### Table View
Displays a tabular listing of a descriptive texts with some value.

If the value is 0, the color is of the row is green, otherwise red.

An item is stored as

{
    "table":[
        {"title":"This is the first row","value":"0"},
        {"title":"This is the second row","value":"14"},
        {"title":"This is the third row","value":"0"},
        {"title":"This is the 4th row,"value":"2"}
]
}

## Configure Infowall
Infowall has a configuration directory on a local disc. The directory contains for instance the configuration
of the dasboard and its items or some executable scripts.

The directory has to be provided by a system property `-Dinfowall.config-root=TODIR`, otherwise
the application fails to start.

Infowall comes with an example directory at ROOT/example/config, have a look at it.

## Storing Items

Independent of a respective view, the JSON items have to be stored by Infowall. There are different
ways to provide the data to Infowall

### Using the REST API
You can push JSON documents to Infowall to the URL
`$APPLICATION_BASE_URL/app/item/$DASHBOARD_ID/$ITEM_NAME`

For instance, if the single item value is stored in the file value.json, you can use curl
to push it to Infowall. The example shows a coll to a Dashboard with the ID "first" and an item with the name "some-count" that runs on localhost:

curl -v --upload-file src/scrapbook/json/value.json -H "Content-Type:application/json" http://localhost:8080/app/item/first/some-count

### Using Groovy Jobs

You can store groovy scripts at $config-root/scripts/$dashboardId/$itemName.groovy, that
provide the JSON data for the defined item.
The triggering is configured in a the Dashboard configuration file.

The groovy script might perform arbitrary tasks, it simply has to return the JSON data to STDOUT.

For example, this script simply stores a random value as a single value item

import infowall.infrastructure.json.SimpleJSONBuilder
import org.slf4j.Logger
import org.slf4j.LoggerFactory

final Logger logger = LoggerFactory.getLogger(getClass())

def builder = new SimpleJSONBuilder()

def rndVal = new Random().nextInt(30);
logger.info("Decided, we have #${rndVal} bugs now.");

builder.result(value:rndVal);

See the example configuration for more examples of groovy scripts.

If you want to test a script, you can call

curl http://localhost:8080/app/exec/$dashboardId/$itemName

and you will retrieve the scripts output.

## Quickstart

1. Pull from github `git clone git@github.com:lgirndt/infowall.git`
1. Build `mvn clean install`

1. Setup the example HSQLDB TODO

MVN_REPO=~/.m2/repository
export CLASSPATH=$MVN_REPO/org/hsqldb/hsqldb/2.0.0/hsqldb-2.0.0.jar:$MVN_REPO/org/hsqldb/sqltool/2.0.0/sqltool-2.0.0.jar
DB_FILE=/tmp/infowall-prod.db

java org.hsqldb.cmdline.SqlTool --inlineRc=url=jdbc:hsqldb:file:$DB_FILE,user=sa,password= src/main/resources/sql/create-schema.sql

1. Insert some example data into infowall
1. run the server `gradle jettyRun -Pinfowall.config-root=DIR_TO_CONFIG`

## Known limitations
- Just looks great on a Webkit based browser like Google Chrome
- Just works with HSLQDB

repository: VijayEluri/infowall

repo_name: VijayEluri/infowall


text:
# System Integrity Management Platform (SIMP)

## IMPORTANT

This project is only approved for material that is completely releasable to the
public.

**Please do not upload material that has not been approved for public release.**

# **MIGRATION IN PROGRESS**

Please be aware that this project is in the process of transitioning legacy
code into GitHub. It may take quite some time before we have a fully functional
system available for immediate download.

We appreciate both your interest and your patience during this period

## Description

SIMP is a framework that aims to provide a reasonable combination of security
compliance and operational flexibility.

The ultimate goal of the project is to provide a complete management
environment focused on compliance with the various profiles in the
[SCAP Security Guide Project](https://fedorahosted.org/scap-security-guide/)
and industry best practice.

Though it is fully capable out of the box, the intent of SIMP is to be molded
to your target environment in such a way that deviations are easily identifiable
to both Operations Teams and Security Officers.

At this time, there are no commercial requirements for the use of SIMP outside
of the purchase of [Red Hat Enterprise Linux](http://www.redhat.com/en/technologies/linux-platforms/enterprise-linux)
licenses as applicable.

### Disclaimer

This Work is provided "as is." Any express or implied warranties, including but
not limited to, the implied warranties of merchantability and fitness for a
particular purpose are disclaimed. In no event shall the United States
Government be liable for any direct, indirect, incidental, special, exemplary
or consequential damages (including, but not limited to, procurement of
substitute goods or services, loss of use, data or profits, or business
interruption) however caused and on any theory of liability, whether in
contract, strict liability, or tort (including negligence or otherwise) arising
in any way out of the use of this Guidance, even if advised of the possibility
of such damage.

The User of this Work agrees to hold harmless and indemnify the United States
Government, its agents, and employees from every claim or liability (whether in
tort or in contract), including attorneys' fees, court costs, and expenses,
arising in direct consequence of Recipient's use of the item, including, but
not limited to, claims or liabilities made for injury to or death of personnel
of User or third parties, damage to or destruction of property of User or third
parties, and infringement or other violations of intellectual property or
technical data rights.

Nothing in this Work is intended to constitute an endorsement, explicit or
implied, by the US Government of any particular manufacturer's product or
service.

## Supported Operating Systems

The following Operating Systems are supported:

* [Red Hat Enterprise Linux](http://www.redhat.com/en/technologies/linux-platforms/enterprise-linux)
    * 6.6
    * 7.1
* [CentOS](https://www.centos.org/)
    * 6.6
    * 7.1-1503-01

## Technology components

SIMP uses Puppet to manage and maintain the configuration of the various
component systems.

Though there are many possible configurations, out of the box SIMP provides:

* Management
    * Puppet Server
    * PuppetDB
    * MCollective
* Authentication
    * OpenLDAP
* Kickstart/Update
    * YUM
    * DNS
    * DHCP
    * TFTP

## Copyrights
> All materials are copyright their respective owners unless otherwise noted.
>
> Per Section 105 of the Copyright Act of 1976, these works are not entitled to
> domestic copyright protection under US Federal law.
>
> The US Government retains the right to pursue copyright protections outside
> of the United States.
>
> The United States Government has unlimited rights in this software and all
> derivatives thereof, pursuant to the contracts under which it was developed and
> the License under which it falls.

Released under the [Apache License, Version 2](http://www.apache.org/licenses/LICENSE-2.0.html "Apache License v2").

## Community

### Google Groups

[simp](https://groups.google.com/forum/?fromgroups#!forum/simp) : A QA Board for the general community.

[simp-users](https://groups.google.com/forum/?fromgroups#!forum/simp-users) : A place for users of SIMP to ask questions, get help, and be part of the community.

[simp-dev](https://groups.google.com/forum/?fromgroups#!forum/simp-dev) : This list is for the development community interested in extending or contributing to the platform.

[simp-announce](https://groups.google.com/forum/?fromgroups#!forum/simp-announce) : Announcements for new versions and security events.

[simp-security](https://groups.google.com/forum/?fromgroups#!forum/simp-security) : A place to file security related issues that will only be seen by the SIMP team.

### Contributions

Please see [CONTRIBUTING](CONTRIBUTING.md) for information on how to contribute to this project.

repository: kendall-moore/SIMP

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: kendall-moore/SIMP


text:
PiFox
=====

Video of the game in action: https://www.youtube.com/watch?v=-5n9IxSQH1M

Developed as an extension to a first year group project at Imperial College London.

Bare Metal 3D rail shooter game

* 5800 lines of ARM assembly (ARMv6 + VFP1)
* Software rasterizer
* 3D objects
* 2D billboards
* Sound using DMA
* NES controller input
* Math & utility library
* GitHub: https://github.com/ICTeam28/PiFox
* Emulator: https://github.com/ICTeam28/PiEmu

Dependencies
-----

Using your favourite Linux package manager, install:

* arm-none-eabi-binutils
* cmake

Build
-----

The project uses CMake and requires an ARM assembler supporting
GNU as syntax.

    mkdir build
    cd build
    cmake ..
    make

Emulation
-----

PiEmu (https://github.com/ICTeam28/PiEmu) can run the game without sound. Assuming PiFox and PiEmu have been cloned in the same directory and both are built, PiEmu must be invoked with the following command inside PiFox's build directory:

    ../../PiEmu/build/piemu --graphics --quiet --memory=256M --addr=65536 --nes kernel.img

A qemu branch can be used to emulate the game at a higher framerate, but sound must be disabled. (https://github.com/Torlus/qemu/tree/rpi)

config.txt
----------

In order to be compatible with qemu, the kernel must be loaded at address 0x10000.

    disable_overscan=1
    disable_pvt=1
    force_turbo=1
    gpu_mem_256=160
    gpu_mem_512=316
    cma_lwm=16
    cma_hwm=32
    kernel_address=65536

Wiring the controller
---------------------

|    NES   |  Raspberry Pi  |
|:--------:|:--------------:|
| GND      | Ground         |
| VCC      | 3v3            |
| CUP      | GPIO 10        |
| OUT 0    | GPIO 11        |
| D1       | GPIO 4         |

![NES Pinout](https://raw.github.com/ICTeam28/PiFox/master/assets/nes-controller-pinout.png)

![Raspberry PI Pinout](https://raw.github.com/ICTeam28/PiFox/master/assets/raspbery-pi-pinout.png)

Authors
-------
Nandor Licker
- Email: nandor.licker13[at]imperial.ac.uk
- Github [@nandor](https://github.com/nandor)

Ilija Radosavovic
- Email: ilija.radosavovic13[at]imperial.ac.uk
- Github [@ir413](https://github.com/ir413)

David Avedissian
- Email: david.avedissian13[at]imperial.ac.uk
- Github [@davedissian](https://github.com/davedissian)
- Twitter [@davedissian](https://twitter.com/davedissian)

Nic Prettejohn
- Email: nicolas.prettejohn13[at]imperial.ac.uk
- Github [@nkp](https://github.com/nkp)
- Twitter [@thisisnkp](https://twitter.com/thisisnkp)

Special thanks
--------------

* https://github.com/dwelch67/raspberrypi
* https://github.com/PeterLemon/RaspberryPi

Special thanks to chpatrick (Patrick Chilton) for his advice.

repository: moneytech/PiFox

gha_language: Assembly

repo_name: moneytech/PiFox


text:
# [generator-example](https://github.com/Tencent/feflow/tree/master/examples/generator-example)

Feflow example template. based on React and Redux.

## Features

- ✔ Easy to create a project with react and redux
- ✔ Support multiple page development
- ✔ Built-in Rem, it's friendly to develop a mobile application
- ✔ Fast build speed and very small artifacts size

## Installation

You need to install [`feflow`](https://github.com/Tencent/feflow) first.

```sh
$ npm install @feflow/cli -g
```

Then install @feflow/generator-example

```sh
$ fef install @feflow/generator-example
```

## Usage

initialize project with interactive inquiry

```sh
$ fef init
```

### Params

- name. project name
- description. some description for your project
- version. project version

initialize project with selected generator

```sh
fef init --generator=@feflow/generator-example --config='{"version":"v0.1.0","description":"项目描述","name":"feflow-demo-v12"}'
```

Note: use arrow keys to select.

license: MIT

repository: heguichuan/feflow

gha_language: TypeScript

gha_license_id: NOASSERTION

repo_name: heguichuan/feflow


text:
Thanks for submitting a PR! :clap:

Please make sure you have selected the correct section and try to include all information for the table (if available).

Aim to use [consistent terminology](https://github.com/jpsingleton/ANCLAFS/issues/7) for status ( **Yes** / **No** / **WIP** / **?** / **{blank}** ) and a bare hyperlink style (no protocol).

Cheers :beers:

:shipit:

repository: jpsingleton/ANCLAFS

gha_language: C#

repo_name: jpsingleton/ANCLAFS


text:
# Media

In this plugin media represents a digital assets, for instance an image, a video or simple PDF file.

Currently, it supports following media types:

- Image (img HTML tag)
- Video (video HTML tag)
- File (a HTML tag)

## General usage

You can render media in three ways:

By rendering a media code template:

```twig
{{ bitbag_cms_render_media('media_code') }}
```

Rendering a media code directly:

```twig
{{ render(path('bitbag_sylius_cms_plugin_shop_media_render', {'code' : 'file', 'template' : '@App/Some/Template/_path.html.twig'})) }}
```

If you want to list media by specific section. Useful for displaying set of images. For example, using "gallery" section you can group set of images and display them as gallery, or even slider.

```twig
{{ render(path('bitbag_sylius_cms_plugin_shop_media_index_by_section_code', {'sectionCode' : 'gallery', 'template' : '@App/Some/Template/_path.html.twig'})) }}
```

### Media provider

You can add your own media provider by adding a service with a tag named `bitbag_sylius_cms_plugin.media_provider`:

```php
app.media_provider.audio:
    class: BitBag\SyliusCmsPlugin\MediaProvider\GenericProvider
    arguments:
        -<EMAIL_ADDRESS>        -<EMAIL_ADDRESS>        - "@@BitBagSyliusCmsPlugin/Shop/Media/Show/audio.html.twig"
        - "media/audio"
    tags:
        - { name: bitbag_sylius_cms_plugin.media_provider, type: audio, label: bitbag_sylius_cms_plugin.ui.audio_provider }
```

## Customization

If you don't know how to override templates yet,
read [Sylius template customization guide](http://docs.sylius.org/en/latest/customization/template.html).

You can create a template under `app/Resources/BitBagSyliusCmsPlugin/views/Shop/Media` location.
Available templates you can override can be found under [this location](../src/Resources/views/Shop/Media).

repository: bykclk/SyliusCmsPlugin

gha_license_id: MIT

repo_name: bykclk/SyliusCmsPlugin


text:
Cake Namespace
==============

The **cake** namespace contains tags providing framework specific functionality.

To use the **cake** namespace in a View include it in the *$namespaces* setting of the **Cml.Parser** component, for example:

```php
public $components = array(
	'Cml.Parser' => array(
		'namespaces' => array(
			'Cml.Cake'
		)
	)
);
```

Once the namespace is available you can access the tags it provides. To use a tag, specify the namespace, followed by the ":" symbol, and then the tag name, for example:

```html
<cake:out value="Hello World" />
```

The tags available from the **cake** namespace are the following:

* [append](Cake/Append.md) - Appends content to a View block.
* [assign](Cake/Assign.md) - Assigns content to a View block.
* [block](Cake/Block.md) - Outputs or captures a View block.
* [button](Cake/Button.md) - Creates a form button.
* [charset](Cake/Charset.md) - Defines the View's character set.
* [checkbox](Cake/Checkbox.md) - Creates a checkbox input.
* [crumbs](Cake/Crumbs.md) - Creates a bread crumbs list.
* [datetime](Cake/Datetime.md) - Create a date-time input.
* [day](Cake/Day.md) - Creates a days input.
* [debug](Cake/Debug.md) - Outputs the debug of a View variable.
* [download](Cake/Download.md) - Defines the View as a download.
* [element](Cake/Element.md) - Outputs or captures an element.
* [error](Cake/Error.md) - Creates an error message.
* [extend](Cake/Extend.md) - Extends a View.
* [fetch](Cake/Fetch.md) - Fetches a View block.
* [file](Cake/File.md) - Creates a file input.
* [form](Cake/Form.md) - Creates a *CakePHP* form.
* [get](Cake/Get.md) - Gets a View variable.
* [header](Cake/Header.md) - Gets a *HTTP* header.
* [helper](Cake/Helper.md) - Accesses a helper.
* [hidden](Cake/Hidden.md) - Creates a hidden input.
* [hour](Cake/Hour.md) - Creates an hours input.
* [image](Cake/Image.md) - Creates an image element.
* [input](Cake/Input.md) - Creates a form input.
* [inputs](Cake/Inputs.md) - Creates a collection of inputs.
* [is](Cake/Is.md) - Determines if the request *is* something.
* [label](Cake/Label.md) - Creates a form label.
* [layout](Cake/Layout.md) - Defines the View layout.
* [link](Cake/Link.md) - Creates an anchor element.
* [log](Cake/Log.md) - Writes to a log file.
* [meridian](Cake/Meridian.md) - Creates a meridian input.
* [minute](Cake/Minute.md) - Creates a minutes input.
* [month](Cake/Month.md) - Creates a months input.
* [out](Cake/Out.md) - Outputs a value, encoded by default.
* [post_button](Cake/PostButton.md) - Creates a post button.
* [post_link](Cake/PostLink.md) - Creates a post link.
* [prepend](Cake/Prepend.md) - Prepends content to a View block.
* [radio](Cake/Radio.md) - Creates a radio button input.
* [request_action](Cake/RequestAction.md) - Performs a request to an action.
* [secure](Cake/Secure.md) - Defines the form security.
* [select](Cake/Select.md) - Creates a select input.
* [set](Cake/Set.md) - Sets a View variable.
* [submit](Cake/Submit.md) - Creates a submit button.
* [textarea](Cake/Textarea.md) - Creates a textarea.
* [type](Cake/Type.md) - Defines the content type of the View.
* [year](Cake/Year.md) - Creates a years input.

repository: jameswatts/cake-markup-language

branch_name: refs/heads/beta

gha_language: PHP

repo_name: jameswatts/cake-markup-language


text:
# Github Buffer

A Chrome extension help you add some repositories interested to buffer.

## Install

## License
[MIT](hhttps://github.com/linrz/github-buffer/blob/master/LICENSE) © [LINRZ](https://github.com/linrz)

repository: linrz/github-buffer

repo_name: linrz/github-buffer


text:
# Hosting a security review

**Audience**: VSP security reviewers

**Context**: details and process for hosting a security review

## Philosophy

The goal of the security review is to ask, "what ways can this system break? How can it be misused?" By nature, a security review defies a concrete checklist.

The goal of this list of questions is to provide starting points for relevant discussions, and to ensure that "obvious" considerations aren't forgotten or missed.

## Questions

This list of questions is _not_ intended to be comprehensive. It _is_ intended to be comprehensively covered in a review.

### Privacy

#### Logs

* Are there any new logging statements? \(FE or BE\). This includes data sent to Sentry, Cloudwatch, Google Analytics, ...?
* What kinds of information are logged in the new logging? Is there anything that uniquely identifies a user \(Personally Identifiable Information\)?

#### User tracking / identity

* Are there any new cookies?
* Are there any new uses of existing cookies?

### Security

* How are systems authenticating with one another?
* Is anyone bypassing any obvious built-in protections? \(CSRF protection in form submissions, auto-escaping in FE template rendering systems, use of `innerHTML`\)

#### Frontend

* Is anyone using `innerHTML`, or otherwise bypassing template rendering system protections like auto-escaping?
* Are there any new cookies?
* Are there any new uses of existing cookies?

#### Backend

* Are there any new REST endpoints exposed by `vets-api`, or new behavior change on existing endpoints?
  * What new interactions are allowed?
  * Is there any new risky data being sent to `vets-api` \(XML, file uploads, etc.\)?
  * How could this endpoint be misused?
* Are there new integrations with VA backends?
  * What data are we sending to this backend?
  * How could this backend integration be misused?

### Infrastructure readiness

#### Traffic

* How much new traffic are you expecting to send to `vets-api`?
  * Consider both average \(typical weekday traffic\) and burst \(e.g. an email blast to Veterans\)

#### Rollout

* What's your rollout plan? Specifically:
  * What % of users are you rolling out to at each phase?
  * What metrics are you looking at before deciding to continue rollout?

#### Incident response

* Is there a playbook for investigating and handling likely failure modes?
* Are there new integrations with VA backends?
  * What is this backend's latency/availability profile?
  * Do we have points of contact for each new backend, in case of outages or security incidents? \(TODO: link to where these should be stored/documented\)

#### SLO definition

_Note: tentative while SLO infrastructure work is underway_

* Are there any new REST endpoints exposed on `vets-api`?
  * Do all new endpoints exposed on `vets-api` have availability + latency expectations?
  * Are those expectations configured in our SLO monitoring system? \(TODO\)


text:
# Cosmopolitan Tastes

## Description

Create, Find, Share and Vote on your best recipes with the world!

## Table of Contents

  - [Contribution](#contribution)
  - [Screenshot](#screenshot)
  - [License](#license)
  - [Badges](#badges)
  - [GitHub](#github)
  - [Heroku](#heroku)

## Screenshot

![](public/assets/screenshot.png)

## Contribution

Made with ❤ by Scot Itakura, Theresa Rutledge, Ruohan Wang

## License

MIT

## Badges

![badmath](https://img.shields.io/conda/l/conda-forge/setuptools?color=Blue&label=License&logo=ISC&logoColor=blue&style=plastic)

## GitHub

My GitHub link: ( https://github.com/TheresaRutledge/CosmopolitanTastes)

## Heroku

Heroku link: ( http://cosmopolitan-tastes.herokuapp.com)

repository: TheresaRutledge/CosmopolitanTastes

gha_language: JavaScript

repo_name: TheresaRutledge/CosmopolitanTastes


text:
<link rel="stylesheet" href="../../../css/enlargeImage.css" />

# Nominative users

## What are the nominative users?

In the Saas,unlike to the on premise, the licensing mode is based on the number of usage of the product. The usage is most of time registered as a number of users over a period of time, but it can also be based on the storage used, the profile of the users, ...

The nominative user is a user dedicated to a product or an aggregation of product

## Access

You can access to "Nominative users" by clicking here :

![select APM](../../img/nominativeMana/access.jpg){: .zoom}

This page will be displayed:

![select APM](../../img/nominativeMana/access2.jpg){: .zoom}

Then click on "Nominative Users", to access to nominative users section

## Possibilities

From there, you have many possibilities :

- Add a new nominative user ([here](#add-a-new-nominative-user))
- Edit an existing nominative user ([here](#edit-an-existing-nominative-user))
- Delete an existing nominative user ([here](#delete-an-existing-nominative-user))
- Get a report of nominative users ([here](#get-a-report-of-nominative-users))

## Add a new nominative user

First make sure that you are an admin and in nominative users section :

![select APM](../../img/nominativeMana/add.jpg){: .zoom}

To add a new nominative user, you have to click on " Add Nominative Users":

![select APM](../../img/nominativeMana/add2.jpg){: .zoom}

This page will be displayed :

![select APM](../../img/nominativeMana/add3.jpg){: .zoom}

You will have to fill the different fields as on the page below:

![select APM](../../img/nominativeMana/add4.jpg){: .zoom}

Once done, click on "Add" to add the nominative user.

Notice that you can add nominative users through a CSV file. Just click on "Upload file" and add the file containing the different as displayed below:

![select APM](../../img/nominativeMana/upload.jpg){: .zoom}

You will have to provide :
The first name, email, username, profile and the activation date.

You can download the tamplate [Here](../../excel/nominativeTemplate.csv)

Notice that this example is for a single product, but it can be used for aggregation by using "Aggregation" section.

## Edit an existing nominative user

To edit an existing nominative user, click on the pencil icon located on the same line of the nominative user to edit

![select APM](../../img/nominativeMana/edit.jpg){: .zoom}

A page containing the nominative user information will be displayed

![select APM](../../img/nominativeMana/edit2.jpg){: .zoom}

You can edit only the "Product Editor", the "Username", the "First name" and the "Activation date".

Once done, click on "Update" to save your changes.

Notice that this action is applicable for aggregations.

## Delete an existing nominative user

To delete an exiting nominative user, click on the trash icon located on the same line of the nominative user to delete.

![select APM](../../img/nominativeMana/del.jpg){: .zoom}

This pop up will be displayed:

![select APM](../../img/nominativeMana/del2.jpg){: .zoom}

Click on "Yes" to confirm your deletion.

Notice that this action is applicable for aggregations.

## Get a report of nominative users

To get a repport of nominative users, click on "Export"

![select APM](../../img/nominativeMana/export.jpg){: .zoom}

A file will be downloaded.

Notice that this action is applicable for aggregations.

repository: Orange-OpenSource/optisam-ui

repo_name: Orange-OpenSource/optisam-ui


text:
---
layout: post
title: How To Install and Configure Codiad in Your Own Server
date: 2015-02-14 23:17:56.000000000 -05:00
---
Codiad IDE in its own definition:

>"...is a web-based IDE framework with a small footprint and minimal requirements."

Having this in mind is expected that configure Codiad in your server should be really easy and it is.
As a solution for coding in a Chromebook, Codiad is almost perfect. For what I want to use, I found two major issues as I will describe along with the text.

######Installation
I followed [this](https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-codiad-a-web-based-ide-on-an-ubuntu-vps) tutorial and it works really well. Besides the installation It shows how to configure htaccess for a better authentication. Although Codiad asks for login too what is a little bit annoying. I dont figure out how to disable this second login but probably there is a way to do this.

######Plugins

Codiad has a plugin system that works simply copying (or cloning) plugins to its plugin folder. And they have a selection of plugins in their [market](http://market.codiad.com/).

So all you need to do is:

    $ cd ~/Codiad/plugins/
    $ git clone https://github.com/Fluidbyte/Codiad-Terminal.git

and you can use a terminal emulator inside your IDE.
To use the terminal you need to put a password ("terminal" by default). The main drawbacks is that it is a really simple terminal (e.g. there is no autocompletion).

I installed the git plugin too:

	git clone https://github.com/Andr3as/Codiad-CodeGit.git

but I didn't try it a lot (I had some issues with my github ssh accounts that time).

It is a really nice option for an web-based IDE. The plugin system is really easy but I think they need to be more useful.

At this time I moved for Cloud9. It is a more powerful IDE and it has advanced terminal and plugin options too.
I made an installation tutorial [here](http://blog.viniciusprado.org/how-to-install-and-configure-cloud9-in-your-own-server).

extension: markdown

gha_language: HTML


text:
# Note Taker

# [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

# Table of Contents
- [Description](#description)
- [Installation](#installation)
- [Usage](#usage)
- [License](#license)
- [Contribution](#contribution)
- [Technologies](#technologies)
- [Questions](#questions)

 ## Description
 An application that can be used to write, save, and delete notes. This application will use an express backend and save and retrieve note data from a JSON file.

 <img src = "https://github.com/Glove1911/Note-Taker/blob/main/public/assets/js/CA3E535C-6442-44ED-BBC8-5EB1B9A54D13_1_105_c.jpeg?raw=true">

 The deployed application can be found [here.](https://warm-falls-75207.herokuapp.com/)

## Installation
To install dependencies run the following command:
```
	npm init npm install
```

## Usage
Run the following command at the CLI:
```
node server.js
```

## License
MIT

## Contribution

## Technologies

## Questions
(https://github.com/Glove1911)

Please contact me at [harrison_glover<EMAIL_ADDRESS>with any questions.

branch_name: refs/heads/main


text:
# Basic Arch Linux ARM Docker images [![Build Status](https://travis-ci.org/agners/archlinuxarm-docker.svg?branch=master)](https://travis-ci.org/agners/archlinuxarm-docker)

Docker images for Arch Linux ARM on AArch32 (ARMv7-A) and AArch64 (ARMv8-A). Built using native pacman and Docker multi-stage builds. Builds weekly by Travis CI on publicly visible infrastructure using Qemu emulation.

 Use the convenient `docker run`:

    docker run --rm -ti agners/archlinuxarm

Instead of using the multi-arch container above, you can also get the architecture specific image directly:

    docker run --rm -ti agners/archlinuxarm-arm32v7

## Tags

|  Tag   |   Update   |  Type   |                                 Description                                        |
|:------:|:----------:|:-------:|:-----------------------------------------------------------------------------------|
| latest | **weekly** | minimal | minimal Arch Linux ARM with pacman support                                        |

### Layer structure

The image is generated from a freshly built pacman rootfs. Pacman has configured
to delete man pages and clean the package cache after installation to keep
images small.

## Issues and improvements

If you want to contribute, get to the [issues-section of this repository](https://github.com/agners/archlinuxarm-docker/issues).

## Common hurdles

### Setting the timezone

Simply add the `TZ` environment-variable and define it with a valid timezone-value.

```
docker run -e TZ=Europe/Berlin agners/archlinuxarm
```

## Building it yourself

### Prerequisites

- Docker with experimental mode on (required for squash)
- sudo or root is neccessary to setup binfmt for Qemu user mode emulation

### Building

- Prepare binfmt use with Qemu user mode using `sudo ./prepare-qemu`
- Run `BUILD_ARCH=<arch> ./build` to build
  - Use `BUILD_ARCH=arm32v7` for ARMv7 Aarch32
  - Use `BUILD_ARCH=arm64v8` for ARMv8 Aarch64

If you want to push the images, run `./push`. *But be aware you have no push access to the repos! Edit the scripts to push to custom Docker Hub locations!*

### Building from scratch

Since the image depends on itself, the question which arise is how this all
started. The initial containers have been created using the tarballs provided by
the Arch Linux ARM project. I used the following steps to bootstrap for each
architecture:

```
sudo tar xvzf ArchLinuxARM-armv7-latest.tar.gz -C tmp-arch
sudo tar cf ArchLinuxARM-armv7-latest.tar -C tmp-arch/ .
docker import ArchLinuxARM-armv7-latest.tar agners/armv7-archlinux:latest
```

## Credits

Ideas have been taken from already existing Docker files for Arch Linux.
However, this repository takes a slightly different approach to create images.

- https://github.com/archlinux/archlinux-docker
  - Focus on Arch Linux for x86
  - Uses docker run in priviledged mode to build images
- https://github.com/lopsided98/archlinux
  - Uses prebuilt tarballs which contain packages not required in containers

repository: lovehifi/archlinuxarm-docker

repo_name: lovehifi/archlinuxarm-docker


text:
---
layout: post
title: The Density Overlap Regions Indicator (DORI) with VASP
date: 2022-11-30
categories: Post
description: A short tutorial on how to calculate the Density Overlap Regions Indicator using VASP's CHGCAR file.
tags: DFT
---

<!-- https://www.c2x.org.uk/visual/VESTA_pot.html -->
<!-- https://chemtools.org/sci_doc_nci.html -->
<!-- https://rh8liuqy.github.io/Finite_Difference.html -->

The Density Overlap Regions Indicator (DORI) provides a compromise between the [:link: Electron Localization Function](../../../2022/01/17/ELF.html)) which highlights the strong electron locatlization, indicating the existance of covalent bonds or lone pairs and the [:link: Non-Covalent Interaction Index](../../../2022/11/28/NCI.html)) which identifies the weak electron localization (and delocalization) of electrons like van der Waals interactions and steric repulsion.

<!--and week localization (which is usually visualized using the [:link: Non-Covalent Interaction Index](../../../2022/11/28/NCI.html)) -->
<!--The Density Overlap Regions Indicator (DORI) proivdes a compromise to find interactions between strong localization (which is usually visualized using the [:link: Electron Localization Function](../../../2022/01/17/ELF.html)) and week localization (which is usually visualized using the [:link: Non-Covalent Interaction Index](../../../2022/11/28/NCI.html)).-->

To define DORI ([:link: 10.1021/ct500490b](https://pubs.acs.org/doi/10.1021/ct500490b)) we first need to define a dimensionless quantity $\theta$:

$$
\theta(\mathbf{r})=\frac{\left[\nabla \mathbf{k}^2(\mathbf{r})\right]^2}{\left[\mathbf{k}^2(\mathbf{r})\right]^3}=\frac{\left \{\nabla\left[\frac{\nabla \rho(\mathbf{r})}{\rho(\mathbf{r})}\right]^2\right \}^2}{\left[\frac{\nabla \rho(\mathbf{r})}{\rho(\mathbf{r})}\right]^6},
$$

where $\mathbf{k}(\mathbf{r})$ is the local momentum vector, defined as:

$$
\mathbf{k} (\mathbf{r}) = \frac{\nabla \rho(\mathbf{r})}{\rho (\mathbf{r})}.
$$

In covalent bonding regions, the density is characterized by the small density gradients, especially at the bond critial points where $\nabla \rho(\mathbf{r}) = 0$. In this case, both the nominator and the denominator of $\theta$ are zero, but since the denominator goes to zero faster, $\theta$ will go to $+\infty$.

To tame this divergent behavior, the DORI is defined as:

$$
\mathrm{DORI} = \frac{\theta}{1+\theta},
$$

so that its a scalar field with a value between $0$ and $1$ where $1$ indicates the potential existance of a chemical bond or interactions.

---

Using VASP's `CHGCAR` file, we can use our previous central finite difference method to calculate gradient of the density. As a result, for Benzene, the following DORI plot was obtained.

![]({{site.baseurl}}/assets/img/post_img/2022-11-30-img1.png){:height="50%" width="50%" .center}

We see that our finite difference result looks almost identical to the result obtained with QE's `pp.x`. Note that these results have subtle differences near the core regions comparing to the RDG calculated using all-electron code like ADF (see Fig. 3(a) of [:link: 10.1021/ct500490b](https://pubs.acs.org/doi/10.1021/ct500490b)). This is probably caused by use of pseudopotentials.

Similar to the [:link: Non-Covalent Interaction Index](../../../2022/11/28/NCI.html), DORI can also be color-coded using $\mathrm{sign}(\lambda_2)\rho(\vec r)$ where $\lambda_2$ is the middel eigenvalue of the Hessian of the charge density. For Benzene:

![]({{site.baseurl}}/assets/img/post_img/2022-11-30-img2.png){:height="30%" width="30%" .center}

We can clearly see that in the middle of the Benzene molecule, there is a high value DORI pocket but the intraction corresponding to that pocket repels electrons (red color - positive eigenvalue of the Hessian). This result suggests that at the center of the Benzene molecule exists a strong steric repulsion.
The blue regions near the molecule, on the other hand, corresponds to the strong electron attraction caused by covalent bonding.
<!--At the bonding regions, we have attractive interactions due to covalent bonding.-->

---

As described at the beginning, DORI can also be used to visualize the weak non-covalent interactions. To demonstrate this, I've put two Benzene molecules together. Their calculated DORI plot is:

![]({{site.baseurl}}/assets/img/post_img/2022-11-30-img3.png){:height="30%" width="30%" .center}

This plot is almost identical to Fig. 4(e) in [:link: 10.1021/ct500490b](https://pubs.acs.org/doi/10.1021/ct500490b). Apart from the regions near the molecules which are similar to our previous results, between two Benzene molecule, there's another region with weak interactions (indicated by the color green). This should be attributed to the weak van der Waals interactions between Benzene molecules.

---

The code to generate these results can be found: [:file_folder: DORI.tar.gz]({{site.baseurl}}/assets/other/2022-11-30-DORI.tar.gz).

To obtain these results:
1. run VASP using the files from `vasp_input.tar.gz`
2. run `DORI.py` and analyze `ELFCAR_DORI.vasp`.
4. run `hessian.py` and plot the color RDG using `hess_color.vasp` and `ELFCAR_DORI.vasp`.


text:
Estatio: an open source estate management system.
=================================================

Estatio is modern and flexible property management software. It offers real estate professionals and service providers the power and flexibility to manage their business in a superior, flexible and cost-effective manner.

## Screenshots ##

The following screenshots (taken 13 december 2014) correspond to the business logic in Estatio's [domain object model](
https://github.com/estatio/estatio/tree/master/dom/src/main/java/org/estatio/dom).

## Building Estatio ##

### Prereqs ###

Estatio runs on Java and is built with [Maven](http://maven.apache.org).  The source code is managed using [git](https://help.github.com/articles/set-up-git), and is held on [github](http://github.com).

If you don't already have them installed, install Java (JDK 6 or later), Maven (3.0.4 or later), and git.

### Download and build Apache Isis ###

Estatio currently uses the snapshot version of [Apache Isis](http://isis.apache.org), and so Isis must be built from source.

Estatio also maintains its [own copy of the Isis codebase](http://github.com/estatio/isis), and so this is what you should download.  (Normally there is very little, if any, difference between the Estatio's copy of Isis and the [official Isis codebase](http://github.com/apache/isis))

Download using git:

    mkdir -p github/estatio
    cd github/estatio
    git clone https://github.com/estatio/isis.git
    cd isis

and build using maven:

    mvn clean install

The clone is approx 83Mb, and takes approx 10 minutes to build.

### Download and build Estatio ###

Estatio itself is also built using maven.

Download using git:

    cd ..
    git clone https://github.com/estatio/estatio.git
    cd estatio

and build using maven:

    mvn clean install -Pjetty-console

The clone is approx 3Mb, and takes approximately 1 minute to build.

## Configure Estatio (JDBC URL) ##

Before Estatio can be run, you must configure its JDBC URL; typically this lives in the `webapp/src/main/webapp/WEB-INF/persistor.properties` properties file.

You can do this most easily by copying a set of property entries from `webapp/src/main/webapp/WEB-INF/persistor-SAMPLE.properties`.

For example, to run against an in-memory HSQLDB, the `persistor.properties` file should consist of:

    isis.persistor.datanucleus.impl.javax.jdo.option.ConnectionDriverName=org.hsqldb.jdbcDriver
    isis.persistor.datanucleus.impl.javax.jdo.option.ConnectionURL=jdbc:hsqldb:mem:test
    isis.persistor.datanucleus.impl.javax.jdo.option.ConnectionUserName=sa
    isis.persistor.datanucleus.impl.javax.jdo.option.ConnectionPassword=

The JDBC driver for HSQLDB is on the classpath.  If you want to connect to some other database, be sure to update the `pom.xml` to add the driver as a `<dependency>`.

## Run Estatio ##

You can run Estatio either using the standalone (self-hosting) version of the WAR, or using `mvn jetty plugin`.

### Running as a self-hosting JAR

Run using:

    java -jar webapp/target/estatio-webapp-0.0.1-SNAPSHOT-jetty-console.war

and press the 'start button'.

Then browse to:

    http://localhost:8080/wicket/

### Running through Maven

Run using:

    cd webapp
    mvn jetty:run

Then browse to:

    http://localhost:8080/estatio-webapp/wicket/

## Use Estatio ##

* Login using estatio-admin/pass or estatio-user/pass.

* Install some demo fixtures:

    Administration > Install Demo Fixtures

* Run a script to setup invoices:

    Administration > Run script: GenerateTopModelInvoice

* Take a look around :-)

If you encounter any bugs, do [let us know](https://github.com/estatio/estatio/blob/master/pom.xml#L52).

## Implementation

This product uses [Apache Isis](http://isis.apache.org), a software framework
developed at [The Apache Software Foundation](http://www.apache.org/).

## Support

You are free to adapt or extend Estatio to your needs.  If you would like assistance in doing so, go to [www.estatio.org](http://www.estatio.org).

You can find plenty of help on using Apache Isis at the [Isis mailing lists](http://isis.apache.org/support.html).  There is also extensive [online documentation](http://isis.apache.org/documentation.html).

## How to generate the AsciiDoc pages

Just run:

    cd adocs/documentation
    mvn site

The `.html` will be generated in `target/site`.  It should be possible to load the HTML straight from the directory.  Alternatively, load from a webserver, eg:

    python -m SimpleHTTPServer

and browse to http://localhost:8000.

The mvn script also generates docbook XML and PDF, but there are some caveats:

* the PDF currently does not include images at all.

* Using [asciidoctor-fopub](https://github.com/asciidoctor/asciidoctor-fopub) the XML can be converted to PDF; however there are currently some issues with images being scaled correctly.

## Thanks

Thanks to

*  [Atlassian](https://www.atlassian.com) for providing an open source [Clover](https://www.atlassian.com/software/clover/overview/) license
* [Headway Software](http://structure101.com/contact/) for providing an open source [Structure 101](http://structure101.com/) license

## Legal Stuff ##

Copyright 2012-2015 [Eurocommercial Properties NV](http://www.eurocommercialproperties.com)

Licensed under [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0)

repository: shijh/estatio

repo_name: shijh/estatio


text:
# diseq 0.1.1

* Prepared CRAN submission. Small adjustments to README style. Updated CRAN comments.

# diseq <IP_ADDRESS>04

* Adjusted file names so that they are consistent with the  API changes.

# diseq <IP_ADDRESS>03

* Fixed `M1mac` issues. Adjusted README to API changes. Replaced `href` with `doi` whenever relevant.

# diseq <IP_ADDRESS>02

* Added macro checks for C++20 execution policies features in C++ sources. Removed calls to `std::ragnes::iota_view` and `std::reduce` to ensure C++11 compatibility.

# diseq <IP_ADDRESS>01

* Adjusted vignettes to API changes.

# diseq <IP_ADDRESS>00

* Introduced the option maximizing the equilibrium model likelihood using `GSL` through `Rcpp`. Added linting and formatting configuration files for R and C++ code. Cleaned C++ code. Reorganized R back-end classes.

# diseq <IP_ADDRESS>04

* Improved README file style.

# diseq <IP_ADDRESS>03

* Corrected style attributes of README file.

# diseq <IP_ADDRESS>02

* Corrected calculation of clustered standard errors by accounting for the number of used classes.

# diseq <IP_ADDRESS>01

* Changes to adjust for depreciating functionality of `dplyr` (as of 0.7.0)

# diseq 0.0.14

* Added option and documentation for estimating clustered standards errors.

# diseq <IP_ADDRESS>02

* Added documentation for the function that return the scores.

# diseq <IP_ADDRESS>01

* Added option for estimating heteroscedasticity-consistent (Huber-White) standard errors.
* Added functionality for extracting the score matrices of the estimated models.

# diseq <IP_ADDRESS>00

* Corrected documentation typos.

# diseq 0.0.13

* Corrections of non-canonical web-links in README. Adjustments before CRAN submission.

# diseq <IP_ADDRESS>02

* Added sections `A quick model tour`, `Alternative packages`, and `Planned extensions` in README.

# diseq <IP_ADDRESS>01

* Added `noLD` in word exceptions list.

# diseq 0.0.12

* Fixed `noLD` issues.

# diseq <IP_ADDRESS>02

* Renamed assessment vignette.

# diseq <IP_ADDRESS>01

* Enabled BFGS-based estimation with numerical gradient. Added CRAN installation instructions in README.

# diseq <IP_ADDRESS>00

* Corrected punctuation errors in documentation.

# diseq 0.0.11

* Removed "get_correlation_variable" from exported functions. Improved the documentation of "minus_log_likelihood". Reintroduced references in description.

# diseq 0.0.10

* Removed references from description to avoid CRAN notes.

# diseq 0.0.9

* Ignoring README.html from build. Removed links from description. Improved documentation examples.

# diseq 0.0.8

* Added examples to constructors, estimation, aggregation, and marginal effect functions.

# diseq <IP_ADDRESS>02

* Skipping directional and stochastic adjustment tests on CRAN to reduce build time.

# diseq <IP_ADDRESS>01

* Quoted all package names in DESCRIPTION. To reduce build time: 1. Removed direction model estimation from equilibrium assessment vignette, 2. Decreased estimation accuracy of basic usage vignette to six digits.

# diseq 0.0.7

* Fixed order of arguments in web-link of estimation documentation. Improved simulation documentation.

# diseq 0.0.6

* Corrected documentation typos. Fixed web-links.

# diseq <IP_ADDRESS>09

* Improved documentation.

# diseq <IP_ADDRESS>08

* Removed unused parameter from the constructor of the equilibrium two stage least square model.

# diseq <IP_ADDRESS>07

* Removed dependence on `pastecs` package.

# diseq <IP_ADDRESS>06

* Reformatted code using the `styler` package. Removed the `lintr` based test.

# diseq <IP_ADDRESS>05

* Adjustments to address breaking changes of the `tibble` package.

# diseq <IP_ADDRESS>04

* Added a vignette with an equilibrium assessment example.

# diseq <IP_ADDRESS>03

* Added model-specific simulation functions.

# diseq <IP_ADDRESS>02

* Refactored simulation code.

# diseq <IP_ADDRESS>01

* Added simulation generating processes for all supported models.

# diseq <IP_ADDRESS>13

* Separated auto-generated derivative code to dedicated derivative files.

# diseq <IP_ADDRESS>12

* Allowed estimation of full information maximum likelihood, equilibrium, deterministic adjustment, and stochastic adjustment with one-sided inclusion of prices.
* Modified model titles' generation.

# diseq <IP_ADDRESS>11

* Added basic_usage vignette.
* Added simulation function at model_base level.
* Added a `NEWS.md` file to track changes to the package.


text:
# tweet-simulator
A twitter bot that uses markov chains to simulate tweets from any user.

Checkout [@sim\_tweet](https://www.twitter.com/sim_tweet) for the bot on twitter

Anybody is free to make a pull request to add functionality. If you have an idea but don't want to implement it feel free to open an issue too. Check CONTRIBUTING.md for more details.

## Implementation

The bot uses [Tweepy](https://www.tweepy.org/) to access the Twitter API.

It looks for mentions on twitter. Valid tweets it will respond to are where the tweet includes @sim\_tweet and @username (where @username is the username of the user to be mimicked).

The bot gets the users last 200 tweets and builds a markov chain of each space separated word appearing in their previous tweets (words except @mentions and t.co links). The bot then uses that markov chain to create a new tweet that looks like something the user might write.

You can email me at [tom<EMAIL_ADDRESS>if you have any questions about the implemenation or contributing, but I'll probably respond sooner if you create an issue.

repository: bowdens/tweet-simulator

gha_language: Python

repo_name: bowdens/tweet-simulator


text:
# Chapter 10. Developing Segmentation Algorithms for Text Recognition

## Requirements

- OpenCV 4.0
- Tesseract

## Steps to build

To compile on Linux, mac or Windows using Mingw

```
mkdir build
cd build
cmake ..
make
```

## Executables

The following applications are generated.

```
./segment
./segmentOcr
./segmentOcrHigh
```


text:
---
layout: post
title: "Intro to JavaScript Workshop"
date: 2018-05-30 09:37:00
author: Admin
excerpt_separator: <!--more-->
categories:
- blog
- GIS
- Events
---
### Introduction to JavaScript Workshop

![js code](/assets/img/blog/code.jpg)

**Date:**  Saturday June 30

**Time:**  1pm - 5pm

**Location:**  Freese & Nichols

**Address:**  10431 Morado Circle, Suite 300, Austin, TX 78759

<!--more-->

CenTex GIS and ATX GIS Day proudly present an Introductory JavaScript workshop! Have you ever wanted to know how to develop a web map using JavaScript? Here's the perfect workshop for novice/beginner participants with little or no programming experience. The class will cover basic programming concepts and syntax as we make a simple web map using the ESRI JavaScript API.

It will include two 2 hour lectures broken down into small sessions/exercises and a walk through of serving your application at the end of the workshop. The class will be taught by local GIS developer professional, Aubrey Drescher.

Students will be required to bring their own laptop with the following software downloaded and installed prior to the workshop:
- Adobe Brackets (http://brackets.io) open-source text editor
- Google Chrome (https://google.com/chrome) web browser

**Suggested donation is $20 to help raise money for ATX GIS Day.**

![atx gis day](/assets/img/blog/atx-gis-day.jpg)

**RSVP here:**<br>
[https://www.eventbrite.com/e/intro-to-java-script-workshop-tickets-46543186925](https://www.eventbrite.com/e/intro-to-java-script-workshop-tickets-46543186925)

gha_language: CSS


text:
# eldap2

Forked from eldap v1.2.2 that contained in **Erlang/OTP 20**

## What different with eldap

- Compiled with erlang.mk
- Always set gen_tcp/ssl to `{active, once}`

The connection process will be crash, when Socket has closed

## Usage

ref: [Erlang/OTP 20 Doc](http://erlang.org/doc/man/eldap.html)


text:
# Avenues+Shallows

This repo shows how to use [Shallows](https://github.com/dreymonde/Shallows) to cache the values processed by [Avenues](https://github.com/dreymonde/Avenues) processors. **Avenues** does not cache retrieved data on disk, and this repo shows you how to implement this kind of functionality using **Shallows** with ease.

## How to use

```swift
let storage: Storage<URL, UIImage> = NSCacheStorage<NSURL, UIImage>().mapKey({ $0 as NSURL })
let diskCache = FileSystemCache.inDirectory(.cachesDirectory, appending: "shallows-images-cache")
let urlKeyedCache: Cache<URL, Data> = diskCache
    .makeCache()
    .mapKeys({ $0.relativeString })
let processor: Processor<URL, UIImage> = URLSessionProcessor()
    .caching(to: urlKeyedCache)
    .mapImage()
let avenue = Avenue(storage: storage, processor: processor)
```

Now your images will be cached to disk. That means that on the next launch, they will be retrieved blazingly fast.

repository: dreymonde/Avenues-Shallows

repo_name: dreymonde/Avenues-Shallows


text:
#### This is a module of [ConvoKit](http://convokit.cornell.edu/)

# Hypergraph Conversation Representations
Tools to build hypergraph representations of conversations and extract features from them (see the [Patterns of Participant Interactions](http://www.cs.cornell.edu/~cristian/Patterns_of_participant_interactions.html) paper).

We also release a [Reddit conversations dataset](https://github.com/CornellNLP/Cornell-Conversational-Analysis-Toolkit/tree/master/datasets/reddit-corpus) for the method to be used with.

## Example script
[Creating a hypergraph from a conversation, extracting features from it and visualizing and interpreting them](https://github.com/CornellNLP/Cornell-Conversational-Analysis-Toolkit/blob/master/examples/hyperconvo/demo.ipynb)

## Basic usage

We recommend using the example script above to familiarize yourself with this module of the toolkit, but here are basic steps:

0. Install [ConvoKit](http://convokit.cornell.edu/)
1. Load corpus: `corpus = convokit.Corpus(filename=...)`
2. Create HyperConvo object: `hc = convokit.HyperConvo(corpus)`
3. Extract hypergraph features: `feats = hc.retrieve_feats()`
4. Optionally, use convenience methods to embed threads or communities in a low-dimensional space for further exploration:

        X_threads, roots = hc.embed_threads(feats)
        X_communities, subreddits = hc.embed_communities(feats, "subreddit")

#### [ConvoKit](http://convokit.cornell.edu/)


text:
This repo is currently under development.

# BirdNET-Electron

Electron app for sound file analysis with BirdNET.

Author: Stefan Kahl

Contact<EMAIL_ADDRESS>
Website: https://birdnet.cornell.edu/

Please cite as (PDF coming soon):

```
@phdthesis{kahl2019identifying,
  title={{Identifying Birds by Sound: Large-scale Acoustic Event Recognition for Avian Activity Monitoring}},
  author={Kahl, Stefan},
  year={2019},
  school={Chemnitz University of Technology}
}
```

## Application setup

First, clone the project and install all dependencies:

```
git clone https://github.com/kahst/BirdNET-Electron.git
cd BirdNET-Electron
npm install
```

Next, launch the app with:

```
npm start
```

## Development setup

Setting up the project requires Node.js, which we need to install first.

After that, we can initialize the source directory with:

```
npm init
```

Follow the prompt to setup ```package.json```.

Now, we need to install electron with:

```
npm install --save-dev electron
```

BirdNET requires Tensorflow.js which we install with:

```
npm install @tensorflow/tfjs
```

Install Bootstrap and its dependencies:

```
npm install bootstrap
npm install jquery
npm install popper.js
```

This app also needs some additional packages that we have to install.

```
npm install audio-loader
npm install audio-resampler
npm install array-normalize
npm install colormap
```

In order to package the app for stand-alone applications, we need electron-packager:

```
npm install electron-packager --save-dev
```

We can now add the export script in the package.json:

```
"scripts": {
    "start": "electron .",
    "export": "electron-packager . --out dist --overwrite"
  }
```

After that, we can export the app with:

```
npm run export
```

repository: kahst/BirdNET-Electron

repo_name: kahst/BirdNET-Electron


text:
<!-- To view this markdown page rendered, try opening VSCode and clicking to open the "Preview" pane -->
# my_first_github_repo
Test repo following the tutorial instructions

This is a change to learn how to make a commit.
It will first be implemented only on the 'readme-edits' branch.

This is a test of a `code` block:
```yaml
output:
  html_document:
    toc: true
    toc_float: true
```

That seems good enough for now.

A line I wrote on my local computer

This is a line from RStudio

This is yet another line (one day I'll actually write some `code`!). It should now come from the correct email address and account.

A few more lines of code - previously, this did not work by SSH, so I am trying again.


text:
# themost-pool
Most Web Framework data adapter for connection pooling

## Install
    npm install @themost/pool
## Usage
Register Generic Pool Adapter on app.json as follows:

    "adapterTypes": [
        ...
        { "name":"...", "invariantName": "...", "type":"..." },
        { "name":"Pool Data Adapter", "invariantName": "pool", "type":"@themost/pool" }
        ...
    ],
    adapters: [
        ...
        { "name":"development", "invariantName":"...", "default":false,
            "options": {
              "server":"localhost",
              "user":"user",
              "password":"password",
              "database":"test"
            }
        },
        { "name":"development_with_pool", "invariantName":"pool", "default":true,
                    "options": {
                      "adapter":"development"
                    }
                }
        ...
    ]

The generic pool adapter will try to instantiate the adapter defined in options.adapter property.

# Options

### adapter:
The name of the data adapter to be linked with this pool adapter.

`@themost/pool` adapter uses [generic-pool](https://github.com/coopernurse/node-pool#documentation).
Read more about `generic-pool` [here](https://github.com/coopernurse/node-pool#documentation)

Important Note: Upgrade from 2.2.x to 2.5.x

Replace `<EMAIL_ADDRESS>configuration:

    {
        "adapter": "development",
        "size": 25,
        "timeout": 30000,
        "lifetime": 1200000
    }

with:

    {
        "adapter": "development",
        "max": 25,
        "acquireTimeoutMillis": 30000
    }

repository: themost-framework/themost-pool

repo_name: themost-framework/themost-pool


text:
---
lang: en_US
title: Using Odysseyn1x (A9X)
description: Guide to installing checkra1n via Odysseyn1x on A9X devices
permalink: /using-odysseyn1x-a9x
---

::: warning
If you are using a computer with an AMD Ryzen CPU, you will likely run into issues. If you do run into issues, you should use a Mac or a computer with an Intel CPU to follow this guide.
:::

!!!include(./docs/en_US/jailbreak/checkra1n/include/semi-tethered.md)!!!

Odysseyn1x is a live bootable Linux environment that allows you to quickly run checkra1n on a compatible device. checkra1n is capable of jailbreaking millions of iOS devices with A7 to A11 SoC's on firmwares 12.0 to 14.8.1.

!!!include(./docs/en_US/jailbreak/checkra1n/include/odysseyra1n-explanation.md)!!!

::: tip
If you are using an A9X device running iOS 14.4.2 or earlier, you should follow [Installing Odysseyra1n](installing-odysseyra1n) and use checkra1n version 0.12.2 instead.
:::

On A9X devices, it is not possible to use Odysseyn1x 2.14 (required for 14.5+ support) without the use of a custom pongoOS and checkra1n in CLI mode. It is possible to use a custom version of Odysseyn1x, however, to work around this.

## Requirements

- 256MB or greater USB Drive
- The latest version of [Odysseyn1x for A9X](https://github.com/asdfugil/checkn1x_a9x_kerninfo_pongoOS/releases/tag/14.5-a9x-2)
    - For 64-bit computers, download the "AMD64" version
    - For 32-bit computers, download the "i686" version
- [balenaEtcher](https://www.balena.io/etcher/)

![A screenshot of the Odysseyn1x menu](/assets/images/Odysseyn1x.png)

!!!include(./docs/en_US/jailbreak/checkra1n/include/unc0ver-migration.md)!!!

## Flashing Odysseyn1x

1. Download and install balenaEtcher
1. Click `Flash from file`
1. Select the odysseyn1x `.iso` file
1. Click `Select target`
1. Select the USB drive you would like to boot from
    - This USB drive will be completely erased
    - Ensure you back up all important data beforehand
1. Click `Flash!`
    - Do not remove your USB Drive until the process has completed
1. Once the flashing has completed, reboot your computer
1. Go into your BIOS settings and disable Secure Boot, then enter the boot picker and select your USB Drive to boot from
    - This is different for every computer
    - Search your PC or motherboard brand to find out how to get to your BIOS settings if you are unsure

## Running checkra1n

1. Once you have loaded odysseyn1x, select `checkra1n (A9X)`
1. You will now be presented with instructions in how to reboot your device into [DFU mode](/faq/#what-is-dfu-mode), click `Start` to begin
    - Follow the instructions until your device reboots to a black screen
1. Once your device boots, you can quit checkra1n, but do not shut down your computer

## The Odysseyra1n script

The following steps only need to be performed once and are optional but highly recommended for a smoother experience and modern bootstrap.

1. Unlock your device
1. Ensure that your computer is trusted by your device
1. Select `Odysseyra1n` in Odysseyn1x
1. Sileo should install to your device
1. Do not close Odysseyn1x as you will need to re-jailbreak in a few minutes

!!!include(./docs/en_US/jailbreak/checkra1n/include/no-loader.md)!!!
!!!include(./docs/en_US/jailbreak/checkra1n/include/end-of-page.md)!!!


text:
---
title: "WordDoc - Create Awesome Word Documents Directly from PowerShell"
excerpt: "Create Documentation directly from PowerShell. Simple Installation from PowerShell Gallery, and as long as you have MS Word Installed you will be creating .docx, .pdf, .html files in minutes!"
permalink: /
layout: splash
header:
  overlay_color: "#5e616c"
  overlay_image: /assets/images/unsplash.jpg
  overlay_filter: rgba(100, 100, 100, 0.5)
  cta_label: " Getting Started"
  cta_url: "/getting-started"
  caption: ""
feature_row:
  - image_path: /assets/images/getting-started-teaser.jpg
    alt: "Getting Started"
    title: "Getting Started"
    excerpt: "Do you just Want to just jump right in and get started with WordDoc straight away?"
    url: "/getting-started"
    btn_label: " Start Here"
    btn_class: "btn--primary"
  - image_path: /assets/images/documentation-teaser.jpg
    alt: "Documentation"
    title: "Documentation"
    excerpt: "Want to dig deeper and learn how to write your own scripts ?"
    url: "/docs"
    btn_label: " Documentation"
    btn_class: "btn--primary"
  - image_path: /assets/images/scripts-teaser.jpg
    alt: "Script Library"
    title: "Script Library"
    excerpt: "Just want to use an existing script Templace ? Check out some great Templates right here."
    url: "/scripts"
    btn_class: "btn--primary"
    btn_label: " Learn More"
---
Are you using this Module Commercially ? {{ site.btn_paypal }}
{: style="text-align: center;"}
{% include feature_row %}

repository: shanehoey/worddoc

gha_language: PowerShell

repo_name: shanehoey/worddoc


text:
# AutoIt MediaDevice

[![Latest Version](https://img.shields.io/badge/Latest-v1.0.0-green.svg)]()
[![AutoIt Version](https://img.shields.io/badge/AutoIt-<IP_ADDRESS>-blue.svg)]()
[![MIT License](https://img.shields.io/github/license/mashape/apistatus.svg)]()
[![Made with Love](https://img.shields.io/badge/Made%20with-%E2%9D%A4-red.svg?colorB=e31b23)]()

AutoIt MediaDevice Library Allows you to communicate with attached media and storage devices.

## Features
* List Files and Folders.
* Delete Files and Folders.
* Copy File From Device.
* Copy File To Device.

## Usage

##### Basic use:
```autoit

#include "..\MediaDevice.au3"

Local $sDevice = _MD_DeviceGet() ;Get First Found Portable Device
Local $oDevice = _MD_DeviceOpen($sDevice)
Local $aDrives = _MD_DeviceGetDrives($oDevice)
_ArrayDisplay($aDrives,"Storage Drives")
_MD_DeviceClose($oDevice)

```

##### More examples [here.](/Examples)

## Release History
See [CHANGELOG.md](CHANGELOG.md)

<!-- ## Acknowledgments & Credits -->

## License

Usage is provided under the [MIT](https://choosealicense.com/licenses/mit/) License.

Copyright © 2021, [Danysys.](https://www.danysys.com)

repository: DanysysTeam/MediaDevice

repo_name: DanysysTeam/MediaDevice


text:
Finit Signals
=============

Finit is often used on embedded and small Linux systems with BusyBox.
Though Finit comes with its own tools for (poweroff, halt, reboot), for
compatibility with the existing BusyBox toolset the following signals
have been adopted:

`SIGHUP`
--------

Same effect as `finit q`, `init q`, or `initctl reload`, reloads all
*.conf files in `/etc/finit.d/`

This also restarts the API (initctl) socket, like SysV init and systemd
does on USR1 with their FIFO/D-Bus.

`SIGUSR1`
---------

Since Finit 4.1 this signal causes Finit to restart its API (initctl)
socket, like SysV init and systemd does on USR1 with their FIFO/D-Bus.

Finit <= 4.0 performed a system halt (like USR2 without power-off), but
this caused compatibility problems with systemd and sysvinit on desktop
systems.  Hence, since Finit 4.1 it is no longer possible to halt a
system with a signal.

`SIGUSR2`
---------

Calls shutdown hooks, including `HOOK_SHUTDOWN`, stopping all running
processes, and unmounts all file systems.  Then tells kernel to power
off the system, if ACPI or similar exists to actually do this.  If the
kernel fails power-off, Finit falls back to halt.

SysV init N/A, systemd dumps its internal state to log.

`SIGTERM`
---------

Like `SIGUSR2`, but tell kernel to reboot the system when done.

SysV init N/A, systemd rexecutes itself.

`SIGINT`
--------

Sent from kernel when the CTRL-ALT-DEL key combo is pressed.  SysV init
and systemd default to reboot with `shutdown -r`.

Finit currently forwards this to `SIGTERM`.

`SIGPWR`
--------

Sent from a power daemon, like `powstatd(8)`, on changes to the
UPS status.  Traditionally SysV init read /etc/powerstatus and
acted on "OK", "FAIL", or "LOW" and then removed the file.
Finit currently forwards this to `SIGUSR2`.

repository: troglobit/finit

gha_language: C

repo_name: troglobit/finit


text:
---
title: Ghetto
playwright: Joshua Sobol
season: In House
season_sort: 80
period: Autumn
venue: New Theatre
date_start: 2009-11-25
date_end: 2009-11-28

cast:
  - role: Srulik
    name: Cem Aytacli
  - role: The Dummy
    name: Lauren Grant
  - role: Kittles
    name: Florian Goebel
  - role: Genz
    name: Will Vickers
  - role: Kruk
    name: Douggie McMeekin
  - role: unknown
    name: Alanna Southgate
  - role: Weiskopf
    name: Oliver Margolis
  - role: unknown
    name: Chloe Keedy
  - role: 'Dr. Ernst Paul'
    name: Topher Collins
  - role: Dessler
    name: Paul Whickman
  - role: unknown
    name: Rose Eccleshare
  - role: unknown
    name: Amy Rushton
  - role: unknown
    name: Peter Cary
  - role: Lionek / Judge / Others
    name: Conrad Cohen
  - role: unknown
    name: Andrew Kennedy
  - role: unknown
    name: Lucien Jack

crew:
  - role: Director
    name: Hatty Preston
  - role: Producer
    name: Libby Galvin
  - role: Technical Director
    name: Philip Geller
  - role: Lighting Designer
    name: Matt Leventhall
  - role: Musical Direction
    name: Angus MacRae
  - role: Stage Manager
    name: Emma Rutherford

assets:
  - type: poster
    image: KG7MmgG

links:
  - type: Review
    href: https://impactnottingham.com/2009/11/ghetto-the-new-theatre/
    snapshot: fJ3pk
    publisher: Impact Nottingham
    author: Sophie Watson
    title: "Ghetto @ Nottingham New Theatre by Sophie Watson"
    date: 2009-11-26
    quote: "‘Ghetto’ is not light hearted and it is certainly not easy viewing. Rather, it is intelligent, confrontational and thoroughly disconcerting. It is something which will stay with you, long after you have left the theatre."
  - type: Review
    href: https://impactnottingham.com/2009/11/ghetto-the-new-theatre-by-mav-reynolds/
    snapshot: izjm3
    publisher: Impact Nottingham
    author: Mav Reynolds
    title: "Ghetto @ Nottingham New Theatre by Mav Reynolds"
    date: 2009-11-27
    quote: "I am very pleased to say Preston, cast and crew have delivered a fascinating, visually arresting, and thought provoking piece of work. I would wholeheartedly recommend that anyone should go and see this. With all its flaws it finds humanity in a heartless world."

published: true
---

Ghetto - "Everytime we put on a show - sold out three weeks in advance!... People who knew next day they'd be on a train to the camps, the night before they'd put on their finery and come to a play."

Set in the Lithuanian Ghetto of Vilna in 1942, Ghetto tells the real story of a small community of Jewish artists who find each other in the midst of mass deprivation and suffering. They resolve to create plays, music and concerts with the hope of putting as many people as possible to work in order to survive.

repository: newtheatre/history-project

repo_name: newtheatre/history-project


text:
## Bitmex Grid Bot

[![GitHub issues](https://img.shields.io/github/issues-raw/LeaveMyYard/BitmexGridTrader?style=flat-square)](https://github.com/LeaveMyYard/BitmexGridTrader/issues)
[![GitHub pull requests](https://img.shields.io/github/issues-pr/LeaveMyYard/BitmexGridTrader?style=flat-square)](https://github.com/LeaveMyYard/BitmexGridTrader/pulls)
[![License](https://img.shields.io/github/license/day8/re-frame.svg?style=flat-square)](LICENSE.txt)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg?style=flat-square)](https://github.com/psf/black)

## Overview

This is the bitmex trading bot, created for Grid strategy on XBTUSD futures pair.

Build with python, all sourse code provided.

It has a PyQt5 user interface, that is easy to use.

Keep in mind, that using different settings could result in different profits and losses. This program is not guaranteed to contain a money-making machine.

Also, this program is new and could contain bugs, that could result in losing some bitcoins. I am not responsible for that, but feel free to report those bugs and I will try to get rid of them

## Installation

Copy this repository's code from github. It was written using Python 3.7.7, but other versions should be compatable also.

Make `cd` to the project's folder and make `pip install -r requirements.txt`

After that, make `python trade.py` and the program will start with the UI.

## Known bugs

* The "Stop bot" button will not stop the bot from updating a grid.

## TODO

- [ ] Add more exchanges to trade on (Binance Futures, BitFinex etc)
- [x] ~~Move exchange handlers to the other repo, make it a package~~
- [ ] Make it into a pip package and make possible for program to be used from code
- [ ] Compile a documentation

## Licence

Bitmex Grid Bot is [MIT licenced](LICENSE.txt)

repository: dannycoin/BitmexGridTrader

repo_name: dannycoin/BitmexGridTrader


text:
# dune-lib

lib for Haxe games development

## Objectives

* lightweight
* easy
* performance

## Compile the samples

**MS Windows**

1. Run the commands to compile it with the file `compile-samples.bat`
2. All the compiled files are in the new directory: `bin-all/`

! For `bin-all/MultiPlayer.swf` and `bin-all/SocketClientTchat.swf` you must run a server

**Linux**

1. Go on this directory
1. Run the commands to compile it: `haxe src/dl/samples/compile-all.hxml`
2. All the compiled files are in the new directory: `bin-all/`

! For `bin-all/MultiPlayer.swf` and `bin-all/SocketClientTchat.swf` you must run a server

## Run the server
width Neko 2.x

**MS Windows**

1. Compile the samples
2. Run the file `bin-all/server/run-server.bat`

**Linux**

1. Compile the samples
2. Run the command to start the server: `sudo neko bin-all/server/SocketServer.n`

! superuser (`sudo`) to use the port 843 (Flash Policy File distributor)

## Roadmap

* sockets
	* 80% client (only flash)
	* 80% server (only neko)

* physic
	* 90% platform jump
	* collisions
		* 70% squares
		* 100% space grid
		* 50% multi-player
	* reaction
		* 25% mass (body)
		* 0% velocity (body)
		* 50% priority
			1. movables (with velocity and mass)
			2. fixes (by area)
* input
	* 0% gamepad
	* 90% keyboard

repository: Namide/dune-lib

repo_name: Namide/dune-lib


text:
#Homebridge-soundtouch

[Bose SoundTouch](https://www.bose.com/soundtouch-systems.html) plugin for [Homebridge](https://github.com/nfarina/homebridge)

This allows you to control your SoundTouch devices with HomeKit and Siri.

##Installation
1. Install homebridge using: npm install -g homebridge
2. Install this plugin using: npm install -g homebridge-soundtouch
3. Update your configuration file. See the sample below.

##Configuration
Example config.json:

```
    "accessories": [
		{
			"accessory": "SoundTouch",
			"name": "Speaker Bathroom",
			"room": "Bathroom"
		}
	],
```

Example config.json for multiple speakers:

```
    "accessories": [
		{
			"accessory": "SoundTouch",
			"name": "Speaker Bathroom",
			"room": "Bathroom"
		},
		{
            "accessory": "SoundTouch",
            "name": "Speaker Kitchen",
            "room": "Kitchen"
        }
	],
```

Example config.json to configure the device as type speaker:

```
    "accessories": [
		{
			"accessory": "SoundTouch",
			"name": "Speaker Bathroom",
			"room": "Bathroom"
			"type": "speaker"
		}
	],
```

Example config.json to use a fix IP Address for the device:

```
    "accessories": [
		{
			"accessory": "SoundTouch",
			"name": "Speaker Bathroom",
			"room": "Bathroom"
			"ip": "<IP_ADDRESS>"
		}
	],
```

Fields:

* "accessory": Must always be "SoundTouch" (required)
* "name": The name you want to use to control the SoundTouch.
* "room": Should match exactly with the name of the SoundTouch device.
* "type": Must be 'Switch' or 'Speaker' (Switch is default). This determine the type of device for HomeKit. (Switch is supported by the official Apple HomeKit app, if you use another third party app, speaker could be used)
* "ip": The IP address of the SoundTouch device. Can be used in case of discovery issues.

Don't use soundtouch or music as name, because Siri will try to open the SoundTouch or Apple Music app.

Controlling the volume with Siri is not possible, because volume is not (yet) supported as a Characteristic.
In fact, for HomeKit this accessory is treated like a switch (because speaker accessories are not supported). Unless you use another HomeKit app and configure the type parameter.

##Connecting

1. Install the Insteon+ app on your iPhone or iPad.
2. Add a home
3. Add a device and select the found 'HomeBridge' accessory (pin code is 031-45-154)

##Siri (English)

* Hé Siri, is speaker bathroom enabled?
* Hé Siri, is speaker bathroom playing?
* Hé Siri, turn speaker bathroom on
* Hé Siri, turn speaker bathroom off

##Siri (Dutch)

* Hé Siri, is de speaker badkamer ingeschakeld?
* Hé Siri, is speaker badkamer aan het spelen?
* Hé Siri, schakel speaker badkamer in
* Hé Siri, schakel speaker badkamer uit

repository: csigritz/homebridge-soundtouch

repo_name: csigritz/homebridge-soundtouch


text:
---
layout: post
title:      "Dynamic Programming"
date:       2020-11-01 23:35:42 +0000
permalink:  dynamic_programming
---

"An algorithm is simply a set of steps used to complete a specific task" (Computer Science: Algorithms). Dynamic programming is a technique to solve some types of algorithm problems. Algorithms have many applications in computer science. Therefore, dynamic programming will be a useful tool in the programmer's tool belt in solving problems that pop up in a programmer's career.

Dynamic programming is an optimization over plain recursion. The main principle of dynamic programming is to store some results of the algorithm as the algorithm progresses, so they do not have to be calculated again later. This can greatly reduce time complexities of some solutions. As an example, by using dynamic programming, the Fibonacci Numbers problem can go from exponential time complexity to linear time complexity. (Dynamic Programming)

```
//Using standard recursion
//Exponential time
int fib(int n)
{
    if (n <= 1)
		    return n;
	  return fib(n-1) + fib(n-2);

}

//Using dynamic programming
//Linear time
int fib_dp(int n)
{
    f[0] = 0;
		f[1] = 1;

		for(i = 2; i <= n; i++)
		{
		    f[i] = f[i-1] + f[i-2];
		}

    return f[n];
}

```

Luckily, in the example above, the dynamic programming solution is not much more difficult to understand than the recursion solution. It simply stores the values of each fib number in f, instead of calculating it again.  Solutions to these problems using Dynamic Programming, in addition to many other types of problems, can be found here: https://www.geeksforgeeks.org/dynamic-programming/ .

I also believe that programmers can be creative and find ways to solve difficult problems that haven't been discovered yet. When designing the overall structure of code, it may be easier than it sounds to find a treasure that no one else has found before. Another very important use of Dynamic Programming is to pass technical interviews. Even if you may never use it in real life, and if all else fails, there is a chance it will show up in a technical interview and be used in coding challenges. You never know when it may become useful. Try to stretch yourself and use it in ways that are unexpected - but still very powerful.

References:
Computer Science: Algorithms. https://edu.gcfglobal.org/en/computer-science/algorithms/1/.

Dynamic Programming. GeeksforGeeks. https://www.geeksforgeeks.org/dynamic-programming/.


text:
This is a tutorial for how to write a complete parser for a simple calculator using LALRPOP.

If you are unfamiliar with what a parser generator is, you should read [Crash course on parsers]
first.

- [Adding LALRPOP to your project](001_adding_lalrpop.md)
- [Parsing parenthesized numbers](002_paren_numbers.md)
- [Type inference](003_type_inference.md)
- [Handling full expressions](004_full_expressions.md)
- [Building ASTs](005_building_asts.md)
- [Macros](006_macros.md)
- [Fallible actions](007_fallible_actions.md)
- [Error recovery](008_error_recovery.md)
- [Passing state parameter](009_state_parameter.md)

This tutorial is still incomplete. Here are some topics that I aim to
cover when I get time to write about them:

- Advice for resolving shift-reduce and reduce-reduce conflicts
- Passing state and type/lifetime parameters to your action code (see e.g. [this test](https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/expr_arena.lalrpop) invoked [from here]).
- Location tracking with `@L` and `@R` (see e.g. [this test](https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/intern_tok.lalrpop)).
- Integrating with external tokenizers (see e.g. [this test](https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/expr.lalrpop) invoked [from here]).
- Conditional macros (no good test to point you at yet, sorry)
- Fallible action code that produces a `Result` (see e.g. [this test](https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/error.lalrpop) invoked [from here]).
- Converting to use `LALR(1)` instead of `LR(1)` (see e.g. [this test](https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/expr_lalr.lalrpop) invoked [from here]).
- Plans for future features

[Crash course on parsers]: ../crash_course.md
[from here]: https://github.com/lalrpop/lalrpop/blob/master/lalrpop-test/src/lib.rs

repository: lalrpop/lalrpop

gha_language: Rust

repo_name: lalrpop/lalrpop


text:
# Message Limits

There are limits on how much data can be sent back and forth between the plugin and engine at a time. There are five scenarios where this comes into play:

1. Inputs sent from the engine to the plugin, as arguments to a [Plugin Operation](../References/Plugin_Operations.md). For example, the schema-defined `Repository` object that is provided as input to plugin operations.

2. Outputs sent back from the plugin to the engine, as the return values from plugin operations.

3. Exception messages and call stacks thrown by plugin code. For example, the `message` field within [User Visible Errors](User_Visible_Errors.md).

4. Inputs sent from the plugin to the engine, as arguments to a [Platform library](../References/Platform_Libraries.md) function. For example, the `message` field that is passed to `logger.debug`.

5. Outputs sent back from the engine to the plugin, as the return values from Platform Library functions. For example, the `stdout` resulting from a call to `libs.run_bash`.

For case 1 and 2, the total size of data must be less than 4 mebibytes (4 MiB).

For case 3, the total size of data must be less than 128 kibibytes (128 KiB).

For case 4 and 5, the total size of data must be less than 192 mebibytes (192 MiB).

The actual size of this information at runtime is dependent on how the Python interpreter chooses to represent the information, so it's not always possible to know ahead of time what the exact size will be.

Here are some examples of where problems may occur:

1. Using `libs.run_bash` to print the entire contents of a large file to stdout.

2. Using a single `logger` command with many pages of output.

3. Throwing an exception with a large message or stack trace.

4. Large amount of metadata in a plugin defined schema like `Repository` or `Virtual Source`.

## How to tell if the message size was exceeded

The plugin operation or platform library callback will fail with a RPC error. The exception will look like:

```
Error
Discovery of "my_plugin" failed: Plugin operation "Repository Discovery" got a RPC error for plugin "my_plugin". UNAVAILABLE: Network closed for unknown reason
```

## What to do if the maximum metadata or message size is exceeded

Reach out to us via the [Virtualization SDK GitHub repository](https://github.com/delphix/virtualization-sdk/) for guidance.

repository: delphix/virtualization-sdk

branch_name: refs/heads/develop

repo_name: delphix/virtualization-sdk


text:
---
title: Download
nav_order: 3
layout: default
permalink: download/
description: "Download"
---

# Download

Burnout Barometer is built on Go and packaged into a single binary.
{: .fs-6 .fw-300 }

You can get the `barometer` executable from the
[Releases](https://github.com/ljvmiranda921/burnout-barometer/releases) page.
For the latest version, follow the instructions below.

1. First, specify your operating system in the `OS` environment variable. Choose
between `linux`, `windows`, or `darwin`:

    ```bash
    export OS=<my-operating-system>  # [linux|windows|darwin]
    ```

2. Then download the executable:

    ```bash
    curl -s https://api.github.com/repos/ljvmiranda921/burnout-barometer/releases/latest \
    | grep "barometer-amd64-${OS}" \
    | cut -d '"' -f 4 \
    | wget -i -
    ```

3. Set-up permissions so that it can be executed. Let's also rename the executable into `barometer`:

    ```bash
    chmod +x barometer-amd64-${OS}
    mv barometer-amd64-${OS} barometer
    ```

Ensure that you have downloaded barometer correctly, run `barometer --version`

## Compiling from source

Optionally, you can clone and build the binary straight from [the
source](https://github.com/ljvmiranda921/burnout-barometer). The following
steps require [Go 1.11](https://golang.org/doc/go1.11) or above.

First, ensure that [Go Modules](https://github.com/golang/go/wiki/Modules) is enabled:

```bash
export GO111MODULE=on
```

Then, clone the repository and build the binary:

```bash
git clone git@github.com:ljvmiranda921/burnout-barometer.git
cd burnout-barometer
go get
go build .
```

---

Once you've successfully downloaded the executable, head over to the
[Installation page]({{ site.baseurl }}/installation) to setup and deploy your
barometer!
{: .info }

gha_language: Go


text:
# docker-snort
Snort is an open-source, free and lightweight network intrusion detection system (NIDS) software for Linux and Windows to detect emerging threats. This container is designed to run snort with standard configurations and forward logs to the DNIF Adapter (AD) over the http API.

On startup the container runs snort with the given parameters, and also runs [snort-agent](https://github.com/dnif/snort-agent) in the background that collects log entries generated by snort and transmits them over HTTP to the DNIF Adapter.

## Getting Started

* Install `docker-ce` more information available on the [Docker Site](https://docs.docker.com/engine/installation/)
* Download and run (dry-run) dnif/snort image using `docker run --rm -it dnif/snort /bin/bash`

## Running Snort
Snort is desinged to run at container initialization, however it needs to be initiated with dynamic variables.

* `HOME_NET` is the local network definition used by snort.
* `INTERFACE` is the local interface that needs to be monitored
* `AD` is the address of the DNIF Adapter (AD)

## Sample Commands

```
docker run --rm -it snort /bin/bash
docker run -d -e HOME_NET=<IP_ADDRESS> -e INTERFACE=eth0 -e AD=<IP_ADDRESS> --net=host --cap-add=NET_ADMIN dnif/snort

```

repository: dnif-archive/docker-snort

repo_name: dnif-archive/docker-snort


text:
---
title: Workflow & basics
---

Running `devspace dev` will do the following:
1. Read the `Dockerfile` and apply in-memory [entrypoint overriding](/docs/cli/development/entrypoint-overrides) (optional)
2. Build a Docker image using the (overridden) `Dockerfile`
3. Push this Docker image to the [DevSpace Container Registry (dscr.io)](/docs/cloud/images/dscr-io)
4. Deploy your Helm chart as defined in `chart/`
5. Start [port forwarding](/docs/cli/development/port-forwarding)
6. Start [real-time code synchronization](/docs/cli/development/synchronization)
7. Start [terminal proxy](/docs/cli/development/terminal)

> It is highly discouraged to run `devspace dev` multiple times in parallel because the port-forwarding as well as the code synchronization processes will interfere with each other.

repository: Milstein/devspace

repo_name: Milstein/devspace


text:
cadejo.instruments.combo.genpatch
=================================

cadejo.midi.program/Bank allows both literal program data and for functions
which are executed to generate program data. genpatch defines such a
function which generate random Combo programs. In general these
*program-functions* should accept an arbitrary number of arguments and
return an association list of parameter key/value pairs.

The gen-combo function below simply ignores its arguments but in more
complex cases arguments may be used to provide 'hints' to the nature of
program to create.

For more details see documentation for combo.data.

<pre>
(ns cadejo.instruments.combo.genpatch
  (:require [cadejo.util.math :as math])
  (:require [cadejo.instruments.combo.program :as program]))

(def bypass program/bypass)
(def low program/low)
(def high program/high)
(def band program/band)
(def notch program/notch)

(def filter-types [bypass bypass bypass bypass
                   low low low low
                   high band notch notch])

(defn gen-combo [& args]
  (let [main-tone (rand-nth '[1 2 3 4])
        a1 (or (and (= main-tone 1) 1.0)(rand))
        a2 (or (and (= main-tone 2) 1.0)(rand))
        a3 (or (and (= main-tone 3) 1.0)(rand))
        a4 (or (and (= main-tone 4) 1.0)(rand))
        w1 (rand)
        w2 (rand)
        w3 (rand)
        w4 (rand)]
    (program/combo :a1 a1 :w1 w1
                   :a2 a2 :w2 w2
                   :a3 a3 :w3 w3
                   :a4 a4 :w4 w4
                   :chorus (math/coin 0.5 0 (rand))
                   :vibrato (list :freq (math/coin 0.75
                                                   (+ 3 (rand 4))
                                                   (rand 7))
                                  :sens (math/coin 0.90 0.01 (rand)))
                   :filter (list :freq (rand-nth '(1 2 3 3 4 4 4 6 6 6 8 8))
                                 :type (rand-nth filter-types))
                   :flanger (list :rate (math/coin 0.80 (rand 0.5)(rand 5))
                                  :depth (math/coin 0.75 (rand 0.5)(rand))
                                  :fb (* (math/coin 0.5 -1 +1)(rand))
                                  :mix (math/coin 0.25 (rand) 0))
                   :reverb (math/coin 0.25 (rand) 0)
                   :amp 0.20)))
</pre>

repository: silky/Cadejo

repo_name: silky/Cadejo


text:
# Connect Electric Imp to Azure IoT Hub

In these examples, you begin by learning the basics of working with Electric Imp. We will use Electric Imp Libraries to seamlessly connect imp-enabled hardware to the cloud by using Azure IoT Hub.

Your imp-enabled hardware device will report environmental sensor values through the Electric Imp impCloud into Azure IoT Hub. Here is an overview diagram:

![EI overview](./example_imgs/EIOverview.png)

There are two step-by-step examples, depending on whether you want to register your imp-enabled device manually with Azure IoT Hub or whether you want the Electric Imp platform to perform that registration automatically.

## Hardware Options

### impExplorer™ Kit

The [impExplorer™ Kit](https://store.electricimp.com/collections/featured-products/products/impexplorer-developer-kit?variant=31118866130) provides a set of sensors and peripherals which are ready to use. These examples will take readings from the onboard temperature/humidity sensor and send the readings to IoT Hub. No other hardware is needed.

#### impExplorer Required Hardware

The impExplorer Kit provides a set of sensors and peripherals which are ready to use, so no other hardware or setup is needed.

### impAccelerator™ Fieldbus Gateway

The [impAccelerator™ Fieldbus Gateway](https://store.electricimp.com/products/impaccelerator-fieldbus-gateway?variant=31118564754) is designed for a variety of industrial use-cases. In this example we will use the MikroBUS socket and a thermocouple to expand the basic functionality of the board to take temperature readings to send to IoT Hub.

#### impAccelerator Required Hardware

- [impAccelerator™ Fieldbus Gateway](https://store.electricimp.com/products/impaccelerator-fieldbus-gateway?variant=31118564754)
- [MikroBUS board](https://shop.mikroe.com/thermo-click)
- [Thermocouple](https://shop.mikroe.com/thermocouple-type-k-glass-braid-insulated)

#### impAccelerator Hardware Setup

You will need to remove the impAccelerator™ Fieldbus Gateway from the enclosure to expose the MikroBUS headers. The THERMO click board plugs directly into the MikroBUS headers.

## Step-by-Step Example: IoT Hub Env Auto Register

This example implements automatic device registration through the IoT Hub device registration APIs.

Find Auto Registration step by step instructions [here](./AutoRegister_StepByStep_Instructions.md)

## Step-by-Step Example: IoT Hub Env Manual Register

This example implements manual device registration through the IoT Hub UI.

Find Manual Registration step by step instructions [here](./ManualRegister_StepByStep_Instructions.md)

repository: mm-gmbd/AzureIoTHub

repo_name: mm-gmbd/AzureIoTHub


text:
# logcat-viewer

:radio: An User Friendly ADB Logcat Viewer written in React and NodeJS

[![NPM](https://nodei.co/npm/logcat-viewer.png?downloads=true&downloadRank=true&stars=true)](https://nodei.co/npm/logcat-viewer)

## Usage

```bash
# install the module globally with npm
$ npm install -g logcat-viewer

# use the module
$ logcat-ui
```

go to [http://localhost:8999](http://localhost:8999) in your browser.

## Screenshots

![screenshot-v1.1.0](https://github.com/lexmartinez/logcat-viewer/raw/master/screenshots/screenshot-1.1.0.jpg)

## Development setup

``` bash
# clone repository
git clone https://github.com/lexmartinez/logcat-viewer.git

# open project folder
cd logcat-viewer

# install dependencies
yarn install

# run the app at localhost:8999
yarn start
```

## License

This project is licensed under MIT License - see the [LICENSE.md](https://github.com/lexmartinez/logcat-viewer/blob/master/LICENSE.md) file for details

repository: cloudnine-digital/logcat-viewer

repo_name: cloudnine-digital/logcat-viewer


text:
- You will write a recursive function that finds and returns size of a string.

int find_size(const char *string)
- Using the function above write a new function that finds how many times a given string is used in a given string.

int char_number(const char *string, const char *wish_to_find)
- Assume every Friday, you have to climb n stairs for C lab on the first floor. You can take your steps as follow: One stair at a time or two stairs at a time. You will write a complete C program to calculate in how many distinct ways you can climb to the top and to print it on the screen.

Your program will include at least two functions as following :
- int combination (int n , int k) : a recursive function to calculate combination
“n choose k” and returns the result.
- int ways (int n) : write a recursive function to calculate and return total number of
ways.


text:
# Meanbee Organisational Structured Data

Add organisation information and contacts to the structured data on the site to be used by [Google's Knowledge Graph](https://developers.google.com/structured-data/customize/contact-points).

## Installation

Install via [Modman](https://github.com/colinmollenhour/modman):

    cd /path/to/magento/root/
    modman init
    modman clone https://github.com/meanbee/magento-meanbee-osd.git

repository: brand-alley/magento-meanbee-osd

repo_name: brand-alley/magento-meanbee-osd