text:
# CMCDSample Demo

## Demo Introduction

This demo showcases how to create a VS2017 project for Sitecore with the following features:

1. Two different Sitecore role servers, Content Manager and Content Delivery, available for debugging.
1. Each Sitecore role server has a "Website" folder mounted as volume with its files stored in the development machine, at debugging time (no need for synchronization)
1. The "Website" folders are embedded in the image at runtime.
1. The Sitecore files, databases and Solr cores are automatically copied from the images to the Development environment (if missing).
1. Support for attaching to IIS process in the Content Manager and Content Delivery containers from VS2017 for debugging

## Prerequisites

* Windows 10 Fall Creators Update
* Docker for Windows
* Visual Studio 2017 15.5 or later
* Clone the [Sitecore base docker-images repository](https://github.com/Sitecore/docker-images) and build the images for the Sitecore version "9.0.1 rev. 171219 XM1 CM".

## Development Environment Setup

1. Clone [this repository](https://github.com/Sitecore/docker-demo) into a folder such as “c:\Docker\Sitecore\docker-demo” (next steps will assume this folder has been used):
1. Copy "**license.xml**" into:
   1.  "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CD\Data**“
   1.  "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CM\Data**“
1. Open VS2017 as Administrator
1. Open the solution “C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**CMCDSample.sln**”
1. Copy all files with extension "*.sample" located in the folder “C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\src\Website\Properties\PublishProfiles\”, and remove the "sample" extension to leave them as “**\*.pubxml**”, in the same folder.
1. Make sure the project “**docker-compose**” is set as StartUp project
1. Build the solution. The two projects in the solution should compile.
1. Review the file "C:\docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**docker-compose.yml**" and update the `BASE_IMAGE` argument with the name used to build the Content Manager (cm) and Content Deliver (cd) base images.
1. Build the solution with the “**DebugCM**” solution configuration ("F5").
   >The first time the containers run, the base images will detect that the required assets (databases, indexes and site files) are missing in their respected VOLUMEs (pointing to the development environment) and will take some time to create them. VS will build the containers and will try to attach to the IIS's process running in one of the sitecore's container (cm or cd), however it will fail because the container will not be ready yet (it will need some more time). In the meantime, the file transfer from the images to the Development environment will keep progressing. Please be patient.
1. The VS' "Output" panel ("Docker" output) will display the IP of one of the sitecore's containers (cm or cd).  Paste each IP on a browser's address bar. Please notice that Sitecore needs some time to warm-up, therefore the initial start may take a bit (up to 1-2 min).
1. The browser will display the OOTB Sitecore’s home page for both, the Content Manager and the Content Delivery servers.
1. Choose one domain for each Sitecore server (ie: "sitecore901.xm1.cm.dev.local" and "sitecore901.xm1.cd.dev.local") and update the local "host" file, associating each of these domains with the IP of the corresponding sitecore container "**cd**" or "**cm**".
1. Confirm that you can browse to both containers using their respective domains.
1. Deploy the Sitecore customizations made in the project "Website" to both, the Content Manager and the Content Deliver Servers:
   1. **Content Delivery:** Use the publication profile named "**Local Dev CD**" to publish the "Website" project to the "**cd**" service
      "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CD\Website**“
   1. **Content Manager:** Use the publication profile named "**Local Dev CM**" to publish the "Website" project to the "**cm**" service
      "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CM\Website**“
1. Refresh the browser (Ctrl + F5) and confirm that the Sitecore default home page has a customization that displays the name of the container and also its Sitecore role.

## Development Process

Sitecore supports multiple sites and multiple URL for each site. It may be necessary to access the site with a specific URL (other than the IP). In these cases, it is necessary to update the development environment's host file every time the container is run (instantiated), which happens the first time VS runs the project.

Following the initial container run, the containers can remain running meanwhile changes are done to the website and published to either the Content Manager or the Content Deliver containers through the standard VS publishing feature, as if the containers were IIS instances running in the development environment (no containerised).
The "Website" project has the following publication profiles to publish changes locally:

* **Local Dev CD:** Publish changes to the "" server/container:
    * "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CD\Website**“
* **Local Dev CM:** Publish changes to the "" server/container:
    * "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CM\Website**“

### Configuration transformations

Each Sitecore role requires its specific configuration settings. Standard configurarion transformations are used in this example to generate the Web.confg file specific for each server role.

The base "Web.config" file that can be found in the "Website" project has been taken directly from the standard base image for the Content Manager role. This allows us to detect changes made in this file in future versions of the same image.

There is one transformation file for each Solution configuration: combination of Debug|Release and Sitecore role (CM|CD)

* DebugCD
* DebugCM
* ReleaseCD
* ReleaseCM

## Debugging Sitecore with VS2017

### Attaching VS2017 to Sitecore

The following steps describes how to attach VS2017 to the IIS process where Sitecore is running within its container.

1. Make sure Sitecore is running by browsing to its IP which can be obtained with either of the following procedures:
   1. Through VS2017
      1. When VS2017 runs a docker project (it must be selected as StartUp project) the website container's IP is displayed in the "Output" panel ("Docker" output). There should be as below example:
         ```text
         ========== Debugging ==========
         docker ps --filter "status=running" --filter "name=dockercompose14165912220825680628_website_" --format {{.ID}} -n 1
         ac58646e9013
         docker inspect --format="{{range .NetworkSettings.Networks}}{{.IPAddress}} {{end}}" ac58646e9013
         <IP_ADDRESS>
         ```
          * Notice that the "**ac58646e9013**" is the container id. It is different every time the container is created
          * The following instruction is used to get the container's IP. Notice the container ID at the end.
         ```text
         docker inspect --format="{{range .NetworkSettings.Networks}}{{.IPAddress}} {{end}}" ac58646e9013
         ```
          * Finally, the last line is the container's IP which also changes every time the container is run.
   1. Through a console
      1. Get the container's ID:
         ```text
         PS C:\> docker ps -a
         CONTAINER ID        IMAGE                                                   COMMAND                  CREATED             STATUS                       PORTS                   NAMES
         ac58646e9013        website:dev                                             "powershell -Command…"   About an hour ago   Up About an hour             <IP_ADDRESS>:37434->80/tcp   dockercompose14165912220825680628_website_1
         984cdde5faee        VSWebsiteRegistry.azurecr.io/sitecore:9.0.171219-sql    "powershell -Command…"   About an hour ago   Up About an hour (healthy)                           dockercompose14165912220825680628_sql_1
         da78adba6ac0        VSWebsiteRegistry.azurecr.io/sitecore:9.0.171219-solr   "powershell -Command…"   About an hour ago   Up About an hour             8983/tcp                dockercompose14165912220825680628_solr_1
         PS C:\>
         ```
          Notice in the table above the container named "**\*_website_1**", with image named "website:dev". This is the website container which IP is needed.
      1. Make sure the container status is "Up" by checking the "STATUS" column.
      1. Copy the container id value.
      4. Run the following command to get the container's IP.
         ```text
         PS C:\> docker inspect --format="{{range .NetworkSettings.Networks}}{{.IPAddress}} {{end}}" ac58646e9013
         <IP_ADDRESS>
         PS C:\>
         ```

### Sitecore logs

Sitecore logs can be found in the following location:
   "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\Data**“

### Content Manager and Content Deliver site files

The site files for the two sitecore roles, in the containers, are directly accessible from the following folders in the development machine:

* Content Deliver:
   * "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CD\Website**“
* Content Manager:
   * "C:\Docker\Sitecore\docker-demo\sitecore\9.0.1 rev. 171219 XM1\VS2017\CMCDSample\\**storage\CM\Website**“

Any change made in the above folders will be automatically detected by Sitecore in the corresponding container.

## Release Configurations

If the solution is switched to the "ReleaseCD" or "ReleaseCM" configurations and re-built, the Sitecore containers are re-created with the Website folder embedded inside along with the project output. This simplifies deployments to other environments (QA, UAT and Production).

## Known issues

1. Visual Studio fails when trying to attach just after starting a debugging session. VS can attach to the running process in container afterwards, though. See section "Attaching VS2017 to Sitecore"

repository: vijayraavi/docker-demo

path: /sitecore/9.0.1 rev. 171219 XM1/VS2017/CMCDSample/README.md

branch_name: refs/heads/develop

repo_name: vijayraavi/docker-demo


text:
# Compliant Control

This repository is based on justagist's [PandaSimulator](https://github.com/justagist/panda_simulator). The folder Compliant_control contains the work related to my master's thesis "Learning Compliant Robotic Manipulation". In the folder, three compliant force controllers are implemented for the Panda robot: Admittance Control (AC), Hybrid Force/Motion Control (HFMC) and Force-based Variable Impedance Control (VIC). Nrontsis' repository [PILCO](https://github.com/nrontsis/PILCO) provides functionality for the model-based Reinforcement Learning algorithm PILCO. Compliant_control provides compatibility between the PILCO-implementation and the implemented force controllers, constituting a PILCO-framework for learning control-strategies.

# Setting Up the Environment

## Setup of the extended Franka Control Interface (FCI)

The extended FCI can be set up in an Ubuntu 18.04 system in the following steps:

  - Install ROS Melodic Morenia

 - Build libfranka and franka_ros

  -  Set up the real-time kernel

  - Build [PandaSimulator](https://github.com/justagist/panda_simulator) and [PandaRobot](https://github.com/justagist/panda_robot)

Both the building of libfranka and franka_ros and the setting up of the real-time kernel, are described in detail in https://frankaemika.github.io/docs/installation_linux.html. The process of building panda_simulator and panda_robot is done according to the respective README files on Github. franka_ros_interface and franka_panda_description are both installed when performing the fourth step.

## Setup of the PILCO compatibility

All compatibility related to PILCO can be achieved through the following steps:

  1) Install the [PILCO](https://github.com/nrontsis/PILCO) implementation

  2) Install OpenAI Gym

  3) Install execnet

The PILCO implementation should preferable be installed in a fresh Conda environment with Python >= 3.7. The installation itself is performed by running the following two commands in the terminal:

- git clone https://github.com/nrontsis/PILCO && cd PILCO}

- python setup.py develop

Step 2 and 3 are performed by similarly running

- pip install gym

in the python 2 environment, and

- pip install execnet

in the Conda environment.

## Setup of the implemented controllers

In order to run the implemented controllers, this package (https://github.com/martihmy/Compliant_control), is to replace panda_simulator. Additionally, the four python scripts in the folder Modifications, is to replace the files with the same names in the PILCO-, franka_ros_interface- and panda_robot packages respectively.

branch_name: refs/heads/main

extension: md

license_type: permissive


text:
git-bookmark(1) -- Keep your bookmarks with your repository
=============================================

## SYNOPSIS

**git-bookmark** init [--session=<name>] [--branch=<name>] [--gitv]
**git-bookmark** add  [--session=<name>] [--branch=<name>] [--gitv] <url>...
**git-bookmark** list [--session=<name>] [--branch=<name>] [--gitv]
**git-bookmark** open [--session=<name>] [--branch=<name>] [--gitv] [--browser=<executable>]
**git-bookmark** edit [--session=<name>] [--branch=<name>] [--gitv] [--editor=<executable>] [--message=<message>]
**git-bookmark** -h | --help
**git-bookmark** --version

## DESCRIPTION

`git-bookmark` is a simple script that doubles as a git subcommand. It makes available some commands to interact with bookmark files on a separate branch, to help to store web sessions related to it.

The bookmark file format is a simple list of line separated URLs (Although no URL is ever checked for validity). It supports empty lines, leading/trailing whitespace and # comments.

Using the packaged `make install` also installs `git-bk` as an alias. This lets `git bk` be used for brevity sake.

The man page is available with `man git-bookmark` or at the [project gh pages](https://qu4tro.github.io/git-bookmark/).

## OPTIONS

 * `-h`, `--help` :
   Displays the help screen.

 * `--version` :
   Displays version information.

 * `--session=<name>` :
   Name of the bookmark file [default: links].

 * `--branch=<name>` :
   Name of the branch to look for the bookmark file [default: bookmarks].

 * `--editor=<executable>` :
   Editor to use when editing a bookmark file [default: `$EDITOR`].

 * `--message=<message>` :
   Commit message when editing. When ommited it will prompt like git does.

 * `--browser=<executable>` :
   Browser to use when opening from a bookmark file [default: `$BROWSER`].

 * `--gitv` :
   Show all of the underlyings git commands output.

## EXAMPLES

Start by **initializing** a new branch to keep the bookmarks within:

    $ git bk init

You may not like the default branch or you may want to use multiple branches. You need to **initialize** for any branch you use.

    $ git bk init --branch=other

**Initializing** is optional if the branch already exists.

New bookmarks can be easily **added**. Each `add` command is a commit on the underlying branch:

    $ git bk add https://github.com/stephenmathieson/git-standup
    $ git bk add https://github.com/basherpm/basher https://en.wikipedia.org/wiki/Man_page

When **adding** the defaults can be overriden with their respective options:

    $ git bk add --branch=other --session=local http://<IP_ADDRESS>:35729/

Comments can be **added** inline:

    $ git bk add --branch=other --session=local "http://<IP_ADDRESS>:8000/ # Server"

The bookmarks can be **listed** as well:

    $ git bk list
    https://github.com/stephenmathieson/git-standup
    https://github.com/basherpm/basher
    https://en.wikipedia.org/wiki/Man_page

    $ git bk list --branch=other --session=local
    http://<IP_ADDRESS>:35729/
    http://<IP_ADDRESS>:8000/

If more manual intervention you can **edit** the file by hand:

    $ git bk edit

By default, it uses `$EDITOR`, but anything in `$PATH` can be specified:

    $ git bk edit --editor=cat --gitv
    https://github.com/stephenmathieson/git-standup
    https://github.com/basherpm/basher
    https://en.wikipedia.org/wiki/Man_page
    On branch bookmarks
    Your branch is up to date with 'origin/bookmarks'.

    nothing to commit, working tree clean

We can see here with the help of `--gitv option, that no commit is generated when no changes are made when editing.

We're here.
Finally, we've arrived to our end **goal**! To **open** the saved bookmarks in your `$BROWSER` simply run:

    $ git bk open

And of course, we can use any of usual options when **opening**:

    $ git bk open --browser=echo --session=local --branch=other
    http://<IP_ADDRESS>:35729/
    http://<IP_ADDRESS>:8000/

## COPYRIGHT

**git-bookmark** - Copyright 2020, Xavier Francisco.
Released under the MIT license.

## SEE ALSO

git(1)

license: MIT

branch_name: refs/heads/master


text:
### Introduction

This is a very basic example in which we will try to run an ubuntu container that echos 'hello world' after every 1 second.

Notes:
* It is a `Deployment`.
* We have specified that we are only interested in 1 replica i.e. only 1 instance of container will be created.
* Since in Kubernetes the most basic unit if a Pod we should say that this will deploy only 1 Pod.
* In this example, the one Pod contains one container.

### Check what we have in the cluster

```bash
$ kubectl get pods
No resources found.
```

```bash
$ kubectl get all
NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   3m
```

### Create the deployment

```bash
$ kubectl create -f example-1-basic/deployment.yaml
deployment "example-1-basic" created
```

To check the state of the cluster

```bash
$ kubectl get all
NAME                                  READY     STATUS    RESTARTS   AGE
po/example-1-basic-3444702635-9ttjp   1/1       Running   0          3m

NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   11m

NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/example-1-basic   1         1         1            1           3m

NAME                            DESIRED   CURRENT   READY     AGE
rs/example-1-basic-3444702635   1         1         1         3m
```

Notes:
* We end up having a `Pod`, `Deployment` and `Replication Set`
* Look at the columns (DESIRED, CURRENT, UP-TO-DATE, AVAILABLE). They all have the value of 1 as we have specified in our deployment that we want only 1 running Pod.

### Check the logs of the Pod

```bash
$ kubectl logs example-1-basic-3444702635-9ttjp
hello world
hello world
hello world
hello world
...
...
```

Note the name of the Pod as this will be different for you.

### Delete the Pod

We will now try to delete the Pod. Because in our Deployment we have specified that we want to have 1 Pod instance always running, Kubernetes should automatically start a new instance after we deleted the Pod manually.

```bash
$ kubectl delete pod example-1-basic-3444702635-9ttjp
pod "example-1-basic-3444702635-9ttjp" deleted

# Make sure to issue below command very quickly to see the status of your
# cluster
$ kubectl get all
NAME                                  READY     STATUS        RESTARTS   AGE
po/example-1-basic-3444702635-9ttjp   1/1       Terminating   0          11m
po/example-1-basic-3444702635-d6wrp   1/1       Running       0          7s

NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   20m

NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/example-1-basic   1         1         1            1           11m

NAME                            DESIRED   CURRENT   READY     AGE
rs/example-1-basic-3444702635   1         1         1         11m
```

As it should be clear, my older Pod instance (example-1-basic-3444702635-9ttjp) is being deleted (Terminating) and a new one is starting. Essentially Kubernetes is respecting what you have asked to do i.e. to make sure that 1 Pod instance of example-1-basic is always running.

### Delete the Deployment

Deleting the deployment is different from deleting the Pod as this is what instructs the Kubernetes that we are not interested anymore in running the Pod.

```bash
$ kubectl delete deployment example-1-basic
deployment "example-1-basic" deleted

# Make sure to issue below command very quickly to see the status of your
# cluster
$ kubectl get all
NAME                                  READY     STATUS        RESTARTS   AGE
po/example-1-basic-3444702635-d6wrp   1/1       Terminating   0          4m

NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   24m
```

### Scaling the Deployment

If you are following the example in steps then make sure to create the deployment again (`kubectl create -f example-1-basic/deployment.yaml`).

In deployment.yaml we have specified that we only want 1 Pod (1 Replica). Our cluster has been running for some time now and a request has arrived to run 3 instances of our Pod. The scaling can be achieved by either modifying the yaml file and recreate it or by issuing the command to scale.

```bash
$ kubectl scale deployment example-1-basic --replicas=3
deployment "example-1-basic" scaled

$ kubectl get all
NAME                                  READY     STATUS              RESTARTS   AGE
po/example-1-basic-3444702635-98lpn   0/1       ContainerCreating   0          3s
po/example-1-basic-3444702635-h7qfm   0/1       ContainerCreating   0          3s
po/example-1-basic-3444702635-zs87f   1/1       Running             0          4m

NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   31m

NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/example-1-basic   3         3         3            2           4m

NAME                            DESIRED   CURRENT   READY     AGE
rs/example-1-basic-3444702635   3         3         2         4m
```

Notice the STATUS column of our Pods.

After few seconds the state of cluster should look like this -:

```bash
$ kubectl get all
NAME                                  READY     STATUS    RESTARTS   AGE
po/example-1-basic-3444702635-98lpn   1/1       Running   0          31s
po/example-1-basic-3444702635-h7qfm   1/1       Running   0          31s
po/example-1-basic-3444702635-zs87f   1/1       Running   0          4m

NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
svc/kubernetes   <IP_ADDRESS>     <none>        443/TCP   32m

NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/example-1-basic   3         3         3            3           4m

NAME                            DESIRED   CURRENT   READY     AGE
rs/example-1-basic-3444702635   3         3         3         4m
```


text:
# Verbal Valence

[![SWH](https://archive.softwareheritage.org/badge/origin/https://github.com/ETCBC/valence/)](https://archive.softwareheritage.org/browse/origin/https://github.com/ETCBC/valence/)
[![DOI](https://zenodo.org/badge/103229517.svg)](https://zenodo.org/badge/latestdoi/103229517)
[![Project Status: Unsupported – The project has reached a stable, usable state but the author(s) have ceased all work on it. A new maintainer may be desired.](https://www.repostatus.org/badges/latest/unsupported.svg)](https://www.repostatus.org/#unsupported)

[![etcbc](programs/images/etcbc.png)](http://www.etcbc.nl)
[![dans](programs/images/dans.png)](https://dans.knaw.nl/en)
[![tf](programs/images/tf-small.png)](https://annotation.github.io/text-fabric/tf)

### BHSA Family

* [bhsa](https://github.com/etcbc/bhsa) Core data and feature documentation
* [phono](https://github.com/etcbc/phono) Phonological representation of Hebrew words
* [parallels](https://github.com/etcbc/parallels) Links between similar verses
* [valence](https://github.com/etcbc/valence) Verbal valence for all occurrences
  of some verbs
* [trees](https://github.com/etcbc/trees) Tree structures for all sentences
* [bridging](https://github.com/etcbc/bridging) Open Scriptures morphology
  ported to the BHSA
* [pipeline](https://github.com/etcbc/pipeline) Generate the BHSA and SHEBANQ
  from internal ETCBC data files
* [shebanq](https://github.com/etcbc/shebanq) Engine of the
  [shebanq](https://shebanq.ancient-data.org) website

### Extended family

* [dss](https://github.com/etcbc/dss) Dead Sea Scrolls
* [extrabiblical](https://github.com/etcbc/extrabiblical)
  Extra-biblical writings from ETCBC-encoded texts
* [peshitta](https://github.com/etcbc/peshitta)
  Syriac translation of the Hebrew Bible
* [syrnt](https://github.com/etcbc/syrnt)
  Syriac translation of the New Testament

## About

Study of verbal valence patterns in Biblical Hebrew,

Part of the
[SYNVAR](https://www.nwo.nl/en/research-and-results/research-projects/i/30/9930.html)
project carried out at the
[ETCBC](http://etcbc.nl)

## Results

The results of this study are being delivered in several forms, summarized here.
It might be helpful to consult a description of the
[sources](https://github.com/ETCBC/valence/wiki/Sources)
first.

* **Visualization**: a
  [tutorial notebook](https://github.com/ETCBC/valence/blob/master/programs/senses.ipynb)
  showing the sense distribution of the 10 most frequent verbs;
* **Annotations**: a set of
  [annotations](https://shebanq.ancient-data.org/hebrew/note?version=4b&id=Mnx2YWxlbmNl&tp=txt_tb1&nget=v)
  in **SHEBANQ** showing the verbal valence analysis in context;
* **Data module**: a set of
  [higher level features](https://github.com/ETCBC/valence/tree/master/tf)
  in **text-fabric** format, storing the flowchart input data and outcomes;
* **Spreadsheets**: a set of
  [CSV files](https://github.com/ETCBC/valence/tree/master/source/4b)
  used in the workflows for data entry;
* **Documents**: a number flowcharts for individual verbs, to be found in the
  [wiki](https://github.com/ETCBC/valence/wiki)
  of this repository;
* **Program code**: a
  [bunch of Jupyter notebooks](https://github.com/ETCBC/valence/tree/master/programs)
  that describe and execute the following tasks:
  1. The data correction workflow, followed by enrichment;
  2. The application of the flowcharts to the whole corpus.

For more information, go to the [wiki of this repo](https://github.com/ETCBC/valence/wiki).

## Authors
* [Janet<EMAIL_ADDRESS>-
  [VU ETCBC](http://etcbc.nl) -
  linguistic researcher in Biblical Hebrew -
  author of the *flowcharts*;
* [Dirk Roorda](https://github.com/dirkroorda) -
  [DANS](https://dans.knaw.nl/en/front-page?set_language=en) -
  author of the notebooks and documentation and the supporting library
  [Text-Fabric](https://github.com/annotation/text-fabric).

## Date

Updated: 2017-09-14

Created: 2017-09-14

repository: ETCBC/valence

repo_name: ETCBC/valence


text:
# docker-magento1

[![Docker Automated Build](https://img.shields.io/docker/automated/sensson/magento1.svg)](https://hub.docker.com/r/sensson/magento1/) [![Docker Build Status](https://img.shields.io/docker/build/sensson/magento1.svg)](https://hub.docker.com/r/sensson/magento1/)

A base Magento 1.9 image that can be used to scale in production. This can
be used in combination with MySQL and Redis. It is opiniated and includes
support for Composer, ionCube, Redis, OPcache, and the required PHP modules
for a basic Magento installation.

It does not include Magento.

# Usage

An example `Dockerfile`

```
FROM sensson/magento1
COPY src/ /var/www/html/
```

# Persistent storage

The container assumes you do not store data in a folder along with the
application. Don't use Docker volumes for scale. Use CephFS, GlusterFS or
integrate with S3 or S3-compatible services such as [Fuga.io](https://fuga.io).

# Configuration

## local.xml

Once the container starts it will always change `app/etc/local.xml` to the
credentials that were specified as environment variable. You should never have
to save your credentials in git. Stay safe.

You can leave some settings empty such as your encryption key:

```
<crypt>
    <key></key>
</crypt>
```

and your database details:

```
<resources>
    <db>
        <table_prefix></table_prefix>
    </db>
    <default_setup>
        <connection>
            <host></host>
            <username></username>
            <password></password>
            <dbname></dbname>
            <active>1</active>
        </connection>
    </default_setup>
</resources>
```

Do not remove the settings completely and always leave `local.xml` in place.
Once the container starts it will automatically populate all required fields.

## Environment variables

Environment variable  | Description                   | Default
--------------------  | -----------                   | -------
MYSQL_HOSTNAME        | MySQL hostname                | mysql
MYSQL_USERNAME        | MySQL username                | root
MYSQL_PASSWORD        | MySQL password                | random
MYSQL_DATABASE        | MySQL database                | magento
TABLE_PREFIX          | Table prefix                  | Empty
CRYPTO_KEY            | Magento Encryption key        | Emtpy
URI                   | Uri (e.g. http://localhost)   | http://localhost
RUNTYPE               | Set to development to enable  | Empty

Include the port mapping in `URI` if you run your shop on a local development
environment, e.g. `http://localhost:3000/`.

## Development mode

Setting `RUNTYPE` to `development` will turn on public error reports. Anything
else will leave it off. It will also set `display_errors` to on in PHP. This is
set to off by default.


text:
# Overriding Type Class Instances

_April 2020_

_by Daniel Winograd-Cort_

I read a post by Cary Robbins titled
[Overriding Type Class Instances](http://caryrobbins.com/dev/overriding-type-class-instances-2/)
that describes a clever way to derive custom type class instances for types using
some type-level programming tricks and the `DerivingVia` extension.  It struck me
that row-types should be able to do nearly the same thing almost for free, and I
took it as a challenge to see if I could make it work.  It required a minor change
to the library (the addition of a specialized `coerce` function for records), but
otherwise it was quite straightforward.

## Example

Extensions and imports for this Literate Haskell file

```haskell
{-# LANGUAGE DerivingVia #-}
{-# LANGUAGE OverloadedLabels #-}
{-# LANGUAGE OverloadedStrings #-}
module OverridingTypeClassInstances where

-- Note that `Data.Row.Aeson` is not exported my the row-types library and
-- currently lives in the src\aeson directory.  You must put it in an
-- appropriate place and make sure to have `aeson` in your environment in order
-- to use this module.

import           Data.Aeson       (ToJSON(..))
import           Data.Char        (ord, toUpper)
import           Data.Coerce
import           Data.Row
import           Data.Row.Aeson   ()
import qualified Data.Row.Records as Rec
import           Data.Text        (Text)
import qualified Data.Text        as Text
import           GHC.Generics     (Generic)

newtype Uptext = Uptext { unUptext :: Text }

instance ToJSON Uptext where
  toJSON = toJSON . Text.toUpper . unUptext

newtype CharArray = CharArray { unCharArray :: String }

instance ToJSON CharArray where
  toJSON = toJSON . map (:[]) . unCharArray
```

Cary's result looks like the following:

```haskell
data MyRec = MyRec
  { foo :: Int
  , bar :: String
  , baz :: Text
  } deriving stock (Show, Eq, Generic)
    deriving (ToJSON)
      via Override MyRec
            '[ String `As` CharArray
             , "baz" `As` Uptext
             ]
```

The idea here is that the `MyRec` data type can have a `ToJSON` instance where
all `String` fields are encoded using the `ToJSON` functionality of the `CharArray`
type class and the `baz` field is encoded using the `ToJSON` of `Uptext`.  The
rest of Cary's post describes how he accomplishes this.

With row-types, it's currently not possible to do a wholesale modification based
on types, but we certainly have machinery for modifying individual fields.  Thus
instead, I propose a slightly different syntax, this time based on row-types
operators:

```haskell
data MyRec = MyRec
  { foo :: Int
  , bar :: String
  , baz :: Text
  } deriving stock (Show, Eq, Generic)
    deriving (ToJSON)
      via Override MyRec (
           "bar" .== CharArray
        .+ "baz" .== Uptext)
```

## Details

The `Override` type is actually very simple:

```haskell
newtype Override t (mods :: Row *) = Override { unOverride :: t }
```

A value of type `Override t mods` is a value of type `t` that will have certain
fields overridden according to `mods`.  The key is in how we define the `ToJSON`
instance for `Override`:

```haskell
instance
  ( ρ ≈ Rec.NativeRow t
  , ρ' ≈ mods .// ρ
  , BiForall ρ ρ' Coercible
  , Rec.FromNative t
  , Forall ρ' ToJSON
  ) => ToJSON (Override t mods) where
  toJSON = toJSON . Rec.coerceRec @ρ @ρ' . Rec.fromNative . unOverride
```
This may look a little intimidating, so let's take it piece by piece.  I'll
start with `unOverride` and work through the composed functions, calling out
elements of the context as they become relevant and necessary.

- `unOverride` is the simplest component.  We must unwrap the  `Override` newtype.

- `Rec.fromNative` is a convenient function for converting a native Haskell data
type value into a row-types record.  It produces a record with exactly the same
fields and types as the given record.  For instance, when called on a value of
type `MyRec`, it will produce a value of type
`Rec ("foo" .== Int .+ "bar" .== String .+ "baz" .== Text)`.  In order to do this,
we need the constraint `Rec.FromNative t`, and it additionally provides a type
synonym `Rec.NativeRow t` which will be equal to the row-type produced.   You can
see that in the  instance's context above, we bind the type variable `ρ` to this type.

- `Rec.coerceRec @ρ @ρ'` is a record coercion turning a record with row-type `ρ`
to one of of type `ρ'`.  This will only succeed if all of the types in `ρ` match
up and are coercible with all the types in `ρ'`, a fact that is captured by the
constraint `BiForall ρ ρ' Coercible`.  What is `ρ'`?  It is precisely `ρ`, but
overwritten with any row bindings in `mods` (this is captured in `ρ' ≈ mods .// ρ`).
For example,
`("bar" .== CharArray) .// ("foo" .== Int .+ "bar" .== String .+ "baz" .== Text)`
becomes `("foo" .== Int .+ "bar" .== CharArray .+ "baz" .== Text)`.

- `toJSON` is the `toJSON` function specialized to records with type `ρ'`, and
it requires the constraint `Forall ρ' ToJSON`, indicating that every field in
`ρ'` must have its own `ToJSON` instance.

Phew!  What does that all mean?  It means we can take a value of type `t`, convert
it to a row-types record, coerce any internal types to newtypes with `ToJSON` instances
we prefer, and then produce the JSON of the result all in one go.  And it works!
It's true that the instance definition is a little hairy, but thankfully we don't
need to mess around with any `Generic` code.

## Exploring Overrides

Cary defines an `override` shorthand and then proceeds to demo
some examples.  I'll do the same.

```haskell
-- | A version of 'Override' that accepts first the value and then the mods type.
override :: a -> (forall mods. Override a mods)
override = Override
```

Now we can write statements in GHCi like:

```
> v = MyRec 3 "foo" "text"
> encode $ override v @Empty
{"foo":3,"baz":"text","bar":"foo"}

> encode $ override v @("bar" .== CharArray .+ "baz" .== Uptext)
{"foo":3,"baz":"TEXT","bar":["f","o","o"]}
```

We also get pretty good type errors when we do things wrong.  For instance, if
we try to override the same field more than once:

```
> encode $ override v @("bar" .== CharArray .+ "bar" .== String)
<interactive>:4:1: error:
    • The label "bar" has conflicting assignments.
      Its type is both CharArray and String.
    • In the expression:
        encode $ override v @("bar" .== CharArray .+ "bar" .== String)
      In an equation for ‘it’:
          it
            = encode $ override v @("bar" .== CharArray .+ "bar" .== IntChar)
```

Alternatively, if you try to coerce to a type that's not coercible, you'll get
a good error:

```
> encode $ override v @("bar" .== Int)
<interactive>:5:1: error:
    • Couldn't match representation of type ‘[Char]’ with that of ‘Int’
        arising from a use of ‘encode’
    • In the expression: encode $ override v @("bar" .== Int)
      In an equation for ‘it’: it = encode $ override v @("bar" .== Int)
```

## Achievements and Limitations

With a simple `newtype` and a one-line `ToJSON` instance (the implementation of
the instance is a simple one line, although I'll admit the context takes a few
more), we've been able to recreate most of the expressiveness of
`generic-override`.  Of course, `generic-override` has one feature that we
don't: namely, being able to override all fields of a particular type in one go.
I can definitely see the use for this feature—for instance, making sure _all_
`Text` fields are encoded in a consistent, perhaps more concise, way—but I don't
see a way to do it elegantly with row-types at this time.[1](#myfootnote1)

But we do gain for what we've given up.  Without needing a `ValidateOverride`
type class, we have clear restrictions (and informative error messages) that
prevent us from duplicate overriding.  Additionally, we of course have all the
other benefits of row-types.

---

1: If/When GHC adopts the ability to use simple, unsaturated
type families, this will become possible.  For instance, one could write something like
```haskell
type family ToUptext t where
  ToUptext Text = Uptext
  ToUptext x = x
```
and then make the override modifications: `Rec.Map ToUptext (Rec.NativeRow MyRec)`.
This in itself is still slightly ugly, but unsaturated type families give us the
ability to write more higher-order type functions, such as a row-types `Filter`.
From there, it's a brief hop to a type-level function `FieldsOfTo MyRec Text Uptext`
which would produce a row-type containing all of the fields of `MyRec` that had
the type `Text`, now with the type `Uptext`.

repository: target/row-types

gha_language: Haskell

gha_license_id: MIT

repo_name: target/row-types


text:
Status: Internal-Only
Author: Jeff Solomon
CreateDate: 2016-03-14
ModifyDate: 2016-04-05

#GR-STWMIG (Steward-Hosted Migrated Data Sources)

**Client(s)**: [STW](../STW.md)
**Density Area**: Northeast

This is a group of sources that can be connected to from within the Steward network. They were all previously used in 3.x via a DRVS connector.

Full list of sources is:

|DBID | Name (Acronym) |
|-----|-----|
|2|Hyde Park (HYDEPARK)| MySQL |
|3| Nissage Cadet (NICAD)| MySQL |
|4|M. Morey Farizan (FARIZAN)| MySQL |
|5|Northeast Nephrology & Internal Medicine (NNIM)| MySQL |
|6|Zuhayr Hemady (HEMADY)| MySQL |
|7|Thomas Kenney (KENNEY)| MySQL |
|9|Ambama Clinic (AMBAMA)| MySQL |
|11|Alonso Medical (ALONSO)| MySQL |
|12|APG  Brockton (APGBROCK)| MySQL |
|13|APG Bridgewater (APGBRIDGE)| MySQL |
|17|Pleasant Valley Internists (PLSVAL)| MySQL |
|18|William Edwards (WEDWRDS)| MySQL |
|19|Sharda Kaul (KAUL)| MySQL |
|20|Michel Lirette (LIRETTE)| MySQL |
|21|Vascular and Vein Associates (VAVA)| MySQL |
|22|Merrimack Valley Pulmonary Associates (MVPA)| MySQL |
|23|Infectious Disease Associates (INFDA)| MySQL |
|24|Luba Tsypkin & Ashish Gandi (LTAG)| MySQL |
|25|Pediatric Professional (PEDPROF)| MySQL |
|26|AASP Allergy and Asthma Speciality (AASP)| MySQL |
|28|Charles S. Chen (CHEN)| MySQL |
|29|Dermatology Associates (DERMASSOC)| MySQL |
|31|Dr.  Stephen Sands (SANDS)| MySQL |
|32|Associates Internal Medicine (AIM) (AIM)| MySQL |
|34|Resil (RESIL)| MySQL |
|35|Timothy Anderson (ANDERSON)| MySQL |
|36|Derm Specialists (DERMSPEC)| MySQL |
|39|Alan Kurland (KURLAND)| MySQL |
|40|Neponset Valley Surgical (NEPVAL)| MySQL |
|41|Robert Patz & Mebel (PATZ)| MySQL |
|42|Steven Ross (ROSS)| MySQL |
|43|Paul Burns (BURNS)| MySQL |
|45|Manish Tandon (TANDON)| MySQL |
|46|Nicole McDonald (MCDON)| MySQL |
|47|Tural Pediatrics (TURALPED)| MySQL |
|49|Michael Romanowsky (RMNWSKY)| MySQL |
|50|Stephen Kovacs (KOVACS)| MySQL |
|51|Bijan Sadrnoori (SADRNRI)| MySQL |
|52|Leonid Kotkin (KOTKIN)| MySQL |
|53|Brian Hinnebusch (HNNBSCH)| MySQL |
|54|John T Frasca (FRASCA)| MySQL |
|55|St Annes Pain Management (SAPM)| MySQL |
|56|Millview Medical Joncas (MILLVW)| MySQL |
|57|Carney Pulmonary (CARNEY)| MySQL |
|58|CPN1 (CPN1)| MySQL |
|59|CPN 2 (CPN2)| MySQL |
|61|Good Sam Production (GSAM)| MySQL |
|62|New England Medical Group (NEMG)| MySQL |
|63|Andrade Medical Associates (ANDRADE)| MySQL |
|64|Kevin McCarthy (KMCCRTHY)| MySQL |
|65|Methuen Medical Group (METHUENMG)| MySQL |
|70|APG Easton (APGEASTON)| MySQL |
|71|Joseph Emma (EMMA)| MySQL |
|72|We Care (WECARE)| MySQL |
|73|Sharma (SHARMA)| MySQL |
|74|Sawyer (SAWYER)| MySQL |
|75|Raouf Sayegh (SAYEGH)| MySQL |
|76|Whittier-Merrimack Valley (WHITMERVAL)| MySQL |
|78|Whittier-Haverhill Family (WHITHAVRHL)| MySQL |
|81|Simon Ho (SMHO)| MySQL |
|82|Dr. Michael Kutka (KUTKA)| MySQL |
|83|Dr. Sidiqqi (SIDIQQI)| MySQL |
|84|Dr. Chapman (CHPMN)| MySQL |
|85|Dr. Maureen Norman (NRMN)| MySQL |
|88|Quincy Internal Med - Dr. Gales (QIMGALES)| MySQL |
|92|Prima CARE (PRIMACARE)| SQL Server |
|93|Associates in Nephrology, PC (ANEPHPC)| SQL Server |
|94|Yuliya Mandel, MD, PC (MANDEL)| SQL Server |
|95|Eric Cohen (ECOHEN)| SQL Server |
|96|Brigida Tironese-Call (TIRON)| SQL Server |
|97|Lydia Zuser (ZUSER)| SQL Server |
|98|Taunton Medical (TAUNTON)| SQL Server |
|99|Mill River Pediatrics (MILLRIV)| SQL Server |
|104|[Loew Family Practice (LOEWFAM)| SQL Server |

Connectivity details can be found on [Box](https://arcadia.box.com/s/pgejoftb0mvzbfzmz263owqcbi3brg8x)

## Sections:
* [Overview](#overview-and-architecture)
* [Custom Configurations](#custom-configurations)
* [Operations](#operations)
* [Data Source](#data-source)
* [Known Issues](#known-issues)
* [External Documentation Links](#external-documents)

##Overview and Architecture

### Implementation Round 1: Migration
[PRIMACARE](./PRIMACARE.md) and [CPN1](./CPN1.md) were chosen as the two pilot practices for the migration of the Steward AA instance from 3.6 (Steward hosted) to 4.x (Arcadia hosted).

Identical configurations (i.e. queries) will be used for all other Steward eCW MySQL (CPN1) and MSSQL (Prima CARE) connectors for this migration.

### Implementation Round 2: HCC/Risk Navigator

Second implementation round to update these queries for HCC Navigator. The scope of this changes is less than the changes required for front end.

Required query changes for this implementation round are:

1.  **New query** will be written and implemented to populated the **progress note table**
2.  Updated **assessment** query that fixes the **primary key** issue identified during the migration project
3.  Update **provider** query to set **provider active indicator** in accordance with Steward’s requirements
4.  Confirm that it is possible given existing encounter/charge records to switch from using encounter types to CPT codes for the **medical encounter** definition. This is considered our standard and preferred approach, so as long as we have the appropriate linkages to make this work, it’s probably best to switch. Given this is eCW and we’ve taken this approach with pretty much all other eCW connectors, I don’t anticipate any issues with this.
5.  Update **patient** query to map **SSN** according to logic in current 4.x eCW patient query.  All other mappings should not change.

For this implementation round, PRIMACARE (SQL Server) and ANDRADE (MySQL) are being used as pilots.

![](../../img/Connector-Client-DB-Extract-CDC.png)

###Database Connection Information

[See connectivity document on Box](https://arcadia.box.com/s/pgejoftb0mvzbfzmz263owqcbi3brg8x)

###Location Hierarchy Configuration

Locations seeds are not required at this time. Will be required in the future, but not until a second round.

##Custom Configurations

### Implementation Round 1: Migration

1. Queries for this connector are to be a direct conversion of existing DRVS queries into syntax that Informatica can use. There should be no updates or additions to these queries beyond what is needed to run the end-to-end ETL and match the content of the existing HDS feed.
2. The criteria for handoff acceptance are as follows:
- Row counts match counts extracted since most recent historical extract in 3.x; The full table row counts do not need to match exactly, due to data no longer existing in the same state in the eCW DB.
- Date field completeness -- % completeness of date fields should match those of the 3.x tables within a reasonable error. This is being tested due to the tight constraints placed on date formatting in Informatica.
3. **Seed data should match exactly that of the 3.x instance within the constraints of the new environment. No new seed mapping is required.**
4. `t_immunization` is not used. Immunizations at Steward are pulled into `t_maintenance` with the *maintenance_imm* query.

### Implementation Round 2: HCC/Risk Navigator

Updates to the above list:

1. This is no longer completely true. See [Overview](#overview-and-architecture) for more details.
2. Requirement for handoff is that the requirements listed above have been completed and validated to QA Team's satisfaction.
3. This is still valid with the exception of medical encounter definition, which should be switch to CPT codes if possible.
4. This is still valid. This change will be implemented in Implementation Round 3.

###SFTP Customization for Steward Sources

See [**Steward Custom SFTP Workflow**](.\STW-Custom-SFTP-Workflow.md).

##Data Source

The data for this connector is pulled from [eCW 9](../../Tech_Delivery/EHR-Documentation/eCW.md).

##Operations
|Restriction | |
|-----|-----|
|Time of day extract/access restrictions| None |
|Is the database production?| No  |
|Frequency of Extracts| Nightly |

##Known Issues

* Queries are based off of historical eCW queries, i.e., certain known issues may still apply.
* Updates will be applied in a future implementation round. More details to come.
* Additional Client Literature [Click Here](https://arcadia.app.box.com/files/0/f/3940812891/Per-Site%20Gap%20Analysis)

##External Documents
- [JIRA Open Issues](https://jira.arcadiasolutions.com/issues/?jql=(labels%20%3D%20GR-STWMIG%20or%20%22Data%20Source%20Acronym%22%20~%20GR-STWMIG)%20and%20status%20!%3D%20Closed)
- [Connector Deployment History](https://github.com/arcadia/qdw/wiki/connector-version)
- [Build Request](https://arcadia.box.com/s/3pctsu7aqbvxzonk7b020khs0x1zerg9)
- SOW (*Unknown. Follow up with the Solution Architect*)

repository: omarnema/mkdocs-material

repo_name: omarnema/mkdocs-material


text:
# form-render

> Yet another form render solution for vue

[![NPM version](https://badgen.net/npm/v/form-render)](https://npmjs.com/package/form-render)
[![NPM download](https://badgen.net/npm/dm/form-render)](https://npmjs.com/package/form-render)
[![License](https://badgen.net/npm/license/form-render)](./LICENSE)
[![$donate](https://badgen.net/badge/$/donate/f2a)](https://patreon.com/evillt)

## Getting started

You might want to run the `example` to see what it can do

```bash
# We assume that you have already installed the required dependencies.

# Build library
yarn build

# Run example
yarn example
```

## Config type check

FormRender expose the `Config` type you can use to type-check your form config:

```ts
// form-config.ts
import { Config } from 'form-render'

const config: Config = {
  props: {},
  items: [...]
}

export default config
```

It also works in `.js` file:

```js
/** @type {import('form-render').Config} */
const config = {
  props: {},
  items: [...]
}

export default config
```

## Contributing

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3.  Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Credits

This repo(form-render) won't exist without the inspirations from following projects or articles:

- Form-render itself
- [@femessage/el-form-render](https://github.com/femessage/el-form-render)
- [elv-form](https://github.com/evillt/elv-form)
- [NoForm](https://github.com/alibaba/nopage/tree/master/packages/form) and [Article](https://zhuanlan.zhihu.com/p/44120143?utm_source=wechat_timeline&utm_medium=social&from=timeline)
- [再也不想写表单了](https://zhuanlan.zhihu.com/p/48241645)
- [Form 表单组件设计之路](https://zhuanlan.zhihu.com/p/56280821)
- [ncform](https://github.com/ncform/ncform)

## Author

**form-render** © [EVILLT](https://github.com/evillt), Released under the [MIT](./LICENSE) License.

Authored and maintained by **EVILLT** with help from contributors ([list](https://github.com/evillt/form-render/contributors)).

> [evila.me](https://evila.me) · GitHub [@evillt](https://github.com/evillt) · Twitter [@evillt](https://twitter.com/evillt)


text:
*Note* - We currently only support Linux

# StressTestSuite
A collection of scripts to generate common competitive programming testcases on Linux.

# What is Stress Testing?
Have you ever been in sitauation where you have written a state-of-the-art algorithm for some task but it your code is generating incorrect output? If yes, have you ever felt lazy to manually generate test cases to detect the bug in your code? Well stress testing solves this very problem. The idea is that instead of generating test cases manually, you write a simple brute force solution that solves the same problem that you are trying to solve with your state-of-the-art algorithm and then leave it to your computer to randomly generate test cases till the ouptuts of both programs don't match.

# How to use

1. Write a bruteforce solution, compile it, and name the executable `brute`.
2. Compile the solution you want to stress-test and name the executable `A`.
3. At the end of `gen.py`, add your code to generate desired test cases.
4. Let the stress testing begin! Run `test.sh` and let it do the hard work for you. Once it finds a mismatch, it will print "Wrong Answer" on your screen and the failed testcase can be found in `testcase.in`. Your program's output on this test case can be found in the file `A.out` and your bruteforce solution's output can be found in `B.out`

# What does each file do?

1. `gen.py` : Use this to generate random testcases by invoking the various functions provided
2. `check.py` : Script used by `test.sh` to check if outputs of the two executable programs match.
2. `test.sh` : This shell scripts creates a random testcase, runs two exectuables simultaneously on the random testcase and checks if the outputs match. It repeats this for 10,000 random test cases.

gha_language: Python


text:
# SunPy Sphinx Theme

[![Build Status](https://travis-ci.org/sunpy/sunpy-sphinx-theme.svg?branch=master)](https://travis-ci.org/sunpy/sunpy-sphinx-theme)

This repository contains the still work in progress sphinx theme for the new website and documentation.

To use put this in your `conf.py` file:

    from sunpy_sphinx_theme.conf import *

We have live version of our documentation that uses SunPy Website source branch and the master version of the theme, [here](http://sunpy.org/sunpy-sphinx-theme).

repository: nabobalis/sunpy-sphinx-theme

repo_name: nabobalis/sunpy-sphinx-theme


text:
# Workshop: Python in Science and Research

Dive into the following topics

- Numeric Computation
- Data Visualization
    - basic plotting
- Machine Learning
- Social Network Analysis

## Up Front Preparations

As this is a notebook class, you should try to setup Python and Git on your machine before we start with the actual workshop.

### Git Installation
The course will be available in github. The most convenient way to fetch it and updates of it from there is installing a [Git Client](https://git-scm.com/downloads).

Please refer to [Basic Git](https://git-scm.com/book/en/v2) for further information, how to work with `git`.

### Python Distribution Installation
The easiest way to do so is by installing the [Anaconda Distribution](https://www.continuum.io/).
Just download and install the current distribution with Python 3.6 or higher as described [in the Anaconda Installation Instructions](https://docs.continuum.io/anaconda/install).

Then test the Anaconda installation by running your first notebook:
Therefore
- `git clone https://github.com/plipp/informatica-pfr-2017.git` and
- run in a terminal:
```bash
$ jupyter-notebook
```
, open in your browser [The Jupyter Notebook for the initial Installation Test](./nbs/0-a-Test%20of%20the%20Installation.ipynb) and run it ...
If all runs through and you see as output in the last cell `All looks good!` you are done!

### Additional Python Package Installation

Further on in the workshop the following additional packages are required.
If you don't succeed to install them upfront, don't worry: If help is needed, we will have enough time to install them together in the course.
```bash
    conda install seaborn

    conda install -c scitools cartopy=0.15.0
    # or
    conda install -c conda-forge cartopy=0.15.1

    conda install networkx
    pip install python-louvain

    pip install graphviz

    pip install xlrd
```
On OS-Level you also will need graphviz.
Please check the [Graphviz Homepage](http://www.graphviz.org/) about how to install on your Machine.

You can check, whether the additional packages also work fine, with [The Jupyter Notebook for the Test of the additional Components](./nbs/0-b-Additional%20Component%20Installation%20Test.ipynb).

## Refresher - Python(3) Basics
If you need a refresher of your Python knowledge the [Interactive Python Tutorial](https://www.learnpython.org/) is a good starting point.

The Lectures
- `Learn the Basics`: All and
- `Advanced Tutorials`
    - Generators
    - List Comprehensions
    - Multiple Function Arguments
    - Sets
    - Partial functions

should be sufficient for attending the Workshop `IF PRO 02 Python für Wissenschaft und Forschung`.

Also [A whirlwind tour of Python](http://www.oreilly.com/programming/free/a-whirlwind-tour-of-python.csp) is a good starting point.

# Further Reading/Resources

This Workshop is inspired by

## MOOCs

### In Python
- [edX - Python for Research](https://www.edx.org/course/using-python-research-harvardx-ph526x) (free)
- [Coursera - Applied Data Science with Python Specialization](https://www.coursera.org/specializations/data-science-python) (free audit)
- [Udacity - Intro to Data Analysis](https://www.udacity.com/course/intro-to-data-analysis--ud170) (free)

### In R
- [The Analytics Edge](https://www.edx.org/course/analytics-edge-mitx-15-071x-3)

## Primers
- [Python Data Science Primer](https://github.com/docmarionum1/python-data-science-primer) (free)

## Books

- [Packt - Practical Datascience Cookbook](https://www.packtpub.com/big-data-and-business-intelligence/practical-data-science-cookbook)

## Free Books/Juypter-Notebooks

- [Python Data Science Handbook](http://nbviewer.jupyter.org/github/jakevdp/PythonDataScienceHandbook/blob/master/notebooks/Index.ipynb)
- [Materials and IPython notebooks for "Python for Data Analysis" by Wes McKinney](https://github.com/wesm/pydata-book)(jupyter-nbs free)

## Library Documentation

- [Numpy](http://www.numpy.org/)
- [Pandas](http://pandas.pydata.org/)
- [Matplotlib](http://matplotlib.org/)
- [NetworkX](http://networkx.readthedocs.io)


text:
Changelog:

This page contains a list of recent updates made to the Codio BoxParts.

### April 29th, 2015
- **Additions**
  - xserver 0.1 beta
- **Improvement**
  - python3 to 3.4.3

### Jun 2nd, 2015
- **Improvement**
  - googleappengine to 1.9.21
  - googleappenginego to 1.9.21
  - googleappenginejava to 1.9.21

### April 29th, 2015
- **Additions**
  - [hub](https://hub.github.com/)
- **Improvement**
  - clasp to 3.1.1
  - gringo to 4.4.0
  - Racket to 6.1.1
  - scons to 2.3.4
  - valgrind to 3.10.1
  - tig to 2.0.3
  - ZeroMQ to 4.0.5
  - PHPMyAdmin to 4.3.10
  - RabbitMQ to 3.4.4
  - RethinkDB to 1.15.3-1
  - MongoDB to 3.0.0
  - Scala to 2.11.6
  - Phalcon to 2.0.0

### April 14th, 2015
- **Additions**
  - luarocks
- **Improvement**
  - openldap to 2.4.40
  - berkeley_db to 6.1.23
  - pypy to 2.4.0

### March 7th, 2015
- **Additions**
  - jq
  - boot
- **Improvement**
  - tomcat updated to 8.0.20
  - the_silver_searcher to 0.29.1
  - swig to 3.0.5
  - setuptools to 12.3

### March 1st, 2015
- **Additions**
  - cppcheck
- **Improvement**
  - tig updated to 2.0.3
  - protobuf updated to 2.6.0
  - r_base updated to 3.1.2
  - racket updated to 6.1.1
  - fish updated to 2.1.2
  - re2c updated to 0.14

### February 22nd, 2015
- **Additions**
  - lftp
- **Improvement**
  - cargo_nightly updated to 0.0.1-pre-nightly-43755c0_2015-02-19 (thanks @adamreid)
  - rust updated to 1.0.0-alpha2 (thanks @adamreid)
  - rust_nightly updated to 1.0.0-nightly-522d09dfe_2015-02-19' (thanks @adamreid)

### February 16th, 2015
- **Additions**
  - frcon
- **Improvement**
  - libcairo2 updated
  - libgif updated
  - pixman updated

###  January 5th, 2015
- **Improvement**
  - fish updated to 2.1.1
  - freepascal updated to 2.6.4
  - freetype updated to 2.5.4
  - glib updated to 2.43.2
  - googleappengine updated to 1.19.17
  - googleappenginego updated to 1.19.7
  - googleappenginejava updated to 1.19.7
  - grails updated to 2.4.4
  - groovy updated to 2.3.8
  - image_magick updated to 6.9.0-3
  - googlecloudsdk updates to 0.9.41
  - influxdb updated to 0.8.7
  - jruby updated to 1.7.17
  - leiningen updated to 2.5.0
  - libffi updated to 3.2.1
  - libpcap updated to 1.6.2
  - libtool updated to 2.4.4
  - lua updated to 5.2.3
  - mc updated to 4.8.13
  - memcached updated to 1.5.21
  - phantomjs updated to 1.9.8

### December 25th, 2014
- **Improvement**
  - mono updated to the 3.10.0

### December 16th, 2014
- **Improvement**
  - composer updated to the latest dev 1.0

### December 12th, 2014
- **Improvement**
  - ack updated to 2.14
  - apr_util updated to 1.5.4
  - apache2 updated to 2.4.10
  - beanstalkd updated to 1.10
  - berkeley_db updated to 6.1.19
  - boost updated to 1.57.0
  - cabal updated to <IP_ADDRESS>
  - cloudfoundry updated to 6.8.0
  - cmake updated to 3.0.2
  - couchdb updated to 1.6.1
  - dropbox updated to 3.0.3
  - elasticbeanstalk updated t0 2.6.4
  - elasticsearch updated to 1.4.1
  - go-lang updated to 1.4

### December 11th, 2014
- **Improvement**
  - dart updated to 1.8.3
  - erlang updated to 17.3
  - mongodb updated to 2.6.6
  - nginx updated to 1.7.8
  - python3 updated to 3.4.2
  - scala updated to 2.11.4
  - sbt updated to 0.13.7

### December 4th, 2014
- **Additions**
  - rustup (thanks @sazzer)

### November 29th, 2014
- **Additions**
  - GNU mpfr (thanks @moollaza)
- **Improvement**
  - oCaml updated to 4.02.1
  - OPAM updated to 1.2.0

### November 11th, 2014
- **Improvement**
  - googleappengine updated to 1.9.15
  - googleappenginego updated to 1.9.15
  - googleappenginejava updated to 1.9.15

### November 5th, 2014
- **Additions**
  - swi_prolog
- **Improvement**
  - dart updated to 1.7.2 (thanks @tbodt)
  - elixir updated to 1.0.2
  - googleappenginego updated to 1.9.14
  - googlecloudsdk updated to 0.9.35

### October 30th, 2014
- **Improvement**
  - meteor updated to 1.0

### October 28th, 2014
- **Improvement**
  - maven updated to 3.2.3 (thanks @tbodt)

### October 23rd, 2014
- **Additions**
  - gdal (thanks @22kaj22)

### October 21st, 2014
- **Additions**
  - freetds (thanks @jondkinney)

### October 20th, 2014
- **Additions**
  - php5-gettext
  - taglib (thanks @joeyfromspace)

### October 19th, 2014
- **Improvement**
  - adminer updated to 4.1.0 (thanks @nblackburn)
  - rethinksv updated to 1.15.1 (thanks @nblackburn)

### October 15th, 2014
- **Additions**
  - valgrind (thanks @jesserayadkins)

### October 10th, 2014
- **Improvement**
  - cargo-nightly updated to 0.0.1-pre-nightly-861c07f_2014-10-07 (thanks @adamreid)
  - rust updated to 0.12.0 (thanks @adamreid)
  - rust-nightly updated to 0.12.0-nightly-63fe80e1f_2014-10-08 (thanks @adamreid)

### September 24th, 2014
- **Additions**
  - gitftp

### September 18th, 2014
- **Additions**
  - cargo-nightly (thanks @adamreid)
- **Improvement**
	- meteor updated to <IP_ADDRESS>
	- rust-nightly updated to 0.12.0-pre-nightly-0e784e168_2014-09-16 (thanks @adamreid)

### September 17th, 2014
- **Improvement**
  - googleappengine updated to 1.9.11
  - googleappenginego updated to 1.9.11
  - googleappenginejava updated to 1.9.11 (thanks for all @eMxyzptlk)

### September 11th, 2014
- **Additions**
  - freetds
  - php_mssql
  - php5_pdo_dblib
- **Improvement**
	- pip fix PATH export
  - neko add export to LD_LIBRARY_PATH

### September 9th, 2014
- **Additions**
  - haxe
  - neko
  - uuid
- **Improvement**
	- postgresql updated to 9.3.5

### September 8th, 2014
- **Improvement**
  - pip updated to 1.5.6
  - setuptools updated to 5.7
  - virtualenv updated to 1.11.6

### September 4th, 2014
- **Improvement**
	- python2 updated to 2.7.8
- **Fixed**
	- python3 support for sqlite3
- **Additions**
	- php5-phalcon (thanks @leob)

### August 8th, 2014
- **Improvement**
	-	meteor updated to 0.8.3

### August 6th, 2014
- **Improvement**
	-	grails updated to 2.4.3

### August 2nd, 2104
- **Improvement**
	-	googlecloudsdk updated to 0.9.28

### July 31st, 2014
- **Improvement**
	-	python3 updated to 3.4.1-1

### July 29th, 2014
- **Additions**
	- php5-sockets
- **Improvement**
	- php (and associated packages) updated to 5.5.15 (thanks @Garbee)

### July 23rd, 2014
- **Improvement**
	- composer updated to 1.0.0-20140724

### July 17th, 2014
- **Fixed**:
  - go installation issues (thanks @mikeroosa)
  - elasticbeanstalk package updated
- **Improvement**
	- ghc updated to 7.8.3

### July 14th, 2014
- **Additions**:
  - enchant
  - php5-apcu
  - php5-enchant
- **Improvement**:
  - go updated to 1.3

### July 5th, 2014
- **Additions**:
  - tree (thanks @juanpabloaj)
- **Improvement**:
  - rust updated to 0.11 (thanks @adamreid)

### June 26th, 2014
- **Additions**:
  - rust-nightly  (thanks @adamreid)
  - snappy
  - spidermonkey
- **Improvement**:
  - rust updated to 0.10 (thanks @adamreid)

### June 23rd, 2014
- **Additions**:
  - couchdb
  - ctags
  - elasticbeanstalk
  - elixir
  - erlang16
  - freetype
  - googleappenginego
  - googleappenginejava
  - googlecloudsdk
  - influxdb
  - jython
  - leveldb
  - libmad
  - protobuf
  - pypy
  - rethinkdb
  - sbt
  - zeromq
  - zip
- **Improvement**:
  - ant updated to 1.9.4
  - apache2 updated to 2.4.9
  - apr updated to 1.5.1
  - composer udpated to 1.0.0-20140623
  - dart updated to 1.4.3
  - erlang updated to 17.0
  - googleappengine updated to 1.9.5
  - meteor updated to 0.8.1
  - phantomjs updated to 1.9.7
  - php5-gd updated to 5.5.10-2
  - phpunit updated to 4.0.14
  - python3 updated to 3.4.1
  - tomcat updated to 7.0.54

### June 13th, 2014
- **Improvements**:
	- postgresql updated to 9.3.4

### June 11th, 2014
- **Additions**:
    - jruby
    - libmemcached
    - php5-memcached
- **Improvements**:
    - mongodb updated to 2.6.1
    - php5-mongo updated to 1.5.3

### May 19th, 2014
- **Improvements**:
    - aspcud updated to 1.9.0-1.
    - opam updated to 1.1.1-20140519.
- **Additions**:
    - clasp
    - gmp
    - gringo
    - scons

### May 5th 2014
- **Improvements**:
    -  python3 updated to 3.4.0.
    -  composer updated to 1.0.0-20140501.
    -  opam was rebuilt.
- **Additions**:
    -  aspcud
    -  bison
    -  boost
    -  flex
    -  glib
    -  htop
    -  libffi
    -  libpcap
    -  Midnight Commander (`mc`)
    -  ncurses
    -  racket
    -  re2c

repository: ijobling/boxparts

repo_name: ijobling/boxparts


text:
# Packmon
Packet analyzer visualizer with capture. Packmon is interpreted as a wireshark like tool running on your browser. This is built using nodeJS backend coupled with a AngularJS front-end.

## Getting Started
To get started, git clone the repository using `git clone https://github.com/satkumar/packmon.git` and then in the project directory, install node dependencies using `npm install` and bower dependencies using `bower install`. This assumes that you already have node (with nodemon module) and bower installed globally (`sudo npm install -g bower`). Then to start the app use `sudo npm start`. The sudo is due to the fact that this application has dependencies on node-pcap and to be able to promiscuously listen on different local interfaces, it needs sudo permission levels.

## Documentation
Packmon is a nodejs-angularjs hybrid app. The nodejs serves as a backend wrapper to offer REST like functions to pcap underneath and angularjs is the front-end to serve a single page app to perform packet captures/analysis. The app depends on [node-pcap](https://github.com/mranney/node_pcap) which is a nodejs module for libpcap native module.

## Contributing
To start contributing please branch from this repository and submit pull requests to be merged on to the main branch.

## License
Copyright (c) 2014 Sathiish Kumar. Licensed under the MIT license.

repository: satkumar/packmon

repo_name: satkumar/packmon


text:
---
title: Our Targets
description: Our Targets
permalink: /key-focus-areas/our-targets/
---

![Overview](/images/framework/framework_overview.jpg)

View our Infographics

#### Our Key Targets for the Green Plan

New targets announced at the Joint Segment on Sustainability (Committee of Supply 2021):

Add over 130 ha of new parks, and enhance around 170 ha of existing parks with more lush vegetation and natural landscapes by end-2026.

"80% of new buildings to be Super Low Energy buildings from 2030, and 80% improvement in energy efficiency over 2005 baseline for best-in-class green buildings by 2030

New registrations of diesel cars and taxis to cease from 2025

8 EV-Ready Towns with chargers at all HDB carparks by 2025

All new car and taxi registrations to be of cleaner-energy models from 2030

60,000 charging points nationwide, including 40,000 in public carparks and 20,000 in private premises by 2030

- Plant [1 million more trees.](../city-in-nature/#:~:text=One%20million%20more%20trees%20will%20be%20planted%20across%20our%20island){:class="external-link"}
- Increase [solar deployment](../energy-reset/#:~:text=Our%20solar%20energy%20deployment%20will%20quadruple%20by%202025){:class="external-link"} to 1.5 giga-watt peak (GWp) by 2025, and at least 2 GWp by 2030.

- Expand [cycling network](../sustainable-living/#:~:text=green%20commutes){:class="external-link"} to 1,320km by 2030.
- Increase rail network to 360km by early 2030s.

- [Reduce waste](../sustainable-living/#:~:text=Circular%20Economy){:class="external-link"} sent to our landfill per capita per day by 20% by 2026, with the goal of reaching 30% by 2030.
- Increase share of trips taken on [mass public transport](../energy-reset/#:~:text=Transport){:class="external-link"} to 75% by 2030.
- At least 20% of [schools](../sustainable-living/#:~:text=20%%20of%20schools%20to%20be%20carbon%20neutral%20by%202030){:class="external-link"} to be carbon neutral by 2030.
- Promote [sustainable fuels](../energy-reset/#:~:text=Transport){:class="external-link"} for international trade and travel.
- Phase out [refrigeration and air-conditioning equipment that use high global warming potential (GWP) refrigerants](https://www.nea.gov.sg/media/news/news/index/nea-introduces-measures-to-reduce-greenhouse-gas-emissions-from-refrigeration-air-conditioning){:class="external-link" target="_blank"} from 4th quarter 2022.
- Use 15% [less energy in HDB towns](../energy-reset/#:~:text=Housing){:class="external-link"} by 2030.

- Produce [30%](../resilient-future/#:~:text=30-by-30%20target){:class="external-link"} of our nutritional needs by 2030 locally (30-by-30 target).

- Introduce an [Enterprise Sustainability Programme](../green-economy/#:~:text=This%20programme){:class="external-link"}, to help enterprises, especially SMEs, embrace sustainability and develop capabilities in this area.
- Create new and diverse job opportunities in sectors such as green finance, sustainability consultancy, verification, credits trading and risk management.
- Be a leading centre for [Green Finance](../green-economy/#:~:text=Green%20Finance%20Masterplan){:class="external-link"} in Asia and globally, by building up the financial sector’s resilience to environmental risks, developing green financial solutions, build knowledge and capabilities, and leveraging innovation and technology.
- Promote homegrown innovation under the [Research and Innovation & Enterprise Plan 2025](../green-economy/#:~:text=%28RIE2025%29){:class="external-link"}, and attract companies to anchor their R&D activities in Singapore to develop new sustainability solutions.
- Green 80% of buildings by Gross Floor Area by 2030

#### Explore the pillars

[![Ideas](/images/framework/framework_ideas.jpg)](https://form.gov.sg/6013d365bedd790011bb9c86)

repository: ouningfei/mse-sgp

repo_name: ouningfei/mse-sgp


text:
[![Conference attendee](https://devternity.com/shields/fellow.svg)](https://devternity.com) [![Build Status](https://travis-ci.org/latcraft/event-manager.svg?branch=master)](https://travis-ci.org/latcraft/event-manager)

# Event manager

Automation tasks for event publishing and support. Most of the tasks are executable through the [CraftBot](https://github.com/latcraft/event-manager/blob/master/BOT.md) commands.

> **NOTE:** For running automation tasks locally, copy contents of the `local.properties` file from the `latcraft/passwords` project to the `local.propeties` file.

## Event publishing

Event publishing process consists of the following steps:

0. **Manual:** Create data record for the event inside `events.json` (https://github.com/latcraft/website/blob/master/data/events.json) and push to Git.

   > **WARNING:** make sure that you removed EventBrite's eventId from the new event record. Otherwise, there is a risk of data corruption.

1. **Automated:** Publish event on EventBrite using the following task:

        gradlew publishEventOnEventBrite

   Or the following `/craftbot` command:

        /craftbot publish eventbrite

   > **WARNING:** This task MUST be executed FIRST and event lead must wait until data inside `events.json` is updated since other tasks depend on it.

   It is safe to rerun this task several times after the first publication if there are any changes in the event description.

2. **Automated:** Generate event cards using the following task:

        gradlew publishCardsOnS3

    Or the following `/craftbot` command:

        /craftbot publish cards

    Cards will be generated on AWS S3 share. Links to the cards will be published inside `#craftbot` channel in Slack.

    > **WARNING:** It is a responsibility of the event lead to share cards at convenient times on social networks.

    Different cards have different purposes (check the *Event cards* section below).

    It is safe to run this task several times if there are any updates to the event data.

3. **Automated:** Copy all contacts from EventBrite to SendGrid using the following task:

        gradlew copyContactsFromEventBriteToSendGrid

    Or the following `/craftbot` command:

        /craftbot copy contacts 4

4. **Automated:** Create invitation e-mail on SendGrid using the following task:

        gradlew publishCampaignOnSendGrid

    Or the following `/craftbot` command:

        /craftbot publish sendgrid

    Link to the e-mail HTML will be published inside `#craftbot` channel in Slack.

     > **WARNING:** Verify e-mail's content and layout before executing next task.

     > **WARNING:** This task MUST be executed after `publishEventOnEventBrite`.

    It is safe to run this task several times.

5. **Automated:** Send the invitation letter using the following task:

        gradlew sendCampaignOnSendGrid

    Or the following `/craftbot` command:

        /craftbot send campaign

    > **WARNING:** This task is not reversible. Double-check HTML e-mail message from previous step before proceeding.

    > **NOTE:** This task is safe to be called multiple times, because explicit check is done on SendGrid level to verify that campaign has not already been sent.

6. **Manual:** Tweet about the event and speakers using LatCraft Twitter account and cards generated above. Pin the tweet about event. Use `normal_event_card_v3`, `workshop_event_card_v1` or `workshop_event_card_v2` card for event and `speaker_card_v2` for speakers.

7. **Manual:** Create Lanyrd event.

8. **Manual:** Create Facebook event. Use `normal_event_facebook_background_v2` or `workshop_facebook_background_v1` card for event background. Use `normal_event_card_v3`, `workshop_event_card_v1` or `workshop_event_card_v2` card for Facebook posts. Use `speaker_card_v2` for Facebook posts about speakers.

9. **Manual:** Create LinkedIn post. Use `normal_event_card_v3`, `workshop_event_card_v1` or `workshop_event_card_v2` card for event announcement post.

## Event cards

- `normal_event_card_v1` (**DEPRECATED**): use for Twitter, LinkedIn; features: **Periscope Video**

    > **WARNING:** Only use this card if we go back to using Periscope. Otherwise use cards with Facebook video streaming.

- `normal_event_card_v2` (**DEPRECATED**): use for Twitter, LinkedIn; features: **Periscope Video**

    > **WARNING:** Only use this card if we go back to using Periscope. Otherwise use cards with Facebook video streaming.

- `normal_event_card_v3`: use for Twitter, LinkedIn; features: **Facebook Video**

- `normal_event_facebook_background_v1`: (**DEPRECATED**): use for **Facebook Event Page background**; features: **Periscope Video**

    > **WARNING:** Only use this card if we go back to using Periscope. Otherwise use cards with Facebook video streaming.

- `normal_event_facebook_background_v2`: use for **Facebook Event Page background**; features: **Facebook Video**

- `workshop_facebook_background_v1`: use for **Facebook Event Page background**; features: **Bring Laptop**

- `workshop_event_card_v1`: use for Twitter, LinkedIn; features: **Bring Laptop**

- `workshop_event_card_v2`: use for Twitter, LinkedIn; features: **Bring Laptop**

- `speaker_card_v1` (**DEPRECATED**): use for Twitter, LinkedIn, Facebook; features: **Periscope Video**

- `speaker_card_v2`: use for Twitter, LinkedIn, Facebook; features: **Facebook Video**

repository: latcraft/event-manager

gha_language: Groovy

repo_name: latcraft/event-manager


text:
# Trifolium amabile var. hemsleyi (Lojac.) D.Heller & Zohary VARIETY

#### Status
ACCEPTED

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
M. Zohary & D. Heller, The genus Trifolium 127. 1984

#### Original name
Trifolium hemsleyi Lojac.

### Remarks
null

repository: mdoering/backbone

repo_name: mdoering/backbone


text:
v1.0.0 2015-06-17 Cambridge (UK)
--------------------------------

- Updated for Unicode 8.0.0
  Incompatible release, new variants cases are introduced, see commit
  adbb5efc036 for details.

v0.9.1 2014-12-23 Cugy (VD)
---------------------------

- Add access to the `Line_break`, `Grapheme_cluster_break`, `Word_break` and
  `Sentence_break` Unicode properties. See the `Uucp.Break` module.
- Improvements and fixes to the minimal Unicode Introduction.

v0.9.0 2014-06-28 Cambridge (UK)
-------------------------------

First release. Part of the work was sponsored by OCaml Labs.

repository: yallop/uucp

repo_name: yallop/uucp


text:
# Graphitex

Graphite client for Elixir with zero dependencies

[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/msoedov/graphitex/blob/master/LICENSE)
[![Hex Version](https://img.shields.io/hexpm/v/graphitex.svg)](https://hex.pm/packages/graphitex)
[![Build Status](https://travis-ci.org/msoedov/graphitex.svg?branch=master)](https://travis-ci.org/msoedov/graphitex)

## Installation

If [available in Hex](https://hex.pm/docs/publish), the package can be installed as:

  1. Add `graphitex` to your list of dependencies in `mix.exs`:

  ```elixir
  def deps do
    [{:graphitex, "~> 0.1.0"}]
  end
  ```

  2. Ensure `graphitex` is started before your application:

  ```elixir
  def application do
    [applications: [:graphitex]]
  end

  ```
  3. Set up configuration in `config.config.exs`:

  ```elixir
  config :graphitex, host: '<IP_ADDRESS>', port: 2003

  ```
  4. API:

  ```elixir
  Graphitex.metric(4, "aws.cluster_one.avg_cpu")
  # or
  Graphitex.metric(4, ["aws", "cluster_one", "avg_cpu"])
  # or
  Graphitex.metric(41.0, [:aws, :cluster_one, :avg_cpu])
  ```

  by default `:os.system_time(:seconds)` used as timestamp, but you can pass `ts` as an argument

  ```elixir
  Graphitex.metric(41, "aws.cluster_one.avg_cpu",:os.system_time(:seconds))

  ```
  likewise there is a shortcut

  ```elixir
  Graphitex.metric(41, "aws.cluster_one.avg_cpu", Graphitex.now)

  ```

  Insert batch:
  ```elixir
   [{4, "client.transactions.east"},
    {2, "client.transactions.west"},
    {5, "client.transactions.north", Graphitex.now}
   ]
  |> Graphitex.metric_batch(batch)

  ```

repository: msoedov/graphitex

gha_language: Elixir

repo_name: msoedov/graphitex


text:
# bash-glob [![NPM version](https://img.shields.io/npm/v/bash-glob.svg?style=flat)](https://www.npmjs.com/package/bash-glob) [![NPM monthly downloads](https://img.shields.io/npm/dm/bash-glob.svg?style=flat)](https://npmjs.org/package/bash-glob) [![NPM total downloads](https://img.shields.io/npm/dt/bash-glob.svg?style=flat)](https://npmjs.org/package/bash-glob) [![Linux Build Status](https://img.shields.io/travis/micromatch/bash-glob.svg?style=flat&label=Travis)](https://travis-ci.org/micromatch/bash-glob)

> Bash-powered globbing for node.js

Please consider following this project's author, [Jon Schlinkert](https://github.com/jonschlinkert), and consider starring the project to show your :heart: and support.

## Install

Install with [npm](https://www.npmjs.com/):

```sh
$ npm install --save bash-glob
```

**Install bash 4.3 or later**

I recommend using [homebrew](https://github.com/Homebrew/homebrew-core) to install/upgrade bash:

```sh
$ brew upgrade bash
```

## Why?

The initial motivation was to use this for generating the `expected` values for comparisons in tests. But as it turns out, this is faster than node-glob in most cases I've tested.

Moreover, this supports the majority of the feature-functionaly in node-glob, and it's more Bash-compliant since, well, it **is** Bash.

**Edge cases**

Inevitably there will be edge cases. Thus far, however, I've found that many of the edge cases that seem to be problematic are already addressed or not problematic for Bash.

Please feel free to [create an issue](../../issues) if you find a bug or have a feature request.

## Usage

```js
var glob = require('bash-glob');
glob(pattern[, options]);
```

## API

### [glob](index.js#L30)

Asynchronously returns an array of files that match the given pattern or patterns.

**Params**

* `patterns` **{String|Array}**: One or more glob patterns to use for matching.
* `options` **{Object}**: Options to pass to bash. See available [options](#options).
* `cb` **{Function}**: Callback function, with `err` and `files` array.

**Example**

```js
var glob = require('bash-glob');
glob('*.js', function(err, files) {
  if (err) return console.log(err);
  console.log(files);
});
```

### [.each](index.js#L98)

Asynchronously glob an array of files that match any of the given `patterns`.

**Params**

* `patterns` **{String}**: One or more glob patterns to use for matching.
* `options` **{Object}**: Options to pass to bash. See available [options](#options).
* `cb` **{Function}**: Callback function, with `err` and `files` array.

**Example**

```js
var glob = require('bash-glob');
glob.each(['*.js', '*.md'], {dot: true}, function(err, files) {
  if (err) return console.log(err);
  console.log(files);
});
```

### [.sync](index.js#L154)

Returns an array of files that match the given patterns or patterns.

**Params**

* `patterns` **{String}**: One or more glob patterns to use for matching.
* `options` **{Object}**: Options to pass to bash. See available [options](#options).
* `returns` **{Array}**: Returns an array of files.

**Example**

```js
var glob = require('bash-glob');
console.log(glob.sync('*.js', {cwd: 'foo'}));
console.log(glob.sync(['*.js'], {cwd: 'bar'}));
```

## Options

The following options may be used with the main `glob` function or any other method:

* `dotglob`: (or `dot`, for [node-glob](https://github.com/Crafity/node-glob) compatibility) Includes filenames beginning with a `.` (dot) in the results of pathname expansion.
* `extglob`: Enable extended [pattern matching](http://wiki.bash-hackers.org/syntax/pattern) features.
* `failglob`: If set, patterns that fail to match filenames during pathname expansion result in an error message.
* `globstar`: Enable recursive globbing with `**`.
* `nocaseglob`: (or `nocase`, for [node-glob](https://github.com/Crafity/node-glob) compatibility) Enable case-insensitive matching in filenames when performing pathname expansion.
* `nullglob`: If set, Bash allows patterns which match no files to expand to a null string, rather than themselves.

## About

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, [please create an issue](../../issues/new).

Please read the [contributing guide](.github/contributing.md) for advice on opening issues, pull requests, and coding standards.

Running Tests

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

```sh
$ npm install && npm test
```

Building docs

_(This project's readme.md is generated by [verb](https://github.com/verbose/verb-generate-readme), please don't edit the readme directly. Any changes to the readme must be made in the [.verb.md](.verb.md) readme template.)_

To generate the readme, run the following command:

```sh
$ npm install -g verbose/verb#dev verb-generate-readme && verb
```

### Related projects

You might also be interested in these projects:

* [bash-match](https://www.npmjs.com/package/bash-match): Match strings using bash. Does not work on windows, and does not read from the… [more](https://github.com/micromatch/bash-match) | [homepage](https://github.com/micromatch/bash-match "Match strings using bash. Does not work on windows, and does not read from the file system. This library requires that Bash 4.3 or higher is installed and is mostly used for checking parity in unit tests.")
* [braces](https://www.npmjs.com/package/braces): Bash-like brace expansion, implemented in JavaScript. Safer than other brace expansion libs, with complete support… [more](https://github.com/micromatch/braces) | [homepage](https://github.com/micromatch/braces "Bash-like brace expansion, implemented in JavaScript. Safer than other brace expansion libs, with complete support for the Bash 4.3 braces specification, without sacrificing speed.")
* [micromatch](https://www.npmjs.com/package/micromatch): Glob matching for javascript/node.js. A drop-in replacement and faster alternative to minimatch and multimatch. | [homepage](https://github.com/micromatch/micromatch "Glob matching for javascript/node.js. A drop-in replacement and faster alternative to minimatch and multimatch.")
* [nanomatch](https://www.npmjs.com/package/nanomatch): Fast, minimal glob matcher for node.js. Similar to micromatch, minimatch and multimatch, but complete Bash… [more](https://github.com/micromatch/nanomatch) | [homepage](https://github.com/micromatch/nanomatch "Fast, minimal glob matcher for node.js. Similar to micromatch, minimatch and multimatch, but complete Bash 4.3 wildcard support only (no support for exglobs, posix brackets or braces)")

### Author

**Jon Schlinkert**

* [github/jonschlinkert](https://github.com/jonschlinkert)
* [twitter/jonschlinkert](https://twitter.com/jonschlinkert)

### License

Copyright © 2017, [Jon Schlinkert](https://github.com/jonschlinkert).
Released under the [MIT License](LICENSE).

***

_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.6.0, on October 22, 2017._


text:
# `broccoli-rollup`

[![Build Status](https://travis-ci.org/chadhietala/broccoli-rollup.svg?branch=master)](https://travis-ci.org/chadhietala/broccoli-rollup)

A [broccoli](https://broccoli.build/) plugin that uses [rollup.js](https://rollupjs.org/) on its input.

## Usage

### Basic

```js
// Brocfile.js
import rollup from 'broccoli-rollup';

export default () =>
  rollup('lib', {
    // nodeModulesPath: string Defaults to process.cwd()
    rollup: {
      input: 'index.js',
      output: {
        file: 'bundle.js',
        format: 'es',
      },
    },
  });
```

### Code Splitting

```js
// Brocfile.js
import rollup from 'broccoli-rollup';

export default () =>
  rollup('lib', {
    // nodeModulesPath: string Defaults to process.cwd()
    rollup: {
      input: 'index.js',
      output: {
        dir: 'chunks',
        format: 'es',
      },
    },
  });
```

### Multiple Output

```js
// Brocfile.js
import rollup from 'broccoli-rollup';

export default () =>
  rollup('lib', {
    // nodeModulesPath: string Defaults to process.cwd()
    rollup: {
      input: 'index.js',
      output: [
        {
          file: 'my-lib.amd.js',
          format: 'amd',
        },
        {
          file: 'my-lib.iife.js',
          name: 'MyLib',
          format: 'iife',
        },
      ],
    },
  });
```

## Notes and Caveats

Broccoli is designed around immutable input and although rollup does expose enough
in the build output for us to write it to disk, this doesn't work with the `onwrite` plugin hook
and requires a significant amount of code to get feature parity with rollup's
`buildOutput.write(outputOptions)`.

We use the following build flow to achieve compatibility and feature parity with rollup's cli
while still adhering to broccoli's immutable input constraints.

1. sync `node.inputPaths[0]` to `${node.cachePath}/build`
2. symlink `options.nodeModulesPath` to `${node.cachePath}/node_modules`
3. change the working directory to `${node.cachePath}/build` (rollup doesn't allow this to be passed in and plugins may also the use cwd)
4. run rollup
5. restore the working directory
6. sync `${node.cachePath}/build` to `node.outputPath` for all files that are different from the input.

If you have any plugins that require hard-coded paths into `node_modules`,
please note that `node_modules` is symlinked above the build path.

So instead of doing `node_modules/x` you need to do `../node_modules/x`.

repository: lblod/frontend-rdfa-editor-demo

gha_language: HTML

repo_name: lblod/frontend-rdfa-editor-demo


text:
##### toplevel

Returns true if the current script is the top (not a child sub-script).

In the following example, the script will halt if it is called directly;
it has to be called from within another bashible script.

```bash
@ Basic checks
  - not toplevel
```

repository: nestorwheelock/bashible

repo_name: nestorwheelock/bashible


text:
# PR for # .

## PR Status
**READY/IN DEVELOPMENT/HOLD**

## Ready for PR?
- [ ] I have updated the CHANGELOG with an entry including a description, a link to my profile, and a link to the issue ticket. This change is filed under an Enhancement or Bug Fix, is shown under the relevant release tag name, and is included in my PR branch.
- [ ] I have run `lein run-lint` to check for linting errors.

## Changes Proposed:
-
-
-

## Breaking changes?
-
-
-

## Screenshot of feature:

@emilyseibert @oconn @dehli

repository: dehli/wombats-web-client

gha_language: Clojure

repo_name: dehli/wombats-web-client


text:
### AVIF (HEIC, HEIF)

 - images where metadata is encoded after image data are not supported (should
   not happen in real world, because such data layout not recommended by standard)
 - cropping transformation (`clap` box) is ignored (anyway, no supported
   by browsers yet)

### JPEG

 - exif (with orientation) is ignored, if placed after image data (should not
   happen in real world, because such data layout not recommended by standard)

### PNG

 - exif (with orientation) is ignored (not supported by browsers anyway)

### WEBP

 - Full download required, because exif data is frequently located at the end
   of file.

gha_language: JavaScript


text:
## 0.8.0+3

* Log messages about automatic configuration of the default app are now less confusing.

## 0.8.0+2

* Remove categories.

## 0.8.0+1

* Log a more detailed warning at build time about the previous AndroidX
  migration.

## 0.8.0

* **Breaking change**. Migrate from the deprecated original Android Support
  Library to AndroidX. This shouldn't result in any functional changes, but it
  requires any Android apps using this plugin to [also
  migrate](https://developer.android.com/jetpack/androidx/migrate) if they're
  using the original support library.

## 0.7.0

* Mark Dart code as deprecated where the newer version AdMob deprecates features (Birthday, Gender, and Family targeting).
* Update gradle dependencies.
* Add documentation for new AndroidManifest requirements.

## 0.6.1+1

* Bump Android dependencies to latest.
* __THIS WAS AN UNINTENTIONAL BREAKING CHANGE__. Users should consume 0.6.1 instead if they need the old API, or 0.7.0 for the bumped version.
* Guide how to fix crash with admob version 17.0.0 in README

## 0.6.1

* listener on MobileAd shouldn't be final.
* Ad listeners can to be set in or out of Ad initialization.

## 0.6.0

* Add nonPersonalizedAds option to MobileAdTargetingInfo

## 0.5.7

* Bumped mockito dependency to pick up Dart 2 support.

## 0.5.6

* Bump Android and Firebase dependency versions.

## 0.5.5

* Updated Gradle tooling to match Android Studio 3.1.2.

## 0.5.4+1

* Graduate to beta.

## 0.5.4

* Fixed a bug that was causing rewarded video failure event to be called on the wrong listener.

## 0.5.3

* Updated Google Play Services dependencies to version 15.0.0.
* Added handling of rewarded video completion event.

## 0.5.2

* Simplified podspec for Cocoapods 1.5.0, avoiding link issues in app archives.

## 0.5.1

* Fixed Dart 2 type errors.

## 0.5.0

* **Breaking change**. The BannerAd constructor now requires an AdSize
  parameter. BannerAds can be created with AdSize.smartBanner, or one of
  the other predefined AdSize values. Previously BannerAds were always
  defined with the smartBanner size.

## 0.4.0

* **Breaking change**. Set SDK constraints to match the Flutter beta release.

## 0.3.2

* Fixed Dart 2 type errors.

## 0.3.1

* Enabled use in Swift projects.

## 0.3.0

* Added support for rewarded video ads.
* **Breaking change**. The properties and parameters named "unitId" in BannerAd
  and InterstitialAd have been renamed to "adUnitId" to better match AdMob's
  documentation and UI.

## 0.2.3

* Simplified and upgraded Android project template to Android SDK 27.
* Updated package description.

## 0.2.2

* Added platform-specific App IDs and ad unit IDs to example.
* Separated load and show functionality for interstitials in example.

## 0.2.1

* Use safe area layout to place ad in iOS 11

## 0.2.0

* **Breaking change**. MobileAd TargetingInfo requestAgent is now hardcoded to 'flutter-alpha'.

## 0.1.0

* **Breaking change**. Upgraded to Gradle 4.1 and Android Studio Gradle plugin
  3.0.1. Older Flutter projects need to upgrade their Gradle setup as well in
  order to use this version of the plugin. Instructions can be found
  [here](https://github.com/flutter/flutter/wiki/Updating-Flutter-projects-to-Gradle-4.1-and-Android-Studio-Gradle-plugin-3.0.1).
* Relaxed GMS dependency to [11.4.0,12.0[

## 0.0.3

* Add FLT prefix to iOS types
* Change GMS dependency to 11.4.+

## 0.0.2

* Change GMS dependency to 11.+

## 0.0.1

* Initial Release: not ready for production use


text:
---
layout: relation
title: 'obj:periph'
shortdef: 'preposed object'
udver: '2'
---

The default word order in Chinese is SVO, that is, the subject normally precedes and the object
follows the verb. Other word orders, like OSV, are communicatively marked (Tremblay, 2005).
We use the `obj:periph` subtype of the [obj]() relation for objects that precede their verb.

~~~ sdparse
這 首 你 剛剛 才 錄 了 。 \n this one you just only record completed .
det(首, 這)
obj:periph(錄, 首)
nsubj(錄, 你)
advmod(錄, 剛剛)
advmod(錄, 才)
aux(錄, 了)
punct(錄, 。)
~~~

“You just recorded this song.”

## References

* Tremblay, A. (2005). Word Order in Mandarin Chinese and Grammatical Relations.
  In: Proceedings of the 19th Pacific Asia Conference on Language, Information and Computation: 333–340.

<!-- Interlanguage links updated Út 9. května 2023, 20:04:26 CEST -->

repository: UniversalDependencies/docs

branch_name: refs/heads/pages-source

repo_name: UniversalDependencies/docs


text:
This is the source for https://electioncal.us which provides election
timeline information and makes it available through the website and
icalendar files.

# Building the site

The site is statically hosted by GitHub. To test it locally, first install the
python requirements with:

    pip install -r requirements.txt

Once those are installed, build the site with:

    python scripts/build_site.py

This generates all of files served statically under the `site` folder. To serve
them locally do:

    python -m http.server --directory site/ 8080

license: ISC

repository: electioncal/us

gha_license_id: NOASSERTION

repo_name: electioncal/us


text:
Track Simplifier / Optimizer online
============

Online Simplifier and Optimizer for GPX / GeoJSON / KML tracks.

Copyright 2014-2023 [Stefano Cudini](https://opengeo.tech/stefano-cudini/)

If this project helped your work help me to keep this alive by [Paypal **DONATION ❤**](https://www.paypal.me/stefanocudini)

Maintainers
----
[Thibault Taillandier (Wilkins)](https://github.com/Wilkins)
[Stefano Cudini](https://opengeo.tech/stefano-cudini/)

Online
----
[opengeo.tech/gpx-simplify-optimizer](https://opengeo.tech/gpx-simplify-optimizer/)

![Image](https://raw.githubusercontent.com/stefanocudini/gpx-simplify-optimizer/master/images/gpx-optimizer.png)

Usage
-----
1. Upload GPX / KML / GeoJSON file
2. Simplify the track on the map by reducing the number of nodes
3. Save or view the simplified track in different formats : GPX / KML / GeoJSON / Mediawiki Maps

Install
-------
```bash
git clone https://github.com/stefanocudini/gpx-simplify-optimizer.git
cd gpx-simplify-optimizer
git submodule init
git submodule update
```

Build
-----
```bash
npm install
grunt
```

Author
-----
Copyright 2022 [Stefano Cudini](https://opengeo.tech/stefano-cudini/)

repository: stefanocudini/gpx-simplify-optimizer

repo_name: stefanocudini/gpx-simplify-optimizer


text:
# tabular-to-object

Convert tabular arrays to associative Objects

## Installation

```sh
npm install --save tabular-to-object
# or
yarn add tabular-to-object
```

## Use

```js
import {toObjects, toRows} from 'tabular-to-object'

toObjects([
	['x', 'y'],
	[1, 2],
	[3, 4],
])
// => [{x: 1, y: 2}, {x: 3, y: 4}]

toRows([{x: 1, y: 2}, {x: 3, y: 4}])
// => [['x', 'y'], [1, 2], [3, 4]]
```

## License

ISC License (ISC) Copyright (c) 2017, Jonathan Apodaca<EMAIL_ADDRESS>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

 IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

repository: jrop/tabular-to-object

repo_name: jrop/tabular-to-object


text:
## StreamingKit

StreamingKit (formally Audjustable) is an audio playback and streaming library for iOS and Mac OSX.  StreamingKit uses CoreAudio to decompress and playback audio (using hardware or software codecs) whilst providing a clean and simple object-oriented API.

[Original project](https://github.com/tumtumtum/StreamingKit)

ADD Feature :
When playing audio from url, you can cache the audio on your local file system.Use:`+(STKDataSource*) dataSourceFromURL:(NSURL*)url andCacheFilePath : (nullable NSString *) filePath`

repository: cndevmingle/StreamingKit

repo_name: cndevmingle/StreamingKit


text:
---
name: Architecture Decision Record
about: Create an architecture decision record to capture an important architecture decision made along with its context and consequences.
title: ''
labels: 'architecture decision record'
assignees: ''

---

## Status

What is the status, such as proposed, accepted, rejected, deprecated, superseded, etc.?

## Context

How does it work today and why a decision is needed? If we've to tell to someone new.

## Problems

What is the issue that we're seeing that is motivating this decision or change?

## Solutions

What is the change that we're proposing and/or doing?

## Consequences

What becomes easier or more difficult to do because of this change?

repository: Talend/ui

repo_name: Talend/ui