text:
# Getting Started gRPC with Go

![Go gRPC](./go-grpc.png)
> Credit https://tutorialedge.net/golang/go-grpc-beginners-tutorial/

### What is gRPC?

>  gRPC is a modern, open source remote procedure call (RPC) framework that can run anywhere

Remote Procedure Calls are something that we use within distributed systems that allow us to communicate between applications. More specifically, it allows us to expose methods within our application that we want other applications to be able to invoke.

### Prerequisites
* Go plugins for the protocol compiler:

* Install the protocol compiler plugins for Go using the following commands:
```bash
$ export GO111MODULE=on  # Enable module mode
$ go get google.golang.org/protobuf/cmd/protoc-gen-go \
         google.golang.org/grpc/cmd/protoc-gen-go-grpc
```

* Update your PATH so that the protoc compiler can find the plugins:
```bash
$ export PATH="$PATH:$(go env GOPATH)/bin"
```
### Usage
First, you need to split the screen with to parts

In the first part of the screen you need to start server with the command:
```bash
$ go run server.go
```
and you'll see the following message:
```bash
gRPC server listening on port 9000
```
After that, you need to start a client to send a request to the gRPC server at the second part of the screen:
```bash
$ go run client.go
```
As soon as you type a command above, you will the see following messages in both screen:
```bash
# On the server side
$ Receive message body from client: Hello From Client !

# On the client side
$  Response from server: Hello From the Server!
```
### With 3rd party client called `grpcurl`

On macOS, grpcurl is available via Homebrew:
```bash
$ brew install grpcurl
```

First, you should start the gRPC server like above:
```bash
$ go run server.go
```

Then, you can get the service list exposed by the service with the command below:
```bash
$ grpcurl -plaintext localhost:9000 list
$ grpcurl -plaintext localhost:9000 list chat.ChatsService
$ grpcurl -plaintext localhost:9000 describe chat.ChatsService.SayHello
```

Invoking gRPC method expose by the service:
```bash
$ grpcurl -d '{"body": "hello from iTerm2"}' -plaintext localhost:9000 chat.ChatsService/SayHello
```


