text:
# anchor-feature-session

Sessions to calculate many features optimally (performing appropriating initialization, caching etc.)

## What is Anchor?

Anchor is a platform for image analysis, developed by [Owen Feehan](http://www.owenfeehan.com) at:

* ETH Zurich
* University of Zurich
* Hoffmann la Roche
* ongoing as a open-source personal/community project

## Documentation

Please consider:

* the [user guide](https://www.anchoranalysis.org/user_guide.html)
* the [developer guide](https://www.anchoranalysis.org/developer_guide.html), especially [anchor](https://www.anchoranalysis.org/developer_guide_repositories_anchor.html) for an overview of all modules in this repository.

Before reading the source code, please:

* Understand Maven and [multi-module projects](https://www.anchoranalysis.org/developer_guide_environment_maven.html).
* Consider Anchor's [architecture](https://www.anchoranalysis.org/developer_guide_architecture_overview.html).
* Consider the role of each [module](https://www.anchoranalysis.org/developer_guide_repositories_anchor.html) in the repository.

repository: anchoranalysis/anchor

gha_language: Java

repo_name: anchoranalysis/anchor


text:
# Mask R-CNN for Object Detection and Segmentation

This is a fork of the [Mask R-CNN](https://github.com/matterport/Mask_RCNN) implementation by matterport. This fork contains only the main model definition and configuration files.

This is intended to be used as a simple library style package, leaving out the examples and demos from the original repository.

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
---
language: English
currentMenu: search
subTitle: Search content
---

# Search content in wallabag

To enable you to find an article quickly, we set up a full search engine.

Click on **Search** in the wallabag menu. Then, enter your search terms.

wallabag will go through all your articles, and lists the ones containing the search terms in their title, their content or their URL.

## Convert this search into ePub format

You can convert the listed articles to the ePub format, so that you can read them in your e-reader, for example. Look at [ePub conversion](epub_conversion.md) for more about this.

## Assign a tag to your search results

You can create a tag based on your search criteria. Look at [Organize articles](Organize_articles.md) for more about this.

repository: torinthiel/wallabag-documentation

repo_name: torinthiel/wallabag-documentation


text:
![agentia-utilities logo](media/logo.png)
---
[![Build Status](https://travis-ci.org/AgentiaSystems/agentia-utilities.svg?branch=master)](https://travis-ci.org/AgentiaSystems/agentia-utilities)
[![Code Climate](https://codeclimate.com/github/AgentiaSystems/agentia-utilities/badges/gpa.svg)](https://codeclimate.com/github/AgentiaSystems/agentia-utilities)
[![Test Coverage](https://codeclimate.com/github/AgentiaSystems/agentia-utilities/badges/coverage.svg)](https://codeclimate.com/github/AgentiaSystems/agentia-utilities)

Multipurpose utilities for by Agentia modules

### Installation

[![NPM version](https://badge.fury.io/js/agentia-utilities.png)](https://www.npmjs.com/package/agentia-utilities)

Install with the Node.js package manager [npm](http://npmjs.org/):

    $ npm install --save agentia-utilities

### Running Tests

We use The Mocha framework along with the Chai assertion library for your unit tests.

You can run our unit tests by cloning our repository, install the module dependencies using `npm install`, then running `npm test`.

    git clone https://github.com/AgentiaSystems/agentia-utilities.git
    npm install
    npm test

You can also use our `gulp` tasks: `test` and `coverage`.

    gulp test
    gulp coverage (which generates a coverage report)

## License
**agentia-utilities** is free and open source under the MIT License.

Copyright (c) 2015 [Johnny Estilles](https://github.com/JohnnyEstilles), [http://www.agentia.asia](http://www.agentia.asia)

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

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

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

repository: alanozzo/easyerp

gha_language: JavaScript

gha_license_id: MIT

repo_name: alanozzo/easyerp


text:
# Aspose.OCR for Cloud

[Aspose.OCR for Cloud](https://products.aspose.cloud/ocr/cloud) is a simple SDK used to add text recognition to your app with simply few line of code.

In details, it's a set of SDKs for optical character recognition and documents scanning in our cloud. It supports reading and recognizing text from most commonly used raster image formats. Just pass specific image to the Aspose.OCR for Cloud API and it will return response with recognized text.

It is easy to get started with Aspose.OCR for Cloud and there is nothing to install. Simply create an account at Aspose for Cloud and get your application information, then you are ready to use [SDKs](#sdk-packages)

## How to use the SDK?

Our API is completely independent of your operating system, database system or development language. You can use any language and platform that supports HTTP to interact with our API. However, manually writing client code can be difficult, error-prone and time-consuming. Therefore, we have provided and support API [SDKs](#sdk-packages) in many development languages in order to make it easier to integrate with us.

## Example

```csharp
static string RecognizeFromUrl(Configuration conf)
{
    string imgUri = @"http://typecast.com/images/uploads/fluid-type-single-column.png";

    OcrApi api = new OcrApi(conf);
    var request = new PostOcrFromUrlOrContentRequest(null, imgUri);
    OCRResponse response = api.PostOcrFromUrlOrContent(request);

    return response.Text;
}

static string RecognizeFromContent(Configuration conf)
{
    string name = "10.png";
    using (FileStream fs = File.OpenRead(name))
    {
        OcrApi api = new OcrApi(conf);
        var request = new PostOcrFromUrlOrContentRequest(fs);
        OCRResponse response = api.PostOcrFromUrlOrContent(request);

        return response.Text;
    }
}
```
_________________________

## Quickstart

Try out our [demo](http://saltov-gpu-3.dynabic.com:8082/) right now or make your own solution using [SDK](#sdk-packages), follow this steps:

#### 1. Get API keys if you haven't

Make a personal account on [Aspose for Cloud](https://dashboard.aspose.cloud/#/) and click _Get Keys_. This keys are usefull for all Aspose Cloud products. If you have any trouble, look at this [detailed manual](https://docs.aspose.cloud/display/totalcloud/Create+New+App+and+Get+App+Key+and+SID).

#### 2. Run Demo
  * Checkout the SDK
  * Open [.NET 2.0](/Aspose.Ocr.Cloud.Sdk.Demo) or [.NET Core](/Aspose.Ocr.Cloud.Sdk.Demo.Net.Core) demo project
  * Set Your AppSid & AppKey
  * Run

_________________________

## SDKs

||||||||||
|-------|----------|-------|-------|-------|---------|---------|----------|-------|
|[.NET](/SDK_V3/SDK/Aspose.OCR-Cloud-SDK-for-.NET)|Java|PHP|Ruby|Python|Node.js|Android|Objective-C|Perl|

## Resources

- **Website:** [https://www.aspose.cloud](https://www.aspose.cloud)
- **Product Home:** [Aspose.OCR Cloud](https://products.aspose.cloud/ocr/family)
- **Documentation:** [Aspose.OCR Cloud Documentation](https://docs.aspose.cloud/display/ocrcloud/Home)
- **Forum:** [Aspose.OCR Cloud Forum](https://forum.aspose.cloud/c/ocr)
- **Blog:** [Aspose.OCR Cloud Blog](https://blog.aspose.cloud/category/ocr/)
- **Pricing:** [Aspose Cloud Pricing](https://purchase.aspose.cloud/pricing).


text:
## 2D目标检测与跟踪

- Generalized Focal Loss V2: Learning Reliable Localization Quality Estimation for Dense Object Detection https://arxiv.org/abs/2011.12885
- CRACT: Cascaded Regression-Align-Classification for Robust Visual Tracking https://arxiv.org/abs/2011.12483
- Sparse R-CNN: End-to-End Object Detection with Learnable Proposals https://arxiv.org/abs/2011.12450
- Robust Correlation Tracking via Multi-channel Fused Features and Reliable Response Map https://arxiv.org/abs/2011.12550

## 分割

- Fast Object Segmentation Learning with Kernel-based Methods for Robotics https://arxiv.org/abs/2011.12805
- Unsupervised Domain Adaptation in Semantic Segmentation via Orthogonal and Clustered Embeddings  https://arxiv.org/abs/2011.12616
- SegBlocks: Block-Based Dynamic Resolution Networks for Real-Time Segmentation https://arxiv.org/abs/2011.12025
- Scaling Wide Residual Networks for Panoptic Segmentation https://arxiv.org/abs/2011.11675

## 车道线检测

- 2020
  - Inter-region affinity distillation for road marking segmentation (CVPR2020)
  - RONELD: Robust Neural Network Output Enhancement for Active Lane Detection (ICPR2020)
  - Key points estimation and point instance segmentation approach for lane detection https://arxiv.org/abs/2002.06604

- 2019
  - 3d-lanenet: End-to-end 3d multiple lane detection (ICCV2019)
  - End-to-end lane detection through differentiable leastsquares fitting (ICCV2019)
  - Learning lightweight lane detection cnns by self attention distillation (ICCV2019)
  - Multi-lane detection using instance segmentation and attentive voting (ICCAS2019)

- 2018
  - Elgan: Embedding loss driven generative adversarial networks for lane detection (ECCV2018)
  - Spatial as deep: Spatial CNN for traffic scene understanding (AAAI2018)
  - Towards end-to-end lane detection: an instance segmentation approach (IV2018)

- 2017
  - Vpgnet: Vanishing point guided network for lane and road marking detection and recognition (ICCV2017)

## 轻量化神经网络

- MicroNet: Towards Image Recognition with Extremely Low FLOPs https://arxiv.org/abs/2011.12289
-

## 数据增强
- KeepAugment: A Simple Information-Preserving Data Augmentation Approach https://arxiv.org/abs/2011.11778

## 神经网络架构设计

## 模型压缩与量化

-  Auto Graph Encoder-Decoder for Model Compression and Network Acceleration https://arxiv.org/abs/2011.12641

## 技巧

- Delving Deep into Label Smoothing https://arxiv.org/abs/2011.12562

## 数据集
- 跟踪
  - GMOT-40: A Benchmark for Generic Multiple Object Tracking  https://arxiv.org/abs/2011.11858

branch_name: refs/heads/main


text:
# CVAE: Conditional Variational Autoencoder

## Description

An autoencoder is an neural network that learns how to encode data (like the pixels of an image) into a smaller representation. This is akin to image compression (although classic image compression algorithms are better!) A Variational Autoencoder (VAE) takes this idea one step further and is trained to generate new images in the style of training data by sprinkling in a little bit of randomness. Conditional Variational Autoencoder (CVAE) is an extension of this idea, with the ability to be more specific about what is generated. From [Two Minute Papers](https://www.youtube.com/watch?v=Rdpbnd0pCiI), the author explains that:

*\"Autoencoders are neural networks that are capable of creating sparse representations of the input data and can therefore be used for image compression. There are denoising autoencoders that after learning these sparse representations, can be presented with noisy images. What is even better is a variant that is called the variational autoencoder that not only learns these sparse representations, but can also draw new images as well. We can, for instance, ask it to create new handwritten digits and we can actually expect the results to make sense!"*

## Quickstart

```js
const cvae = ml5.CVAE('model/quick_draw/manifest.json', modelReady);

function modelReady() {
  // generate an image of an airplane
  cvae.generate('airplane', gotImage);
}

function gotImage(error, result) {
  if (error) {
    console.log(error);
    return;
  }
  // log the result
  console.log(result);
}
```

## Usage

### Initialize

```js
const magic = ml5.CVAE(?model, ?callback);
```

#### Parameters
* **model**: REQUIRED. The url path to your model. Can be an absolute or relative path.
* **callback**: REQUIRED. A function to run once the model has been loaded.

### Properties

***
#### .ready
> *BOOLEAN*. Boolean value that specifies if the model has loaded.
***

### Methods

***
#### .generate(label, callback);
> Given a label, will generate an image.

```js
cvae.generate(label, callback);
```

📥 **Inputs**

* **label**: REQUIRED. String. A label of the feature your want to generate.
* **callback**: REQUIRED. Function. A function to handle the results of ".generate()". Likely a function to do something with the generated image data.

📤 **Outputs**

* **Object**: Returns "raw", "blob", and "tensor". If p5.js is available, a "p5Image" will be returned as well.

***

## Examples

**p5.js**
* [CVAE_QuickDraw](https://github.com/ml5js/ml5-library/tree/development/examples/p5js/CVAE/CVAE_QuickDraw)

**p5 web editor**
* [CVAE_QuickDraw](https://editor.p5js.org/ml5/sketches/CVAE_QuickDraw)

**plain javascript**
* [CVAE_QuickDraw](https://github.com/ml5js/ml5-library/tree/development/examples/javascript/CVAE/CVAE_QuickDraw)

## Demo

No demos yet - contribute one today!

## Tutorials

No tutorials yet - contribute one today!

## Acknowledgements

**Contributors**:
  * Wenhe Li & Dingsu (Derek) Wang

**Credits**:
  * Paper Reference | Website URL | Github Repo | Book reference | etc

## Source Code

[/src/CVAE/](https://github.com/ml5js/ml5-library/tree/development/src/CVAE)

branch_name: refs/heads/development


text:
---
title: Istio Multicluster
description: Install Istio with multicluster support.
weight: 60
keywords: [kubernetes,multicluster]
---

Instructions for the installation of Istio multicluster.

## Prerequisites

* Two or more Kubernetes clusters with **1.9 or newer**.

* The ability to deploy the [Istio control plane](/docs/setup/kubernetes/quick-start/)
on **one** Kubernetes cluster.

*   The usage of an RFC1918 network, VPN, or alternative more advanced network techniques
to meet the following requirements:

    * Individual cluster Pod CIDR ranges and service CIDR ranges must be unique
across the multicluster environment and may not overlap.

    * All pod CIDRs in every cluster must be routable to each other.

    * All Kubernetes control plane API servers must be routable to each other.

* Helm **2.7.2 or newer**.  The use of Tiller is optional.

## Overview

Multicluster functions by enabling Kubernetes control planes running
a remote configuration to connect to **one** Istio control plane.
Once one or more remote Kubernetes clusters are connected to the
Istio control plane, Envoy can then communicate with the **single**
Istio control plane and form a mesh network across multiple Kubernetes
clusters.

This guide describes how to install a multicluster Istio topology using the
manifests and Helm charts provided within the Istio repository.

## Deploy the local Istio control plane

Install the [Istio control plane](/docs/setup/kubernetes/quick-start/#installation-steps)
on **one** Kubernetes cluster.

## Install the Istio remote on every remote cluster

The istio-remote component must be deployed to each remote Kubernetes
cluster.  There are two approaches to installing the remote.  The remote
can be installed and managed entirely by Helm and Tiller, or via Helm and
`kubectl`.

### Set environment variables for Pod IPs from Istio control plane needed by remote

Please wait for the Istio control plane to finish initializing
before proceeding to steps in this section.

These operations must be run on the Istio control plane cluster
to capture the Istio control-plane service endpoints--e.g. Pilot, Policy,
and Statsd Pod IP endpoints.

If Helm is used with Tiller on each remote, copy the environment
variables to each node before using Helm to connect the remote
cluster to the Istio control plane.

{{< text bash >}}
$ export PILOT_POD_IP=$(kubectl -n istio-system get pod -l istio=pilot -o jsonpath='{.items[0].status.podIP}')
$ export POLICY_POD_IP=$(kubectl -n istio-system get pod -l istio-mixer-type=policy -o jsonpath='{.items[0].status.podIP}')
$ export STATSD_POD_IP=$(kubectl -n istio-system get pod -l istio=statsd-prom-bridge -o jsonpath='{.items[0].status.podIP}')
$ export TELEMETRY_POD_IP=$(kubectl -n istio-system get pod -l istio-mixer-type=telemetry -o jsonpath='{.items[0].status.podIP}')
$ export ZIPKIN_POD_IP=$(kubectl -n istio-system get pod -l app=jaeger -o jsonpath='{range .items[*]}{.status.podIP}{end}')
{{< /text >}}

Proceed to one of the options for connecting the remote cluster to the local cluster:

* Via [`kubectl` with Helm](#use-kubectl-with-helm-to-connect-the-remote-cluster-to-the-local)

* Via [Helm plus Tiller](#alternatively-use-helm-and-tiller-to-connect-the-remote-cluster-to-the-local)

* Using *sidecar Injection.*  The default behavior is to enable automatic sidecar injection on the remote clusters.  For manual sidecar injection refer to the [manual sidecar example](#remote-cluster-manual-sidecar-injection-example)

### Use `kubectl` with Helm to connect the remote cluster to the local

1.  Use the `helm template` command on a remote to specify the Istio control plane service endpoints:

    {{< text bash >}}
    $ helm template install/kubernetes/helm/istio-remote --namespace istio-system \
    --name istio-remote \
    --set global.remotePilotAddress=${PILOT_POD_IP} \
    --set global.remotePolicyAddress=${POLICY_POD_IP} \
    --set global.remoteTelemetryAddress=${TELEMETRY_POD_IP} \
    --set global.proxy.envoyStatsd.enabled=true \
    --set global.proxy.envoyStatsd.host=${STATSD_POD_IP} \
    --set global.remoteZipkinAddress=${ZIPKIN_POD_IP} > $HOME/istio-remote.yaml
    {{< /text >}}

1.  Create a namespace for remote Istio.

    {{< text bash >}}
    $ kubectl create ns istio-system
    {{< /text >}}

1.  Instantiate the remote cluster's connection to the Istio control plane:

    {{< text bash >}}
    $ kubectl apply -f $HOME/istio-remote.yaml
    {{< /text >}}

1.  Label all the remote cluster's namespaces requiring auto-sidecar injection.  The following example labels the `default` namespace.

    {{< text bash >}}
    $ kubectl label namespace default istio-injection=enabled
    {{< /text >}}

    Repeat for any additional kubernetes namespaces to setup auto-sidecar injection.

### Alternatively use Helm and Tiller to connect the remote cluster to the local

1.  If a service account has not already been installed for Helm, please
install one:

    {{< text bash >}}
    $ kubectl apply -f install/kubernetes/helm/helm-service-account.yaml
    {{< /text >}}

1.  Initialize Helm:

    {{< text bash >}}
    $ helm init --service-account tiller
    {{< /text >}}

1.  Install the Helm chart:

    {{< text bash >}}
    $ helm install install/kubernetes/helm/istio-remote --name istio-remote  --namespace istio-system --set global.remotePilotAddress=${PILOT_POD_IP} --set global.remotePolicyAddress=${POLICY_POD_IP} --set global.remoteTelemetryAddress=${TELEMETRY_POD_IP} --set global.proxy.envoyStatsd.enabled=true --set global.proxy.envoyStatsd.host=${STATSD_POD_IP} --set global.remoteZipkinAddress=${ZIPKIN_POD_IP}
    {{< /text >}}

### Helm configuration parameters

In order for the remote cluster's sidecars interaction with the Istio control plane, the `pilot`,
`policy`, `telemetry`, `statsd`, and tracing service endpoints need to be configured in
the `istio-remote` Helm chart.  The chart enables automatic sidecar injection in the remote
cluster by default but it can be disabled via a chart variable.  The following table describes
the `istio-remote` Helm chart's configuration values.

| Helm Variable | Accepted Values | Default | Purpose of Value |
| --- | --- | --- | --- |
| `global.remotePilotAddress` | A valid IP address or hostname | None | Specifies the Istio control plane's pilot Pod IP address or remote cluster DNS resolvable hostname |
| `global.remotePolicyAddress` | A valid IP address or hostname | None | Specifies the Istio control plane's policy Pod IP address or remote cluster DNS resolvable hostname |
| `global.remoteTelemetryAddress` | A valid IP address or hostname | None | Specifies the Istio control plane's telemetry Pod IP address or remote cluster DNS resolvable hostname |
| `global.proxy.envoyStatsd.enabled` | true, false | false | Specifies whether the Istio control plane has Statsd enabled |
| `global.proxy.envoyStatsd.host` | A valid IP address or hostname | None | Specifies the Istio control plane's `statsd-prom-bridge` Pod IP address or remote cluster DNS resolvable hostname.  Ignored if `global.proxy.envoyStatsd.enabled=false`. |
| `global.remoteZipkinAddress` | A valid IP address or hostname | None | Specifies the Istio control plane's tracing application Pod IP address or remote cluster DNS resolvable hostname--e.g. `zipkin` or `jaeger`. |
| `sidecarInjectorWebhook.enabled` | true, false | true | Specifies whether to enable automatic sidecar injection on the remote cluster |
| `global.remotePilotCreateSvcEndpoint` | true, false | false | If set, a selector-less service and endpoint for `istio-pilot` are created with the `remotePilotAddress` IP, which ensures the `istio-pilot.<namespace>` is DNS resolvable in the remote cluster. |

## Generate `kubeconfigs` for remote clusters

The Istio control plane requires access to all clusters in the mesh to
discover services, endpoints, and pod attributes.  The following
describes how to generate a `kubeconfig` file for a remote cluster to be used by
the Istio control plane.

The `istio-remote` Helm chart creates a Kubernetes service account named `istio-multi`
in the remote cluster with the minimal RBAC access required.  The following procedure
generates a `kubeconfig` file for the remote cluster using the credentials of the
`istio-multi` service account created by the `istio-remote` Helm chart.

The following procedure should be performed on each remote cluster to be
added to the service mesh.  The procedure requires cluster-admin user access
to the remote cluster.

1.  Prepare environment variables for building the `kubeconfig` file for `ServiceAccount` `istio-multi`:

    {{< text bash >}}
    $ export WORK_DIR=$(pwd)
    $ CLUSTER_NAME=$(kubectl config view --minify=true -o "jsonpath={.clusters[].name}")
    $ export KUBECFG_FILE=${WORK_DIR}/${CLUSTER_NAME}
    $ SERVER=$(kubectl config view --minify=true -o "jsonpath={.clusters[].cluster.server}")
    $ NAMESPACE=istio-system
    $ SERVICE_ACCOUNT=istio-multi
    $ SECRET_NAME=$(kubectl get sa ${SERVICE_ACCOUNT} -n ${NAMESPACE} -o jsonpath='{.secrets[].name}')
    $ CA_DATA=$(kubectl get secret ${SECRET_NAME} -n ${NAMESPACE} -o "jsonpath={.data['ca\.crt']}")
    $ TOKEN=$(kubectl get secret ${SECRET_NAME} -n ${NAMESPACE} -o "jsonpath={.data['token']}" | base64 --decode)
    {{< /text >}}

    __NOTE__: An alternative to `base64 --decode` is `openssl enc -d -base64 -A` on many systems.

1. Create a `kubeconfig` file in the working directory for the `ServiceAccount` `istio-multi`:

    {{< text bash >}}
    $ cat <<EOF > ${KUBECFG_FILE}
    apiVersion: v1
    clusters:
       - cluster:
           certificate-authority-data: ${CA_DATA}
           server: ${SERVER}
         name: ${CLUSTER_NAME}
    contexts:
       - context:
           cluster: ${CLUSTER_NAME}
           user: ${CLUSTER_NAME}
         name: ${CLUSTER_NAME}
    current-context: ${CLUSTER_NAME}
    kind: Config
    preferences: {}
    users:
       - name: ${CLUSTER_NAME}
         user:
           token: ${TOKEN}
    EOF
    {{< /text >}}

1. _(Optional)_  Create file with environment variables for creating the remote cluster secret:

    {{< text bash >}}
    $ cat <<EOF > remote_cluster_env_vars
    export CLUSTER_NAME=${CLUSTER_NAME}
    export KUBECFG_FILE=${KUBECFG_FILE}
    export NAMESPACE=${NAMESPACE}
    EOF
    {{< /text >}}

At this point, the remote clusters' `kubeconfig` files have been created in the current directory.
The filename for a cluster is the same as the original `kubeconfig` cluster name.

## Instantiate the credentials for each remote cluster

Execute this work on the cluster running the Istio control
plane using the `WORK_DIR`, `CLUSTER_NAME`, and `NAMESPACE` environment values set during the
[Generate kubeconfig for remote clusters](#generate-kubeconfigs-for-remote-clusters) steps.

* _(Optional)_  Source the environment variables file created for the remote cluster secret:

    {{< text bash >}}
    $ source remote_cluster_env_vars
    {{< /text >}}

Istio can be installed in a different namespace other than
istio-system.

The local cluster running the Istio control plane does not need
it's secrets stored and labeled. The local node is always aware of
its Kubernetes credentials, but the local node is not aware of
the remote nodes' credentials.

Create a secret and label it properly for each remote cluster:

{{< text bash >}}
$ kubectl create secret generic ${CLUSTER_NAME} --from-file ${KUBECFG_FILE} -n ${NAMESPACE}
$ kubectl label secret ${CLUSTER_NAME} istio/multiCluster=true -n ${NAMESPACE}
{{< /text >}}

{{< warning_icon >}}
Kubernetes secret data keys have to conform to `DNS-1123 subdomain`
[format](https://tools.ietf.org/html/rfc1123#page-13), so the filename can't have
underscores for example.  To resolve any issue you can simply change the filename
to conform to the format.

## Uninstalling

> The uninstall method must match the installation method (`Helm and kubectl` or `Helm and Tiller` based).

### Use `kubectl` to uninstall istio-remote

{{< text bash >}}
$ kubectl delete -f $HOME/istio-remote.yaml
{{< /text >}}

### Alternatively use Helm and Tiller to uninstall istio-remote

{{< text bash >}}
$ helm delete --purge istio-remote
{{< /text >}}

## Remote cluster manual sidecar injection example

The following example shows how to use the `helm template` command to generate the
manifest for the remote cluster with automatic sidecar injection disabled.  Additionally,
the example indicates how to use the remote clusters' configmaps with the `istioctl kube-inject`
command to generate any application manifests for the remote cluster.

The following procedure is to be performed against the remote cluster.

> The endpoint IP environment variables need to be set as in the [above section](#set-environment-variables-for-pod-ips-from-istio-control-plane-needed-by-remote)

1.  Use the `helm template` command on a remote to specify the Istio control plane service endpoints:

    {{< text bash >}}
    $ helm template install/kubernetes/helm/istio-remote --namespace istio-system --name istio-remote --set global.remotePilotAddress=${PILOT_POD_IP} --set global.remotePolicyAddress=${POLICY_POD_IP} --set global.remoteTelemetryAddress=${TELEMETRY_POD_IP} --set global.proxy.envoyStatsd.enabled=true --set global.proxy.envoyStatsd.host=${STATSD_POD_IP} --set global.remoteZipkinAddress=${ZIPKIN_POD_IP} --set sidecarInjectorWebhook.enabled=false > $HOME/istio-remote_noautoinj.yaml
    {{< /text >}}

1.  Create a namespace for remote Istio.

    {{< text bash >}}
    $ kubectl create ns istio-system
    {{< /text >}}

1.  Instantiate the remote cluster's connection to the Istio control plane:

    {{< text bash >}}
    $ kubectl apply -f $HOME/istio-remote_noautoinj.yaml
    {{< /text >}}

1.  [Generate kubeconfig for remote clusters](#generate-kubeconfigs-for-remote-clusters)

1.  [Instantiate the credentials for each remote cluster](#instantiate-the-credentials-for-each-remote-cluster)

### Manually inject sidecars into application manifests

The following is an example `istioctl` command to inject sidecars into application manifests.  The commands should be run in a shell with `kubeconfig` context setup for the remote cluster.

{{< text bash >}}
$ ORIGINAL_SVC_MANIFEST=mysvc-v1.yaml
$ istioctl kube-inject --injectConfigMapName istio-sidecar-injector --meshConfigMapName istio -f ${ORIGINAL_SVC_MANIFEST} | kubectl apply -f -
{{< /text >}}

## Accessing services from different clusters

Kubernetes resolves DNS on a cluster basis. Because DNS resolution is tied to
the cluster, you must define the service object in every cluster where a
client runs, regardless of the location of the service's endpoints.
To ensure this is the case, duplicate the service object to every cluster
using `kubectl`. Duplication ensures Kubernetes can resolve the service name
in any cluster. Since the service objects are defined in a namespace, you must
define the namespace if it doesn't exist, and include it in the service
definitions in all clusters.

## Deployment considerations

The above procedure provides a simple and step by step guide to deploy a multicluster
environment.  A production environment might require additional steps or more complex
deployment options.  The procedure gathers the endpoint IPs of Istio services and uses
them to invoke Helm. This create Istio services on the remote clusters. As part of
creating those services and endpoints in the remote cluster Kubernetes will
add DNS entries into kube-dns.  This allows kube-dns in the remote clusters to
resolve the Istio service names for all envoy sidecars in those remote clusters.
Since Kubernetes pods don't have stable IPs, restart of any Istio service pod in
the control plane cluster will cause its endpoint to be changed. Therefore, any
connection made from remote clusters to that endpoint will be broken. This is
documented in [Istio issue #4822](https://github.com/istio/istio/issues/4822)

There are a number of ways to either avoid or resolve this scenario. This section
provides a high level overview of these options.

* Update the DNS entries
* Use a load balancer service type
* Expose the Istio services via a gateway

### Update the DNS entries

Upon any failure or pod restart kube-dns on the remote clusters can be
updated with the correct endpoint mappings for the Istio services.  There
are a number of ways this can be done. The most obvious is to rerun the Helm
install in the remote cluster after the Istio services on the control plane
cluster have restarted.

### Use load balance service type

In Kubernetes, you can declare a service with a service type to be
[`LoadBalancer`](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types).
A simple solution to the pod restart issue is to use load balancers for the
Istio services. You can then use the load balancer IPs as the Istio services's
endpoint IPs to configure the remote clusters. You may need balancer IPs for
these Istio services: `istio-pilot, istio-telemetry, istio-policy,
istio-statsd-prom-bridge, zipkin`

Currently, Istio installation doesn't provide an option to specify service types
for the Istio services. But you can modify the Istio Helm charts or the Istio
manifests yourself.

### Expose the Istio services via a gateway

This uses the Istio Ingress gateway functionality.  The remote clusters have the
`istio-pilot, istio-telemetry, istio-policy, istio-statsd-prom-bridge, zipkin`
services pointing to the load balanced IP of the Istio ingress.  All the services
can point to the same IP.  The ingress gateway is then provided with destination
rules to reach the proper Istio service in the main cluster.

Within this option there are 2 sub-options.  One is to re-use the default Istio ingress gateway
installed with the provided manifests or Helm charts.  The other option is to create another
Istio ingress gateway specifically for multicluster.

## Security

Istio supports deployment of mutual TLS between the control plane components as well as between
sidecar injected application pods.

### Control plane security

The steps to enable control plane security are as follows:

1.  Istio control plane cluster deployed with
    1.  control plane security enabled
    1.  `citadel` certificate self signing disabled
    1.  a secret named `cacerts` in the Istio control plane namespace with the [CA certificates](/docs/tasks/security/plugin-ca-cert/#plugging-in-the-existing-certificate-and-key)

1.  Istio remote clusters deployed with
    1.  control plane security enabled
    1.  `citadel` certificate self signing disabled
    1.  a secret named `cacerts` in the Istio control plane namespace with the [CA certificates](/docs/tasks/security/plugin-ca-cert/#plugging-in-the-existing-certificate-and-key)
        1.  The CA certificate for the remote clusters needs to be signed by the same CA or root CA as the main cluster.
    1.  Istio pilot service hostname resolvable via DNS
        1.  Required because Istio configures the sidecar to verify the certificate subject names using the `istio-pilot.<namespace>` subject name format.
    1.  Control plane IPs or resolvable host names set

### Mutual TLS between application pods

The steps to enable mutual TLS for all application pods are as follows:

1.  Istio control plane cluster deployed with
    1.  Global mutual TLS enabled
    1.  `citadel` certificate self signing disabled
    1.  a secret named `cacerts` in the Istio control plane namespace with the [CA certificates](/docs/tasks/security/plugin-ca-cert/#plugging-in-the-existing-certificate-and-key)

1.  Istio remote clusters deployed with
    1.  Global mutual TLS enabled
    1.  `citadel` certificate self signing disabled
    1.  a secret named `cacerts` in the Istio control plane namespace with the [CA certificates](/docs/tasks/security/plugin-ca-cert/#plugging-in-the-existing-certificate-and-key)
        1.  The CA certificate for the remote clusters needs to be signed by the same CA or root CA as the main cluster.

> The CA certificate steps are identical for both control plane security and application pod security steps.

### Example deployment

The following is an example procedure to install Istio with both control plane mutual TLS and application pod
mutual TLS enabled.  The example sets up a remote cluster with a selector-less service and endpoint for `istio-pilot` to
allow the remote sidecars to resolve the `istio-pilot.istio-system` hostname via its local Kubernetes DNS.

1.  *Primary Cluster.*  Deployment of the Istio control plane cluster

    1.  Create the `cacerts` secret from the Istio samples certificate in the `istio-system` namespace:

        {{< text bash >}}
        $ kubectl create ns istio-system
        $ kubectl create secret generic cacerts -n istio-system --from-file=samples/certs/ca-cert.pem --from-file=samples/certs/ca-key.pem --from-file=samples/certs/root-cert.pem --from-file=samples/certs/cert-chain.pem
        {{< /text >}}

    1.  Deploy the Istio control plane with control plane and application pod security enabled

        {{< text bash >}}
        $ helm template --namespace=istio-system \
          --values install/kubernetes/helm/istio/values.yaml \
          --set global.mtls.enabled=true \
          --set security.selfSigned=false \
          --set global.controlPlaneSecurityEnabled=true \
          install/kubernetes/helm/istio > ${HOME}/istio-auth.yaml
        $ kubectl apply -f ${HOME}/istio-auth.yaml
        {{< /text >}}

1.  *Remote Cluster.*  Deployment of remote cluster's istio components

    1.  Create the `cacerts` secret from the Istio samples certificate in the `istio-system` namespace:

        {{< text bash >}}
        $ kubectl create ns istio-system
        $ kubectl create secret generic cacerts -n istio-system --from-file=samples/certs/ca-cert.pem --from-file=samples/certs/ca-key.pem --from-file=samples/certs/root-cert.pem --from-file=samples/certs/cert-chain.pem
        {{< /text >}}

    1.  Set endpoint IP environment variables as in the [setting environment variables](#set-environment-variables-for-pod-ips-from-istio-control-plane-needed-by-remote) section

    1.  Deploy the remote cluster's components with control plane and application pod security enabled.  Also, enable creation of the `istio-pilot` selector-less service and endpoint to get a DNS entry in the remote cluster.

        {{< text bash >}}
        $ helm template install/kubernetes/helm/istio-remote \
          --name istio-remote \
          --namespace=istio-system \
          --set global.mtls.enabled=true \
          --set security.selfSigned=false \
          --set global.controlPlaneSecurityEnabled=true \
          --set global.remotePilotCreateSvcEndpoint=true \
          --set global.remotePilotAddress=${PILOT_POD_IP} \
          --set global.remotePolicyAddress=${POLICY_POD_IP} \
          --set global.remoteTelemetryAddress=${TELEMETRY_POD_IP} \
          --set global.proxy.envoyStatsd.enabled=true \
          --set global.proxy.envoyStatsd.host=${STATSD_POD_IP} > ${HOME}/istio-remote-auth.yaml
        $ kubectl apply -f ${HOME}/istio-remote-auth.yaml
        {{< /text >}}

    1.  [Generate kubeconfig for remote cluster](#generate-kubeconfigs-for-remote-clusters)

1.  *Primary Cluster.*  [Instantiate the credentials for each remote cluster](#instantiate-the-credentials-for-each-remote-cluster)

At this point all of the Istio components in both clusters are configured for mutual TLS between application
sidecars and the control plane components as well as between the other application sidecars.


text:
# **husk**

 Author: Alice "Duchess" Archer

 Copyright (c) 2015 Isaac Archer under the MIT License

Project Name: Husk

Project Description:

>Husk is a configurable irc bot using rirc v 0.3.4 [framework](https://github.com/The-Duchess/ruby-irc-framework)

>- it is configured via a ruby [script](https://github.com/The-Duchess/husk/blob/master/config.rb) file that sets variables for the irc bot

>- it is plugable using the plugin design and manager in rirc

>- it has a core set of [commands](https://github.com/The-Duchess/husk) to change state of the bot that can be reloaded during runtime for updates making it truly modular so it never has to restart.

Plugins

- [sed](https://github.com/The-Duchess/husk/blob/master/plugins/sed.rb) style search replace; note: requires linux core utils

- system [stats](https://github.com/The-Duchess/husk/blob/master/plugins/stats.rb); note: requires linux core utils

- git pull [update](https://github.com/The-Duchess/husk/blob/master/plugins/update.rb) plugin; note: requires git to be in your path

- [urban dictionary](https://github.com/The-Duchess/husk/blob/master/plugins/urbdict.rb) search; note: requires some libraries

>- require 'cgi'

>- require 'json'

>- require 'open-uri'

- [YouTube](https://github.com/The-Duchess/husk/blob/master/plugins/youtube.rb) video information; note: requires some libraries and gems

>- require 'google/api_client'

>- require 'json'

>- require 'uri'

>- require 'net/http'

>- require 'multi_json'

>- require 'date'

- [weather](https://github.com/The-Duchess/husk/blob/master/plugins/weather.rb) weather; note requires some libraries and gems

>- require 'net/http'

>- require 'optparse'

>- require 'open-uri'

>- require 'json'

>- require 'date'

repository: The-Duchess/husk

repo_name: The-Duchess/husk


text:
# Local Development

## Backend

### Initial configuration

1. First, create an `.env` file based on the one provided as example

   `cp GIT_PROJECT_DIR/Closure_Project/.env.example GIT_PROJECT_DIR/Closure_Project/.env`

   Alternatively, if the environment variable `ENV_PATH` is set, it will be used instead of the default `.env` path.
   (If you do so, it is recommended to use an absolute path)

2. You can modify the `DATABASE_URL` to refer to a local `sqlite` database. Note that the database path is relative to your working directory
   when executing the backend server via `python manage.py`(or a WSGI/ASGI web server), and not to the env file.

   To be consistent with the project, it is recommended you set it to `sqlite:///db.sqlite3`, and
   run the server within the `GIT_PROJECT_DIR/Closure_Project` folder, that is:

   ```shell
   cd GIT_PROJECT_DIR/Closure_Project
   python manage.py runserver
   ```

   (within a virtual environment of course)

3. Make sure  `GS_BUCKET_NAME` is commented out in order to use Django's default filesystem based static file storage, otherwise
   the cloud storage will be used, which requires deployment in order to propogate any changes.

repository: ScDor/Closure

gha_language: Python

repo_name: ScDor/Closure


text:
# Eventer

The libmtev eventer can be configured through a top-level `<eventer>`
configuration block.

```xml
<application>
  <eventer [ implementation="..." ]>
    <key>value</key>
    ...
  </eventer>
</application>
```

The `implementation` attribute is optional and must be supported on  the
platform; it is recommended that one omit this from configurataions.  Valid
values are `epoll`, `kqueue`, and `ports`.

The keys and values supported are:

 * ##### debugging

   If this key is present and the value is anything other than "0", eventer
   debugging facilities will be enabled.  This can be slow and should not be
   used in production.

 * ##### show_loop_callbacks_threshold

   Specify a millsecond threshold for logging of "slow" callbacks in eventer
   loops.  The default is 0 (all are logged), -1 disables logging.  Logging
   is sent to a log stream called `debug/eventer/callbacks/loop/<loopname>`.

 * ##### show_jobq_callbacks_threshold

   Like `show_loop_callbacks_threshold`, but for callbacks run in
   asynchronous job queues. Logging is sent to a log stream called
   `debug/eventer/callbacks/jobq/<queuename>`.

 * ##### rlim_nofiles

   Specified the number of file descriptors desired. libmtev will attempt to up
   the operating system limits to allow the application to open this many
   files.  The specified value must be at least 256.  If not specified, a
   default value of 1048576 will be used.

 * ##### default_queue_threads

   This specified the number of threads that should be used to manage the default
   asynchronous job queue.  If not specified, a value of 10 is used.

 * ##### concurrency

   The number of event loop threads to start.  This effects the concurrency
   of the default event loop and sets the default of any non-default event
   loops.  If not specified or specified as 0, the library will attempt to
   make a reasonable guess as to a good concurrency level based on the number
   of CPU cores in the system.

 * ##### loop_<name>

   This establishes a new named event loop and sets its concurrency and watchdog
   timeout to the provided values. The format is:
   `concurrency[,timeout_in_seconds]`

   If a concurrency value of 0 is provided, then the named event loop will use the
   default concurrency specified by the `concurrency` key.  Floating point notation
   can be used to specify subsecond or partial second timeouts.  If unspecified or
   specified as 0, the timeout will default to the global setting (which defaults
   to 5.0 unless overriden by the application).

 * ##### jobq_<name>

   This establishes a new named jobq and sets parameters around concurrency
   and memory safety.  The format of the value is:
   `concurrency[,min[,max[,safety[,backlog[,lifo]]]]]`.  Concurrency, min, max, and backlog are all
   unsigned integers. Concurrency must be greater than zero.  If minimum is omitted or
   zero, no minimum is set.  If max is omitted, it is set to min.  If max is
   zero, there is no maximum.  Safety can be one of `none` , `cs` , or
   `gc` (default).  For more information om memory settings see [eventer_jobq.h](https://github.com/circonus-labs/libmtev/tree/master/src/eventer/eventer_jobq.h) and [mtev_memory.h](https://github.com/circonus-labs/libmtev/tree/master/src/utils/mtev_memory.h). Backlog sets
   the advisory queue length backlog limit for the queue. The `lifo` setting instructs the
   jobq to process jobs last-in-first-out.  The values for this field is either `lifo` or
   `fifo`.

   > Note that this merely creates the jobq. One must find and use it
   > programmatically within the software.  It is designed to have a code-free
   > way of allowing operators to adjust parameters around jobqs used within
   > an application.

 * ##### default_jobq_ordering

   Specifies the default job consumption order for jobqs that don't explicitly
   declare an ordering requirement. Valid values are `lifo` and `fifo`. If
   unspecified, the default for this setting is FIFO.

 * ##### default_ca_chain

   Specified the path to a file containing a PEM encoded set of certificate authorities
   to trust by default.

 * ##### ssl_ctx_cache_expiry

   Sets the default number of seconds after which cached SSL contexts will be released.
   The default is 5 seconds.

 * ##### ssl_dhparam<bits>_file & ssl_dhparam<bits>

   By default 2048 bit NIST DH paramaters will be used.
   If you would like to create new ones, you may specify a file name and a new set of
   parameters of `bits` bits will be generated and stored for reuse.

repository: pjulien/libmtev

gha_license_id: NOASSERTION

repo_name: pjulien/libmtev


text:
![LICENSE](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)
![Security Status](https://img.shields.io/security-headers?label=Security&url=https%3A%2F%2Fgithub.com&style=flat-square)
![Gluten Status](https://img.shields.io/badge/Gluten-Free-green.svg)
![Eco Status](https://img.shields.io/badge/ECO-Friendly-green.svg)

# Personal portfolio

Team name: Team B

This project is for educational porpuses only. Pull request are welcome, but priority for project authors! Thank you for your cooperation!

Design: https://new-per.netlify.app/demo-3.html

## Project features

- Github pages
- multi-page
- content rendering with JS
- fontawesome icons
- SCSS animations
- JS import-export

## Authors

==== Matas [Github] (https://github.com/BoxInCoded) ====
==== Mykolas [Github] (https://github.com/Myk0l4s) ====
==== Agne [Github] (https://github.com/AgneR81) ====
==== Julius [Github] (https://github.com/Juliu51) ====
==== Dalius [Github] (https://github.com/DaliusLun)


text:
# TimeoutSensor
Timeout Sensor for Android Applications

![img](http://i.imgur.com/qesbp7B.png)

This library will make it easy to set a session timeout duration and monitor the application for inactivity.  If there has not been any user interaction for the specified amount of time, a dialog will pop up and give the user an additional 30 seconds to respond otherwise the application will kill itself.

Make sure to add to your gradle:

	allprojects {
		repositories {
			...
			maven { url 'https://jitpack.io' }
		}
	}

    	dependencies {
	        compile 'com.github.buradd:TimeoutSensor:1.8'
	}

To use, you must extend all of your activities with TimeoutActivity (or TimeoutCompatActivity if you use AppCompat):

    public class MainActivity extends TimeoutActivity {

    }

    //OR IF YOU USE APPCOMPAT,

    public class MainActivity extends TimeoutCompatActivity {

    }

Then, start the sensor and provide the duration (in minutes.):

    //This will start the sensor to check for 15 minutes of inactivity.
    TimeoutSensor.start(15);

You can also set the duration and call start separately:

    TimeoutSensor.setTimeoutDuration(15);
    TimeoutSensor.start();

You may stop the sensor at any time:

    TimeoutSensor.stop();

The dialog fragment can be customized:

    //set the Title
    TimeoutSensor.setDialogTitle("ATTENTION:");

    //set the Message
    TimeoutSensor.setDialogMessage("Your session is about to expire.");

    //set the Button Text
    TimeoutSensor.setDialogButton("STAY SIGNED IN");

    //set the TextView Text (this can take %s which will be replaced by the remaining seconds of the dialogs timer)
    TimeoutSensor.setDialogTextview("Session will expire in: %s seconds.");

![img](http://i.imgur.com/qesbp7B.png)

There is a sample APK available here:
https://github.com/buradd/TimeoutSensor/blob/master/sample/app/TimeoutSensorSample.apk

That's it!

repository: SefuZeph/TimeoutSensor

repo_name: SefuZeph/TimeoutSensor


text:
# Phone numbers
The Phone Numbers resource lets you get phone numbers for use with your programs and manage numbers you already have.

## Properties
| Property       | Description                                                                                |
|:---------------|:-------------------------------------------------------------------------------------------------|
| id             | The unique id of the phone number.                                                               |
| name           | A name you choose for this number.                                                               |
| number         | The telephone number in E.164 format.                                                            |
| nationalNumber | The telephone number in a friendly national format, e.g. (555) 5555-5555                         |
| city           | The city of the phone number.                                                                    |
| state          | The state of the phone number.                                                                   |
| applicationId  | The unique id of an Application you want to associate with this number.                          |
| application    | The URI of the application associated with the number for inbound phone calls and text messages. |
| fallbackNumber | Number to transfer an incoming call when the callback/fallback events can’t be delivered.        |
| price          | The monthly price for this number.                                                               |
| createdTime    | Date when the number was created. Timestamp follows the ISO8601 format (UTC).                    |
| numberState    | The phone number state, values are `enabled` or `released`                                       |

## GET phoneNumbers
Gets a list of your numbers. Since this operation uses HTTP GET, all the properties are specified as HTTP request parameters.

### Supported Parameters
| Parameter     | Description                                                                                | Mandatory |
|:--------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------|
| page          | Used for pagination to indicate the page requested for querying a list of phone numbers. If no value is specified the default is 0.                                          | No        |
| size          | Used for pagination to indicate the size of each page requested for querying a list of phone numbers. If no value is specified the default value is 25. (Maximum value 1000) | No        |
| applicationId | Used to filter the retrieved list of numbers by an associated application ID.                                                                                | No        |
| state         | Used to filter the retrieved list of numbers allocated for the authenticated user by a US state.                                                                             | No        |
| name          | Used to filter the retrieved list of numbers allocated for the authenticated user by it’s name.                                                                              | No        |
| city          | Used to filter the retrieved list of numbers allocated for the authenticated user by it’s city.                                                                              | No        |
| numberState   | Used to filter the retrieved list of numbers allocated for the authenticated user by the number state.                                                                       | No        |

### Example: List phone numbers

```shell
curl -v -X GET https://api.catapult.inetwork.com/v1/users/{userId}/phoneNumbers \
	-u {token}:{secret} \
	-H "Content-type: application/json"
```

```js
// Promise
client.PhoneNumber.list({size: 1000}).then(function(numbersResponse){});

// Callback
client.PhoneNumber.list({size: 1000}, function(err, numbersResponse){});
```

```csharp
var numbers = client.PhoneNumber.List(new PhoneNumberQuery {Size = 1000});
Console.WriteLine(numbers.First().Number);
// +1234568790
```

```ruby
numbers = PhoneNumber.list(client, {:size => 1000})
```

```go
numbers, _ := client.GetPhoneNumbers(&bandwidth.GetPhoneNumbersQuery{Size: 1000})
```

> The above command returns JSON structured like this:

```json
[
{
   "id": "{numberId1}",
   "application": "https://catapult.inetwork.com/v1/users/users/u-ly123/applications/a-j321",
   "number":"{number1}",
   "nationalNumber":"{national_number1}",
   "name": "home phone",
   "createdTime": "2013-02-13T17:46:08.374Z",
   "state": "NC",
   "price": "0.60",
   "numberState": "enabled"
},
{
   "id": "{numberId2}",
   "application": "https://catapult.inetwork.com/v1/users/users/u-ly123/applications/a-j123",
   "number":"{number2}",
   "nationalNumber":"{national_number2}",
   "name": "work phone",
   "createdTime": "2013-02-13T18:32:05.223Z",
   "state": "NC",
   "price": "0.60",
   "numberState": "enabled"
}
]
```

## POST phoneNumbers
Allocates a number so you can use it to make and receive calls and send and receive messages.

### Supported Parameters
| Parameter      | Description                                                                                | Mandatory |
|:---------------|:--------------------------------------------------------------------------------------------|:----------|
| number         | An available telephone number you want to use (must be in E.164 format, like +19195551212). | Yes       |
| name           | A name you choose for this number.                                                          | No        |
| applicationId  | The unique id of an Application you want to associate with this number.                     | No        |
| fallbackNumber | Number to transfer an incoming call when the callback/fallback events can’t be delivered.   | No        |

### Example: Allocate a phone number to your account
To allocate the phone number {number} with the name "home phone" and the fallbackNumber {fallback_number} you can make calls with it, send the following request:

```shell
curl -v -X POST https://api.catapult.inetwork.com/v1/users/{userId}/ \
	-u {token}:{secret} \
	-H "Content-type: application/json" \
		-d \
	'
	{
		"number": "+15555555555",
		"name": "home phone"
		"fallbackNumber": "{fallback_number}"
	}'
```

```js
//Allocate number +1234567980

// Promise
client.PhoneNumber.create({ number : "+1234567890" }).then(function(number){});

// Callback
client.PhoneNumber.create({ number : "+1234567890" }, function(err, number){});
```

```csharp
var number = await client.PhoneNumber.CreateAsync(new CreatePhoneNumberData {Number = "+1234567890"});
Console.WriteLine(number.Id);
// {numberId}
```

```ruby
number = PhoneNumber.create(client, {:number => "+1234567890"})
```

```go
number, _ := client.CreatePhoneNumber(&bandwidth.CreatePhoneNumberData{Number: "+1234567890"})
```

> The above command returns HTTP Header structured like this:

```
HTTP/1.1 201 Created
Location: /v1/users/{userId}/phoneNumbers/{numberId}
```

## GET phoneNumbers/{numberId}
Gets information about one of your numbers using the number's ID. No query parameters are supported.

or

Gets information about one of your numbers using the E.164 number string, like "+19195551212". Remember to URL encode the plus sign prefix. No query parameters are supported.

### Example: Get number properties by E.164 or Id

```shell
curl -v -X GET https://api.catapult.inetwork.com/v1/users/{userId}/phoneNumbers/%20{number} \
	-u {token}:{secret} \
	-H "Content-type: application/json"
```

```js
// Promise
client.PhoneNumber.get(numberId).then(function(number){});
// or
client.PhoneNumber.get("+1234567890").then(function(number){});

// Callback
client.PhoneNumber.get(numberId, function(err, number){});
// or
client.PhoneNumber.get("+1234567890", function(err, number){});
```

```csharp
var number = await client.PhoneNumber.GetAsync("+1234567890");
Console.WriteLine(number.Name);
// Home phone number
```

```ruby
number = PhoneNumber.get(client, "+1234567890")
```

```go
number, _ := client.GetPhoneNumber(numberId)
```

> The above command returns JSON structured like this:

```
{
   "id": "{numberId}",
   "application": "https://catapult.inetwork.com/.../applications/{applicationId}",
   "number":"{number}",
   "nationalNumber":"{national_number}",
   "name": "home phone",
   "createdTime": "2013-02-13T17:46:08.374Z",
   "city": "Raleigh",
   "state": "NC",
   "price": "0.60",
   "numberState": "enabled"
}
```

## POST phoneNumbers/{numberId}
Makes changes to a number you have. POST a new JSON representation with the property values you desire to the URL that you got back in the "Location" header when you first allocated it. Properties you don't send will remain unchanged. The "numberId" refers to the numberId or the number itself. When using the number itself remember to URL encode the plus sign prefix.

### Supported Parameters
| Parameter      | Description                                                                                | Mandatory |
|:---------------|:-----------------------------------------------------------------------------------------------------------------|:----------|
| applicationId  | The unique id of an Application resource you want to associate with this number for incoming calls and messages. | No        |
| name           | A name you choose for this number.                                                                               | No        |
| fallbackNumber | Number to transfer an incoming call when the callback/fallback events can’t be delivered.                        | No        |

### Example: Change the Application resource a phone number uses for inbound calls and messages

```shell
curl -v -X POST https://api.catapult.inetwork.com/v1/users/{userId}/phoneNumbers/{numberId} \
	-u {token}:{secret} \
	-H "Content-type: application/json" \
		-d \
	'
	{
		"applicationId": "{application_id}"
	}'
```

```js
// Promise
client.PhoneNumber.update(numberId, {applicationId: "{application_id}"}).then(function(){});

// Callback
client.PhoneNumber.update(numberId, {applicationId: "{application_id}"}, function(err){});
```

```csharp
await client.PhoneNumber.UpdateAsync(numberId, new UpdatePhoneNUmberData {
    ApplicationId = "{application_id}"
});
```

```ruby
phoneNumber.update({:application_id => "{application_id}"})
```

```go
client.UpdatePhoneNumber("{numberId}", &bandwidth.UpdatePhoneNumberData{ApplicationID: "{applicationId}"})
```

## DELETE phoneNumbers/{numberId}
Removes a number from your account so you can no longer make or receive calls, or send or receive messages with it. When you remove a number from your account, it will not be available to add back to your account, so be careful.

```shell
curl -v -X DELETE https://api.catapult.inetwork.com/v1/users/{userId}/phoneNumbers/{numberId} \
	-u {token}:{secret} \
	-H "Content-type: application/json"
```

```js
// Promise
client.PhoneNumber.delete(numberId).then(function(){});

// Callback
client.PhoneNumber.delete(numberId, function(err){});
```

```csharp
await client.PhoneNumber.DeleteAsync(numberId);
```

```ruby
phoneNumber.delete()
```

```go
client.DeletePhoneNumber("{numberId}")
```

repository: dtolb/bandwidth-slate-docs

repo_name: dtolb/bandwidth-slate-docs


text:
**autoupdateftp** uses for auto download file from ftp sever. Incremental downloads are implemented. What's more, it can maintain downloading the specified file directory.

***updateftp.conf***
```
#ftp attribute
ftp_host = your ftp host
username = ftp sever login username
password = ftp sever login password
#ftp_path used for setting the root directory
#in the ftp sever, '/' represents the root
#directory is the ftp sever root directory
ftp_path = /
#update_dirs used for setting auto-update directory
#below in the root directory of the ftp sever,
#format: data1, data2, '/' represents to update all.
update_dirs = /
#exclude_dirs used for setting ignore the directory
#below in the root directory of the ftp sever
#when download file from ftp sever. format: data1, data2, default is none.
#What's more, if you want to set the exclude_dirs,
#the update_dire = / is a requirement.
exclude_dirs = Trader_LL
#root_dir used for setting the root directory of saving data
#from the ftp sever
root_dir = data
```
***Dependencies***
**autoupdateftp** was developed on Windows 7. In principal, **autoupdateftp** should work with any Windows
distribution as long as the following software dependencies are satisfied.

1. Python [version 3.6.1 or higher]
2. Ftputil python Libtaries [version 3.3.1 or higher]
```
pip install ftputil
```

***run autoupdateftp***
```
python autoupdateftp
````

repository: gongshijun/autoupdateftp

repo_name: gongshijun/autoupdateftp


text:
# Introduction

- who am I?
- who are you and what do you do in your free time?
- who has had experience with programming?
- who knows what a programming language is?
- explain why I am using Python (and what it is)
    ```JavaScript
    function thisFunc(param) {
      if (this) {
        that();
      }
    }
    ```
    ``` Python
    def this_func(param):
      if this:
        that()
    ```
- where can I find resources?

## outline for course
- Week 1: execution, variables, booleans, if
- Week 2: blocks, loops, and modules
- Week 3: functions, scope, and exceptions
- Week 4: lists, tuples, and dictionaries
- Week 5: TBD
- Week 6: TBD

## Koding accounts

- does everyone have them set up?
- workspaces - what are they and how will we use them?
- what is a text editor?
- what is a terminal?
- how do I call programs from a terminal and what does that mean?
- IDLE (just FYI because the book uses IDLE)

# Basics

## getting started

### running basic expressions
How to run a program (Hello World)

### its okay to make mistakes.
An error just means that the program didn't work. Keep experimenting to get it
right.

its important to be precise though because computers will try to do whatever it
is you tell them to do

### order of operations

programs are full of operators and operands. Knowing the proper order that
things are executed is critical to successful programming.

## variables

### data types

- floating points
- integers
- strings

### operators with data types

```
'Alice' + ' is hungry'
'Alice' + 4
'Alice' * 5
```

### storing data types

```
name = 'Alice'
age = 7
age = age + 1
age += 1
name = 'Bob'
```

### variable names

RULES:
- single word (single_word)
- letters, numbers and underscore (_also_valid_2)
- cannot begin with number
- case sensitive (spam does not equal SPAM)
- use variable names that describe the container
- the book uses camelCase but we will use Python PEP8 standard
    (underscore_separated)

## comments
- Good programming not only ensures that the computer can understand what you
    want but also so other programmers (including yourself) can understand.
    Comments are an important part of communicating to other humans down the
    road who will read your code

## print
- print is one of the most important things you will ever learn in programming.
    You can place print statements anywhere in your code so that you can display
    a message to the screen. This can help you find the errors in your code as
    well as provide the foundation to many fun and interesting programs.

## input
- the raw_input function is how you can collect information from users who may
    run your program.

## len
- this function will tell you how many characters are in a string

## str(), int(), float()
- anything can typically be converted to a string but numbers need to be PARSED.
    Not all strings are numbers ('four' and '4'. Which one parses?)

# if, else, elif

### booleans
True and False are reserved words

#### comparison operators
- ==
- !=
- >
- <
- <=
- >=
- and
- or
- not

expressions

```
 42   <  50 == True
 50  ==  50 == True
 51  !=  50 == True
'42' !=  42 == True
```

combining expressions

```
(1 < 2) and (2 > 3) == False
(1 < 2) or  (2 > 3) == True
```

control flow

```
if name == 'Reed':
  print 'Hello Reed'
elif name == 'Britney':
  print 'Hello Britney'
else:
  print "I don't know you"
```

# Review
- variables and data types
- special functions
- booleans
- if, elif, else

# Homework

Review your program (basics.py)

## tip calculator

## grade calculator

## Practice Questions

repository: reedcwilson/programming-fundamentals

repo_name: reedcwilson/programming-fundamentals


text:
---
layout: post
title: "Human activity recognition from mobile inertial sensors using recurrence plots"
date: 2017-12-05 00:49:07
categories: arXiv_CV
tags: arXiv_CV Classification Recognition
author: Otávio A. B. Penatti, Milton F. S. Santos
mathjax: true
---

* content
{:toc}

##### Abstract
Inertial sensors are present in most mobile devices nowadays and such devices are used by people during most of their daily activities. In this paper, we present an approach for human activity recognition based on inertial sensors by employing recurrence plots (RP) and visual descriptors. The pipeline of the proposed approach is the following: compute RPs from sensor data, compute visual features from RPs and use them in a machine learning protocol. As RPs generate texture visual patterns, we transform the problem of sensor data classification to a problem of texture classification. Experiments for classifying human activities based on accelerometer data showed that the proposed approach obtains the highest accuracies, outperforming time- and frequency-domain features directly extracted from sensor data. The best results are obtained when using RGB RPs, in which each RGB channel corresponds to the RP of an independent accelerometer axis.

##### Abstract (translated by Google)
惯性传感器目前在大多数移动设备中都存在，并且这些设备在大多数日常活动中被人们使用。在本文中，我们提出了一种基于惯性传感器的人类活动识别方法，采用递归图（RP）和视觉描述符。所提出的方法的流水线如下：从传感器数据计算RP，计算来自RP的视觉特征，并将其用在机器学习协议中。由于RP生成纹理视觉模式，我们将传感器数据分类问题转化为纹理分类问题。基于加速度计数据对人类活动进行分类的实验表明，所提出的方法获得最高的精度，优于传感器数据直接提取的时域和频域特征。使用RGB RP时获得最佳结果，其中每个RGB通道对应于独立加速度计轴的RP。

##### URL
[http://arxiv.org/abs/1712.01429](http://arxiv.org/abs/1712.01429)

##### PDF
[http://arxiv.org/pdf/1712.01429](http://arxiv.org/pdf/1712.01429)


text:
# zorgpiraten
[![Netlify Status](https://api.netlify.com/api/v1/badges/19ed0eaa-1b85-4b01-a042-9d1e791a9e70/deploy-status)](https://app.netlify.com/sites/zorgpiraten/deploys)

This repository contains our exploratory data visualisation for [Pointer](https://pointer.kro-ncrv.nl/).
It shows all Dutch Healthcare institutions and their profits as a pecentage of their total revenues. It's possible to search for different institutions by name or filter the data on the past few years and on different types of healthcare.

To learn more about the reasons for building this application, please visit [Pointer.kro-ncrv.nl](https://pointer.kro-ncrv.nl/zorgcowboys).

## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development purposes.

### Prerequisites
To start working on this project, first clone this repository with `git clone https://github.com/lennartdeknikker/zorgpiraten.git`.
Then install the necessary node modules with `npm install`.

This application uses the vue-cli to run the development environment. It's recommended to install this globally with:
```
npm install -g @vue/cli
```

### Usage
Use the following commands to get the application running, build a minified production version in the dist folder or lint and fix files.

#### Compiles and hot-reloads for development
```
npm run serve
```

#### Compiles and minifies for production
```
npm run build
```

#### Lints and fixes files
```
npm run lint
```

### Settings
All data used in this visualisation is obtained from the `public/rawdata.json` file. This file can be changed to show data for different years or make corrections.

To add or change institutions to be highlighted, showing a gif and linking to other webpages going in depth on specific cases, it's possible to change the `public/zorgcowboys.json` file. Just add new institutions to the array like shown below or change the existing data.
```
  {
    "name": "De Kroon Zorginstelling B.V.",
    "link": "https://pointer.kro-ncrv.nl/artikelen/op-deze-manier-vind-je-zorginstellingen-die-megawinsten-maken",
    "gif": "de-kroon-zorginstelling-bv.gif"
  },
```
Don't forget to add the corresponding .gif files to the `public/images` folder.

## Built with
- [Vue](https://vuejs.org/) - the javascript framework used.
- [D3](https://d3js.org/) - Datavisualisation library

## Collaboration
When collaborating on this project, please do so as instructed below.
### Create a new issue
To make changes, please first create a new issue. Add this issue to the project 'zorgcowboys' and move it to the right place on the [kanban board](https://github.com/lennartdeknikker/zorgpiraten/projects/1) under projects.

### Create a new branch for this new issue
Then create a new branch locally for the specific issue you're working on:
```
git checkout -b issue-name
```
Create the new branch on the remote with
```
git push origin issue-name
```
Then push the branch and set the remote as upstream with
```
git push --set-upstream origin isse-name
```

### Push your changes
1. Stage changes with `git add .`.
2. Then add these staged changes to a new commit. When adding commits, please use the gitmoji's found [here](https://gitmoji.carloscuesta.me/) like this: `git commit -m ":tada: create the boilerplate"` and formulate the commit message as: this commit will \<commit message\>.
3. Push your commits to the branch with `git push`.

### Create a new pull request
When you have solved the issue, you've been working on, you can do a pull request to merge your branch with the master branch. To do that:
1. Go to the online repository.
2. Select the branch you've worked on.
3. Click "create pull request"
4. Add me: lennartdeknikker to "assignees"
5. Write down a summary of your changes
6. Create the pull request

After reviewing your request, your changes will be merged with the master branch and the branch for that issue will be deleted.

## Authors
- Eva Janssen
- [JesseJRos](https://github.com/JesseJRos)
- [lennartdeknikker](https://github.com/lennartdeknikker)

## License
This project is licensed under the MIT License - see the [LICENSE](./LICENSE) file for details.

## Acknowledgements
- Thanks to Pointer for clear briefing and helpful feedback along the way.
- Thanks to  Maaike van Cruchten, [Razpudding](https://github.com/Razpudding) and other teachers for inspiring coaching sessions.

repository: lennartdeknikker/zorgpiraten

gha_language: Vue

repo_name: lennartdeknikker/zorgpiraten


text:
# M0_C9 - Sudoku Validator
Repository with prompt and code for Module 1, Challenge 9: Sudoku Validator.

## Prompt
Sudoku is a number puzzle consisting of a 9x9 grid of single-digit numbers 1-9. The following constraints must be met when filling out a Sudoku puzzle:

- The numbers 1-9 appear only once in each row.
- The numbers 1-9 appear only once in each column.
- The numbers 1-9 appear only once in each 3x3 subsection that composes the main grid (9 total).

[Read more about the rules here](https://en.wikipedia.org/wiki/Sudoku).

### Requirements
Given a 2D list representing a completed Sudoku puzzle, write a function that validates it.

- The function takes in a 2D list (list containing lists) as a parameter.
- It returns `True` if the puzzle is a valid solution, `False` if not.

## Example 1
```
$ python3 sudoku_validator.py test_cases/valid1.txt
5 3 4 6 7 8 9 1 2
6 7 2 1 9 5 3 4 8
1 9 8 3 4 2 5 6 7
8 5 9 7 6 1 4 2 3
4 2 6 8 5 3 7 9 1
7 1 3 9 2 4 8 5 6
9 6 1 5 3 7 2 8 4
2 8 7 4 1 9 6 3 5
3 4 5 2 8 6 1 7 9

True
```

The above puzzle is valid, so the output should be `True`.

## Example 2
```
$ python3 sudoku_validator.py test_cases/invalid_duplicate1.txt
5 3 4 6 7 8 9 1 2
6 7 2 1 9 5 3 4 8
1 9 8 3 4 2 5 6 7
8 5 9 7 6 1 4 2 3
4 2 6 8 5 3 7 9 1
7 1 3 9 2 4 8 5 6
9 6 1 5 3 7 2 8 4
2 8 7 4 7 9 6 3 5
3 4 5 2 8 6 1 7 9

False
```

This example is invalid: the 8th row contains the number `7` multiple times. Alternatively, the 5th column also has `7` multiple times as well.

## Assumptions
- The grid will always be 9x9 (you don't have to check for invalid number of columns and rows)
- The grid will always contain numbers (you don't have to check for type)

## Notes and Hints
- Remember to check for edge cases. If you're curious, you can check the test cases in `test_cases`
- You can test your own puzzles by specifying a custom path to a file when running your program (e.g., `python3 sudoku_validator.py PATH/TO/TEST/FILE.txt`). See other test files in `test_cases` for the proper format

## Knowledge Tested
- Conditionals
- Loops
- Sets
- Lists
- Nested Data Structures

## Instructions
1. Fork this repository to your own account.
2. Clone the forked repository to your local computer.
3. Inside `sudoku_validator.py`, you will implement your code. You should only modify the function `validate()` and nothing else.
4. While you're writing and/or when you're done, you can execute the provided tests to verify your program works by running `python3 test_sudoku_validator.py`. All tests are passing if you see `OK` in the output. You may also test manually by inputing rows of input.


text:
---
layout: default
---

# 1995-10-02 - Time Lag (was Re: Yet Another "(Fwd) Internet  Euro-Clipper")

## Header Data

From<EMAIL_ADDRESS>(Patrick Horgan)

To<EMAIL_ADDRESS>Message Hash: bef29a8c452454129af6ee66d93dad288ce8d44d0ecf77f7d6af48d23dbeacbb

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1995-10-02 19:48:51 UTC

Raw Date: Mon, 2 Oct 95 12:48:51 PDT

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Patrick Horgan)
Date: Mon, 2 Oct 95 12:48:51 PDT
To<EMAIL_ADDRESS>Subject: Time Lag (was Re: Yet Another "(Fwd) Internet  Euro-Clipper")
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

>
> At 12:20 PM 10/2/95, Peter Trei wrote:
>
> >For those curious about the latency, I'm posting this at 12:08, on the US
> >east coast.
> >How long did it take to reach you?
>
> I got it at 09:14, Pacific Daylight Time, so there appears to be no lag.

I got it at 11:53 PDT.  I just checked the headers and the delay was split
in a couple of places.  (Correcting all times for PDT)

thunk              -> 9:10  -> alcor.process.com. (And they're off and running!)
alcor.process.com. -> 9:10  -> toad.com.          (delivered in 0 time:)
toad.com.          -> 11:29 -> relay3.uu.net.     (Sat on toad 2hrs, 19 min)
relay3.uu.net.     -> 11:54 -> mail2.pilot.net.   (Sat on relay3 25 mins )
mail2.pilot.net.   -> 11:53 -> verity.com.        (delivered into the past!)

Of course these delays can vary a few minutes either way because of
inaccuracies of time clocks on various machines.

Patrick
   _______________________________________________________________________
  /  These opinions are mine, and not Verity's (except by coincidence;).  \
 |                                                       (\                |
 |  Patrick J. Horgan         Verity Inc.                 \\    Have       |
 |<EMAIL_ADDRESS>      1550 Plymouth Street         \\  _ Sword     |
 |  Phone :<PHONE_NUMBER>     Mountain View                 \\/    Will    |
 |  FAX   :<PHONE_NUMBER>     California 94303             _/\\     Travel |
  \___________________________________________________________\)__________/

{% endraw %}
```

## Thread

+ Return to [October 1995](/archive/1995/10)

+ Return to<EMAIL_ADDRESS>(Patrick Horgan)](/authors/patrick_at_verity_com_patrick_horgan_)"

+ 1995-10-02 (Mon, 2 Oct 95 12:48:51 PDT) - Time Lag (was Re: Yet Another "(Fwd) Internet  Euro-Clipper") -<EMAIL_ADDRESS>(Patrick Horgan)_


text:
[VIRHT58E linename IS NOT AN OUTPUT LINE: CANNOT CONNECT termid](https://virtel.readthedocs.io/en/latest/manuals/virtel/Virtel459MG/messages.html?highlight=VIRHT58E#VIRHT58E)

`Module`
- VIRHTTP

`Meaning`
- A scenario invoked by terminal termid has attempted to make an outbound HTTP request via the HTTP line whose external name is linename, but the line definition does not permit outbound calls.

`Action`
- Modify the definition of line linename setting the “Possible calls” field to 2 or 3.

repository: olepicard/tldrZ

repo_name: olepicard/tldrZ


text:
---
title: Whanganui High School welcomes record number of first year students
feature_image:
  description: "New students Millie-Rose Broughton and Quin Harris-Campbell take a
    stroll around Whanganui High School with principal Martin McAllen. "
  credit: Bevan Conley
  image: https://res.cloudinary.com/whanganuihigh/image/upload/v1612472242/News/WHS_welcomes_record_number_of_first_year_students._chron_5.2.21._Photo_bevan_conley.jpg
news_author:
  date: 2021-02-04T20:57:03.278Z
  publication: Whanganui Chronicle
  name: Liz Wylie
show_in_slider: true
date: 2021-02-04T20:57:03.381Z
---
Whanganui High School has welcomed the largest intake of first-year students in its 63-year history.

Millie-Rose Broughton and Quin Harris-Campbell are two of the 367 students beginning their Year 9 education at the school this week.

Quin has come from Huntley School in Marton which had a roll of about 140 students last year.

"Even though WHS is a big school, it is quite easy to find your way around," Quin said.

"There are lots of areas I haven't visited yet but finding my way between classes has been okay."

Quin has a long-term ambition to study engineering although he's also a keen sportsman and would like to join the Central Stags cricket team someday.

Millie-Rose completed her primary education at Faith City School in Whanganui which has a roll of about 150 students.

"I'm interested in becoming a first responder and I'm also quite interested in veterinary science," she said.

"I'm enjoying the new experience of moving between classrooms and having different teachers."

Both students said coming to a school with a roll of almost 1500 doesn't phase them.

"Even though there are lots of people here it doesn't feel crowded," Quin said.

There are 29 students in each of their form classes and they believe that is a good number.

Principal Martin McAllen said class sizes were something he liked to reassure prospective students and parents about before they come to the school.

"Some think that because we're a big school, we have big classes which is not the case," he said.

"Year 9 students have come from over 20 schools in this region and I visited as many as I could last year.

"After the Covid disruptions in 2020, we tried something different and invited new students and their parents to visit during class times and it worked so well, we're considering doing it again this year."

McAllen said most students coped well during the Covid-19 level 4 lockdown last year although there was a fair amount of anxiety for some students and families as well as staff.

"The early days of the lockdown were not so bad but as time went on and uncertainty grew, it was an anxious time. There was a range of responses and we had to make sure to maintain good communication with our students and families.

"Being such a big workplace, there was a lot of logistical planning involved when we reopened - we had to order a lot of hand sanitiser as there 78 classrooms as well as common areas."

McAllen said he hopes there won't need to be another lockdown but the school would cope well if there was.

WHS has an extensive rebuilding programme scheduled for 2021.

The digital technology department will be remodelled and there will be new decking outside the canteen as well as more covered areas around the school.

"There will also be 44 new outdoor tables made of permanent materials that won't deteriorate like a lot of the wooden ones have," McAllen said.

WHS will hold a Year 9 Parents Information Evening on February 17.

gha_language: Blade


text:
[grunt-runner](https://atom.io/packages/grunt-runner)
================

Build your project using Grunt from Atom.

![in action!](http://i.imgur.com/bqn9QQY.png)

## How to use
 1. Open a project with a Gruntfile in the project root.
 2. Open the task list (`ctrl-alt-g`) and choose a task to run, or input a new one.
 3. The output from the grunt task will be shown in bottom toolbar. Toggle
 the log with `ctrl-alt-t`, toggle the entire toolbar with
 `ctrl-alt-shift-t`. The toolbar will appear automatically if Grunt Runner was able to find and
 parse a `Gruntfile`, otherwise you can toggle it on yourself.
 4. If your task doesn't end automatically (e.g. watches files for changes) you
 can force it stop from the toolbar or by pressing `ctrl-alt-shift-g`.

## Troubleshooting
 1. By default this package will try to use the the grunt module in your `[projectDir]/node_modules`
 directory. If for some reason that doesn't work, you can choose a path to look for the grunt module
 in by going to the settings. (e.g. `/usr/bin` or `~/path-to-global/node_modules`)
 2. For OS X Yosemite (and higher?) PATH error see this article https://github.com/kokarn/atom-grunt-runner/wiki/Config#user-content-troubleshooting-for-yosemite-os-x-1010
 3. If your project has more than one Gruntfile.js or Gruntfile.js is not located in a project root folder then you can use the *Gruntfile Paths* setting. The order matters: first valid Gruntfile found will be used.

repository: kokarn/atom-grunt-runner

gha_language: CoffeeScript

repo_name: kokarn/atom-grunt-runner


text:
# Windows 7

## Windows

* [TurboTop](http://www.savardsoftware.com/downloads/ttsetup.exe) - make windows appear always on top.

## Time

* [Hourglass](http://chris.dziemborowicz.com/apps/hourglass/) - counter up/down (incl. MM:SS), always on top, pop up, sounds. [Formats](http://chris.dziemborowicz.com/apps/hourglass/#details): "2:00 pm"

license: Unlicense

repository: nikolaygit/webdev

repo_name: nikolaygit/webdev


text:
jurov
=====

jurov is a compiler for the MiniJava language. Is is written in C and
should compile on Mac OS X and Linux.

For an introduction to MiniJava, see the documentation.

Dependencies
------------
* [Python](http://www.python.org/) >= 2.3 or
  [Jython](http://www.jython.org/) >= 2.5
* [bison](http://www.gnu.org/software/bison/)
* [flex](http://flex.sourceforge.net/)

Building
--------
First, make sure that you have the dependences listed above installed.
Then, to build jurov, simply run
    ./waf configure build

To remove all the binaries produced by the build, run
    ./waf distclean

Specs
-----
jurov have been developed using BDD. It uses
[CuTest](http://cutest.sourceforge.net/) as the test framework with additional
macros on top. Since CuTest is so small, it is bundled
together with jurov. To run all the specs, just run
    ./waf configure build --spec

Documentation
-------------
jurov uses [Doxygen](http://www.stack.nl/~dimitri/doxygen/) for all its
documentation. To build the documentation you first need to install
Doxygen. When doxygen is installed, run
    cd doc/ && doxygen

To view the documentation, just open
    doc/build/html/index.html

with your favorite browser.

License
-------
jurov is licensed under the BSD license (3-clause BSD), see the LICENSE file
for more details.

repository: edvbld/jurov

repo_name: edvbld/jurov


text:
# Useful Tools

These are the most useful tools out there for AzerothCore development.

- [Keira3](https://www.azerothcore.org/Keira3/) is a Database Editor for AzerothCore. Learn more about the tool [here](https://github.com/azerothcore/keira3#readme).

- [SpellWork](https://github.com/azerothcore/spellwork) is a tool to browse and display information about World of Wacraft spells. Learn more about the tool [here](https://github.com/azerothcore/spellwork#readme).

- [Unused Guid Search](https://github.com/azerothcore/Unused-Guid-Search) is a tool to find entry or GUID gaps in the database. Learn more about the tool [here](https://github.com/azerothcore/Unused-Guid-Search#readme).

- [Waypoint Creator](https://github.com/malcrom/WaypointCreator) is a tool to create waypoints from sniffed packet data. Learn more about the tool [here](https://github.com/malcrom/WaypointCreator#readme).

- [WoW Flags Checker](https://github.com/azerothcore/wow-flags-checker) is a web based tool to find all flags in a bitmask for creatures. Learn more about the tool [here](https://github.com/azerothcore/wow-flags-checker#readme).

- [WoW Database Editor](https://github.com/BAndysc/WoWDatabaseEditor) is an IDE for Smart Scripts and database editing. Learn more about the tool [here](https://github.com/BAndysc/WoWDatabaseEditor#readme)

- [AoWoW](https://github.com/azerothcore/aowow) is an armory/database viewer adapted for AzerothCore. Learn more about the tool [here](https://github.com/azerothcore/aowow#readme)

If you'd like to find more tools you can check out the [AzerothCore Catalogue](https://www.azerothcore.org/catalogue.html).

If you have made a useful tool that you would like to be forked or featured in the catalogue, join the Discord server and ping one of the Staff.

repository: azerothcore/wiki

gha_language: CSS

repo_name: azerothcore/wiki


text:
## pdf xfa form to xml with pdf extractor sdk in VBScript using ByteScout Data Extraction Suite

### pdf xfa form to xml with pdf extractor sdk in VBScript

Here you may get thousands pre-made source code samples for simple implementation in your own programming VBScript projects. ByteScout Data Extraction Suite helps with pdf xfa form to xml with pdf extractor sdk in VBScript. ByteScout Data Extraction Suite is the bundle that includes three SDK tools for data extraction from PDF, scans, images and from spreadsheets: PDF Extractor SDK, Data Extraction SDK, Barcode Reader SDK.

Save time on writing and testing code by using the code below and use it in your application. To use pdf xfa form to xml with pdf extractor sdk in your VBScript project or application just copy & paste the code and then run your app! Check these VBScript sample code examples to see if they acknowledge to your needs and requirements for the project.

Visit our website to get a free trial version of ByteScout Data Extraction Suite. Free trial contains many of source code samples to help you with your VBScript project.

## REQUEST FREE TECH SUPPORT

[Click here to get in touch](https://bytescout.zendesk.com/hc/en-us/requests/new?subject=ByteScout%20Data%20Extraction%20Suite%20Question)

or just send email to [support@bytescout.com](mailto:support@bytescout.com?subject=ByteScout%20Data%20Extraction%20Suite%20Question)

## ON-PREMISE OFFLINE SDK

[Get Your 60 Day Free Trial](https://bytescout.com/download/web-installer?utm_source=github-readme)
[Explore SDK Docs](https://bytescout.com/documentation/index.html?utm_source=github-readme)
[Sign Up For Online Training](https://academy.bytescout.com/)

## ON-DEMAND REST WEB API

[Get your API key](https://pdf.co/documentation/api?utm_source=github-readme)
[Explore Web API Documentation](https://pdf.co/documentation/api?utm_source=github-readme)
[Explore Web API Samples](https://github.com/bytescout/ByteScout-SDK-SourceCode/tree/master/PDF.co%20Web%20API)

## VIDEO REVIEW

[https://www.youtube.com/watch?v=NEwNs2b9YN8](https://www.youtube.com/watch?v=NEwNs2b9YN8)

<!-- code block begin -->

##### ****XfaFormToXml.vbs:**

```
' Create Bytescout.PDFExtractor.XMLExtractor object
Set extractor = CreateObject("Bytescout.PDFExtractor.XFAFormExtractor")

extractor.RegistrationName = "demo"
extractor.RegistrationKey = "demo"

' Load sample PDF document
extractor.LoadDocumentFromFile "..\..\samplexfa.pdf"

' Iterate through content types. See type descriptions below.
For i = 0 To 12

    count = extractor.GetCount(i) ' Get count of files of given type

    For j = 0 To count - 1
        extractor.SaveToFile i, j, CStr(i) & "-" & CStr(j) & ".xml"
    Next

Next

WScript.Echo "XFA form data has been extracted to XML files."

' XFAFormContentType enumeration:
'
' 0 - "config" type;
' 1 - "connectionSet" type;
' 2 - "datasets" type;
' 3 - "form" type;
' 4 - "localeSet" type;
' 5 - "postamble" type;
' 6 - "preamble" type;
' 7 - "schema" type;
' 8 - "template" type;
' 9 - "xfdf" type;
' 10 - "xmpmeta" type;
' 11 - "<xdp:xdp>" opening tag type;
' 12 - "<xdp:xdp>" closing tag type.

```

<!-- code block end -->

url: https://raw.githubusercontent.com/bytescout/ByteScout-SDK-SourceCode/67a20983df78dea26d2a8f25ec98000d3ec81928/Data Extraction Suite/VBScript/Pdf xfa form to xml with pdf extractor sdk/README.md

repository: bytescout/ByteScout-SDK-SourceCode

gha_language: HTML

repo_name: bytescout/ByteScout-SDK-SourceCode


text:
---
title: Salvage crews begin pumping fuel
tags:
  - May 1978
---

Salvage crews begin pumping fuel oil off the Florida Silverbow in an effort to refloat her from a reef 13 miles northeast of Key West. [Photo] [In the Keys Area News.]

Newspapers: **Miami Morning News or The Miami Herald**

Page: **1**, Section: **C**


text:
# Blueprintnotincluded

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.3.8.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.

## Running unit tests

Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).

## Localization
If you want to contribute translations to Blueprintnotincluded, you can edit files of your language in [i18n](./src/i18n). You can use Poedit to edit those XLF files. If the file for your language is not there, please create an issus. Alternatively you can add it by yourself in the following steps:
1. add your language in the `languages` field of [xliffmerge.json](./xliffmerge.json)
2. Run `npm run extract-i18n`
3. Add your language in [angular.json](./angular.json)(`projects.blueprintnotincluded.i18n.locales`)
4. To translate the in-game names (elements and buildings name etc.), an in-game string file (.po) should be added to [src\assets\strings](src\assets\strings). It should also be mentioned in [game-string-service.ts](src\app\module-blueprint\services\game-string-service.ts).
5. (Optional) To sever a localized build, a new configuration in [angular.json](./angular.json) is needed.
6. (Optional) Finally you can add the new language to the [top manual](src\app\module-blueprint\components\component-menu\component-menu.component.ts).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).

repository: simonlourson/blueprintnotincluded

gha_language: TypeScript

repo_name: simonlourson/blueprintnotincluded


text:
---
date: 2020-02-21
title: Frittata (Oven edition)
categories:
  - Breakfast
  - Snack
  - High Protein
featured_image: https://res.cloudinary.com/recipeimages/image/upload/v1582806218/recipe-images/frittata_i9mpax.jpg
recipe:
  servings: 4 big servings
  prep: 10 minutes
  cook: 35 minutes
  ingredients_markdown: |-
    * 110 gr bell peppers
    * 60 gr mushrooms
    * 60 gr onions
    * 90 gr zucchini
    * 160 gr egg whites
    * 120 gr low fat milk
    * 30 gr olives (kalamon)
    * 110 gr feta light
    * 2 eggs
    * salt / pepper / oregano
  directions_markdown: |-
    1. Pre heat oven to 180°C.
    2. Chop all the veggies into small pieces and deep fry using a non-stick frying pan (you can add olive oil but it is not necessary because all of the veggies have their own liquids). Afterwards, put all of the veggies into a bowl to cool down for 5 mins.
    3. Crumble the feta cheese with your hands into a different bowl.
    4. Whisk the mix of egg whites, eggs, milk, salt, pepper and oregano into a different bowl.
    5. Add all of the ingredients into the bowl with the eggs and whisk the mix until all of the ingredients are merged.
    6. Pour the mix into an ovenproof dish and bake at 180°C for 30' - 35' (It doesn't hurt to keep an eye in the oven every now and then :) ).
  tips_markdown:
    \"Store it in the refrigerator and you will have every morning a delicious breakfast :) \"
---
Frittata is an egg-based Italian dish similar to an omelette or crustless quiche or scrambled eggs, enriched with additional ingredients such as meats, cheeses or vegetables. The word frittata is Italian and roughly translates to "fried".

The Italian word frittata derives from friggere and roughly means "fried". This was originally a general term for cooking eggs in a skillet, anywhere on the spectrum from fried egg, through conventional omelette, to an Italian version of the Spanish omelette, made with fried potato. Outside Italy, frittata was seen as equivalent to "omelette" until at least the mid-1950s.

This particular recipe has a twist. It is baked in the oven in order to reduce the overall caloric intake.

repository: DDimitris/recipes-of-a-psychopath

repo_name: DDimitris/recipes-of-a-psychopath


text:
## SSL Handshake Status Check

The *SSL Handshake Check* checks that SSL certificates are valid and a TLS handshake can be completed successfully against the domain/port specified.

The check runs every 5 minutes (spec.runInterval), with a check timeout set to 3 minutes (spec.timeout). If the check
does not complete within the given timeout it will report a timeout error on the status page.

#### NOTE:
Self-signed certificate checks are not supported by this check. Please use the *ssl-selfsign-handshake* check for TLS handshake checks on self-signed certificates.

#### SSL Handshake Check Kube Spec:
```yaml
apiVersion: comcast.github.io/v1
kind: KuberhealthyCheck
metadata:
  name: ssl-handshake
  namespace: kuberhealthy
spec:
  runInterval: 5m
  timeout: 3m
  podSpec:
    containers:
      - env:
          # Domain name env variable must be updated to the domain on which you wish to check the SSL for
          - name: DOMAIN_NAME
            value: "google.com"
          # If not using default SSL port of 443, port name env variable must be updated
          - name: PORT
            value: "443"
        image: kuberhealthy/ssl-handshake-check:v1.2.0
        imagePullPolicy: IfNotPresent
        name: main
        resources:
          requests:
            cpu: 10m
            memory: 50Mi
```

#### How-to

To implement the SSL Handshake Check with Kuberhealthy, update the spec sheet to the domain name and port number you wish to test and apply:

`kubectl apply -f ssl-handshake-check.yaml`

You can use the default values as well by running:

`kubectl apply -f https://raw.githubusercontent.com/Comcast/kuberhealthy/v2.3.0/cmd/ssl-handshake-check/ssl-handshake-check.yaml`

 Make sure you are using the latest release of Kuberhealthy 2.3.0.


text:
# fully-customisable-neural-network
 This is the implementation of a fully customizable neural network with arbitrary no. of hidden layers using only NumPy, in Python.

 # Documentation
 - tanh activation function has been used in this model.
 - ```tanhderiv(K)```: calculates the derivative of the tanh function.
 - ```initialisetheta(m,n,nodes,yn)```: initialises the parameter theta for all the given layers.
 - ```hiddenlayer(m,nodes)```: initialises the hidden layers with one in all nodes.
 - ```forwardpropogation(x,theta,hidden)``` : performs a pass of forward propogation on X and returns the output as well as the updated
                                              value of hidden layers.
 - ```delta_function(m,hidden,output,y,theta)``` : Calculates derivative of  loss with respect to activations in each layer.
 - ``` update_theta(x,delta,hidden,theta)``` : Updates the value of weights for a single pass of forward and backward propogation.
 - ```main()``` : performs the forward and backward propogation a given number of times to minimise the loss function.


text:
Buttons Debounce
=============

Allows for the ease of using a button. Automatically debounces and advances states as required. Supports short press, long press, and button releases based actions to occur.

repository: CraigComberbach/ButtonControl

branch_name: refs/heads/GenericInterface

gha_language: C

repo_name: CraigComberbach/ButtonControl


text:
# Path Suggestion

## Usage

Can reduce suggestions by namespace, path, etc.

## Setup

```
./gradlew genSources
```

Then import the gradle project in Intellij Idea.

## License

The project is under the Unlicense.

repository: liachmodded/pathsuggestion

gha_license_id: Unlicense

repo_name: liachmodded/pathsuggestion


text:
# sparsify [WIP]
A simple, flexible, no-nonsense neural network sparsification library for PyTorch

## What ?
Sparsify is a pruning library that aims to make research in the field of pruning, model compression,
sparse neural networks easy. You can take your PyTorch model and replace conv, dense layers with
masked layers. The pruner class has everything you need for weight pruning, but can easily be
extended for other types of importance measures.

## Currently supported:
* Weight and unit pruning
    * Global and per-layer pruning
    * One time and Ramping pruning
    * Weight, mask reset

## To-do:
* Implement Single shot pruning algorithms like SNIP, GraSP
* Have a generalized pruner class that can take in any pytorch model instead of replacing
layers for a given model (use hooks to override forward method)
* Extend support for Language models, Transformers
* Write unit-tests, examples

### Code Credits
These repositories have been helpful.
* [Some help in pruning methods](https://github.com/srk97/defense)
* [Vision models](https://github.com/pytorch/vision/tree/master/torchvision/models)

### Contributions
Please feel free to suggest ways to improve or add new features, open an issue for the same.

repository: DwaraknathT/sparsify

repo_name: DwaraknathT/sparsify