text:
# concorde-cookie
[![npm version](https://badge.fury.io/js/%40wetransfer%2Fconcorde-cookie.svg)](https://badge.fury.io/js/%40wetransfer%2Fconcorde-cookie)

Cookie module. Handy functions to deal with cookies on the browser.

## Installation

```sh
npm install @wetransfer/concorde-cookie --save
```

## Usage

### In the browser

Import the package if your are using a package bundler like Webpack or Parcel:

```js
import Cookie from '@wetransfer/concorde-cookie';

if (Cookie.get('SSID')) {
  // Do some magic!
}
```

Or load directly the final bundle on your browser, using a script tag. All concorde.js modules will be available in a global variable called `WT`:

```html
<!-- This will load the latest version of @wetransfer/concorde-cookie module -->
<script<EMAIL_ADDRESS><script>
  WT.cookie.set('SSID', 'BBlPjuhTimjov9RCB', { secure: true });
</script>
```

### On the server

```js
const Cookie = require('@wetransfer/concorde-cookie');

Cookie.set('SSID', 'BBlPjuhTimjov9RCB', { secure: true });
```

## Methods

**Cookie.configure**

Configure default options used when settings values for cookies. If all your cookies must present the same property, like secure, use this method before setting the cookie values.

```js
Cookie.configure({ secure: true });
Cookie.set('foo', 'bar');
// => foo=bar; secure'
```

The following options can be configured:

```js
Cookie.configure({
  // Cookie expiration date
  expires: new Date('Fri, 01 Jan 2016 09:05:12 GMT'),
  // Sets the URI to which the Cookie applies. Must be an absolute path.
  path: '/path',
  // Sets the domain to which the Cookie applies. If a domain is specified, subdomains are always included.
  domain: 'wetransfer.com',
  // Cookie to only be transmitted over secure protocol as https.
  secure:true,
});
```

**Cookie.get**

Get the value from a cookie, given a cookie name.

```js
Cookie.get('foo');
// => 'bar'

// Default value in case cookies are not available or the value has not been set previously.
Cookie.get('nonexistant', { defaultValue: 1 });
// => 1

// If raw property is true, the value of the cookie is not decoded.
Cookie.get('bar', { raw: true });
// => 'bar%20value'
```

**Cookie.set**

Set the value for a cookie. If extra options are specified, they will override default options defined with `configure method`.

```js
Cookie.set('foo', 'bar');
// => 'foo=bar'

// Set extra options for the current cookie
Cookie.set('foo', 'bar', { secure: true});
// => 'foo=bar; secure'
```

**Cookie.unset**

Unsets the value of a cookie, with `null`, and expires it.

```js
Cookie.unset('foo');
// => 'foo=null; expires=Thu, 21 Dec 2017 10:57:39 GMT'
```

## Development

In case you want to develop/debug this module while integrating with other project, please follow these steps:

* Run `npm link` to create a global symlink to that module
* Run `npm run build:watch` to listen to changes and rebuild the module
* Link to this module from your project with `npm link @wetransfer/concorde-cookie`

license: MIT

branch_name: refs/heads/master

extension: md

gha_language: JavaScript

gha_license_id: MIT

license_type: permissive


text:
# CONTRIBUTING

Contributions are always welcome, no matter how large or small. Before contributing, please read the
[code of conduct](CODE_OF_CONDUCT.md).

## Setup

From the root of the repository:

```sh
npm install
npm run build -- --scope=@netlify/framework-info
npm test -- --scope=@netlify/framework-info
```

## Releasing

Merge the release PR

### Creating a prerelease

1. Create a branch named `releases/framework-info/<tag>/<version>` with the version and tag you'd like to release.
2. Push the branch to the repo.

For example, a branch named `releases/framework-info/rc/4.0.0` will create the version `v4.0.0-rc` and publish it under
the `rc` tag.

## License

By contributing to Netlify Node Client, you agree that your contributions will be licensed under its
[MIT license](LICENSE).

repository: netlify/build

branch_name: refs/heads/main

gha_language: TypeScript

repo_name: netlify/build


text:
# OSecurityUser - getPassword()

Retrieves the user password.

## Passwords

Users in OrientDB have passwords, allowing you to authenticate their access to the Server.  Using this method you can retrieve the password from the user instance.

### Syntax

```
String OSecurityUser().getPassword()
```

#### Return Value

This method returns a `String` instance, which represents the password for the account.

repository: orientechnologies/orientdb-docs

gha_language: CSS

repo_name: orientechnologies/orientdb-docs


text:
  OFV

A responsive front-end for an online fruits and vegetables store

## Table of Contents
- [Synopsis](#synopsis)
- [Install](#install)
- [Usage](#usage)
- [Screenshots](#screenshots)
- [License](#license)

## Synopsis
The problem put forward was to design a responsive web front-end for an online fruit
and vegetable store using the Bootstrap framework.

The website should provide functionality for the following :

+ User login and registration
+ Showcase of products available for sale
+ Specific item information available for each item
+ User comments for each item
+ Functionality to present current specials to the customer
+ The website needs to be fully responsive

 **[Click here to view a demo of this website](https://www.joshcannons.com/ofv/)**

## Install

First, make a directory to install the files to and change to that directory using :

```bash
 mkdir ofv && cd ofv
```

Then all you need to do is clone the project from github into the directory by using :

```bash
 git clone https://github.com/josh-privata/OFV.git
```

## Usage

To use this application simply view the 'default.html' file in a web browser.

Assuming you are still in the ofv directory, this can be done from the terminal using the
command :

```bash
$ google-chrome default.html
```

or

```bash
$ firefox default.html
```

or

```bash
$ chromium default.html
```

**Note :** This application requires javascript to be run in the browser

## Screenshots

## License
[BSD](LICENSE) Copyright (c) 2016 [Josh Cannons](http://joshcannons.com).

repository: josh-privata/OFV-School

repo_name: josh-privata/OFV-School


text:
# Smith: Open-source framework for rapid creation of AI agents

## Overview

I'm honestly not sure yet what Smith should be. I'll fill this out as soon as
I know more.

By the way, I named it Smith after the character Agent Smith in the Matrix.
I also intend for this framework to function as a smithy for quickly creating
AI agents.

In the meantime, here are some nice quotes.

## Quotes

> "The unexamined life is not worth living." - Socrates

> "Every man is guilty of all the good he did not do." - Voltaire

> "The line dividing good and evil cuts through the heart of every human
> being." - Aleksandr Solzhenitsyn

> "For every thousand hacking at the leaves of evil, there is one hacking
> at the root." - Henry David Thoreau

> "Those who do not feel the littleness of great things in themselves are
> apt to overlook the greatness of little things in others." - Okakura Kakuzo

> "While nothing is easier than to denounce the evildoer, nothing is harder
> than to understand him." - Fyodor Dostoevsky

> "There are only 10 kinds of people in the world.
>  Those who understand binary and those who don't."

repository: justingaylor/smith

extension: markdown

gha_language: Ruby

repo_name: justingaylor/smith


text:
# Events

nodemon will emit events based on the child process.

## Commands

- restart
- config:update
- quit

## States

- start - child process has started
- crash - child process has crashed (nodemon will not emit exit)
- exit - child process has cleanly exited (ie. no crash)
- restart([ array of files triggering the restart ]) - child process has restarted
- config:update - nodemon's config has changed

## Messages

- log({ type, message (plain text log), colour (colour coded log) }) - logging from nodemon (not the child process)
- stdout - the stdout stream from the child process
- stderr - the stderr stream from the child process
- readable - stdout and stderr streams are ready ([example](https://github.com/remy/nodemon#pipe-output-to-somewhere-else))

Note that if you want to supress the normal stdout & stderr of the child, in favour
of processing the stream manually using the stdout/stderr nodemon events, pass
nodemon the option of `stdout: false`.

## Using nodemon events

If nodemon is required, events can be bound and emitted on the nodemon object:

```js
var nodemon = require('nodemon');

nodemon({ script: 'app.js' }).on('start', function () {
  console.log('nodemon started');
}).on('crash', function () {
  console.log('script crashed for some reason');
});

// force a restart
nodemon.emit('restart');

// force a quit
nodemon.emit('quit');
```

## Using nodemon as child process

If nodemon is a spawned process, then the child (nodemon) will emit message
events whereby the event argument contains the event type, and instead of
emitting events, you `send` the command:

```js
// using `spawn` as example, can use other functions like `fork`, etc
// https://nodejs.org/api/child_process.html
const { spawn } = require('child_process');

function spawnNodemon() {
  const cp = spawn('nodemon', ['path/to/file.js', '--watch', 'path/to/watch'], {
    // the important part is the 4th option 'ipc'
    // this way `process.send` will be available in the child process (nodemon)
    // so it can communicate back with parent process (through `.on()`, `.send()`)
    // https://nodejs.org/api/child_process.html#child_process_options_stdio
    stdio: ['pipe', 'pipe', 'pipe', 'ipc'],
  });

  return cp;
}

var app = spawnNodemon();

app.on('message', function (event) {
  if (event.type === 'start') {
    console.log('nodemon started');
  } else if (event.type === 'crash') {
    console.log('script crashed for some reason');
  }
});

// force a restart
app.send('restart');

// force a quit
app.send('quit');
```

Note that even though the child will still emit a `message` event whose type is
`exit`, it makes more sense to listen to the actual `exit` event on the child:

```js
app.on('exit', function () {
  console.log('nodemon quit');
});
```

repository: remy/nodemon

repo_name: remy/nodemon


text:
# SnugInt
A safe integer addition library written for use with C++ 14.
## Philosophy
C and C++ are fundamentally flawed due to specific vulnerabilities present in both languages.
one such vulnerability is Integer overflow, or the process of integer memory going outside of its allocated space

an example of such an overflow would be something like the following:
```objectivec
unsigned int a = 12;
unsigned int b = 13;
unsigned int c = a - b;
```
what we would expect is that the value of C would be 0, as an unsigned number cannot be negative.
Instead we end up with the value of `4,294,967,295` in `c` and this is due to the memory wrapping
and swapping memory it should not have access to.

this can ultimately cause unpredictable behavior from your programs which is undesirable and should be prevented.
To combat such issues, I wrote this proof of concept library based on the idea of pre and post integer checks.
## Building
```bash
cmake .
make
sudo make install
```

## Usage
SnugInt is intended to be used to prevent integer overflow as seen in the example below
```objectivec
try
{   // perform the operation
    SnugInt<unsigned int> si1 = 1;
    SnugInt<unsigned int> si2 = 10;
    si1 = si1 - si2;
} catch (std::exception& e)
{
    // handle the exception
}
```
SnugInt can also be used to perform safe integer operations with similar types
```objectivec
try
{
    SnugInt<long> si1 = 1000000;
    long l2 = 100000;
    si1 = si1 * l2;
} catch (std::exception& e)
{
    // handle the exception
}
```

## Exceptions
You can use the exceptions like this to make detecting and handling more specific.
```objectivec
try
{
    // SnugInt operation
} catch (SnugInt_Type_Mismatch_Exception& e)
{
    // handle the type mismatch exception
}
```
There are the following exceptions

```
SnugInt_Addition_Overflow_Exception
    called when overflow during addition is preditcted

SnugInt_Addition_Underflow_Exception
    called when undeflow during addition is predicted

SnugInt_Subtraction_Overflow_Exception
    called when overflow during subtraction is predicted

SnugInt_Subtraction_Underflow_Exception
    called when underflow during subtraction is predicted

SnugInt_Multiplication_Overflow_Exception
    called when overflow during multiplication is predicted

SnugInt_Multiplication_Underflow_Exception
    called when underflow during multiplication is predicted

SnugInt_Size_Mismatch_Exception
    called when a size mismatch during assignment is detected

SnugInt_Type_Mismatch_Exception
    called when an unsupported type is used during assignment
```

## License
This project is licensed under the Apache License Version 2.0 - See the [LICENSE](LICENSE) file for details

repository: YOUR-WORST-TACO/SnugInt

repo_name: YOUR-WORST-TACO/SnugInt


text:
# Envoy Front Proxy Demos

Sets of Envoy Front Proxy demos

- [HTTP Routing: Simple Match Routing](../httproute-simple-match)
- [HTTP Routing: Routing based on Header Condition](../httproute-header-match)
- [HTTP Routing: Blue Green Traffic Splitting](../httproute-blue-green)

---
[Top](../README.md)


text:
###  Redfish vs. RedHelix
Redfish and RedHelix differ on the type of RESTful interface and how the data is presented to the end user.
RedHelix also attempts to provide a consistent interface to hardware.

#### Consistent Interface
Redfish, in an effort to maximize the hardware platforms it supports, makes most identifying data optional. For example, it allows both
Part Number and Model Number for servers, chassis and power supplies. Some vendors supply both, some only one and some none. It also does not
mandate a UUID for each piece of hardware and is makes no demands on the the UUID remaining constant when firmware or hardware is upgraded.
In a Data Center if you upgrade hardware you don't want the history of the hardware to disappear due to a firmware upgrade. To allow hardware
vendors or Data Center operators to change the UUID without losing the devices history RedHelix assigns it's own UUID to each device.

Redfish does not constrain the number of characters in strings such as model number, manufacture name, sensor name or hardware description.
And it should not. The design of Redfish is to maximize it's adoption for the hardware layer.

In contrast RedHelix includes a GUI and limits have to placed on these strings to have consistent user interface for table, data entry fields
 etc. In most places the limit of 50 characters has been enforced. An exception is for the hardware description which is 1000 characters.

If any limit that is a problem, this open source and fork or other change will happen. Search the GitHub repository for the string
RED_HELIX_DEFINED to see all the limits which are static integers. There are currently 57 of them and all constrained to the maven project
redhx-core-api which contains only Java interfaces and enumerations. By design the single maven project could be forked and the limits changed
without modifying any Java classes.

#### RESTful Interface
Redfish provides the HTTP protocol and JSON messages to monitor a single implementation of Redfish at a single HTTP connection to a TCP port number.
RedHelix allows a single HTTP connection to a TCP port number to monitor servers a multiple physical data centers, rooms and racks.
RedHelix allows queries to be filtered by any combination of:

 * siteName
 * roomName
 * rackName
 * redfishHardwareType
 * manufacturerName
 * redfishSchemaVersion
 * poweredBy
 * cooledBy
 * poweredOnState
 * operatingState

These are examples of how to get the list of UUID, assigned by RedHelix, of the devices in the RedHelix database.

1. To get all devices managed by a RedHelix implementation call the RESTful URL
   * http://localhost:8080/RedHelix.svc/v1/hardwareId
2. To get all devices powered off use the query poweredOff from the above list to make this URL
   * http://localhost:8080/RedHelix.svc/v1/hardwareId?$poweredOnState=off
3. To get all devices manufactured by Acme Computer at the Data Center in Hong Kong use the URL
   * http://localhost:8080/RedHelix.svc/v1/hardwareId?$manufacturerName="Acme Computer"$siteName="Hong Kong"
4. To get all power supplys in room DataHall-17
   * http://localhost:8080/RedHelix.svc/v1/hardwareId?$redfishHardwareType="PowerSupply"$roomName="DataHall-17"

RedHelix provides a database contaning multiple servers that implement Redfish and the history for
each server. At present the database is only in limited to what is in memory and when the Java Virtual Machine shuts down all history is destroyed.

#### Discovery of the RESTful interface
Redfish has an optional protocol called "SimpleService Discovery Protocol" (SSDP), that allows discovery of Redfish enabled servers. RedHelix servers
can not be discovered using SSDP.
Prior knowledge of the IP address and TCP port number, and possibly account name and number, are required to access a RedHelix server. The user of
RedHelix can define how Redfish servers are found. It may be a scan of IP address, a fixed set IPs or enabling the use of SSDP.

#### Graphics User Interface
RedHelix will contain a Graphic User Interface based on [AngularJS](https://angularjs.org). This is under development in the GitHub branch labled
version 0.2.


text:
# Money transfer service

Simple implementation a RESTful API (including data model and the backing implementation)
for money transfers between accounts.

## Built With

* [Java 11](https://www.oracle.com/technetwork/java/javase/downloads/index.html)
* [Maven](https://maven.apache.org/)
* [Vert.x](https://vertx.io/)
* [JavaMoney](http://javamoney.github.io/)
* [JUnit 5](https://junit.org/junit5/)

### Building
```
mvn clean package
```
### Running the tests

#### Unit tests
```
mvn clean test
```
#### Integration tests
```
mvn clean verify
```

### Deployment
```
java -jar money-transfer-service-0.0.1.jar
```

## Versioning

We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/your/project/tags).

## Authors

* **Daniil Perestoronin**

## License

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


text:
## CONTRIBUTING.md:

You are free to download/clone/fork/use this repository.

If you find this repository useful, I would be happy if you could
**reference this repository** if you use it in your work.

# Pull request:
Pull requests generally welcomed but please open an issue to discuss the work
scope before you start for I really hate wasting your time. Also, Atomic
commits are preferred.


text:
# Changelog

## [Unreleased](https://github.com/hariharan235/Test_webhook/tree/HEAD)

[Full Changelog](https://github.com/hariharan235/Test_webhook/compare/38e30973390ab52d76c7c534f3eacb02261203ad...HEAD)

**Fixed bugs:**

- Add more tests for max [\#1](https://github.com/hariharan235/Test_webhook/issues/1)

**Closed issues:**

- Fix badge not pointing to jenkins server [\#5](https://github.com/hariharan235/Test_webhook/issues/5)
- Fix unusedfunction in max.c [\#4](https://github.com/hariharan235/Test_webhook/issues/4)

**Merged pull requests:**

- Change name of coverage report to coverage.xml [\#3](https://github.com/hariharan235/Test_webhook/pull/3) ([hariharan235](https://github.com/hariharan235))
- Test pr [\#2](https://github.com/hariharan235/Test_webhook/pull/2) ([hariharan235](https://github.com/hariharan235))

gha_language: C


text:
# My Awesome Project
Short description

## Why?
Why does this project exist?

## Installation

### Requirements
* PHP 7

### Installation
Describe how to install the project.

## Usage
How to use it.

## Kudos
Room for a small thank you to dependencies or other helping stuff.

## Contributing
See the [CONTRIBUTING](./.github/CONTRIBUTING.md) file.

## License
Copyright (c) 2019 until now, [Frank Bültge](https://bueltge.de)

Good news, this plugin is free for everyone! Since it's released under the [MIT License](./LICENSE) you can use it free of charge on your personal or commercial website.

repository: bueltge/php-project-template

repo_name: bueltge/php-project-template


text:
# mb_acc

Get micro:bit accelerometer data

![chart](data/graph.png)

# Requirements

Python 2

A micro:bit

Micro Python

A charting program that understands CSV files

# Setup

Press CLONE OR DOWNLOAD and then DOWNLOAD ZIP.

Unzip the zip file

Open python.microbit.org

Drag hex_files/acc.py into the editor

Press the DOWNLOAD button to get a hex file

Drag and drop this hex file onto your micro:bit

# Running the code

run the test.py program on PC/Mac using Python 2
(might work on Python 3, not tested though)

Follow the instructions when asked to 'remove' and then 'connect' your
micro:bit - this detects which communications port it is plugged into on
your computer.

Note, if you use a different USB port later, delete the file portscan.cache
and it will force it to re-detect.

When the program runs, it creates a file 'log.csv' and appends x,y,z accelerometer
data 10 times a second. It also displays this on the console screen.

Move your micro:bit in the x,y and z planes.

When you have finished, CTRL-C or stop the python program.

# Analysing the data

Import log.csv into a spreadsheet program or other charting program that
can import and chart CSV files.

# Errors?

We've done some work recently to improve the error handling with the
pyserial library. It seems that some pre-installed pyserial packages
on some distributions have a subtly different API. Thanks to Andy
for helping me debug this on his Linux Mint 18/python 2.7.11 setup

In particular, pyserial 3.0.1 has this bug in it, but pyserial 3.2.1
has the bug fixed. So, if you are using a pre-installed pyserial
of around the 3.0.1 era, it's API is broken, and you should really
update it to the latest version.


text:
## TransTrack: Multiple-Object Tracking with Transformer

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

![](transtrack.png)

## Introduction
[TransTrack: Multiple-Object Tracking with Transformer](https://arxiv.org/abs/2012.15460)

## Models
Training data | Training time | Validation MOTA | download
:---:|:---:|:---:|:---:
[crowdhuman, mot_half](track_exps/crowdhuman_mot_trainhalf.sh) |  36h + 1h  | 65.4 | [model](https://drive.google.com/drive/folders/1DjPL8xWoXDASrxgsA3O06EspJRdUXFQ-?usp=sharing)
[crowdhuman](track_exps/crowdhuman_train.sh)                   |  36h       | 53.8 | [model](https://drive.google.com/drive/folders/1DjPL8xWoXDASrxgsA3O06EspJRdUXFQ-?usp=sharing)
[mot_half](track_exps/mot_trainhalf.sh)                        |  8h        | 61.6 | [model](https://drive.google.com/drive/folders/1DjPL8xWoXDASrxgsA3O06EspJRdUXFQ-?usp=sharing_)

Models are also available in [Baidu Drive](https://pan.baidu.com/s/1dcHuHUZ9y2s7LEmvtVHZZw) by code m4iv.

#### Notes
- Evaluating crowdhuman-training model and mot-training model use different command lines, see Steps.
- We observe about 1 MOTA noise.
- If the resulting MOTA of your self-trained model is not desired, playing around with the --track_thresh sometimes gives a better performance.
- The training time is on 8 NVIDIA V100 GPUs with batchsize 16.
- We use the models pre-trained on imagenet.

## Demo

## Installation
The codebases are built on top of [Deformable DETR](https://github.com/fundamentalvision/Deformable-DETR) and [CenterTrack](https://github.com/xingyizhou/CenterTrack).

#### Requirements
- Linux, CUDA>=9.2, GCC>=5.4
- Python>=3.7
- PyTorch ≥ 1.5 and [torchvision](https://github.com/pytorch/vision/) that matches the PyTorch installation.
  You can install them together at [pytorch.org](https://pytorch.org) to make sure of this
- OpenCV is optional and needed by demo and visualization

#### Steps
1. Install and build libs
```
git clone https://github.com/PeizeSun/TransTrack.git
cd TransTrack
cd models/ops
python setup.py build install
cd ../..
pip install -r requirements.txt
```

2. Prepare dataset
```
mkdir -p crowdhuman/annotations
cp -r /path_to_crowdhuman_dataset/annotations/CrowdHuman_val.json crowdhuman/annotations/CrowdHuman_val.json
cp -r /path_to_crowdhuman_dataset/annotations/CrowdHuman_train.json crowdhuman/annotations/CrowdHuman_train.json
cp -r /path_to_crowdhuman_dataset/CrowdHuman_train crowdhuman/CrowdHuman_train
cp -r /path_to_crowdhuman_dataset/CrowdHuman_val crowdhuman/CrowdHuman_val
mkdir mot
cp -r /path_to_mot_dataset/train mot/train
cp -r /path_to_mot_dataset/test mot/test
python track_tools/convert_mot_to_coco.py
```
CrowdHuman dataset is available in [CrowdHuman](https://www.crowdhuman.org/). We provide annotations of [json format](https://drive.google.com/drive/folders/1DjPL8xWoXDASrxgsA3O06EspJRdUXFQ-?usp=sharing).

MOT dataset is available in [MOT](https://motchallenge.net/).

3. Pre-train on crowdhuman
```
sh track_exps/crowdhuman_train.sh
python track_tools/crowdhuman_model_to_mot.py
```
The pre-trained model is available [crowdhuman_final.pth](https://drive.google.com/drive/folders/1DjPL8xWoXDASrxgsA3O06EspJRdUXFQ-?usp=sharing).

4. Train TransTrack
```
sh track_exps/crowdhuman_mot_trainhalf.sh
```

5. Evaluate TransTrack
```
sh track_exps/mot_val.sh
sh track_exps/mot_eval.sh
```

6. Visualize TransTrack
```
python track_tools/txt2video.py
```

#### Notes
- Evaluate pre-trained CrowdHuman model on MOT
```
sh track_exps/det_val.sh
sh track_exps/mot_eval.sh
```

## License

TransTrack is released under MIT License.

## Citing

If you use TransTrack in your research or wish to refer to the baseline results published here, please use the following BibTeX entries:

```BibTeX

@article{transtrack,
  title   =  {TransTrack: Multiple-Object Tracking with Transformer},
  author  =  {Peize Sun and Yi Jiang and Rufeng Zhang and Enze Xie and Jinkun Cao and Xinting Hu and Tao Kong and Zehuan Yuan and Changhu Wang and Ping Luo},
  journal =  {arXiv preprint arXiv: 2012.15460},
  year    =  {2020}
}

```


text:
# Release Process

1. Check that you've followed the setup steps listed [here](https://plugins.gradle.org/docs/submit)
1. Update `CHANGES.md`
1. Ensure that there is a milestone for the version, and that appropriate issues are associated with the milestone.
1. Update the plugin version in `build.gradle` under "version"
1. Commit and tag with the version number
1. Run `./gradlew clean build publishPlugins`
1. Update the version the next SNAPSHOT and commit.
1. Push
1. If there was a issue requesting the release, close it.
1. Close the milestone.
1. Go to the [GitHub Releases page](https://github.com/commercehub-oss/gradle-avro-plugin/releases), click "Draft a new release", select the tag version, use the version number as the title, copy the relevant segment from `CHANGES.md` into the description, and click "Publish release".


text:
Default
======

Default Node.js + Socket.IO + jQuery + Express.js project boilerplate

Tired of doing ``express YOUR_PROJECT_NAME`` and having to:

* rename files, make new ones,
* then configure your app to support Socket.IO interaction and
* manage user data structure, with join/quit/synchronization events?

Try Default!

It offers:

* app.js renamed to server.js
* Public directories renamed to css, js, img
* Includes latest version of minified jQuery
* Server HTTP request logger
* Favicon

* User class shared between client and server
* Keep users data structure synchronized between client and server
* Manage user join/quit websocket events with Socket.IO
* All connection events are logged on console.log

* Debug console toggable with "\", show number of total connected users and their session id

Examples of projects based on Default:

* [Wander](https://github.com/Fabryz/wander)
* [Mangonel](https://github.com/Fabryz/mangonel)
* [Mirror](https://github.com/Fabryz/mirror)
* [Closer](https://github.com/Fabryz/closer)

Requirements
------------

* [Node.js](http://nodejs.org/)
* [Npm](http://npmjs.org/)

Modules:

* [Express](http://expressjs.com/)
* [Socket.io](http://socket.io/)

Installation
----------

1. Clone the repository with ``git clone git://github.com/Fabryz/default.git YOUR_PROJECT_NAME``
2. Install dependencies with ``npm install``
3. Start the server with ``node server.js``
4. Point your browser to ``YOUR_SERVER_IP:8080``
5. [Congratulate yourself](http://i.imgur.com/WAxOG.gif) for the time you have now gained, start developing

License
-------

MIT License

Copyright (c) 2012 Fabrizio Codello

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

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

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

repository: haiyun-document/default

repo_name: haiyun-document/default


text:
# Table of Contents

### Learning and Setup
[Getting started](getting-started.md)

[High Level Overview](high-level-overview.md)

### Release
[Release Process](release-process.md)

### Testing
[Controller Testing Tools](controller-testing.md)

### Utility
[Setting up private registry](private-registry.md)


text:
---
layout: post
title: Lecturer position in climate science (Melbourne, Australia)
subtitle: University of Melbourne
tags: [lecturer, Australia, climate]
comments: false
---
The School of Geography, Earth and Atmospheric Sciences at the University
of Melbourne is inviting applications for a Lecturer/Senior Lecturer in
Climate Science. This is a tenure-track position and the successful
applicant will join an active group of climate scientists, atmospheric
scientists and climate impacts researchers.

For further information and details on how to apply follow this link:

https://jobs.unimelb.edu.au/en/job/911371/lecturersenior-lecturer-in-climate-science

Applications close on the 2nd March at 11:55pm Australian Eastern Daylight Time.

Contact details: Prof. Todd Lane<EMAIL_ADDRESS>


text:
# SmartJudge - Dispute Resolution for Smart Contracts

## About

SmartJudge [1] is a framework for private, trustless, and efficient trades between two parties.
Exemplary use cases are the selling of digital files and atomic exchanges of cryptocurrencies.
SmartJudge works via blinded trade agreements and optimic trade excutions, which allows to keep the trade agreement and save costly verifications of the trading partnes' honesty.
If the receiver of the traded good does not acknowledge the reception of its goods, a on-chain identification of the misbehaving party is launched.
Through small, yet sufficient security deposits, SmartJudge ensures that an honest party is reimboursed all fees in case an on-chain verification is necessary.

## Presentation of the Accompanying Paper at IEEE ICBC 2019

[![IMAGE ALT TEXT](https://i.imgur.com/yUlWk7O.png)](https://youtu.be/ilWwCqGA-_Y?t=2599 "IEEE ICBC Technical Session - 9 190517")

## Examplary Use Case: Privacy-preserving ETH-BTC Atomic Swaps

**DISCLAIMER: THIS IS A PROOF-OF-CONCEPT, DO NOT USE FOR TRADING VALUABLE ASSETS!**

This repository contains two major smart contracts; First, the SmartJudge framework that generalizes the optimistic trade of any asset for which the exchange verifiable on the Ethereum blockchain.
Secondly, we provide a use-case-specific verifier for the atomic exchange of Ether and Bitcoins that does not require a trusted third party.
To get started, you first deploy the `meditor.sol` smart contract.
Afterward, you deploy the `atomic-swap-verifier.sol` smart contract and indicate the address of the mediator during deployment.
Finally, you have to register the new verifier with the mediator (you can register multiple verifiers with one mediator).

We provide two Python scripts that take care of deploying the smart contracts (`deploy.py`) and showing the execution of trades between honest and between dishonest trading partners (`trade.py`).
For our example trades, we assume that Alice wants to exchange her Ether for Bitcoins and that both trading partners regard the Bitcoin block number 514490 as included in the Bitcoin chain (e.g., six blocks have been mined on top of it).
The transaction [0xab95a18c...ef3e9735](https://www.blockchain.com/btc/tx/ab95a18c001454c361d70a0cd26df1b124498e5b4444ef4ca5f77725ef3e9735) is in our example the payment by Bob to Alice's Bitcoin address, whose existence and correctness is proven by the verifier if necessary (i.e., if Alice refuses to conclude the trade gracefully).

## License

This work is licensed under the MIT license.

## Links

\[1\] Eric Wagner, Achim Völker, Frederik Fuhrmann, Roman Matzutt and Klaus Wehrle.
     [Dispute Resolution for Smart-contract bases Two-Party Protocols](https://roman-matzutt.de/paper/2019-icbc-wagner-dispute-resolution.pdf)
     IEEE International Conference on Blockchain and Cryptocurrency 2019 (ICBC 2019)

repository: cryptobuks/smartjudge

repo_name: cryptobuks/smartjudge


text:
# Q_kp_multiband_ZB_strain
Computes the electronic band structure of bulk ZB semiconductor with k.p 6 or 8 bands models WITH STRAIN

![image](https://user-images.githubusercontent.com/35040499/113293629-4d371e00-92f6-11eb-9c45-23732d71d9ba.png)


text:
# bad selector(s)

    Code
      rec %>% step_regex(description, rows, pattern = "(rock|stony)")
    Condition
      Error in `step_regex()`:
      ! For this step, at most a single selector can be used.

---

    Code
      prep(rec4, training = covers)
    Condition
      Error in `prep()`:
      ! The regular expression input should be character or factor

# printing

    Code
      print(rec1)
    Output
      Recipe

      Inputs:

            role #variables
       predictor          3

      Operations:

      Regular expression dummy variable using "(rock|stony)"

---

    Code
      prep(rec1)
    Output
      Recipe

      Inputs:

            role #variables
       predictor          3

      Training data contained 40 data points and no missing data.

      Operations:

      Regular expression dummy variable using "(rock|stony)" [trained]

# empty printing

    Code
      rec
    Output
      Recipe

      Inputs:

            role #variables
         outcome          1
       predictor         10

      Operations:

      Regular expression dummy variable using "."

---

    Code
      rec
    Output
      Recipe

      Inputs:

            role #variables
         outcome          1
       predictor         10

      Training data contained 32 data points and no missing data.

      Operations:

      Regular expression dummy variable using "." [trained]

repository: DavisVaughan/recipes

repo_name: DavisVaughan/recipes


text:
## Simple Admin Panel

This is a simple admin panel for testing purposes and to get to know Laravel better.

## Features

- Admin login can be accessed in the route /admin
- User login
- Currently it can save a content with a title, content and a. featured image (the image is not treated and is saved in /storage folder)

## What's next

- Enhance admin panel design
- Treat images (crop, resize)
- Add a gallery option
- Add a form to create new types of content
- Add the option to create a custom form for every type of content
- When creating a new content, add the option to set the content type

repository: resmall/simple-admin-panel

repo_name: resmall/simple-admin-panel


text:
# Just a Snake

All said, just a Snake inspired from that good old game. **Completed, 20 levels playable with bonus etc**.
Tiles might look familiar for most are taken from GB classics.

All details here: http://electrogeek.cc/just%20a%20snake.html

![Screenshot](http://electrogeek.cc/files/justasnake-composition-20200504.png)

repository: AlanFromJapan/Gameboy

repo_name: AlanFromJapan/Gameboy


text:
---
layout: post
title: "Hack24 '17, The Greatest Place On Earth"
description: "Taking part in Hack24, a Nottingham Hackathon."
date: 2017-03-24
image: "assets/img/posts/twitter.jpg"
tags: ['2017']
---

----

A summary of Hack24 2017. Also, a love letter to Hack24.

---

### My Tech Life and Tech Notts.

[Tech Nottingham](http://www.technottingham.com/), [Hack24](http://www.hack24.co.uk) and the people involved are incredibly close to my heart. [Moreton](https://twitter.com/allmobro) (my taller half) took me to Tech Nottingham before I even
 started my Computer Science course. I think this was partly to get me inspired but also so that I could meet people and the tech world didn't feel so daunting and scary.

 Soon after that I was attending the first Hack24. It's strange to think my life in tech has been pretty much documented by Hack24 photos.

Even what is now a massive part of my life, [Women In Tech Nottingham](www.womenintechnotts.co.uk) (WITNOTTS), would not have happened if it weren't for the Sewards. [Andrew](https://twitter.com/MrAndrew) is the one who talked me into creating a safe space to encourage more people into the social part of our fine tech community.

Talking of, just under a year ago I did an interview with [Jonathan](https://twitter.com/jbjon) on [Twine Radio](http://twineradio.co.uk/) talking about the plans I had for it at the time. I stated that I wanted the group to have a presence at Hack24 in 2017. At the time I had no idea that this could be a real possibility, it was a pipe dream.

> I think that brings us nicely to this years hack...

### Hack24 2017

So we fast forward to last weekend. WITNOTTS is no longer a solo burden of love, but I now have [Helen Clark](https://twitter.com/LittleHelli). Helen has been an absolute god send over the last few months. We have both grown up with Hack24, coming on leaps and bounds over the last 3 years. We both love the Tech Nottingham community and do our best to get more people involved. She really drives a lot of the work we do.

We mentioned to Hack24 that we wanted to bring a team of our member to the event and they very  kindly donated 8 tickets to WITNOTTS for this year.
Enough for two whole teams.

*Team Wild Garlic, Basil, Olive Oil, Pine Nuts & a Pinch of Salt & Pepper:* Amy Dickens, Maria Digregorio, Bety Mehide & Alexa Spors

*Team Totally Triumphant Bodacious Babes:* Helen Clark, Elsa, Jessica White & Laura Rossi

Both teams came to the event with the aim of having fun. It's safe to say we achieved that! The ladies were fully supportive of each other constantly making sure that the others were doing okay and having a laugh. Even if many of Elsa's laughs were directed at the face I make when I'm concentrating. (Don't worry Elsa - I still think you are awesome!)

The WITNOTTS Code of Conduct is based off the classic Bill and Ted quote _"Be Excellent To Each Other"_. I could not be prouder of our members and
how much they live and breathe this ethic. We helped each other. We helped others. We had a good time and made sure everyone around us was having
a good time too. The rest of Nottingham must have a similar ethic as our stickers disappeared quickly.

A lot happened while we were coding.  In summary - the hot chocolate was addictive, the company couldn't have been better and the volunteers are world class. If you haven't done Hack24 before, you should sign up for next year. In my three years I have joined a group of strangers, gone with a group organised at work and, this year, gone with people I wanted to get to know better. Every year I have managed to make new friends,
learn and laugh.

Finally the air horn sounded and it was time to make our videos. Luckily, Helen is a video queen! Helen, Laura and Elsa set up a story board and plan (this was while I was doing some last minute code pre-airhorn). They decided that we should use our app as a means of showing what it was all about, which meant running around Nottingham doing bonkers things and tweeting about it. If it hasn't been removed yet you can view Team Totally Triumphant Bodacious Babes entry here:

After the video had been submitted we had a couple of hours to waste while the judging was done. We then met up again for the awards ceremony.

### The Results

All in all not only did the WITNOTTS teams do well, but some teams containing our members did as well!

- Team Wild Garlic, Basil, Olive Oil, Pine Nuts & a Pinch of Salt & Pepper won two challenges: Esendex and Packed Pixels.
- Team Totally Triumphant Bodacious Babes came second in the Cronofy challenge
- WITNOTTS members Samathy and Alex's team won the Unidays challenge

v

I'm not going to lie - I was ECSTATIC that we won something. I couldn't stop giggling for a long time afterwards purely due to the shock. Add on to the fact it was a model Delorean... well anyone who has been to WITNOTTS or seen me talk knows how much I love a good ol' cult film reference. I don't think any of us expected to get a prize so after all our toil, we were overjoyed to have won something.

The best result in my opinion though is that we had ladies in our teams that hadn't been to many tech events and for which this was their first Hack.

Not only are they planning to go to Hack24 2018, but have also been asking about other events in Nottingham and have been inspired to complete tech
related projects. Getting people inspired by tech and to join in with the greater tech community is what makes all this worthwhile. Bringing more people into it, strengthening it & making it thrive.

Thank you [Tech Nottingham](http://www.technottingham.com/) for building a welcoming tech family.

### Other Hack24 Blogs:

- [Helen Clark - Being excellent to each other at<EMAIL_ADDRESS>- [Emma Seward - Hack24 2017: Big dreams, big hacks, big weekend](http://www.hack24.co.uk/blog/2017/3/23/hack24-2017-big-dreams-big-hacks-big-weekend?utm_content=buffer9780a&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer)
- [Matt Brunt - HACK 24: 2017 LIVE BLOG](https://mfyu.co.uk/post/hack-24-2017-live-blog)

---

gha_language: SCSS


text:
---
title: spread
tags: list,intermediate
---

Flattens a list, by spreading its elements into a new list.

- Loop over elements, use `list.extend()` if the element is a list, `list.append()` otherwise.

```py
def spread(arg):
  ret = []
  for i in arg:
    ret.extend(i) if isinstance(i, list) else ret.append(i)
  return ret
```

```py
spread([1, 2, 3, [4, 5, 6], [7], 8, 9]) # [1, 2, 3, 4, 5, 6, 7, 8, 9]
```


text:
# bs-recoil

Experimental ReasonML bindings to [recoil](https://github.com/facebookexperimental/recoil).

## Usage

- clone this directory
- yarn install
- yarn dev
- go to http://localhost:1234

example directory contains the todo app from the recoil doc

repository: Coobaha/bs-recoil

repo_name: Coobaha/bs-recoil


text:
## Bottle Google App Engine Base Project

Project based on https://github.com/GoogleCloudPlatform/appengine-python-bottle-skeleton

## Run Locally

###The easy way

1. Install the [App Engine Python SDK](https://developers.google.com/appengine/downloads).
See the README file for directions. You'll need python 2.7 and [pip 1.4 or later](http://www.pip-installer.org/en/latest/installing.html) installed too. Add app engine to your PATH if necessary.

2. Clone this repository with

   ```shell
   git clone<EMAIL_ADDRESS>   ```
3. Install dependencies in the project's `lib/` directory.
   Note: App Engine can only import libraries from inside your project directory.

   ```shell
   cd bottle-gae-base-project
   pip install -r requirements.txt -t lib/
    # libs for development enviroment
   pip install -r requirements-dev.txt
   ```
4. Run this project locally from the command line:

   ```
   dev_appserver.py .
   ```

Open [http://localhost:8080](http://localhost:8080)

### The very easy way ;)

If you are in Unix environment...

1. Install the [App Engine Python SDK](https://developers.google.com/appengine/downloads).
See the README file for directions. You'll need python 2.7 and [pip 1.4 or later](http://www.pip-installer.org/en/latest/installing.html) installed too. Add app engine to your PATH if necessary.

2. Clone this repository with

   ```shell
   git clone<EMAIL_ADDRESS>   ```
3. Setup enviroment

   ```shell
   cd bottle-gae-base-project
   source setup.sh
   ```

4. Run the dev server
   ```shell
   fab run_server
   ```

   Fabric Available commands:
   ```
    babel_compile             compile all locales
    babel_extract             extract terms to be transalated
    babel_extract_update      extract terms and update all po files
    babel_init                initialize a locale - use it carefully it overwrites your current po file
    babel_update              update po transtation files
    deploy                    deploy app to the cloud -  don't forget to edit the fabfile.py to add you app id
    run_server                start dev server
    ```

## Deploy
To deploy the application:

1. Use the [Admin Console](https://appengine.google.com) to create an app and
   get the project/app id. (App id and project id are identical)
1. [Deploy the
   application](https://developers.google.com/appengine/docs/python/tools/uploadinganapp) with

   ```
   appcfg.py -A <your-project-id> --oauth2 update .
   ```

2. Or
   ```
   fab deploy
   ```

repository: aleal/bottle-gae-base-project

repo_name: aleal/bottle-gae-base-project


text:
> [Go to French version](/fr/Règlements/Décrets,%20ordonnances%20et%20règlements%20statutaires/88/313.md)

# Rules of Practice and Procedure of the Royal Canadian Mounted Police External Review Committee

**SOR/88-313**

Enabling authorities:
- [ROYAL CANADIAN MOUNTED POLICE ACT](/en/Acts/Revised%20Statutes%20of%20Canada/R/R-10.md)

Date registered: 8 June 1988

----------

The Royal Canadian Mounted Police External Review Committee, pursuant to section 29[*] of the [Royal Canadian Mounted Police Act](/en/Acts/Revised%20Statutes%20of%20Canada/R/R-10.md), hereby makes the annexed Rules of Practice and Procedure of the Royal Canadian Mounted Police External Review Committee.

*: S.C. 1986, c. 11, s. 15

Ottawa, June 8, 1988

## Short Title

**1** These Rules may be cited as the RCMP External Review Committee Rules of Practice and Procedure.

## Interpretation

**2** In these Rules,

***Act*** means the [Royal Canadian Mounted Police Act](/en/Acts/Revised%20Statutes%20of%20Canada/R/R-10.md); (*Loi*)

***Committee member*** means a person appointed as a member of the Committee pursuant to subsection 25(1) of the Act; (*membre du Comité*)

***Executive Director***[Revoked, SOR/91-544, s. 1]

***interested person*** means a person who satisfies the Committee that the person has a substantial and direct interest in a matter being heard by the Committee; (*personne intéressée*)

***record*** means the whole or any part of any book, document, paper, card, tape or other thing in or on which information is written, recorded, stored or reproduced. (*pièce*)

***registered mail*** means trace mail that provides proof of the date of mailing, of signature on delivery and a means of establishing delivery status; (*courrier recommandé*)

***Registrar*** means the person appointed pursuant to subsection 27(2) of the Act and designated as Registrar by the Committee Chairman. (*greffier*)
> SOR/91-544, s. 1.

## Matters Not Otherwise Provided for in These Rules

**3** Where any matter arises during the course of proceedings before the Committee not otherwise provided for in these Rules, the Committee may take whatever steps it considers necessary to settle the matter.

## Holidays

**4** Where a time limit or deadline set out under these Rules falls on a Saturday or statutory holiday, the time limit or deadline shall be extended to the next working day.

## Interested Person

**5**

- **(1)** Except where the Committee considers an application to appear on the day of hearing, a person seeking to appear before the Committee shall, not later than five working days before the date of the hearing of that matter, file with the Committee an application in writing setting out the nature of the person’s interest in the matter before the Committee.

- **(2)** The Registrar shall send a copy of the application referred to in subsection (1) to the parties to the matter being heard by the Committee.
> SOR/91-544, s. 2.

## Meetings by Telephone or other Means of Telecommunication

**6** Committee members may participate in meetings by telephone or other means of telecommunication.

## Providing of Records

**7**

- **(1)** When referring a matter to the Committee, the Commissioner or the Commissioner’s delegate shall send to the Committee Chairman, as the case may be,
	- **(a)** a bound copy of the record required to be furnished under subsection 33(3) of the Act, including the style of the cause and an index; or
	- **(b)** three bound copies of the record referred to in subsection 45.15(4) or 45.25(3) of the Act, including in each case the style of the cause and an index.

- **(2)** The Commissioner or the Commissioner’s delegate shall certify by affidavit that the record required to be provided to the Committee Chairman by the Commissioner in respect of a matter referred to the Committee has been so provided.

- **(3)** In the case of a matter referred under section 33 of the Act, the Commissioner or the Commissioner’s delegate shall certify by affidavit that the appropriate officer and the member presenting the grievance have each been provided with a copy of the record sent to the Committee pursuant to subsection (1)(a).
> SOR/91-544, s. 3; SOR/97-437, s. 1.

## Written Submissions

**8**

- **(1)** In the course of reviewing a matter referred to the Committee by the Commissioner, the Committee Chairman may permit the parties and interested persons to file written submissions for the purpose of clarifying the matter.

- **(2)** On receiving the submission from a party or interested person, the Committee Chairman shall provide a copy of it to all other parties and interested persons.

- **(3)** Any of the parties or interested persons may, within 14 days after receiving the submission or within such longer period as is allowed by the Committee where justified in the circumstances, file a written response to it with the Committee.
> SOR/91-544, s. 4; SOR/97-437, s. 1.

## Conflict of Interest

**9**

- **(1)** A Committee member shall immediately notify the Committee Chairman where the Committee member,
	- **(a)** apart from any functions as a Committee member, has had previous, or has any current, personal or professional association with a member whose grievance, formal disciplinary appeal or discharge or demotion appeal is before the Committee; or
	- **(b)** is an employee, associate, counsel or member of a legal firm that is representing the member referred to in paragraph (a).

- **(2)** Where the Committee Chairman determines that the Committee member has a real or potential conflict of interest, the Committee Chairman shall request the Committee member to withdraw from any further participation in the matter before the Committee.

## Filing of Records

**10**

- **(1)** Any record required by these Rules to be filed with the Committee shall be addressed to the Registrar and be either sent by registered mail or delivered by hand to the office of the Registrar.

- **(2)** Where a record is sent by registered mail, the effective date of filing is the date of mailing.
> SOR/91-544, s. 5.

## Production of Records

**11**

- **(1)** Where the Committee Chairman decides to institute a hearing to inquire into a matter, any party to that matter may, at any time before the hearing, request in writing that another party to that matter produce for inspection a record and copies of that record.

- **(2)** The person to whom a request is made in accordance with subsection (1) shall produce the record requested within a reasonable time from the date on which the request is received.

- **(3)** Where a party fails to produce a record in accordance with subsection (2), the party may not present the record in evidence at the hearing, unless the party satisfies the Committee that the party has sufficient cause for failing to produce the record.

## Conference or Preliminary Procedures

**12** The Committee may, verbally or in writing, direct the parties to appear before the Committee at a specified time and place, or to file submissions in writing to the Committee, for the purpose of formulating issues and assisting the Committee in the consideration of
- **(a)** the simplification of issues;
- **(b)** the necessity or desirability of amending any submission for the purpose of clarification, amplification or limitation;
- **(c)** the admissibility of certain facts or the proof of them by affidavit, or the use by any party of reports or other matters of public record;
- **(d)** the procedure at the hearing;
- **(e)** the exchange among the parties of records and exhibits proposed to be submitted at the hearing; and
- **(f)** any other matters that may assist in the simplification of the evidence and conduct of the proceedings.
> SOR/91-544, s. 6; SOR/97-437, s. 2.

## Official Languages

**13** At a hearing before the Committee, a party or an interested person is entitled to make representations to the Committee, to present evidence and to examine and cross-examine witnesses in either official language.

## Arguments

**14** The Committee may direct a party or an interested person to file a written argument in addition to any verbal argument.
> SOR/91-544, s. 7.

## Stay of Proceedings

**15** Where a party or an interested person has not complied with any requirement of these Rules, the Committee may stay the proceedings until it is satisfied that the requirement has been complied with or take such other measures as it considers just and reasonable in the circumstances.

## Postponements

**16**

- **(1)** Where a notice of hearing has been issued, any party may, with the consent of all of the other parties to the hearing and after notifying all interested persons, file with the Committee a written request for a postponement of the hearing.

- **(2)** Where a party does not consent to a postponement, the party seeking the postponement may, after sending a written notice to all of the other parties and interested persons, appear before the Committee at a time and place set for the hearing and request that the hearing be postponed.
> SOR/91-544, s. 8.

## Adjournments

**17** The Committee may adjourn a hearing at any time in order to permit a party to the hearing, or an interested person, to obtain such additional information as the Committee deems necessary to a full investigation and full consideration of the matter.

## Sittings

**18** A hearing, once commenced, shall proceed from day to day so far as, in the opinion of the Committee, may be practicable, and, if necessary, may proceed in the evenings and on Saturdays at the discretion of the Committee.

## Summons

**19**

- **(1)** [Repealed, SOR/97-437, s. 3]

- **(2)** A summons may be issued on written request by a party or an interested person.

- **(3)** Unless the Committee directs otherwise, no summons to a person may be issued for the production of an original record if the record, by virtue of a statutory provision or a provision made pursuant to statute, may be proved by a copy in a prescribed manner.

- **(4)** A summons to any person shall be served on the person to whom it is issued in accordance with section 47.2 of the Act.

- **(5)** [Revoked, SOR/91-544, s. 9]
> SOR/91-544, s. 9; SOR/97-437, s. 3.

## Submissions of Claims

**20** Claims under subsections 35(12) and 46(3) of the Act must be submitted to the Registrar for consideration by the Committee.
> SOR/91-544, s. 10; SOR/97-437, s. 4.

**21** [Revoked, SOR/91-544, s. 10]

repository: TravisMadill/CanadianLaws

path: /en/Regulations/Statutory Orders and Regulations/88/313.md

repo_name: TravisMadill/CanadianLaws


text:
# Penn State IEEE
# Introduction to MATLAB
October 15, 2020

### About
Attendees to this workshop learned the basics of using the MATLAB programming language in the context of the electrical engineering classes taught at Penn State. This event was held remotely due to the COVID-19 pandemic.

### Required Tools
- (WIP)

### Parts List
- (WIP)

### Resources
- (WIP)


text:
# Micro-Controller options

## Adafruit Feather STM32F405

- Link to buy from [Adafruit](https://www.adafruit.com/product/4382)
- Schematic
  [Github](https://github.com/adafruit/Adafruit-Feather-STM32F405-Express-PCB)
- Programming help
  [Adafruit](https://www.digikey.co.nz/en/videos/a/adafruit/programming-the-adafruit-feather-stm32f405-express-with-stm32cubeide-maker-io)


text:
---
layout: default
---

# 1996-11-08 - Re: Why is cryptoanarchy irreversible?

## Header Data

From<EMAIL_ADDRESS>(Peter Hendrickson)

To: jim bell<EMAIL_ADDRESS>Message Hash: c8b8c3603d752a07402f6f84519bd34408e8890dab171c923962a53b2881dc0e

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1996-11-08 17:02:55 UTC

Raw Date: Fri, 8 Nov 1996 09:02:55 -0800 (PST)

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Peter Hendrickson)
Date: Fri, 8 Nov 1996 09:02:55 -0800 (PST)
To: jim bell<EMAIL_ADDRESS>Subject: Re: Why is cryptoanarchy irreversible?
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At 3:51 AM 11/8/1996, jim bell wrote:
>At 06:25 PM 11/7/96 -0800, Peter Hendrickson wrote:
>>At 5:12 PM 11/7/1996, jim bell wrote:
>>> BTW, some of your confusion is probably based is the false assumptions in
>>> your last sentence above.  "..wide use of strong cryptography results in
>>> widely unpopular activities such as sarin attacks and political
>>> assassinations."

>> No, you're confused, but it's probably my fault.  We don't really know
>> what cryptoanarchy will be like.  We all have ideas about it.  Some
>> we share and some we don't.  But we won't really know until we see it
>> happen.

> Well, uh, with all due respect, but while it's obviously true that we won't
> know EXACTLY how it'll be, that doesn't mean that no portion of we imagine
> will come true.

At last some respect!  (I agree with your point.)

> This is particularly true on the big issues.   For example, you hypothesized
> that "wide use of strong cryptography resuts in widely unpopular activities
> such as sarin attacks and political activities.  I pointed out, almost
> certainly correctly, that these are wrong:

Yes, I think they are probably wrong.  But, not everybody shares our view.
Some people claim that we should not be allowed to communicate privately
because of the terrible things that would happen if cryptoanarchy were
to develop.  But, these people want to make it illegal now (a big hassle)
long before it is clear that we are going to have these problems.

Imagine for a moment that LSD was just invented.  Somebody then pointed
out that it was possible to randomly dose people without their knowledge.
The amounts required are virtually indetectible until it is too late.

This is certainly possible, but in practice it almost never happens.  I
can only think of one incident I have heard about where somebody took
a recreational drug involuntarily, and that was an accident.

A lot of the things we talk about are that way.  If they are not, it
is entirely possible to put a stop to them, should there be broad
popular support to do so.

> 1.  To believe that use in cryptography will result in greater numbers of
> random attacks on innocent civilians.  As I pointed out, the exact opposite
> should be true:  A greater ability to target the guilty means less reason to
> kill the innocent.

I imagine the guilty will never figure out that a pre-emptive attack
on the innocent would be advisable.

> 2.  To believe that political assassination will be unpopular even if the
> ordinary citizen has an effective say in who's going to die.

Why don't you take an off-list poll of core cypherpunks and see how
many of them share your view?  I suspect not many.  If not even cypherpunks
are open to the idea, how many voters will be?

> In other words, based on my understanding these beliefs are diametrically
> opposed to the truth.  Not simply a difference in extent, we're talking a
> 180-degree change.

> Your response is a sheepish, "but we won't really know until we see it
> happen."   Harrumph!

What happened to my "all due respect"? ;-)

>> My whole point is based on the proposition that the doomsayers are right.

> Which doomsayers?  What version of "doom"?

Take a look at this essay by D. Denning:
http://www.cosc.georgetown.edu/~denning/crypto/Future.html

Denning writes:
> A few years ago, the phrase crypto anarchy was coined to suggest the
> impending arrival of a Brave New World in which governments, as we
> know them, have crumbled, disappeared, and been replaced by virtual
> communities of individuals doing as they wish without interference.
> Proponents argue that crypto anarchy is the inevitable -- and highly
> desirable -- outcome of the release of public key cryptography into
> the world. With this technology, they say, it will be impossible for
> governments to control information, compile dossiers, conduct
> wiretaps, regulate economic arrangements, and even collect taxes.
> Individuals will be liberated from coercion by their physical
> neighbors and by governments. This view has been argued recently by
> Tim May [1].

> Behind the anarchists' vision is a belief that a guarantee of
> absolute privacy and anonymous transactions would make for a civil
> society based on a libertarian free market. They ally themselves
> with Jefferson and Hayek who would be horrified at the suggestion
> that a society with no government control would be either civil or
> free. Adam Ferguson once said "Liberty or Freedom is not, as the
> origin of the name may seem to imply, an exemption from all
> restraints, but rather the most effectual applications of every just
> restraint to all members of a free society whether they be
> magistrates or subjects." Hayek opens The Fatal Conceit, The Errors
> of Socialism (The University of Chicago Press, 1988, ed. W.W.
> Bartley III) with Ferguson's quote.

> Although May limply asserts that anarchy does not mean lawlessness
> and social disorder, the absence of government would lead to exactly
> these states of chaos.

Leaving aside Denning's snide (and evasive) remark about Tim, if her
assessment of cryptoanarchy is correct, that will become clear in
due time.  There is no reason at all to think that it cannot be
rolled back in the unlikely event that a disaster results.

I would comment parenthetically that Denning's understanding of
Jefferson is limited.  Jefferson once said he preferred a free
press to government.  Jefferson once said that he thought a revolution
every twenty years was healthy for a society.  Jefferson was an
accomplished mathematician.  Jefferson invented a pretty good cipher.
Jefferson was a cypherpunk to the marrow!

>> I believe D. Denning has suggested that cryptoanarchy will result in
>> the breakdown of our society.

> I suppose that depends a lot on what a person means by the phrase, "our
> society."  Used as you (and maybe she, as well) this sounds like a
> code-word.  To a statist, "society" is basically the stratification system
> that has developed to let one group of people control another.  By that
> standard, cryptoanarchy WILL "result in the breakdown of our society."   But
> that's all for the good.

While I may not have paraphrased Denning and her (few) cohorts as
accurately as I would have liked, I think your question is better
directed towards them.

Presumably when Denning says "social disorder" she is not thinking of
disorderly relationships such as choosing your own job, or friends,
or spouse, or whatever.

Peter Hendrickson
<EMAIL_ADDRESS>

{% endraw %}
```

## Thread

+ Return to [November 1996](/archive/1996/11)

+ Return to<EMAIL_ADDRESS>(Peter Hendrickson)](/authors/ph_at_netcom_com_peter_hendrickson_)"

+ 1996-11-08 (Fri, 8 Nov 1996 09:02:55 -0800 (PST)) - Re: Why is cryptoanarchy irreversible? -<EMAIL_ADDRESS>(Peter Hendrickson)_


text:
# MSCeleb1M-C1-Rewrite

Recognize celebrities from their face images! This code rebuilds Tensorflow graph and imports models provided in [wuyuebupt/MSCeleb1MTensorflowModel](https://github.com/wuyuebupt/MSCeleb1MTensorflowModel). For more information, see original repo.

Please download the pre-trained model from [wuyuebupt/MSCeleb1MTensorflowModel](https://github.com/wuyuebupt/MSCeleb1MTensorflowModel) and extract it. Set `--meta_graph` and `--model` arguments to the paths to MetaGraph dump and model file.

```
python3 identify.py \
    --meta_graph=model/graph-0707-065819.meta \
    --model=model/model-990960 \
    --input=FaceImageCroppedWithAlignment.tsv
```


text:
# Wax [![Build Status](https://dev.azure.com/tom-englert/Open%20Source/_apis/build/status/Wax?branchName=master)](https://dev.azure.com/tom-englert/Open%20Source/_build/latest?definitionId=47&branchName=master)
An interactive editor for [WiX Toolset](http://wixtoolset.org/) setup projects.

_Wax keeps your candle burning_

While it's an easy task to create an empty setup project with the [WiX Toolset](http://wixtoolset.org/), populating the list of deployable
files and even more keeping the list up to date can be a very fumbling task.
This tool is a Visual Studio Extension that helps you to create, verify and maintain the list of the deployed files in an interactive GUI.

Just select the projects that you want to install in the list box on the left side.
Two data grids on the right will show you the target directories needed and files to be installed, and how they are mapped to the file nodes in your WiX setup project.

Files that have no corresponding item in the WiX setup project are show in red. You can add them to the setup project by clicking the '+' button in the rightmost column.
Files that already exist in the setup project are shown in yellow. You can link them together by clicking the '?' button in the rightmost column.
Files that already exist in the setup project but have multiple matches are shown in orange. You can link items together by selecting the proper file from the combo box.

The file grid supports multiple selection, so you can apply all commands to many files in one step.

![Wax main screen](http://tom-englert.github.io/Wax/Screenshot.png)

## Installation

---
### Make sure you have installed the [WiX Toolset](http://wixtoolset.org/) before installing Wax!
---

This tool is a Visual Studio Extension. Use the Visual Studio Extension Manager, install from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=TomEnglert.Wax), or download the binaries and double click the Wax.vsix in the windows explorer.

The Wax editor is a tool to maintain WiX projects, so you should have installed the [WiX Toolset](http://wixtoolset.org/).

## Usage

### Preparing the solution

We'll assume here that you already have a solution with some projects that you want to deploy.
The Wax editor is collecting the output of the selected project(s) to install and all dependencies to populate the files list.
In order to get the full benefit from this tool, all files that need to be installed should be part of the projects.
Files that are not generated by the build, e.g. read-me files or documentation, should be added to the project with the `Build Action` set to `Content` and `Copy to Output Directory` to `Copy always` or `Copy if newer`.
If you follow this pattern, you won't have to manually fumble around with additional files in the WiX project.

### Create a new WiX Setup project

If you don't already have a WiX Setup project in your solution, create a new one now:
- In Visual Studio Click `File`, then click `New`, then click `Project`.
- Choose the Windows Installer XML node in the Project types tree, then select Setup Project
- Name your project and press OK.

### Open the editor

The WiX Setup Editor menu entry is located in the Visual Studios "Tools" menu.

![Wax main screen](http://tom-englert.github.io/Wax/Screenshot.png)

When parsing the projects, all files of the `Built`, `ContentFiles` and `LocalizedResourceDlls` build groups are collected. If you want to deploy the symbol files with your project, check the `Deploy symbols` toggle button in the tool bar.

There are five sections you have to edit in sequential order. If a green check mark appears in the top right corner, this section is complete. If there is a red exclamation mark, the section needs editing.

If you have made conceptual changes to your solution while the editor is open, click the refresh button.

### (1) Select the WiX project to edit.

As the first step select the WiX project you want to edit. If there is only one setup project in the solution, it will be already selected.

### (2) Map the root directory.

The editor needs to know the root directory definition in the wix file. Simply select it from the items in the combo box.
If you have created a new WiX Setup project, there is only one and it is named ```INSTALLFOLDER```.

### (3) Select the project(s) to install.

Select the project(s) that you want to install. This is maybe just the one .exe project in your solution.
Since dependencies are detected automatically and don't need to be selected explicitly, they are not shown in the list; also test projects are hidden by default.
However if you think some project is missing here, check the "Show all projects" check box to see every project of the solution.

Every project you select will be automatically added to the WiX projects references, so the build order will be correct and you can use project reference variables in the WiX project.

### (4) Create the directory mappings.

If you projects need to deploy files into subdirectories of the ```INSTALLFOLDER```, you need to define or map them here.
If you are starting with an empty project, just click on the "+" in the rightmost column of each directory to create the WiX definitions.
If there are already directories defined in the WiX project, a combo box will appear where you can select the directory that maps to the projects output folder.

### (5) Create the file mappings.

The file mappings list shows all output from the selected projects.
If you are starting with an empty WiX project, all files will be shown in red and the state is "Unmapped".
You can select all files and click on the "+" button in the rightmost column to create all files entries.

If you are editing an existing WiX project that you have created manually or e.g. with the "Harvest" tool, files might also appear as "Unique" or "Ambiguous".
"Unique" means that there is only one file with that name in the whole solution, so it probably matches the file to be installed. Click on the "?" button in the rightmost column to confirm the match.
"Ambiguous" means that there are several files with the same name. Use the combo box to select the matching file.

### Post processing

#### Save all files
Wax adds a new file to your setup project, named ```<project name>.wax```. This file stores all configurations you have made in the above steps. Make sure to save this file with your project, since it contains all information you need to maintain the project later. Also make sure the WiX files (.wxs, .wxi) are saved.

#### Check your feature tree
Wax will add a ComponentGroupRef node for all component groups it creates to the first feature it finds in your project. If you have just one feature defined, this will be fine; if you have more than one feature in your setup project, copy or move the entries as desired.

```
  <Product ...>
    <Feature Id="ProductFeature" Title="ACME.Setup" Level="1">
      <ComponentGroupRef Id="ProductComponents" />
      <ComponentGroupRef Id="de_files" />
      <ComponentGroupRef Id="fr_files" />
    </Feature>
  </Product>
```

Now you should be able to build the setup project.

Powered by

Support this Project:

repository: hxhlb/Wax

repo_name: hxhlb/Wax


text:
---
title: dlx lxc profile assign
description: dlx lxc profile assign
lead: dlx lxc profile assign
date: 2021-10-12T10:37:58Z
lastmod: 2021-10-12T10:37:58Z
draft: false
images: []
menu:
  docs:
    parent: "cli"
weight: 100
toc: true
---
## dlx lxc profile assign

Assign sets of profiles to instances

### Synopsis

Description:
  Assign sets of profiles to instances

```
dlx lxc profile assign [<remote>:]<instance> <profiles> [flags]
```

### Examples

```
  lxc profile assign foo default,bar
      Set the profiles for "foo" to "default" and "bar".

  lxc profile assign foo default
      Reset "foo" to only using the "default" profile.

  lxc profile assign foo ''
      Remove all profile from "foo"
```

### Options inherited from parent commands

```
      --debug         Show all debug messages
      --force-local   Force using the local unix socket
  -h, --help          Print help
      --project       Override the source project
  -q, --quiet         Don't show progress information
  -v, --verbose       Show all information messages
      --version       Print version number
```

### SEE ALSO

* [dlx lxc profile](/docs/cmd/dlx_lxc_profile)	 - Manage profiles

repository: fineimew/dlx

repo_name: fineimew/dlx


text:
[![Maven Central](https://maven-badges.herokuapp.com/maven-central/com.github.riteshkukreja/vertx-annotations/badge.svg)](https://maven-badges.herokuapp.com/maven-central/com.github.riteshkukreja/vertx-annotations)
[![Build Status](https://travis-ci.com/riteshkukreja/vertx-annotations.svg?branch=master)](https://travis-ci.com/riteshkukreja/vertx-annotations)
[![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat)](https://github.com/riteshkukreja/vertx-annotations/issues)
[![Issues](https://img.shields.io/github/issues-raw/riteshkukreja/vertx-annotations.svg?maxAge=2592000)](https://github.com/riteshkukreja/vertx-annotations/issues)

# vertx-annotations
Boilerplate code generator for Vert.x applications.

## Introduction
Vert.x applications are great way to build scalable and reactive applications. But you tends to create more boilerplate code with each vertical.
This library aims to reduce those boilerplate code by automatically generating it for your application based on couple of annotations.

## Annotations
### @HttpVertical
It's a class based annotation which generates a HttpVertical for all paths targeted inside the class. Paths are targeted using @Get and @Post annotations on  the class methods.

### @Get
It's a method based annotation which specifies a Get method route for the parent vertical.

### @Post
It's a method based annotation which specifies a Post method route for the parent vertical.

### @MessageHandler
It's a method based annotation which generates a EventBusVertical for specified path.

## Sample App
1. Add dependency to your `pom.xml`
```xml
<dependency>
  <groupId>com.github.riteshkukreja</groupId>
  <artifactId>vertx-annotations</artifactId>
  <version>1.0.0</version>
</dependency>
```

2. Create a file named `UserHandler.java` and insert following code
```java

@HttpVertical("/user")
public class UserHandler {

    @Get("/")
    public void sayHello(RoutingContext context) {
        context.response().end("Hello");
    }

}

```

3. Set generated vertical as your starting vertical.
```xml
<properties>
    <main.verticle>gen.verticals.MainVerticalGen</main.verticle>
</properties>

<plugins>
    <!--  Add Maven shade plugin to generate fat-jar -->
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-shade-plugin</artifactId>
        <version>2.4.3</version>
        <executions>
            <execution>
                <phase>package</phase>
                <goals>
                    <goal>shade</goal>
                </goals>
                <configuration>
                    <transformers>
                        <transformer
                                implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                            <manifestEntries>
                                <Main-Class>io.vertx.core.Launcher</Main-Class>
                                <Main-Verticle>${main.verticle}</Main-Verticle>
                            </manifestEntries>
                        </transformer>
                    </transformers>
                    <outputFile>${project.build.directory}/${project.artifactId}-${project.version}-fat.jar</outputFile>
                </configuration>
            </execution>
        </executions>
    </plugin>
</plugins>
```

4. Compile and run your fat-jar
```bash
java -jar <fat-jar>.jar
```

# Contributing
Pull requests for new features, bug fixes, and suggestions are welcome!

# License
This project is licensed under [MIT](https://github.com/riteshkukreja/vertx-annotations/blob/master/LICENSE)

repository: riteshkukreja/vertx-annotations

repo_name: riteshkukreja/vertx-annotations


text:
### [Volume of Histogram](https://leetcode.com/problems/volume-of-histogram-lcci)

Imagine a histogram (bar graph). Design an algorithm to compute the volume of water it could hold if someone poured water across the top. You can assume that each histogram bar has width 1.

The above elevation map is represented by array [0,1,0,2,1,0,1,3,2,1,2,1]. In this case, 6 units of water (blue section) are being trapped. Thanks Marcos for contributing this image!

Example:

Input: [0,1,0,2,1,0,1,3,2,1,2,1]
Output: 6

url: https://raw.githubusercontent.com/6leetcode/6leetcode/0c0973c634c881bd874bad5a0526b91a2d83f1a0/questions/LCCI/面试题 17.21. Volume of Histogram/README.md


text:
# Homework-6

The file `exercise.c` contains C code for application login.
Once executed, the program asks you for a password and, if it matches a secret saved inside the program it will print `Correct password!`.

Having access to the program source code, you have to find the program input such that it lets you exploit the buffer overflow vulnerability and login with an arbitrary password (different than the one stored inside the program).

Repeat the exercise with and without line 9

```c
 char version[3] = "1.0";
```

Is it different? Why?

1. Write a single page report explaining the vulnerability and how you can exploit it.
2. Try to fix the vulnerability

repository: mfranzil-unitn/unitn-m-st

repo_name: mfranzil-unitn/unitn-m-st


text:
[Previous](./ans20-01.md)                [Exercise](../ex/ex21-01.md)            [Next](./ans21-02.md)

# Exercise 21 - Measure the distance of spots to the border of the nucleus
## Exercise 21.1 - Spot detection using a Difference of Gaussian (DOG) Filter
Aims:
- write a function to implement the DoG- filter
- use it to detect spots

The Difference of Gaussian (DOG) can help us to segment spots in a given range of sizes.
A DoG-filter can be implemented in the following way:
- create a copy of the image I1 and apply a Gaussian blur filter with a small sigma s1 to it
- create a copy of the image I2 and apply a Gaussian blur filter with a big sigma s2 to it
- Subtract the image I2 from the image I1

Write a function that implements the DoG-filter! The function should work on a copy of the active image.
It has two parameters ``sigma1`` and ``sigma2``.

You will need to use ``Duplicate``, the ``Gaussian blur`` filter
and the ``Image Calculator``. If you need to switch between different images, you can use
``getImageID()`` and ``selectImage()`` and ``getTitle()``.

Try the DOG on the image in the folder ``images/21`` with sigma1 = 1.4 and sigma2 = 3.

```java

DoG(1.4, 3);

function DoG(sigma1, sigma2) {
```
Your code starts after this line
```java
	run("Duplicate...", " ");
	bigBlurID = getImageID();
	run("Duplicate...", " ");
	smallBlurID = getImageID();
	run("Gaussian Blur...", "sigma="+sigma1);
	selectImage(bigBlurID);
	bigBlurTitle = getTitle();
	run("Gaussian Blur...", "sigma="+sigma2);
	imageCalculator("subtract", smallBlurID, bigBlurID);
	close(bigBlurTitle);
```

Your code ends before this line
```java
}
```
[Previous](./ans20-01.md)                [Exercise](../ex/ex21-01.md)            [Next](./ans21-02.md)


text:
# Change Log

All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.

## [0.8.1](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.8.0<EMAIL_ADDRESS>(2021-08-03)

### Bug Fixes

* **parser:** Fix expected type for `enum` property when type is `"number"` ([29c16eb](https://github.com/simonlovesyou/cling/commit/29c16eb7841b8b8e40c371d9be41678be0c42c9b))

# [0.8.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.7.3<EMAIL_ADDRESS>(2021-08-02)

### Features

* **parser:** Add support for parsing array types ([3173266](https://github.com/simonlovesyou/cling/commit/31732660dea333a07981e54df6f7f0b46dfa5efa))
* **parser:** Remove `format` property from Array arguments ([1248fc2](https://github.com/simonlovesyou/cling/commit/1248fc220d05230878f659a8a74e7a67db17b49e))

## 0.7.3 (2021-08-02)

**Note:** Version bump only for package @cling/parser

## [0.7.2](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.7.1<EMAIL_ADDRESS>(2021-07-30)

**Note:** Version bump only for package @cling/parser

## [0.7.1](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.7.0<EMAIL_ADDRESS>(2021-07-30)

### Bug Fixes

* **parser:** Convert Argument schemas to JSON schemas for validation ([#19](https://github.com/simonlovesyou/cling/issues/19)) ([6014edf](https://github.com/simonlovesyou/cling/commit/6014edf8708b6b690ee002d773a8e27db985f514))

# 0.7.0 (2021-07-30)

### Features

* **parser:** Add/Move `convertArgumentToJSONSchema` utility function from @cling/utils` ([b2dc2ed](https://github.com/simonlovesyou/cling/commit/b2dc2edf05658e8391c4628e8997782dc6bc1d68))

## 0.6.9 (2021-07-24)

**Note:** Version bump only for package @cling/parser

## [0.6.8](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.7<EMAIL_ADDRESS>(2021-07-24)

**Note:** Version bump only for package @cling/parser

## [0.6.7](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.6<EMAIL_ADDRESS>(2021-07-23)

**Note:** Version bump only for package @cling/parser

## [0.6.6](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.5<EMAIL_ADDRESS>(2021-07-23)

**Note:** Version bump only for package @cling/parser

## [0.6.5](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.4<EMAIL_ADDRESS>(2021-07-23)

**Note:** Version bump only for package @cling/parser

## [0.6.4](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.3<EMAIL_ADDRESS>(2021-07-23)

**Note:** Version bump only for package @cling/parser

## [0.6.3](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.2<EMAIL_ADDRESS>(2021-07-23)

**Note:** Version bump only for package @cling/parser

## [0.6.2](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.6.1<EMAIL_ADDRESS>(2021-07-17)

**Note:** Version bump only for package @cling/parser

## 0.6.1 (2021-07-17)

### Bug Fixes

* **parser:** Update library schema so that commands are optional in resulting object ([8500c7f](https://github.com/simonlovesyou/cling/commit/8500c7f040c19b9d4158d8c07bfb6be85512aea0))

# [0.6.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.5.2<EMAIL_ADDRESS>(2021-07-17)

### Features

* **parser:** Export common types ([97cd10d](https://github.com/simonlovesyou/cling/commit/97cd10d4d43955324ee42c466e2749abe2af4bac))

## [0.5.2](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.5.1<EMAIL_ADDRESS>(2021-07-17)

### Bug Fixes

* **parser:** Fix inferred type for tuples ([32c11a4](https://github.com/simonlovesyou/cling/commit/32c11a45b281c458c0cf78c78fdae6c12a92e44d))
* **parser:** Fix so that number enums can also be inferred ([a62e86e](https://github.com/simonlovesyou/cling/commit/a62e86ef818f969859451fb4680c61f8a9b0460c))

## 0.5.1 (2021-07-17)

### Bug Fixes

* **parser:** Fix incorrectly inferrence of enum types/values ([b891b52](https://github.com/simonlovesyou/cling/commit/b891b5272d2287476272ec42d4f902bc4f78e143))

# [0.5.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.6<EMAIL_ADDRESS>(2021-07-17)

### Features

* **parser:** Add support for enums ([#13](https://github.com/simonlovesyou/cling/issues/13)) ([c21e791](https://github.com/simonlovesyou/cling/commit/c21e7915f75a0ce084b38fd8f3d2c4dcd0e2e380))

## [0.4.6](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.5<EMAIL_ADDRESS>(2021-07-16)

### Bug Fixes

* Fix positional parser type ([#12](https://github.com/simonlovesyou/cling/issues/12)) ([41103c8](https://github.com/simonlovesyou/cling/commit/41103c812b63bf2bec3c7e45adcce8a1cbe6b737))

## [0.4.5](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.2<EMAIL_ADDRESS>(2021-07-15)

**Note:** Version bump only for package @cling/parser

## [0.4.4](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.2<EMAIL_ADDRESS>(2021-07-14)

**Note:** Version bump only for package @cling/parser

## [0.4.3](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.2<EMAIL_ADDRESS>(2021-07-14)

**Note:** Version bump only for package @cling/parser

## [0.4.2](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.1<EMAIL_ADDRESS>(2021-07-12)

**Note:** Version bump only for package @cling/parser

## [0.4.1](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.4.0<EMAIL_ADDRESS>(2021-07-12)

### Bug Fixes

* **parser:** Fix bug where boolean options where not correctly parsed ([1591ba6](https://github.com/simonlovesyou/cling/commit/1591ba614f23f37bd9698f1df0e08380b8998825))

# [0.4.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.3.0<EMAIL_ADDRESS>(2021-05-22)

### Features

* **parser:** Add error message prefix with key name ([bd70057](https://github.com/simonlovesyou/cling/commit/bd700573dc3fa62388235384fa34e67cd90e1cd6))

# [0.3.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.2.3<EMAIL_ADDRESS>(2021-05-22)

### Bug Fixes

* **parser:** Add proper handling of missing positional arguments ([5b41f0b](https://github.com/simonlovesyou/cling/commit/5b41f0b3677327dfebdb1e619255748bd196ae1b))
* **parser:** Remove ts-node as a dependency ([4352e9f](https://github.com/simonlovesyou/cling/commit/4352e9ffef133f71a0c436058574316c8ad04bd0))

### Features

* **parser:** Add format validation ([05c0d34](https://github.com/simonlovesyou/cling/commit/05c0d34ef4dbef78176ad357d50eb22a4d4fa013))

## [0.2.3](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.2.2<EMAIL_ADDRESS>(2021-05-18)

### Bug Fixes

* **parser:** Make values from options optional ([72eff7a](https://github.com/simonlovesyou/cling/commit/72eff7a566e94539909383575ac5802bf8f839f2))

## [0.2.2](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.2.1<EMAIL_ADDRESS>(2021-05-17)

### Bug Fixes

* **parser:** Reduce tarball size ([62ab810](https://github.com/simonlovesyou/cling/commit/62ab8108cf420659ea2d89be554ee739e5baf949))

## [0.2.1](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.2.0<EMAIL_ADDRESS>(2021-05-17)

### Bug Fixes

* **parser:** Add typings property in package json ([b5ef029](https://github.com/simonlovesyou/cling/commit/b5ef029a146b0ac9778dc97ca7b7f9e43f9ab4a5))

# [0.2.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.1.0<EMAIL_ADDRESS>(2021-05-17)

### Bug Fixes

* **parser:** Use correct tsconfig ([8d17f0c](https://github.com/simonlovesyou/cling/commit/8d17f0cea50aeb88759ba497fd28338717c08086))

### Features

* **parser:** Add inferring of return data and update the return signature of the library ([9fdd71c](https://github.com/simonlovesyou/cling/commit/9fdd71cebba2bfef448507c99623a5a5d8cc37cc))
* **parser:** Add support for commands & update return response API ([9d1a817](https://github.com/simonlovesyou/cling/commit/9d1a817fbbade1b867c30b100ca99ec44fcca6b0))
* **parser:** Add support for inferring more types ([89d5b80](https://github.com/simonlovesyou/cling/commit/89d5b80f041056e60ca7df0f37cee7814b85906b))
* **parser:** Add support for parsing array types ([e18a3b1](https://github.com/simonlovesyou/cling/commit/e18a3b110d8b30a71a5d20bacd28dd00f1fc91c3))
* **parser:** Remove support for $ref in schema ([082a33f](https://github.com/simonlovesyou/cling/commit/082a33f6815cfaa66a2c31732921f4c23e3babdc))
* **parser:** Remove support for object type in schema ([77e1f81](https://github.com/simonlovesyou/cling/commit/77e1f819981f1758ecd21f504b4b193bc1334286))

# [0.1.0](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.0.5<EMAIL_ADDRESS>(2021-05-09)

### Features

* **parser:** Expose `Argument` as export ([938b6fb](https://github.com/simonlovesyou/cling/commit/938b6fbb4dd597d75e50b691d8c1fca9924881a6))
* **parser:** Remove `name` as property of `Argument` ([ac4a3da](https://github.com/simonlovesyou/cling/commit/ac4a3da523eb1d579de518f011ebdb0572f69348))

## [0.0.5](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.0.4<EMAIL_ADDRESS>(2021-05-09)

### Bug Fixes

* **parser:** Expose the internal schema type from root ([dcb513b](https://github.com/simonlovesyou/cling/commit/dcb513b1461082b69f0b1440e83687135d819c04))

## [0.0.4](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.0.3<EMAIL_ADDRESS>(2021-05-03)

### Bug Fixes

* **parser:** Rename positionals argument name to reduce chance of name conflict ([d8ba24a](https://github.com/simonlovesyou/cling/commit/d8ba24ae121ef23823275f98ea1bfa1a374e28b0))

## [0.0.3](https://github.com/simonlovesyou/cling/compare/@cling/parser@0.0.2<EMAIL_ADDRESS>(2021-05-03)

### Bug Fixes

* **parser:** Remove test code execution in main lib file ([abecd75](https://github.com/simonlovesyou/cling/commit/abecd75af1f7cfda78b43265b3ac075cdb397fa2))

## 0.0.2 (2021-05-01)

**Note:** Version bump only for package @cling/parser

repository: simonlovesyou/cling

repo_name: simonlovesyou/cling


text:
## Description

Your task is to build a Node.js command-line application that takes in information about employees on a software engineering team, then generates an HTML webpage that displays summaries for each person. Testing is key to making code maintainable, so you’ll also write a unit test for every part of your code and ensure that it passes each test.

Because this application won’t be deployed, you’ll need to provide a link to a walkthrough video that demonstrates its functionality and all of the tests passing. You’ll need to submit a link to the video AND add it to the readme of your project.

# company_profile_CLI
OOP: Team profile generator

## Classes:
The application includes ```Employee```, ```Manager```, ```Engineer```, and ```Intern``` classes. The latter three child classes extend from the parent class ```Employee```. These child classes will inheret the properties ```name```, ```id```, and ```email```, along with their methods.

![UML_diagram](assets/imgs/company_profile_CLI.jpeg)

```javascript
class Employee {
    constructor(name, id, email) {
        this.name = name;
        this.id = id;
        this.email = email;
        if(this.name === undefined || this.id === undefined || this.email === undefined) {
            throw new Error("Expected parameters must be valid arguments");
        };
    };
```
Each child class possesses their own unique property and method in conjunction with those inherited from the parent class using the ```super``` function.

```javascript
class Manager extends Employee {
    constructor(name, id, email, officeNumber) {
        super(name, id, email);
        this.officeNumber = officeNumber;
        if(this.name === undefined || this.id === undefined || this.email === undefined) {
            throw new Error("Expected parameters must be valid arguments");
        };
    };

```
## Testing
Unit tests are written for each class, ensuring each test passes. The initial tests are designed to fail at first until the most simple code is written to get the tests to pass.

![UML_diagram](assets/imgs/passed_tests.PNG)

Once initial tests have passed, code will then be refactored to deliver a solid, functioning app.

gha_language: HTML


text:
# μυέω -ῶ

<!-- Status: S2=NeedsEdits -->
<!-- Lexica used for edits:   -->

## Word data

* Strongs: G34530

* Alternate spellings:

* Principle Parts:

* Part of speech:

* Instances in Scripture: 1

* All Scriptures cited: Yes

## Etymology:

[μύω](), to shut the mouth),

* LXX/Hebrew glosses:

* Time Period/Ancient Authors:

* Related words:

* Antonyms for all senses

* Synonyms for all senses:

## Senses

### Sense  1.0:

#### Definition:

#### Glosses:

to initiate into the mysteries;

#### Explanation:

to instruct;

#### Citations:

to initiate into the mysteries (so chiefly in cl.; LXX, [[III Mac 2:30](3Macc.2.30)](3Macc.2.30)); hence, to instruct: pass., [Phl 4:12](Php 4:12) (RV, I have learned the secret).†

repository: mandolyte/uw-obsidian

repo_name: mandolyte/uw-obsidian


text:
# ECO_Camera
A computer vision system based surveillance system to prevent unauthorised waste disposal in public places.
***
## Setup
1. Clone the repository
2. Download and copy pretrained weights to the root folder
3. Install requirements `pip install -r requirements.txt`
4. Install Tesseract OCR engine.
5.

gha_language: Python