text:
# Payment Tracker

Payment Tracker is a simple CLI application that allows user to track payments with in different currency.

# Getting started
## Prerequisites
Before you start building the application, you need to:
 * Install the latest version of [Java](https://java.com)
 * Donwload and unpact latest version of [Maven](https://maven.apache.org/download.html).
 * Set the environment variable `JAVA_HOME`.
 * Set you favorite IDE.

## Installing
Once you have installed and configured our environment, you can build the application.

Download or fork this project from GitHub repository and jump to the project director.
```
$ cd payment-tracker
```
In this directory run maven installation goal:
```
$ mvn clean install
```
This will build the application and create also one executable jar package.

## Running the application
After installation move to the target directory:
```
$ cd target
```
and start the application
```
$ java -jar payment-tracker-1.0-SNAPSHOT-with-dependencies.jar
```

# How to use
When you start the application and welcome screen shows, you can enter commands or payment directly.

## Startup parameters
You can start the application without any parameter or use one of this:
 * `-h` - prints help message and quit the application.
 * `-v` - prints version description of the application and quit the application.
 * `-f` - load payments from text file. You have to specify full file path.
Every other startup parameter are invalid. In that case the application prints help message and quits.

## Commands
The application command line interface read every user input. Possible commands are:
 * `add` - add new payment. You have to enter payment in right format. Payment format is three capital letters, space and decimal number.
 * `help` - prints help message.
 * `version` - prints version description of the application.
 * `load` - load payments from text file. You have to specify full file path.
 * `quit` - end the application.

You can also enter single payment directly in right format. If you insert payment in wrong format or enter any other command, the application will print Invalid command message to the error output. This does not terminate the application.

# License
Payment Tracker application is distributed under MIT license.

repository: ptacekp/payment-tracker

gha_language: Java

repo_name: ptacekp/payment-tracker


text:
---
external help file: PSAptGetUpdate-help.xml
Module Name: PSAptGetUpdate
online version: https://github.com/iricigor/psaptgetupdate/blob/master/Docs/Find-ScriptFromCache.md
schema: 2.0.0
---

# Find-ScriptFromCache

## SYNOPSIS
Finds PowerShell scripts with given name using local cache.

## SYNTAX

```
Find-ScriptFromCache [-ScriptName] <String[]> [<CommonParameters>]
```

## DESCRIPTION

The Find-ScriptFromCache cmdlet finds PowerShell scripts with given name(s) using local cache.
Local cache is obtained/updated with command `Update-PSRepositoryCache` (or using its alias `psaptgetupdate`).
Searching local cache is about 20-100 times faster than online search performed via `Find-Script` command from PowerShellGet.

## EXAMPLES

### Example 1

```powershell
PS C:\> Find-ScriptFromCache 'Get-FolderAge' | Select Name, Description
```

```
Name          Description
----          -----------
Get-FolderAge Get-FolderAge returns `LastModifiedDate` for a specified folder(s) and if folders were modified after ...
```

## PARAMETERS

### -ScriptName

Specifies the names of one or more scripts to search for.
Only scripts that exactly match the specified names are returned.
If no matches are found, no error is returned.

```yaml
Type: String[]
Parameter Sets: (All)
Aliases: Name

Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False
```

### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### System.String[]

## OUTPUTS

### System.Object

## NOTES

## RELATED LINKS

license: MIT

repository: iricigor/psaptgetupdate

branch_name: refs/heads/master

extension: md

gha_language: PowerShell

gha_license_id: MIT

license_type: permissive

repo_name: iricigor/psaptgetupdate


text:
## Autodesk Inventor code samples ##

### bspline-surface ###

This example shows how to create a B-spline surface from an arbitrarily-chosen set of control points, z = 0.3 * cos(2*x^2 + 2*y^2).
Originally this example was built to help troubleshoot the long time required to create complex splines.
For a spline with m-by-n control points, the time seems to go as O(n^3 * m^3) in Inventor 14.

### interactive-mesh ###

This example shows how to create a static triangle mesh in the current document.

repository: CodeReclaimers/inventor-code-samples

repo_name: CodeReclaimers/inventor-code-samples


text:
---
layout: post
title: Ha and MacPherson Labs receive Kuni Foundation Discovery Grant for Cancer Research
shorttitle: Lab receives Kuni Foundation Grant
author: Gavin Ha
image: /images/news/kuni-01.png
---

The labs of [Gavin Ha](/) and [David MacPherson](https://research.fredhutch.org/macpherson/en.html){:target="_blank"} receive a 3-year grant from the [Kuni Foundation](https://www.kunifoundation.org/){:target="_blank"} to develop lung cancer diagnostics for subtyping and predicting response to novel treatments using innovative methods to analyze cell-free DNA. The outcome of this work will have great potential to both guide cancer treatment decisions and to enable early lung cancer detection. We are grateful to the Kuni Foundation for their generous support of our pursuit to improve the lives of patients with lung cancer.

gha_language: JavaScript


text:
The Preferences dialog is accessible via the `Settings > Preferences` menu option or via the `CTRL+P` keyboard shortcut.

### Binaries

The binaries sheet allows the location of optional 3rd party binaries to be configured.

![Binaries](../img/preferences_binaries.png)

#### ffmpeg

BEQDesigner uses [ffmpeg](https://ffmpeg.org/) for all AV file processing such as audio extraction or remuxing. It uses ffmpeg for the actual processing and ffprobe for discovering information about the file.

If ffmpeg is not on your `PATH` (which typically means you are a Windows user) then set the location here.

#### minidsp-rs

BEQDesigner can use [minidsp-rs](https://github.com/mrene/minidsp-rs) to load filters into a minidsp 2x4HD.

### Analysis

![Analysis](../img/preferences_analysis.png)

These options control how audio files are presented for analysis and are applied only when a signal is added.

* Target Fs: sets the sample rate to use when audio is decimated (either when adding a signal or extracting audio)
* Resolution: determines the FFT length used in the STFT analysis, the FFT length will be set to aim for the chosen frequency resolution.
    * The actual resolution is constrained by the requirement for a power of 2 FFT length, for example if the sample rate is 1000Hz and the target is 1.0Hz resolution then the FFT length will be 1024 and the actual frequency resolution will be 1000/1024 = 0.976Hz.
    * If the sample rate is 48kHz and the target is 1.0Hz then the FFT length will be 65536 and the actual resolution will be 48000/65536 = 0.732Hz
* Avg/Peak Window: a list of window types is presented corresponding to the [scipy window functions](https://docs.scipy.org/doc/scipy/reference/signal.windows.html#module-scipy.signal.windows), a description of how different window types behave is outside the scope of this guide.

!!! warning
    These options should be left at the default values for all known BEQ purposes.

### Extraction

![Extract](../img/preferences_extraction.png)

These options set some defaults for the [Extract Audio](./extract_audio.md) dialog.

* Default Output Directory: default location for extracted audio files
* Extract Complete Sound: if an audio file is set here, the file will be played whenever audio extraction completes
* All remaining checkboxes: sets the default state of the named checkboxes

### Style

![Style](../img/preferences_style.png)

These options influence the look and feel of BEQDesigner.

* Theme: different colour schemes for the various charts, does not apply to the waveform view.
* Smooth?
    * if unchecked, simple line graphs are drawn to join from one point to the next hence graphs will have a slightly 'spiky' appearance.
    * if checked, an [interpolation method](https://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.PchipInterpolator.html#scipy.interpolate.PchipInterpolator) is applied which retains an accurate shape while smoothing the edges slightly
* Speclab Line Colours?
    * a compatibility mode for speclab users, if checked each peak curve will be rendered in a shade of red while the average will be in a shade of green.
    * if unchecked, peak and average for each signal will be the same colour but colours for each signal will vary accordingly to the theme.
    * as a rule of thumb, speclab mode is easier to read when viewing a single signal only but becomes unreadable when you have many signals (e.g. a multichannel audio track)
* Image Format
    * the default format to use when exporting as a image, choice of png or jpg

### Graph

![Graph](../img/preferences_graph.png)

These options set defaults for the magnitude graph layout

* Frequency Axis Log Scale? : if checked, use a log scale otherwise linear
* Precalculate Octave Smoothing
  * if checked, all fractional octave curves will be precomputed when the signal is added
  * if unchecked, the smoothed view is calculated as the option changes
* Auto Expand Y Limits? : if checked, the y axis range will automatically expand to fit all visible data on screen (when the graph is in auto ranging mode)
* x min/max: default x axis range for graphs

### Filter

![Filter](../img/preferences_defaults.png)

These options set defaults for the corresponding controls on [Filter Design](./add_filter.md) dialog

* Default Q and Frequency for each commonly used filter type (low shelf, high shelf, peaking)
* BM LPF: sets the frequency for the low pass filter applied in the [Bass Management Simulation](../workflow/bass_management.md)

### System

![System](../img/preferences_system.png)

Check the *Check for updates on startup?* option to allow BEQDesigner to query the github releases api on startup.

Check the *Include Beta Versions?* option to be notified when new prerelease versions are published.

If the latest release is not the current release, an alert will be shown to notify you.

### BEQ Files

![BEQ](../img/preferences_beq.png)

Allows configuration of git repos which are store published beq filters.

* Directory: the location to which downloaded files should be place

### Where are preferences stored?

Settings are stored using a [Qt feature](https://doc.qt.io/qt-5/qsettings.html#locations-where-application-settings-are-stored) so the location is OS specific.

* Windows: in the registry under `HKEY_CURRENT_USER\Software\3ll3d00d\BEQDesigner`
* Linux: in `3ll3d00d/BEQDesigner.conf` in a directory specified by `$XDG_CONFIG_DIRS` (for example, on KDE this is $HOME/3ll3d00d/BEQDesigner.conf)
* OSX: in `$HOME/Library/Preferences/3ll3d00d.BEQDesigner.plist`

gha_language: Python


text:
# Parking Lot Generator

## Summary
Parking lot diagrams are used in Feature Driven Development (FDD) to visualize a
rolled up project status. In addition to FDD projects, Parking lot diagrams also
may be useful on XP or Scrum projects. To read more about parking lot diagrams,
see Summarizing Progress with Parking Lot Diagrams.

This documentation is a little sparse. In between now and when I can fill it
out, feel free to contact me with any questions.

## Dependencies
This application is packaged with Composer and
built using Box. The Makefile assumes that the box executible is in your
path

## Parking Lot Diagram
A parking lot diagram is a high-level visualization of a project status.
Traditionally, parking lot diagrams represent Feature Areas, Feature Sets, and
Features. This may be analogous to a hierarchy of Epics, Features, and Stories.

### Example Parking Lot Diagram
![example](./assets/images/example.png)

## Building
To build, run 'composer install' in the top level directory. Then run 'make'.
The executable will be built to bin/ParkingLotGenerator.phar. Again, the make
file assumes that the box executible is in your PATH (and named 'box', not
box.phar).

## Usage

### Configuration

The configuration file describes the feature areas, feature sets, and features
from which the parking lot diagram will be built.

**Feature Areas** - Feature areas consist of a unique name and an array of
feature sets.

**Feature Sets** - Feature sets consist of a feature set name (unique to the
feature area), owner, and an array of features.

**Features** - Features consist of a feature name (unique to the feature set),
due date, and status. The due date should be in the format "mm/dd/YYYY". The
status may be "Open", "In Progress", or "Completed".

#### Example
```json
{
    "feature areas": [
        {
            "name": "Feature Area 1",
            "featureSets": [
                {
                    "name: "Feature Set 1",
                    "owner": "MSS",
                    "features": [
                        {
                            "name": "feature 1",
                            "dueDate": "01/07/2017",
                            "status": "Open"
                        },
                        {
                            "name": "feature 2",
                            "dueDate": "01/07/2017",
                            "status": "In Progress"
                        },
                        {
                            "name": "feature 2",
                            "dueDate": "01/07/2017",
                            "status": "Completed"
                        }
                    ]
                }
            ]
        }
    ]
}
```

### Execution
Run `php bin/ParkingLotGenerator.phar --help` to display the help.
~~~
Description:
  Generates a Parking Lot diagram from an input CSV.

Usage:
  php ParkingLotGenerator.phar -h | --help
  php ParkingLotGenerator.phar --version
  php ParkingLotGenerator.phar --input <file path> [--output <file_path>]

Options:
  -h --help                           Show Help
  --version                           Show the version and git commit of this build
  --project-name                      The name of the project
  --input                             The input json file
  --output                            Optional output file (default: './parking_lot.html')

Output: Outputs an html file that contains a ParkingLot Diagram
~~~

#### Example
`php bin/ParkingLotGenerator.phar --project-name "Example Project" --input "$HOME/example.json" --output "/var/www/html/parking_lot.html"`

#### Note
You will need to copy assets/css/style.css to the same destination directory as
your output html.

## Known issues and shortcomings

* I'm not all that great with CSS. The generated report could probably use a
  face lift.
    * No attempt has been made to ensure a consistent look and feel across
      different browsers.
* The style.css must be manually copied to the destination directory.
* While there is some input validation, it's not as robust as it could be. The
  input config file could be better validated.
    * WARNING: The Parking Lot Generator is
      currently vulnerable to XSS and other attacks as the input file is assumed
      to be trusted.
* There are currently no application level configuration options (e.g. the
  report title and "Generated" message are not configurable)
* This documentation is a little sparse. In between now and when I can fill it
  out, feel free to contact me with any questions.

repository: mssalvatore/parking-lot-generator

repo_name: mssalvatore/parking-lot-generator


text:
# CDC-ct-workflow-modeling

~~~~
The core functionality of this package is contained in src/WorkflowModel.py. Running this program directly
through python will produce summary statistics along with the json data files that contain all of the
information about the run. Matlab wrapper code is also included to facilitate easy change of configuration
settings and enhanced visualization capabilities.

All of the base configuration settings are in src/pytools/config.txt. This file uses the convention that
comments are designated by a ‘#’ and configuration parameters and values are of the format parameter = value.
These can be changed directly in the file, but can also be specified in run.m when executing from Matlab. To
specify deviations from the values in config.txt, run.m can be updated using the convention
setup.<parameter> = <value>; in the section “Deviate from default, if desired”

Running the application through Matlab is done by running run.m while in the base directory. The base
directory also needs to be added to the Matlab path. Once the run is complete functions such as basicPlot.m
and prettyPlot.m are used to explore the values produced by the run. Additional visualization and analytic
tools will use the results stored in the variable arraysOut. This contains several types of information
including the dispensation of each of the individuals in the simulation as well pre-summarized information
pertaining to a wide range of interesting metrics.

The individual status’ stored in arraysOut.arrays.ISM are coded according to the specification in
process_logs.py. Each of these two character codes define the behavior and state of the individual on each
day. The first digit is:

0 – Normal behavior

1 – Minimal restriction

2 – Moderate restriction

3 – Maximal restriction

And the second digit is:

1 – Exposed

2 – Pre-symptomatic

3 – Symptomatic

4 – Asymptomatic

5 – Uninfected

6 – Recovered

The other information is contained in arraysOut.arrays.days and arraysOut.arrays.people. The ‘days’ array summarizes each day with a count of each event of interest. The ‘people’ array provides all of the pertinent information about each person, such as which individual generated them and whether or not they were ever tested.
~~~~

## Disclaimer

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited. This material is based
upon work supported by the Under Secretary of Defense for Research and Engineering under Air Force
ContractNo. FA8702-15-D-0001. Any opinions, findings, conclusions or recommendations expressed in this
material are those of the author(s) and do not necessarily reflect the views of the Under Secretary of
Defense for Research and Engineering.

© 2020 Massachusetts Institute of Technology

Delivered to the U.S. Government with Unlimited Rights, as defined in DFARS Part<PHONE_NUMBER> or 7014
(Feb 2014). Notwithstanding any copyright notice, U.S. Government rights in this work are defined by DFARS
252.227-7013 or DFARS252.227-7014 as detailed above. Use of this work other than as specifically
authorized by the U.S. Government may violate any copyrights that exist in this work.

repository: mit-ll/SimAEN

branch_name: refs/heads/main

repo_name: mit-ll/SimAEN


text:
# EE are giving away a free Nintendo Switch for Black Friday

Published at: **2019-11-07T11:18:05+00:00**

Author: **Neil Bennett, https://www.birminghammail.co.uk/authors/neil-bennett/**

Original: [birminghammail](https://www.birminghammail.co.uk/whats-on/shopping/ee-giving-away-free-nintendo-17215255)

Mobile network operator EE are giving customers to bag a great free gift when they buy selected Hauwei or Samsung handsets.
The EE website listed a wide range of mobile phone deals that come with their very own free Christmas gift in the form of a Toshiba 4KTV or a Nintendo Switch games console.
The deal is available on EE's Pay Monthly Deals. Limited time offers are also available on EE's SIM-Only deals, Upgrade Deals, Pay-As-You-Go Deals and Broadband Deals.
To check out all of EE's current deals, click here and use the tabs at the head of the page.
To view all of these deals in full, click here to be redirected through to the EE website . All of these deals come with unlimited minutes and texts and EU roaming
64GB memory, 10GB data, £31 per month
64GB memory, 10GB data, £20 today, £28 per month
128GB memory, 10GB data, £34 per month
128GB memory, 10GB data, £50 today, £59 per month
128GB memory, 10GB data, £39 per month
Link: shop.ee.co.uk/mobile-phone-deals

license: Unlicense

repository: dsadlollioygjmzvcxv/tdc-exported

repo_name: dsadlollioygjmzvcxv/tdc-exported


text:
# **Responsive Web Design Learning**
***
## 1. Essential of Responsive
## 2. Media queries
## 3. Fuild layout and responsive image

### Flexbox alignment properties
two axis: main axis and cross axis

if flow-direction = row, main axis is horizontal axis, cross axis is vertical axis
if flow-direction = colunm, main axis is vertical axis, cross axis is horizontal axis

### Possible alignment values
- flex-start: begin at the starting edge of its flex container
- flex-end: at the end of the flex container
- center: Puts it in the middle of the flex container
- baseline: Sets all flex items in the container so that their baselines align
- stretch: Makes the items stretch to the size of their flex container (in the cross axis)

### The justify-content property
- Controll in main axis: justify-content and justify-self
- Possible values:
  - flex-start
  - flex-end
  - center
  - space-between
  - space-around

### The flex property
flex: grow shrink basic

### Simple sticky footer
Use flex: 1 to put footer on the bottom of the page

### Changing source order
Use order: <number> and media queries to re-ordering web structure

## Responsive Images
### The intrinsic problem of responsive images
Need to tell browser which images is the most appropriate?

### Simple resolution switching with srcset
srcset provide list of images that browser can choose. Base on resolution of the screen
But how about size of image

### Advanced switching with srcset and sizes
```html
<img srcset="scones-small.jpg 450w, scones-medium.jpg 900w" sizes="(min-width: 17em) 100vw, (min-width: 40em) 50vw" src="scones-small" alt="Scones">
```
- When device has width larger then 17em, image will pretenting to used in 100vw wide, if device has at least 40em wide, then image intend to be shown at 50vw
- On 320px wide device with 2x resolution. => requires image with 320 x 2 = 640px wide.
And browser might decide to use 900w image wide - scones-medium.jpg

### Did you say the browser 'might' pick one image over another?
- *sizes* attributes are merely hints, can not ensure browser will always obey. Relate to ascertain network conditions.
- User can setting their device to only download 1x iamge or only download 2x image.
- Alternative to the browser deciding is use the *picture* element.

### Art direction with the picture element
```html
<picture>
  <source media="(min-width: 30em)" srcset="cake-table.jpg">
  <source media="(min-width: 60em)" srcset="cake-shop.jpg">
  <img src="scones.jpg" alt="One way or another, you WILL get cake.">
</picture>
```
- *picture* is wrapper
- style image by *img* tag
- srcset works exactly the same as previous example
- *img* provide fallback image
- Key different is *source* tag. tell browser which image is need to load.

### Facilitate new-fangled image formats
**WEBP**
```html
<picture>
  <source type="image/webp" srcset="scones-baby-yeah.webp">
  <img src="scones-baby-yeah.jpg" alt="Again, you WILL eat cake.">
</picture>

```

## 4. HTML 5 for Responsive Web Design
### HTML5 markup - understood by all mordern browsers
All modern browsers understand the new sematic elements of HTML 5
Event older version of IE can be served a tiny 'polyfill' to allow it render these new elements

### Starting an HTML 5 page the right way
```html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
  </head>
</html>
```
* DOCTYPE means the type of document to communicate with browser
* html tag and lang attribute: root of document and language for the page
* meta charset define encoding

### Mighty \ tag

- HTML 4.01
```html
<h2><a href="index.html">The home page</a></h2>
<p><a href="index.html"> This paragraph also links to the home page</a></p>
<a href="index.html"><img src="home-page.png" alt="home-slide" /></a>
```
- HTML 5
```html
<a href="index.html">
  <h2>The home page</h2>
  <p>This paragraph also links to the home page</p>
  <img src="home-page.png" alt="home-slide" />
</a>
```

Limitation:
- Can't wrap a tag by another a tag
- can't wrap interactive elements (buttons, ...) by a tag
- Can't wrap a form with a tag

### New sematic elements in HTML 5
#### The \ element
- Contains the main block of content
- Main content area includes that is unique to that document and
excludes content that is repeated across a set of documents: navigation links, copy right information, site logos, banners.

#### The \
 element
- Define a generic section of a document
Ex: one section for contact information, another section for new feeds,...

#### The \ element
- Is used to wrap major navigation links to other pages or parts within the same page.
- Usually markup your navigation elements with an un-ordered list \
 and bunch of \

list.

#### The \
 element
- Easy to confusion with \

- Used to wrap a self-contained piece of information
- Content inside \
 is independent
- Example would be blog posts or new stories.

#### The \ element
- Used for content that is tengentially (tiep tuyen) related to the content around it.
- Used for sidebar, pull quotes, advertising, and group of navigation elements.

#### The \
 and \
 elements
- Used for illutrations, diagrams, photos, code listings, etc
```html
<figure class="MoneyShot">
  <img class="MoneyShotImg" src="img/scones.jpg" alt="Incredible scones" />
  <figcaption class="ImageCaption"> Incredible scones, picture from Wikipedia </figcaption>
</figure>
```

#### The \ and \ elements
- Use to create open and close widget

#### The \ element
- Can be used for masthead area of site's header
- It can also be used as an introduction to other content such as a section within an \
 element


text:
# topology-aware-scheduling deployer

`deployer` is a set of go packages and a command line tool to setup all the components and settings needed to enable
the topology-aware-scheduling on a kubernetes cluster. Additionally, the tool can validate if the cluster configuration
is compatible to the topology-aware-scheduling requirements.

## requirements

* kubernetes >= 1.21
* a valid `kubeconfig`
* **validation only** `kubectl` >= 1.21 in your `PATH`

## how does it work?

### deploy on a kubernetes cluster

Considering a kind cluster configured like this:
```yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:
- |
  kind: KubeletConfiguration
  cpuManagerPolicy: "static"
  topologyManagerPolicy: "single-numa-node"
  reservedSystemCPUs: "0,16"
  featureGates:
    KubeletPodResourcesGetAllocatable: true
nodes:
- role: control-plane
- role: worker
- role: worker
- role: worker
```

Deploy all the topology-aware scheduling components:
```
$ kubectl get nodes
NAME                 STATUS   ROLES                  AGE     VERSION
kind-control-plane   Ready    control-plane,master   3m48s   v1.21.1
kind-worker          Ready    worker                 3m15s   v1.21.1
kind-worker2         Ready    worker                 3m15s   v1.21.1
kind-worker3         Ready    worker                 3m15s   v1.21.1

$ ./deployer deploy -W
2021/07/20 06:16:34 deploying topology-aware-scheduling API...
2021/07/20 06:16:34 -  API> created CustomResourceDefinition "noderesourcetopologies.topology.node.k8s.io"
2021/07/20 06:16:34 ...deployed topology-aware-scheduling API!
2021/07/20 06:16:34 deploying topology-aware-scheduling topology updater...
2021/07/20 06:16:35 -  RTE> created Namespace "tas-topology-updater"
2021/07/20 06:16:35 -  RTE> created ServiceAccount "rte"
2021/07/20 06:16:35 -  RTE> created ClusterRole "rte"
2021/07/20 06:16:35 -  RTE> created ClusterRoleBinding "rte"
2021/07/20 06:16:35 -  RTE> created DaemonSet "resource-topology-exporter-ds"
2021/07/20 06:16:35 wait for all the pods in deployment tas-topology-updater resource-topology-exporter-ds to be running and ready
2021/07/20 06:16:35 no pods found for tas-topology-updater resource-topology-exporter-ds
2021/07/20 06:16:36 pod tas-topology-updater resource-topology-exporter-ds-xb88c not ready yet (Pending)
2021/07/20 06:16:37 all the pods in daemonset tas-topology-updater resource-topology-exporter-ds are running and ready!
2021/07/20 06:16:37 ...deployed topology-aware-scheduling topology updater!
2021/07/20 06:16:37 deploying topology-aware-scheduling scheduler plugin...
2021/07/20 06:16:38 -  SCD> created ServiceAccount "topo-aware-scheduler"
2021/07/20 06:16:38 -  SCD> created ClusterRole "noderesourcetoplogy-handler"
2021/07/20 06:16:38 -  SCD> created ClusterRoleBinding "topo-aware-scheduler-as-kube-scheduler"
2021/07/20 06:16:38 -  SCD> created ClusterRoleBinding "noderesourcetoplogy"
2021/07/20 06:16:38 -  SCD> created ClusterRoleBinding "topo-aware-scheduler-as-volume-scheduler"
2021/07/20 06:16:38 -  SCD> created RoleBinding "topo-aware-scheduler-as-kube-scheduler"
2021/07/20 06:16:38 -  SCD> created ConfigMap "topo-aware-scheduler-config"
2021/07/20 06:16:38 -  SCD> created Deployment "topo-aware-scheduler"
2021/07/20 06:16:38 wait for all the pods in deployment kube-system topo-aware-scheduler to be running and ready
2021/07/20 06:16:38 no pods found for kube-system topo-aware-scheduler
2021/07/20 06:16:48 all the pods in deployment kube-system topo-aware-scheduler are running and ready!
2021/07/20 06:16:48 ...deployed topology-aware-scheduling scheduler plugin!
```

#### cleaning up (removing):

```
$ ./deployer remove -W
2021/07/20 06:18:12 removing topology-aware-scheduling scheduler plugin...
2021/07/20 06:18:13 -  SCD> deleted Deployment "topo-aware-scheduler"
2021/07/20 06:18:13 wait for all the pods in deployment kube-system topo-aware-scheduler to be gone
2021/07/20 06:18:13 error removing: still 1 pods found for kube-system topo-aware-scheduler
2021/07/20 06:18:13 removing topology-aware-scheduling topology updater...
2021/07/20 06:18:13 -  RTE> deleted Namespace "tas-topology-updater"
2021/07/20 06:18:13 wait for the deployment namespace "tas-topology-updater" to be gone
2021/07/20 06:18:40 namespace gone for daemonset "tas-topology-updater"!
2021/07/20 06:18:40 -  RTE> deleted ClusterRoleBinding "rte"
2021/07/20 06:18:40 -  RTE> deleted ClusterRole "rte"
2021/07/20 06:18:40 ...removed topology-aware-scheduling topology updater!
2021/07/20 06:18:40 removing topology-aware-scheduling API...
2021/07/20 06:18:41 -  API> deleted CustomResourceDefinition "noderesourcetopologies.topology.node.k8s.io"
2021/07/20 06:18:41 ...removed topology-aware-scheduling API!
```

### validate the cluster configuration:

A kind cluster with the correct configuration:
```yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:
- |
  kind: KubeletConfiguration
  cpuManagerPolicy: "static"
  topologyManagerPolicy: "single-numa-node"
  reservedSystemCPUs: "0,16"
  featureGates:
    KubeletPodResourcesGetAllocatable: true
nodes:
- role: control-plane
- role: worker
- role: worker
- role: worker
```

Does pass the validation:
```
$ ./deployer validate
PASSED>>: the cluster configuration looks ok!
```

A kind cluster configured like this
```yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:
- |
  kind: KubeletConfiguration
  cpuManagerPolicy: "static"
  reservedSystemCPUs: "0,16"
nodes:
- role: control-plane
- role: worker
- role: worker
- role: worker
```

Does **not** pass the validation:
```
$ ./deployer validate
ERROR#000: Incorrect configuration of node "kind-worker" area "kubelet" component "feature gates" setting "": expected "present" detected "missing data"
ERROR#001: Incorrect configuration of node "kind-worker" area "kubelet" component "topology manager" setting "policy": expected "single-numa-node" detected "none"
ERROR#002: Incorrect configuration of node "kind-worker2" area "kubelet" component "feature gates" setting "": expected "present" detected "missing data"
ERROR#003: Incorrect configuration of node "kind-worker2" area "kubelet" component "topology manager" setting "policy": expected "single-numa-node" detected "none"
ERROR#004: Incorrect configuration of node "kind-worker3" area "kubelet" component "feature gates" setting "": expected "present" detected "missing data"
ERROR#005: Incorrect configuration of node "kind-worker3" area "kubelet" component "topology manager" setting "policy": expected "single-numa-node" detected "none"
```

## license
(C) 2021 Red Hat Inc and licensed under the Apache License v2

## build
just run
```bash
make
```

## releases

You can download pre-built binaries for Linux from the `releases` section.
No container images are available nor planned.

repository: Tal-or/deployer

repo_name: Tal-or/deployer


text:
Booleans in Haxe are represented by the `Bool` type, whose values can be either `true` or `false`.

Haxe supports three [boolean operators][operators]: `!` (unary NOT), `&&` (binary AND), and `||` (binary OR)

Compound boolean expressions (`&&` and `||`) use _short-circuit_ evaluation, where expressions are evaluated from left to right but only as far as necessary. This is significant in cases such as the following:

```haxe
object != null && object.field == x
```

The first boolean check ensures that `object.field` is only accessed if `object` is not `null`, guarding against a runtime error.

The three boolean operators have different [precedence][precedence] and are evaluated in this order: `!` -> `&&` -> `||`.

Enclosing expressions in parantheses `()` allows overriding these precedence rules, as the parantheses have a higher precedence.

```haxe
!true && false   // => false
!(true && false) // => true
```

[operators]: https://haxe.org/manual/expression-operators-binops.html
[precedence]: https://haxe.org/manual/expression-operators-precedence.html

repository: SaschaMann/haxe

repo_name: SaschaMann/haxe


text:
# CompareEcoli
Steven Song
Tufts University
COMP 150 Computational Systems Biology
Spring 2019

### Purpose
Can we use genome-scale models for *E. coli*, obtained from [BiGG Database](https://github.com/sbrg/bigg_models), and flux based analysis to predict strain efficiency at given tasks?

### Usage
Prerequisites:
- Python 3
- Matlab 2019a
- [COBRA Toolbox](https://github.com/opencobra/cobratoolbox)

Steps to Run:
1. Initialize COBRA Toolbox
2. Run evalDNAProteinSynthesis.m

### Results
Results can be found in the Excel document named "results".

repository: StevenSong/CompareEcoli

repo_name: StevenSong/CompareEcoli


text:
# dissonance
dissonance is a clone of Discord, a website and a desktop application that has live text and voice chat.
The clone focuses on the text chat portion of the website.

[Link to site](https://dissonance-app.herokuapp.com/)

## Key Features
- Users, you can sign up or demo the site. Joined server and messaages will be saved and linked to your account.
- List of servers a user can freely join and leave, as well as the ability to create their own.
- Seperate channels to keep discussion of topics seperate.
- Live chat! Chat messages will instantly appear on screen without needing a refresh for everyone in the channel.

## Technology stack
The technologies used were
- postgreSQL for database
- ruby on rails for the backend MVC framework
- React.js for the frontend library.
- Redux for frontend state management

Deep delve
 ***
Live chat is a tricky problem, when messages appear on your screen it's hard to keep track of chat if all we have is just the body of the message. So we need to additionally present not just the message but also other helpful information like who sent it and when it was sent.
To solve this I conditionally have react dispatch a thunk action creator if the user that sent the message is not in the redux store already, when the response comes back we now have new information about the user that sent the message and we can now keep track of who sent what message.

```
App.chatRoom = App.cable.subscriptions.create(
  { channel: 'ChatChannel' },
  {
    received: (data) => {
      const { message: { authorId }, message } = data;

      receiveMessage(message);

      if (!users[authorId]) {
        fetchUser(authorId);
      }
    },
```


text:
# [Numbers with d occurrences of digit d](https://www.codewars.com/kata/numbers-with-d-occurences-of-digit-d "https://www.codewars.com/kata/5a40fc7ce1ce0e34440000a3")

In this kata, we want to discover a small property of numbers.
We say that a number is a **dd** number if it contains d occurrences of a digit d, (d is in [1,9]).

## Examples

* 664444309 is a **dd** number, as it contains 4 occurrences of the number 4
* 30313, 122 are **dd** numbers as they respectively contain 3 occurrences of the number 3, and (1 occurrence of the number 1 AND 2 occurrences of the number 2)
* 123109, 0, 56542 are not **dd** numbers

## Task

Your task is to implement a function called `is_dd` (`isDd` in javascript) that takes a **positive** number (type depends on the language) and returns a boolean corresponding to whether the number is a **dd** number or not.

repository: ParanoidUser/codewars-handbook

repo_name: ParanoidUser/codewars-handbook


text:
# AngularJS tells a compelling story With just a few simple Angular tricks, I could write the whole rendering system in almost no lines of javascript. Here’s how I did it. To create the board, it was as simple as a nested ngRepeat.

function setupBoard() {
  $scope.board = [];
  for (var i = 0; i < BOARD_SIZE; i++) {
    $scope.board[i] = [];
    for (var j = 0; j < BOARD_SIZE; j++) {
      $scope.board[i][j] = false;
    }
  }
}

## Notice that we set each board position to false. That is simply, for performance reasons, to specify whether or not the snake is currently inhabiting that location.

Now we have an n x n board for our snake to roam. If you look back at the HTML, you will see that there is a setStyling function being set in our ng-style tag. This is our rendering engine for the game…pretty intense. All it does is compares the position with the board, fruit, and snake, and determines what color to show at that position.

$scope.setStyling = function(col, row) {
  if (isGameOver) {
    return COLORS.GAME_OVER;
  } else if (fruit.x == row && fruit.y == col) {
    return COLORS.FRUIT;
  } else if (snake.parts[0].x == row && snake.parts[0].y == col) {
    return COLORS.SNAKE_HEAD;
  } else if ($scope.board[col][row] === true) {
    return COLORS.SNAKE_BODY;
  }
  return COLORS.BOARD;
};

## The last piece of the puzzle is to add an ‘update’ method to update our board, snake, and fruit. For this I utilized the $timeout method rather than $interval, to allow for dynamic speed (every 5 fruits eaten speeds up the interval).I simply add a new piece to the front, and pop off the current tail. The $timeout completion fires of a digest which will call the setStyling for each column/row.

function update() {
  var newHead = getNewHead();
  if (boardCollision(newHead) || selfCollision(newHead)) {
    return gameOver();
  } else if (fruitCollision(newHead)) {
    eatFruit();
  }
  // Remove tail
  var oldTail = snake.parts.pop();
  $scope.board[oldTail.y][oldTail.x] = false;
  // Add new front part
  snake.parts.unshift(newHead);
  $scope.board[newHead.y][newHead.x] = true;
  // Do it again
  snake.direction = tempDirection;
  $timeout(update, interval);
}
## Because of the way we use ng-style, AngularJS handles all the magic of rendering our columns and rows, and changing the styles accordingly. All we do is manage state.

##### I thought it was a great little project to practice important Angular principles while exploring alternative uses for the framework. Hope you all enjoy.


text:
# HddNagger
A small windows service which prevents your "sleepy" hard driver from sleeping.

## How does it work?
It is a simple windows service. You install the executable as a service and in the service's properties you set the (preferably) root folder where the service can create and immediately delete a temporary file with a random file name.

Example for the argument:

D:\

## Why would I need this?
  * Just an example code
    It is a short example how a windows service can be done, although in this project the code quality isn't the best.

  * To solve an issue
    It was just an interesting experiment for myself and also a solution to a problem which was bugging me for a while and couldn't find an easy solution. The problem was that I have replaced my DVD drive in my laptop and put a HDD in the place of it. Unfortunately for some reasons the laptop was handling the HDD as a DVD drive so if there were no read/write actions then it has put it to sleep. If I was playing and the game wanted to load a cutscene it took several seconds while the HDD started spinning. That is solved by this windows service because it writes a temporary file on it in every second and then deletes it.

## License
MIT license included.

repository: poseen/HddNagger

repo_name: poseen/HddNagger


text:
# Ferret Website

Built with Hugo

## Prerequisites
- [Go](https://golang.org/doc/install)
- [Hugo](https://gohugo.io/getting-started/installing/)
- [Node.js](https://nodejs.org/en/download/)
- [Mage](https://magefile.org) for building the website.
- [frep](https://github.com/subchen/frep/releases)(optional) is the tool used for templating the documentation

## Getting Started
### Installing dependencies
```bash
go mod tidy && mage install
```

### Dev server
```bash
mage serve
```

### Generating API docs
Generating `stdlib` documentation requires doc rep YAML.

```bash
mage generate
```

### Publishing
```bash
mage publish
```

branch_name: refs/heads/dev

gha_language: HTML


text:
---
identifier: MIR:00000548
name: ExAC Gene
description: The Exome Aggregation Consortium (ExAC) is a coalition of investigators seeking to aggregate and harmonize exome sequencing data from a variety of large-scale sequencing projects, and to make summary data available for the wider scientific community. The data pertains to unrelated individuals sequenced as part of various disease-specific and population genetic studies and serves as a reference set of allele frequencies for severe disease studies. This collection references gene information.
prefix: exac.gene
pattern: ^ENSG\d{11}$
prefixed: 0
local_id: ENSG00000169174
resources:
 - identifier: MIR:00100725
   accessurl: http://exac.broadinstitute.org/gene/${lid}
   keyword: proprotein convertase
   description: ExAC Gene at Exome Aggregation Consortium
   homepage: http://exac.broadinstitute.org/
   institution: Exome Aggregation Consortium (ExAC), Cambridge, Massachusetts
   location: USA
   official: false
---

repository: cmungall/registry

repo_name: cmungall/registry


text:
Note! The batch running of specifications in continuous integration scenarios is significantly different in Storyteller 3 as a direct result of poor experiences with earlier versions. Besides some internal performance optimization, Storyteller 3 tries to be much more aggressive in failing fast in continuous integration to prevent runaway builds and provide faster feedback for teams that depend on Storyteller for regression testing.

## Storyteller 5

In Storyteller 5, you can run all the specifications with the project console application itself, so from the
root directory of the project at the command line, it's just:

```
dotnet run
```

To only run one suite at a time, try:

```
dotnet run -- run "suite path"
```

## Storyteller 4

Storyteller specifications can be executed from the command line tool with the `dotnet storyteller run` command. You may either run all the specifications (for smaller projects or faster systems), or run one suite of specifications at a time.

## Storyteller 3

Storyteller specifications can be executed from the command line tool with the `st run` command. You may either run all the specifications (for smaller projects or faster systems), or run one suite of specifications at a time.

## Fast Build, Slow Build

In usage over the years, I will run the Storyteller specifications as part of the normal automated build for a codebase **if they _feel_ fast enough**. Since Storyteller is going to be more frequently used for integration testing, the Storyteller specifications can easily become slower or intolerably long running for the kind of quick feedback you want in your normal automated build. In this common case, the Storyteller team recommends a _cascading build_ where your normal build runs first with your "fast" tests, then on success triggers a secondary build to run the Storyteller specifications.

The reasoning is to create more effective and quicker feedback cycles. A team using a cascading build may follow a policy of waiting on the fast build before continuing any work after a push to source control, but only deal with the slower, cascading build when and if it fails.

## Critical and Catastropic Exceptions

Storyteller 3 introduces two new exceptions that you can choose to throw yourself:

1. `StorytellerCriticalException` -- tells Storyteller that the current specification cannot possibly succeed and causes Storyteller to stop executing the specification wherever it's at. Internally, Storyteller treats any failure in `Fixture.SetUp()` or `Fixture.TearDown()` as a critical exception. A classic example is using Storyteller to test a web application where a section of a specification starts by trying to open the application to a certain Url. If the web server returns an error on the request, Storyteller should not bother to try to find the expected elements on the screen. It should fail quickly with a clear indication that it was unable to load the web page.
1. `StorytellerCatastropicException` -- tells Storyteller that the current system under test is in an invalid state and to stop trying to execute anything else. You can throw this exception yourself if you detect something like an unavailable database connection that makes the system unusable. Internally, Storyteller throws this exception if the `ISystem` fails to start or if it cannot create an `IExecutionContext`.

See <[linkto:documentation/engine/system_under_test]> for more information.

## Retries

I hate to tell you this, but it is somewhat likely that your Storyteller specifications are going to fail sometimes in your continuous integration runs. It's also somewhat likely that you may hit specifications that are consistently reliable -- especially when you are testing against any kind of system that involves a lot of asynchronous operations like just about any modern web application. To this end, the original Storyteller team adopted the idea of "retries," where a specification that fails can be retried a configured number of times (we got this idea from jQuery as I recall).

This "retry" capability has produced very mixed results in real usage. In the early days of [Selenium](http://www.seleniumhq.org) when the browser automation was so unreliable, the retry capability made our automated testing much more useful. Today, the retry capability is still valuable when we use Storyteller against asynchronous messaging systems. That being said, the retry capability in older versions of Storyteller has also been detrimental when it too aggressively tries to retry specifications that have no chance of ever succeeding or when the system under test itself is in an invalid state -- often hitting the timeout for each specification on each retry.

To that end, Storyteller 3 changes the retry policy a bit to [fail faster](http://en.wikipedia.org/wiki/Fail-fast):
* The retry count **as of now** is specified per specification with the default being no retries unless this is overridden by the `st run --retries [#]` or `st open --retries [#]` flags. This [may change later](https://github.com/DarthFubuMVC/StoryTeller2/issues/151) based on our shop's experience with Storyteller 3. For now, however, the attitude we are taking is that retries are a potentially harmful property that must be explicitly enabled.
* Specifications marked as _Acceptance_ will never be retried.
* If in the course of executing a Specification the Storyteller engine hits a "critical" or "catastropic" exception, the specification will no longer be retried even if it has not exceeded its maxiumum number of retries. A "critical" exception is any failure from a `Fixture.SetUp()`, `Fixture.TearDown()`, or the `StorytellerCriticalException` being thrown by grammars.
* If the system under test itself fails to start or cannot create an execution context, the entire batch of specifications is aborted, but the results are still shown.

See <[linkto:documentation/using/instrumentation]> for more information on adding and using instrumentation against your Storyteller specifications.

## Lifecycle

Storyteller has always treated _Acceptance_ and _Regression_ specifications somewhat differently in the command line execution. _Acceptance_ specifications are executed strictly for informational purposes, are never retried in the case of failures, and do not count toward the success or failure of the execution run. _Regression_ specifications on the other hand can be retried and any number of _Regression_ failures will cause the `st run` command to return a non-zero return code denoting a failure.

See <[linkto:documentation/using/lifecycle]> for more information.

## Results

The specification execution results are written to a single html file with **no other file dependencies**. In continuous integration scenarios, you would want to have this file written to a place where your CI server will save this file as an artifact tagged to the build. For example, my teams write the Storyteller results to an `/artifacts` folder and configure our TeamCity build server to automatically store any file written to that directory as build artifacts. Most CI servers today will allow you to expose this html file from the build server website to browse the results.

The results page is a single page application with a tabular summary view of all the specifications executed, how long each took to execute, the high level result counts, and the number of retries. From the summary, you can drill into individual specifications by clicking on the specification name.

## AppVeyor Integration

Note! This was added in Storyteller 4.2

For better AppVeyor results, use the `dotnet storyteller run --appveyor` flag to direct Storyteller to output the Console logging
that AppVeyor expects.

## Command Usage

<[command-usage:st/run]>
The `st run` command allows you to run specifications from an optimized batch mode from the command line. This command will also optionally dump out a couple additional  reports about the specifications that executed that may be useful for custom reporting or performance optimization. The CSV option is a dump of the performance tracing across all the specifications. The JSON dump is a raw dump of the Storyteller runtime model for the specifications.
<[/command-usage:st/run]>

repository: lhaussknecht/Storyteller

gha_license_id: NOASSERTION

repo_name: lhaussknecht/Storyteller


text:
# 02.Separate

> Example of VueJS project with multiple files.

*Please note that I committed the `dist` folder which is not a normal thing to do.  I did it simply to allow github pages to serve up the example web page.*

## To recreate this project

``` bash
# install vue-cli
npm i -g vue-cli

# generate out the webpack template
vue init webpack my-project-name
```

## Build Setup

``` bash
# install dependencies
npm install

# serve with hot reload at localhost:8080
npm run dev

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build --report
```

For a detailed explanation on how things work, check out the [guide](http://vuejs-templates.github.io/webpack/) and [docs for vue-loader](http://vuejs.github.io/vue-loader).

---

## Add Vuex to the project

```
yarn add vuex
```

### main.js

```
import Vuex from 'vuex'

Vue.use(Vuex)
```

Create a store:

```
const store = new Vuex.Store({
	state: { your: 'state' },
	mutations: { mymutator: (state, value) => { state.your = value },
	actions: { myaction: (context, value) => { context.commit('mymutator', value)
	})
```

Add store to Vue application:

```
new Vue({
  el: '#app',
  template: '<App/>',
  components: { App },
  store
})
```

repository: Atlanta-VueJS/getting-started

repo_name: Atlanta-VueJS/getting-started


text:
# Contribution Guidelines

Contributions are welcome.

Ensure your pull request adheres to the following guidelines:

- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make sure your contribution is useful before submitting.
- Make an individual pull request for each suggestion.
- Use the following format: `[title](link) - Description.`
- Additions should be added to the end of the relevant category.
- New categories, or improvements to the existing categorization are welcome.
- Keep descriptions short and simple, but descriptive.
- Start the description with a capital and end with a full stop/period.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
- The pull request should have a useful title and include a link to the package and why it should be included.
- We use badges:
  - ![Code quality: Golden](https://img.shields.io/badge/code%20quality-golden-yellow.svg)  for popular and battle tested packages ```![Code quality: golden](https://img.shields.io/badge/code%20quality-golden-yellow.svg) ```
  - ![Not maintained](https://img.shields.io/badge/maintained%3F-no-red.svg) for packages that are no longer actively maintained ```![Not maintained](https://img.shields.io/badge/Maintained%3F-no-red.svg)```
  - ![Speed: Blazing](https://img.shields.io/badge/speed-blazing%20%F0%9F%94%A5-brightgreen.svg) for packages with exceptional performance ```![Speed: Blazing](https://img.shields.io/badge/speed-blazing%20%F0%9F%94%A5-brightgreen.svg)```
  - ![Size: Tiny](https://img.shields.io/badge/size-tiny-blue.svg) for packages that have a tiny footprint ```![Size: Tiny](https://img.shields.io/badge/size-tiny-blue.svg)```
  - Packages that no longer work or should not be recommended for whatever reasons will be removed. They have no badge. Please indicate the reasons for removal in the pull request.
  - Feel like we need _more badges_? Make a pull request!

Thank you for your help!


text:
---
layout: 	project_page
title:  	"Axiome"
date:   	2017-06-01 23:30:00 +0100
category: 	school-project
thumb:		/assets/axiome.png

#page_link:  http://taraquinsac.fr/gallery/axiome/

excerpt: |
  Family interactive story that you discover through an AR device. Student project @ENJMIN.

type: "Interactive experience"
platforms: "Windows / Android"
inputs: "Smartphone"
tools: "Unity / Vuforia / Wwise"

abstract: |
  Axiome is a **site-specific experience** in which the player use augmented reality to learn more about a seemingly peaceful family. In an room specifically furnished for the installation, see things as they are, behind apparences.

banner: {"type": "video", "src": "https://player.vimeo.com/video/229407210"}

team:
  - {"name": "Tara Quinsac", "role": "Artist"}
  - {"name": "Clémentine Soulard--Pignon", "role": "Game designer"}
  - {"name": "Tristan Pradens", "role": "Sound designer"}
  - {"name": "Guillaume Voisinet", "role": "Producer"}
  - {"name": "Clément Rondeau", "role": "Developer"}

tasks:
  - Vuforia integration
  - Wwise integration
  - Server application
  - Smartphone application
  - Arduino + RaspberryPI homemade radio
---
 Axiome is our end of first year project at the CNAM-ENJMIN school. For this project we had the possibility to create a game that isn't a video game, and we took this opportunity to create something on which we hadn't worked on before : **a site-specific experience**.

 The goal was to put a player in a familiar environment, like a grandma's living room, and tell him : "You have 10 minutes to discover this place", we also wanted to add the idea that **behind a photo there is a story**. It can be the place where the photo has been taken, the comment of the photograp, or a detail that can be hidden at first sight.

 To add this effect to the experience we added an AR application that recognize pictures drawn by our artist and replace them by an animated version. With that we were able to tell a story through 3 photo albums, and framed pictures.

 My work on this project was to learn how to do AR with Unity, I choosed **Vuforia** because their documentation is complete and there is a good community around Vuforia/Unity projects.

 I've quickly prototyped an application that was able to **recoginize the first pictures done** by Tara, to be sure that the art direction was accepted by Vuforia. After that I've worked on tools to help the integration because there was a lot of pictures and animations.

 In the middle of the project I've worked on something very different, when we started the project we've found an old radio that wasn't working but it had been used for an old project and some wires were still here. It was perfect inside our room because it matched the time period we were targeting, and we also find the idea to create our own radio program very cool.

 So I've worked with an **Arduino** to get inputs from the two main buttons (volume and frequency), the volume button was totally unusable so I've glued a magnet to it and placed a hall effect sensor to get the position of the magnet. Unfortunately the only sensor that I've wasn't powerfull enough, so it was only usable as an on/off button.

 The frequency button was usable and wires were already here, I only had to check the values that it was giving to get the position of the button and the targeted frequency. I've placed a range of frequencies were we hear the radio program, and on all the other frequencies we hear a white noise.

 To play the sound I've used a **RaspberryPI** that was running a Raspbian on which a pygame program was launched at startup. This program was only reading inputs of the Arduino (it was used as an analog numeric converter in the end) and triggering sounds following the inputs.

To end the project I've worked on the server application that was monitoring the experience and was connected to the television where the player could see their progress, and the speakers that were playing house ambiant sounds to immerse the player and small feedback sounds when they were discovering new characters.

To help the installation I've also added an auto-connect system to the smartphone, because we knew that during the 2 days of presentation we were going to change the smartphone at least twice a day to charge it.

We are really proud of the project because a lot of players were **embodying their role** and some of them were also embarassed to search inside a room that wasn't their. We encountered only one error on a smartphone swap but during the 2 days the application has worked seamlessly.


text:
# ACETelPrompt

`ACETelPrompt` is an helper to easily make phone call using the telprompt scheme.

Using telprompt first gives a prompt asking whether the user wants to make the call or cancel it. If the user selects the call option from the prompt that is displayed, the call is placed and the control returns back to the app after the call is finished.

The helper uses blocks to get the user choice also logging the phone duration.

## Example Usage

```objective-c
    [ACETelPrompt callPhoneNumber:self.phoneField.text
                             call:^(NSTimeInterval duration) {
                                 NSLog(@"User made a call of %.1f seconds", duration);

                             } cancel:^{
                                 NSLog(@"User cancelled the call");
                             }];
```

## Cocoapods

1. Add `pod 'ACETelPrompt'` to your Podfile.
2. Run `pod install`

## License

ACETelPrompt is available under the MIT license. See the LICENSE file for more info.


text:
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.6.0] - 2020-10-29

### ADDED

- JavaScript `Image />` snippets (@ScottAgirs)

## [1.5.0] - 2020-10-21

### ADDED

- TypeScript support (@Nnadozie)

## [1.4.1] - 2020-06-26

### UPDATE

- readme file with expanded snippets

## [1.4.0] - 2020-06-26

### ADDED

- `gsp→` | Next.js getStaticProps() export
- `gspaths→` | Next.js getStaticProps() export
- `gssp→` | Next.js getServerSideProps() export

## [1.3.0] - 2020-05-12

### ADDED

- `fce→` | Functional Component as named export
- `fcde→` | Functional Component with default export

### Changed

- `fc→` // now does NOT export itself, use `fce→` instead

## [1.2.1] - 2020-05-01

### Changed

- Change snippet display name

## [1.1.5] - 2020-05-01

### Fixed

- Logo url

## [1.1.4] - 2020-05-01

### Fixed

- Next.js spelling

## [1.1.3] - 2020-05-01

### Changed

- Updated logos + README

## [1.1.2] - 2020-05-01

### Changed

- Cleaned up `fc` and `fcst`

## [1.1.1] - 2020-05-01

### Added

- New logo

### Changed

- Updated README

## [1.1.0] - 2019-12-25

### Added

- Support for React, Typescript, Typescript React

## [1.0.0] - 2019 June 10th

- Initial React Snippets by Scott Agirs Release

repository: ijsto/reactnextjssnippets

repo_name: ijsto/reactnextjssnippets


text:
# Mac mamo file parser

Parse Mac Memo.app data.
But this script support under Yosemite.
I don't try later from Yosemite.

## Version

* python2.7

## Usage

You can run script after you download Note file and put it on macmemo directory.
(Maybe file name is `Note.mbox`)

```bash
cd macmemo
python2.7 macmemo Note.mbox
```

This script export separated file in macMemo directory.

## Licence

MIT

repository: pyohei/macmemo-parser

repo_name: pyohei/macmemo-parser


text:
# Deploy Tanzu Kubernetes Clusters

After you have deployed a management cluster to vSphere, Amazon EC2, or Azure, or you have connected the Tanzu CLI to a vSphere with Tanzu Supervisor Cluster, you can use the Tanzu CLI to deploy Tanzu Kubernetes clusters.

To deploy a Tanzu Kubernetes cluster, you create a configuration file that specifies the different options with which to deploy the cluster. You then run the `tanzu cluster create` command, specifying the configuration file in the `--file` option.

This topic describes the most basic configuration options for Tanzu Kubernetes clusters.

## Prerequisites for Cluster Deployment {#prereqs}

* You have followed the procedures in [Install the Tanzu CLI and Other Tools](../install-cli.md) and [Deploying Management Clusters](../mgmt-clusters/deploy-management-clusters.md) to deploy a management cluster to vSphere, Amazon EC2, or Azure.
* You have already upgraded the management cluster to the version that corresponds with the Tanzu CLI version. If you attempt to deploy a Tanzu Kubernetes cluster with an updated CLI without upgrading the management cluster first, the Tanzu CLI returns the error `Error: validation failed: version mismatch between management cluster and cli version. Please upgrade your management cluster to the latest to continue.` For instructions on how to upgrade management clusters, see [Upgrade Management Clusters](../upgrade-tkg/management-cluster.md).
* Alternatively, you have a vSphere 7 instance on which a vSphere with Tanzu Supervisor Cluster is running. To deploy clusters to a vSphere 7 instance on which the vSphere with Tanzu feature is enabled, you must connect the Tanzu CLI to the vSphere with Tanzu Supervisor Cluster. For information about how to do this, see [Use the Tanzu CLI with a vSphere with Tanzu Supervisor Cluster](connect-vsphere7.md).
* **vSphere**: If you are deploying Tanzu Kubernetes clusters to vSphere, each cluster requires one static virtual IP address to provide a stable endpoint for Kubernetes. Make sure that this IP address is not in the DHCP range, but is in the same subnet as the DHCP range.
* **Azure**: If you are deploying Tanzu Kubernetes clusters to Azure, each cluster requires a Network Security Group (NSG) for its worker nodes named `CLUSTER-NAME-node-nsg`, where `CLUSTER-NAME` is the name of the cluster. For more information, see [Network Security Groups on Azure](../mgmt-clusters/azure.md#nsgs).
* Configure Tanzu Kubernetes cluster node size depending on cluster complexity and expected demand.
For more information, see [Minimum VM Sizes for Cluster Nodes](../mgmt-clusters/vsphere.md#vsphere-vm-sizes).

## Create a Tanzu Kubernetes Cluster Configuration File {#config}

When you deploy a Tanzu Kubernetes cluster, most of the configuration for the cluster is the same as the configuration of the management cluster that you use to deploy it. Because most of the configuration is the same, the easiest way to obtain an initial configuration file for a Tanzu Kubernetes cluster is to make a copy of the management cluster configuration file and to update it.

1. Locate the YAML configuration file for the management cluster.

   * If you deployed the management cluster from the installer interface and you did not specify the `--file` option when you ran `tanzu management-cluster create --ui`, the configuration file is saved in `~/.config/tanzu/tkg/clusterconfigs/`. The file has a randomly generated name, for example, `bm8xk9bv1v.yaml`.
   * If you deployed the management cluster from the installer interface and you did specify the `--file` option, the management cluster configuration is taken from in the file that you specified.
   * If you deployed the management cluster from the Tanzu CLI without using the installer interface, the management cluster configuration is taken from either a file that you specified in the `--file` option, or from the default location, `~/.config/tanzu/tkg/cluster-config.yaml`.

1. Make a copy of the management cluster configuration file and save it with a new name.

   For example, save the file as `my-aws-tkc.yaml`, `my-azure-tkc.yaml` or `my-vsphere-tkc.yaml`.

**IMPORTANT**: The recommended practice is to use a dedicated configuration file for every Tanzu Kubernetes cluster that you deploy.

## Deploy a Tanzu Kubernetes Cluster with Minimum Configuration {#deploy}

The simplest way to deploy a Tanzu Kubernetes cluster is to specify a configuration that is identical to that of the management cluster. In this case, you only need to specify a name for the cluster. If you are deploying the cluster to vSphere, you must also specify an IP address or FQDN for the Kubernetes API endpoint.

**Note**: To configure a workload cluster to use an OS other than the default Ubuntu v20.0.4, you must set the `OS_NAME` and `OS_VERSION` values in the cluster configuration file.
The installer interface does not include node VM OS values in the management cluster configuration files that it saves to `~/.config/tanzu/tkg/clusterconfigs`.

1. Open the new YAML cluster configuration file in a text editor.
1. Optionally set a name for the cluster in the `CLUSTER_NAME` variable.

   For example, if you are deploying the cluster to vSphere, set the name to `my-vsphere-tkc`.

   ```yaml
   CLUSTER_NAME: my-vsphere-tkc
   ```

   If you do not specify a `CLUSTER_NAME` value in the cluster configuration file or as an environment variable,
   you must pass it as the first argument to the `tanzu cluster create` command.
   The `CLUSTER_NAME` value passed to `tanzu cluster create` overrides the name you set in the configuration file.

   Workload cluster names must be must be 42 characters or less, and must comply with DNS hostname requirements as amended in [RFC 1123](https://tools.ietf.org/html/rfc1123).

1. If you are deploying the cluster to vSphere, specify a static virtual IP address or FQDN in the `VSPHERE_CONTROL_PLANE_ENDPOINT` variable.

   No two clusters, including any management cluster and workload cluster, can have the same `VSPHERE_CONTROL_PLANE_ENDPOINT` address.

   * Ensure that this IP address is not in the DHCP range, but is in the same subnet as the DHCP range.
   * If you mapped a fully qualified domain name (FQDN) to the VIP address, you can specify the FQDN instead of the VIP address.

   ```yaml
   VSPHERE_CONTROL_PLANE_ENDPOINT: <IP_ADDRESS>
   ```

1. Save the configuration file.
1. Run the `tanzu cluster create` command, specifying the path to the configuration file in the `--file` option.

   If you saved the Tanzu Kubernetes cluster configuration file `my-vsphere-tkc.yaml` in the default `clusterconfigs` folder, run the following command to create a cluster with a name that you specified in the configuration file:

   ```sh
   tanzu cluster create --file .tanzu/tkg/clusterconfigs/my-vsphere-tkc.yaml
   ```

   If you did not specify a name in the configuration file, or to create a cluster with a different name to the one that you specified, specify the cluster name in the `tanzu cluster create` command. For example, to create a cluster named `another-vsphere-tkc` from the configuration file `my-vsphere-tkc.yaml`, run the following command:

   ```sh
   tanzu cluster create another-vsphere-tkc --file .tanzu/tkg/clusterconfigs/my-vsphere-tkc.yaml
   ```

   Any name that you specify in the `tanzu cluster create` command will override the name you set in the configuration file.

1. To see information about the cluster, run the `tanzu cluster get` command, specifying the cluster name.

   ```sh
   tanzu cluster get my-vsphere-tkc
   ```

   The output lists information about the status of the control plane and worker nodes, the Kubernetes version that the cluster is running, and the names of the nodes.

    ```sh
    NAME             NAMESPACE  STATUS   CONTROLPLANE  WORKERS  KUBERNETES        ROLES
    my-vsphere-tkc   default    running  1/1           1/1      v1.20.5+vmware.1  <none>

    Details:

    NAME                                                                READY  SEVERITY  REASON  SINCE  MESSAGE
    /my-vsphere-tkc                                                    True                     17m
    ├─ClusterInfrastructure - VSphereCluster/my-vsphere-tkc            True                     19m
    ├─ControlPlane - KubeadmControlPlane/my-vsphere-tkc-control-plane  True                     17m
    │ └─Machine/my-vsphere-tkc-control-plane-ss9rt                     True                     17m
    └─Workers
      └─MachineDeployment/my-vsphere-tkc-md-0
        └─Machine/my-vsphere-tkc-md-0-657958d58-mgtpp                  True                     8m33s

    ```

The cluster runs the default version of Kubernetes for this Tanzu Kubernetes Grid release, which in Tanzu Kubernetes Grid v1.3.0 is v1.20.1.

## Deploy a Cluster with Different Numbers of Control Plane and Worker Nodes {#deploy-counts}

In the preceding example, because you did not change any of the node settings in the Tanzu Kubernetes cluster configuration file, the resulting Tanzu Kubernetes cluster has the same numbers of control plane and worker nodes as the management cluster. The nodes have the same CPU, memory, and disk configuration as the management cluster nodes.

* If you selected **Development** in the **Management Cluster Settings** section of the installer interface, or specified `CLUSTER_PLAN: dev` and the default numbers of nodes in the management cluster configuration, the Tanzu Kubernetes cluster consists of the following VMs or instances:

  * vSphere:
    * One control plane node, with a name similar to `my-dev-cluster-control-plane-nj4z6`.
    * One worker node, with a name similar to `my-dev-cluster-md-0-6ff9f5cffb-jhcrh`.
  * Amazon EC2:
    * One control plane node, with a name similar to `my-dev-cluster-control-plane-d78t5`.
    * One EC2 bastion node, with the name  `my-dev-cluster-bastion`.
    * One worker node, with a name similar to `my-dev-cluster-md-0-2vsr4`.
  * Azure:
    * One control plane node, with a name similar to `my-dev-cluster-20200902052434-control-plane-4d4p4`.
    * One worker node, with a name similar to `my-dev-cluster-20200827115645-md-0-rjdbr`.
* If you selected **Production** in the **Management Cluster Settings** section of the installer interface, or specified `CLUSTER_PLAN: prod` and the default numbers of nodes in the management cluster configuration file, Tanzu CLI deploys a cluster with three control plane nodes and automatically implements stacked control plane HA for the cluster. The Tanzu Kubernetes cluster consists of the following VMs or instances:

  * vSphere
    * Three control plane nodes, with names similar to `my-prod-cluster-control-plane-nj4z6`.
    * Three worker nodes, with names similar to `my-prod-cluster-md-0-6ff9f5cffb-jhcrh`.
  * Amazon EC2:
    * Three control plane nodes, with names similar to `my-prod-cluster-control-plane-d78t5`.
    * One EC2 bastion node, with the name  `my-prod-cluster-bastion`.
    * Three worker nodes, with names similar to `my-prod-cluster-md-0-2vsr4`.
  * Azure:
    * Three control plane nodes, with names similar to `my-prod-cluster-20200902052434-control-plane-4d4p4`.
    * Three worker nodes, with names similar to `my-prod-cluster-20200827115645-md-0-rjdbr`.

If you copied the cluster configuration from the management cluster, you can update the `CLUSTER_PLAN` variable in the configuration to deploy a Tanzu Kubernetes cluster that uses the `prod` plan, even if the management cluster was deployed with the `dev` plan, and the reverse.

```yaml
CLUSTER_PLAN: prod
```

To deploy a Tanzu Kubernetes cluster with more control plane nodes than the `dev` and `prod` plans define by default, specify the `CONTROL_PLANE_MACHINE_COUNT` variable in the cluster configuration file. The number of control plane nodes that you specify in `CONTROL_PLANE_MACHINE_COUNT` must be uneven.

```yaml
CONTROL_PLANE_MACHINE_COUNT: 5
```

Specify the number of worker nodes for the cluster in the `WORKER_MACHINE_COUNT` variable.

```yaml
WORKER_MACHINE_COUNT: 10
```

How you configure the size and resource configurations of the nodes depends on whether you are deploying clusters to vSphere, Amazon EC2, or Azure. For information about how to configure the nodes, see the appropriate topic for each provider:

* [Deploy Tanzu Kubernetes Clusters to vSphere](vsphere.md)
* [Deploy Tanzu Kubernetes Clusters to Amazon EC2](aws.md)
* [Deploy Tanzu Kubernetes Clusters to Azure](azure.md).

## Configure Common Settings {#common-config}

You configure proxies, Machine Health Check, private registries, and Antrea  on Tanzu Kubernetes Clusters in the same way as you do for management clusters. For information, see [Create a Management Cluster Configuration File from a Template](../mgmt-clusters/create-config-file.md).

## Deploy a Cluster in a Specific Namespace {#namespace}

If you have created namespaces in your Tanzu Kubernetes Grid instance, you can deploy Tanzu Kubernetes clusters to those namespaces by specifying the `NAMESPACE` variable. If you do not specify the the `NAMESPACE` variable, Tanzu Kubernetes Grid places clusters in the `default` namespace. Any namespace that you identify in the `NAMESPACE` variable must exist in the management cluster before you run the command. For example, you might want to create different types of clusters in dedicated namespaces. For information about creating namespaces in the management cluster, see [Create Namespaces in the Management Cluster](../cluster-lifecycle/multiple-management-clusters.md#create-namespaces).

```yaml
NAMESPACE: production
```

**NOTE**: If you have created namespaces, you must provide a unique name for all Tanzu Kubernetes clusters across all namespaces. If you provide a cluster name that is in use in another namespace in the same instance, the deployment fails with an error.

## Create Tanzu Kubernetes Cluster Manifest Files {#manifest}

You can use the Tanzu CLI to create cluster manifest files for Tanzu Kubernetes clusters without actually creating the clusters.
To generate a cluster manifest YAML file that you can pass to `kubectl apply -f`, run the `tanzu cluster create` command with the `--dry-run` option and save the output to a file. Use the same options and configuration `--file` that you would use if you were creating the cluster, for example:

```sh
tanzu cluster create my-cluster --file my-cluster-config.yaml --dry-run > my-cluster-manifest.yaml
```

### Deploy a Cluster from a Saved Manifest File {#deploy-manifest}

To deploy a cluster from the saved manifest file, pass it to the `kubectl apply -f` command.
For example:

```sh
kubectl config use-context my-mgmt-context-admin@my-mgmt-context
```

```sh
kubectl apply -f my-cluster-manifest.yaml
```

## Advanced Configuration of Tanzu Kubernetes Clusters {#advanced}

If you need to deploy a Tanzu Kubernetes cluster with more advanced configuration, rather than copying the configuration file of the management cluster, see the topics that describe the options that are specific to each infrastructure provider.

* [Deploy Tanzu Kubernetes Clusters to vSphere](vsphere.md)
* [Use the Tanzu CLI with a vSphere with Tanzu Supervisor Cluster](connect-vsphere7.md)
* [Deploy Tanzu Kubernetes Clusters to Amazon EC2](aws.md)
* [Deploy Tanzu Kubernetes Clusters to Azure](azure.md)

Each of the topics on deployment to vSphere, Amazon EC2, and Azure include Tanzu Kubernetes cluster templates, that contain all of the options that you can use for each provider.

You can further customize the configuration of your Tanzu Kubernetes clusters by performing the following types of operations:

* [Deploy Tanzu Kubernetes Clusters with Different Kubernetes Versions](k8s-versions.md)
* [Customize Tanzu Kubernetes Cluster Networking](networking.md)
* [Create Persistent Volumes with Storage Classes](storage.md)

## What to Do Next

After you have deployed Tanzu Kubernetes clusters, the Tanzu CLI provides commands and options to perform the following cluster lifecycle management operations. See [Managing Cluster Lifecycles](../cluster-lifecycle/index.md).

repository: JitenPalaparthi/community-edition

repo_name: JitenPalaparthi/community-edition


text:
# Budget Tracker

![GitHub license](https://img.shields.io/badge/Licenses-MIT-blue.svg)

This tracker will help you to track any income or outcome to have healty finances. And can work offline so you will not be worry to use it on places that dont have internet cause it will save the information on the Device/computer and once it detects that is online can upload that information on the DB

## Table of Contents

- [Installation](#installation)
- [Usage](#usage)
- [License](#license)
- [Questions](#questions)

## Installation

Use the package manager [npm](https://docs.npmjs.com/cli/v7/commands/npm-install) to install all the dependencies that are on the package.json

```bash
npm install
```

## Usage

To Run the system you need to use the follow command

```bash
npm start
```

![System View](./readmeFiles/systemView.gif)

## [Budget Tracker GitHub Code](https://github.com/izaack89/budget-tracker)

## [Budget Tracker Live](https://mysterious-citadel-18926.herokuapp.com/)

## Budget Tracker References

- [IndexDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB) - IndexDB Information
- [Manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest) - Manifest Information
- [Service Worker PWA](https://developers.google.com/web/ilt/pwa/introduction-to-service-worker) - Worker PWA Information

## Questions

If you have any questions about the repository, open an issue or contact me directly at<EMAIL_ADDRESS>You can find more of my work at [izaack89](https://github.com/izaack89)

## Author

- **German Ramirez** - [GitHub](https://github.com/izaack89/)

![Badge for GitHub](https://img.shields.io/github/languages/top/izaack89/budget-tracker?style=plastic&logo=github)


text:
# Angry Birds Angry Birds
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.

### Parametric EQs
In case of using parametric equalizer, apply preamp of **-6.7dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-6.9dB**.

| Type    | Fc      |    Q | Gain    |
|:--------|:--------|:-----|:--------|
| Peaking | 20 Hz   | 0.22 | -4.8 dB |
| Peaking | 110 Hz  | 0.2  | -8.8 dB |
| Peaking | 1948 Hz | 0.34 | 8.7 dB  |
| Peaking | 4843 Hz | 0.81 | -7.1 dB |
| Peaking | 6422 Hz | 4.68 | 6.9 dB  |
| Peaking | 230 Hz  | 3.8  | 1.2 dB  |
| Peaking | 270 Hz  | 2.47 | -0.9 dB |
| Peaking | 1833 Hz | 1.53 | -2.3 dB |
| Peaking | 2141 Hz | 0.93 | 2.1 dB  |
| Peaking | 3477 Hz | 3.74 | -1.6 dB |

### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-7.7dB**
(if available) and set gains manually with these parameters.

| Type    | Fc       |    Q | Gain     |
|:--------|:---------|:-----|:---------|
| Peaking | 31 Hz    | 1.41 | -10.5 dB |
| Peaking | 62 Hz    | 1.41 | -8.8 dB  |
| Peaking | 125 Hz   | 1.41 | -8.0 dB  |
| Peaking | 250 Hz   | 1.41 | -5.7 dB  |
| Peaking | 500 Hz   | 1.41 | -1.6 dB  |
| Peaking | 1000 Hz  | 1.41 | 4.1 dB   |
| Peaking | 2000 Hz  | 1.41 | 6.7 dB   |
| Peaking | 4000 Hz  | 1.41 | -0.9 dB  |
| Peaking | 8000 Hz  | 1.41 | 1.2 dB   |
| Peaking | 16000 Hz | 1.41 | -0.3 dB  |

### Graphs
![](https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results/referenceaudioanalyzer/zero/Angry%20Birds%20Angry%20Birds/Angry%20Birds%20Angry%20Birds.png)

path: /results/referenceaudioanalyzer/zero/Angry Birds Angry Birds/README.md


text:
# Descriptive Code Name

A description of what the code does

## Use Case

A description on how to use

## Workflow

How to use the code

## Expression Template

Place the actual code here

## Example Output

- Image of example output
- Link to website that uses

### License
    Copyright 2019 BC Provincial Government

    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

repository: bcgov/gis-pantry

gha_language: Jupyter Notebook

repo_name: bcgov/gis-pantry


text:
# android-gpuimage-ndkbuild-sample
Android NDK Build Sample using android-gpuimage lib base on Android Studio

You should see android-gpuimage and iOS GPUImage framework

https://github.com/CyberAgent/android-gpuimage
https://github.com/BradLarson/GPUImage

# Future
I will compare the noen and the android-gpuimage lib.

branch_name: refs/heads/develop


text:
sFlow
=====

![Travis CI](https://travis-ci.org/tarrant/rust-sflow.svg?branch=master)

sFlow is owned by [InMon](http://www.inmon.com) and [licensed](http://www.inmon.com/technology/sflowlicense.txt) for public use. As this is an open source project it will do its best to adhere to the specification as written while still providing workarounds as needed. The underlying protocol is implemented but not all record types are currently implemented.

repository: andir/rust-sflow

repo_name: andir/rust-sflow


text:
# immcheck - Runtime immutability checks library
[![Go Reference](https://pkg.go.dev/badge/github.com/goodbadreviewer/immcheck.svg)](https://pkg.go.dev/github.com/goodbadreviewer/immcheck) ![Build](https://github.com/goodbadreviewer/immcheck/actions/workflows/build.yml/badge.svg) ![Linters](https://github.com/goodbadreviewer/immcheck/actions/workflows/golangci-lint.yml/badge.svg) [![Go Report Card](https://goreportcard.com/badge/github.com/goodbadreviewer/immcheck)](https://goreportcard.com/report/github.com/goodbadreviewer/immcheck) [![Coverage Status](https://coveralls.io/repos/github/goodbadreviewer/immcheck/badge.svg)](https://coveralls.io/github/goodbadreviewer/immcheck)

Example:

```go
m := map[string]string{
    "k1": "v1",
}
m["k2"] = "v2"
// returns function that you can call to verify that m didn't change
checkFunction := immcheck.EnsureImmutability(&m)
checkFunction() // no mutations are fine

func() {
    defer func() {
        mutationPanic := recover()
        fmt.Println(mutationPanic)
    }()

    // you can also use defer for such checks
    // now when we mutate m, we will get panic at the end of the function
    defer immcheck.EnsureImmutability(&m)()

    // it is also possible to set a finalizer that can check
    // if object remained immutable from this point till garbage collection
    immcheck.CheckImmutabilityOnFinalization(&m)

    // this function works only with `-race` or `-tags immcheck` build flags
    defer immcheck.RaceEnsureImmutability(&m)()

    // this function works only with `-race` or `-tags immcheck` build flags as well
    immcheck.RaceCheckImmutabilityOnFinalization(&m)

    delete(m, "k1")
}()
```

repository: PuddingBot/immcheck

repo_name: PuddingBot/immcheck


text:
STYled console.LOG

## Table of Contents

- [Introduction](#introduction)
- [Install](#install)
- [Usage](#usage)
  - [Recipe](#recipe)
  - [Styles Dictionary](#styles-dictionary)
  - [Mapper Dictionary](#mapper-dictionary)
- [Example](#example)
- [Contributing](#contributing)
- [Credits](#credits)
- [License](#license)

## Introduction

[![codecov](https://codecov.io/gh/jukben/stylog/branch/master/graph/badge.svg)](https://codecov.io/gh/jukben/stylog)

Stylog is a stylish way how to easily format [rich console.log messages](https://developers.google.com/web/tools/chrome-devtools/console/console-write#styling_console_output_with_css).

_It's overengineered on purpose I just wanted to write it in the "old school" way and avoid RegExps. It has been written with a nostalgic memory to the Dragon Book 🐲_

## Install

`yarn add stylog`

_The library is targeted for the last two version of Chrome, it's designed to be used mostly in dev mode within latest dev tools._

## Usage

### API

```js
stylog(
  (recipe: string),
  (stylesDictionary: ?{
    [id: string]: {
      [property: string]: string
    }
  }),
  (mapperDictionary ?{
    [id: string]: (value: string) => string
  })
);
```

If you are fan of FP you can take full advantage of the data-last curried version!✌

```js
stylog.fp(mapperDictionary)(stylesDictionary)(recipe);
```

### Recipe

- **_text_** is everything outside (non-escaped) "**{**"
- **_styled text_** start with "**{**" followed by **id** (string) and optionally **text** (multiline string) then it should be closed with "**}**"
- each **_styled text_** may have corresponding style in _stylesDictionary_ otherwise it would be rendered as **_text_**
- **_styled text_** can be escaped by \ (in template literal you have to use \\\ ) then it would be considered as **_text_**

```
This is normal text {styled this is styled text}
```

```
This is normal text \{styled this is also normal text}
```

### Styles Dictionary

- is an nullable-object where key should be string matching **id** of **_styled text_** and value is supposed to be object of CSS properties in camelCase notation.
- it could be null

```js
{
  styled: {
    fontSize: "20px"; // or "fontSize: 20" :)
  }
}
```

### Mapper Dictionary

- is an nullable-object where key should be string matching **id** of **_styled text_** and value is supposed to be an function which takes that matched string and returns modified string (optionally could return falsy value which will act as empty string)

```js
{
  // return c👏l👏a👏p👏e👏d string
  clap: s => {
    return [...s]
      .map((a, i) => `${a}${i !== s.length - 1 ? "👏" : ""}`)
      .join("");
  };
}
```

## Example

Check it out the `example/index.html` for interactive playground! 🙌

```js
stylog(
  `{big Hello, everyone! This is nicely styled text!}
and non-styled text. Lovely, right? {bold *clap* *clap* *clap*}

{image [GANDALF]} {red Be aware! Wild Gandalf appears!}

.
.
.

\\{gandalf}

.
.
.

not like this

.
.
.
{gandalf}

{clap Awesome}`,
  {
    bold: {
      fontWeight: "bold"
    },
    big: {
      fontSize: "25px",
      border: "1px solid black",
      padding: "10px"
    },
    image: {
      display: "block !important",
      color: "gray",
      fontSize: "10px",
      background: `url("https://vignette.wikia.nocookie.net/casshan/images/d/dc/Warn.png/revision/latest?cb=20120614181856")`,
      backgroundSize: "15px 15px",
      backgroundRepeat: "no-repeat",
      backgroundPosition: "left",
      paddingLeft: "15px"
    },
    red: {
      color: "red",
      textDecoration: "underline"
    },
    gandalf: {
      display: "block !important",
      color: "gray",
      fontSize: "300px",
      lineHeight: "150px",
      display: "block !important",
      background: `url("https://i.giphy.com/media/FyetIxXamPsfC/giphy.webp")`,
      backgroundSize: "200px",
      backgroundRepeat: "no-repeat",
      backgroundPosition: "left"
    },
    clap: {
      background: "black",
      color: "yellow"
    }
  },
  {
    clap: s => {
      return [...s]
        .map((a, i) => `${a}${i !== s.length - 1 ? "👏" : ""}`)
        .join("");
    }
  }
);
```

will produce this:

## Contributing

Do you miss something? Open an issue, I'd like to hear more about your use case. You can also fork this repository and run `yarn && yarn dev`, do stuff in the playground (`example/index.html`), then run `yarn test` and finally send a PR! ❤

## Credits

I got the inspiration for this project from https://github.com/adamschwartz/log, especially from this [issue](https://github.com/adamschwartz/log/issues/43). Thanks @whitefire0 and @adamschwartz.

## License

The MIT License (MIT) 2018 - Jakub Beneš

repository: jukben/stylog

repo_name: jukben/stylog


text:
# Lincheck

Aurora creates 3 lincheck instances, each with different f_Mz codewords, and the same f_z codeword.
These lincheck instances all use the same, verifier chosen `alpha` term.
These lincheck codewords are then collectively reduced to the amortized univariate sumcheck protocol.
This suggests that the protocol ought to be a `multi_lincheck`.

Note that each lincheck instance's codeword is of the form:
`p_1(alpha)|L * f_Mz - p_2(alpha, M)|L * f_z`,
where `p_1, p_2` are polynomials constructed from evaluations in the same systematic domain.

`p_2` gets constructed over the codeword domain for every lincheck instance, as it is M dependent.
Since `p_1` is the same across all linchecks, it can simply be computed once.
This means that for the 3 codewords, 4 polynomial interpolations, and 4 FFTs into the codeword domain are required.

There is an additional optimization we can take, using the information that `f_z` is common to all lincheck instances!
The amortization in the univariate sumcheck protocol takes a random linear combination of the provided codewords.
Let `r_A, r_B, r_C` be these random scalar coefficients.
```
r_A * (p_1(alpha) * f_Az - p_2(alpha, A) * f_z)
 + r_B * (p_1(alpha) * f_Bz - p_2(alpha, B) * f_z)
 + r_C * (p_1(alpha) * f_Cz - p_2(alpha, C) * f_z)
= (r_A * f_Az + r_B * f_Bz + r_C * f_Cz) * (p_1(alpha))
  - (r_A * p_2(alpha, A) + r_B * p_2(alpha, B) + r_C * p_2(alpha, C)) * f_z
```

The important part of this is that the second term `(r_A * p_2(alpha, A) + r_B * p_2(alpha, B) + r_C * p_2(alpha, C))` can be computed from its systematic evaluations directly.
This saves the prover 2 interpolations and 2 FFTs into the codeword domain,
and saves the verifier two lagrange interpolations per query point.

This technique can be extended to arbitrarily many lincheck instances that share `f_z`.

repository: AntoineRondelet/libiop

repo_name: AntoineRondelet/libiop


text:
# βρώσιμος, ον.

<!-- Status: S2=NeedsFinalCheck -->
<!-- Lexica used for edits: LN MM -->

## Word data

* Strongs: G10340.

* Alternate spellings:

* Principle Parts:

* Part of speech:

[Noun substantive_adj](http://ugg.readthedocs.io/en/latest/noun_substantive_adj.html).

* Instances in the New Testament: 1.

* All Scriptures cited: Yes.

## Etymology:

* LXX/Hebrew glosses:

* Time Period/Ancient Authors:

* Related words:

[βρῶσις](../G10350/01.md): eating.

* Antonyms for all senses:

* Synonyms for all senses:

## Senses:

### Sense  1.0:

#### Definition:

edible

#### Glosses:

edible, eatable

#### Explanation:

#### Citations:

; [ἔτι](../G20890/01.md) [δὲ](../G11610/01.md) [ἀπιστούντων](../G05690/01.md) [αὐτῶν](../G08460/01.md) [ἀπὸ](../G05750/01.md) [τῆς](../G35880/01.md) [χαρᾶς](../G54790/01.md) [καὶ](../G25320/01.md) [θαυμαζόντων](../G22960/01.md) [εἶπεν](../G30040/01.md) [αὐτοῖς](../G08460/01.md) [ἔχετέ](../G21920/01.md) [τι](../G51000/01.md) [βρώσιμον](../G10340/01.md) [ἐνθάδε](../G17590/01.md)
; " Now when they still could not believe it because of the joy and amazement, he said to them Do you have anything here to eat?"" (ULT):
[Luke 24:41](luk 24:41).

repository: mandolyte/uw-obsidian

repo_name: mandolyte/uw-obsidian


text:
# Karaf Features: Routes

## What is it?

Some more routing stuff (in addition of the messaging feature) for Osgiliath framework

## How to use?

Reference this feature in your pom:
```
<dependency>
			<groupId>net.osgiliath.framework</groupId>
			<version>${osgiliath.maven.version.version}</version>
			<artifactId>net.osgiliath.feature.routes</artifactId>
			<type>xml</type>
			<classifier>features</classifier>
		</dependency>
```
And don't forget to add the feature you want to use on your app features.xml

You can now have some more routing stuffs on your project


text:
# Dungeon Battle
Dungeon Battle is an RPG Battle Game. The user gets to select from one of THREE combatant classes, and battle scary Dungeon monsters. Who will win?

## Wireframes:

## Technologies Used

-HTML

-CSS

-Javascript

-Bootstrap

This is a web-based game. a modern web browser that supports HTML5 and CSS is required.

User Stories:

As a User, I should be able to identify and select one of three combatant classes: Mage, Crusader or Witch Doctor

As a User, I should be able to see who my combatant is battling

As a User, I should be able to attack my opponent

As a User, I should be able to see my attack damage reflected on my opponents' stats, and Vice/Versa

As a User, I should be able to see whose turn it is (Mine vs Computer)

As a User, I should know who won

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)


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.39.0](https://github.com/tinacms/tinacms/compare/v0.38.0...v0.39.0) (2021-03-30)

### Bug Fixes

* copyright ([e4323c2](https://github.com/tinacms/tinacms/commit/e4323c25b7e893005bffad1827018b523b7f6939)), closes [#1778](https://github.com/tinacms/tinacms/issues/1778)

# [0.33.0](https://github.com/tinacms/tinacms/compare/v0.32.1...v0.33.0) (2020-11-16)

**Note:** Version bump only for package @tinacms/media

# [0.32.0](https://github.com/tinacms/tinacms/compare/v0.31.0...v0.32.0) (2020-10-20)

**Note:** Version bump only for package @tinacms/media

# [0.31.0](https://github.com/tinacms/tinacms/compare/v0.30.0...v0.31.0) (2020-10-05)

### Bug Fixes

* **@tinacms/media:** deprecated since these interfaces were graduated to core ([39f1a72](https://github.com/tinacms/tinacms/commit/39f1a729a112fbab24af4c1e319cdc94867325aa))

### Features

* **@tinacms/media:** add optional previewSrc to Media interface ([664701e](https://github.com/tinacms/tinacms/commit/664701e912f11c554f7852eed608f28f3dafd00e))
* **@tinacms/media:** added id property to Media interface ([95ce72c](https://github.com/tinacms/tinacms/commit/95ce72ca76c69d4838efdef0cc196957d9107ff6))
* **@tinacms/media:** cms.media has all of the MediaStore methods ([6109f74](https://github.com/tinacms/tinacms/commit/6109f74b41c315b4800a7764e26b92e3f61f1197)), closes [#1458](https://github.com/tinacms/tinacms/issues/1458)
* **@tinacms/media:** cms.media has all of the MediaStore methods ([97b080b](https://github.com/tinacms/tinacms/commit/97b080b90f246f312aefc11d396ec2cde207ef36)), closes [#1458](https://github.com/tinacms/tinacms/issues/1458)
* **@tinacms/media:** The media in the store can be listed ([8704c29](https://github.com/tinacms/tinacms/commit/8704c290d6161606fb8dae661714dd64d720c686)), closes [#1451](https://github.com/tinacms/tinacms/issues/1451)
* **@tinacms/media:** the Media interface now has a 'type' prop that can be 'file' or 'dir' ([1a867cf](https://github.com/tinacms/tinacms/commit/1a867cfb53b5e6accbdc5e63a41c401fee2ed2d7))

# [0.29.0](https://github.com/tinacms/tinacms/compare/v0.28.0...v0.29.0) (2020-08-25)

**Note:** Version bump only for package @tinacms/media

# [0.28.0](https://github.com/tinacms/tinacms/compare/v0.27.3...v0.28.0) (2020-08-17)

### Features

* **@tinacms/media:** MediaStore's can have an optional previewSrc method ([e4024d2](https://github.com/tinacms/tinacms/commit/e4024d2404dd833617fed5715c3d1f8fb397ee46))

# [0.26.0](https://github.com/tinacms/tinacms/compare/v0.25.0...v0.26.0) (2020-08-03)

**Note:** Version bump only for package @tinacms/media

# 0.1.0 (2020-03-23)

### Features

* introduce @tinacms/media ([a1be1b6](https://github.com/tinacms/tinacms/commit/a1be1b6))

repository: bshackelford/tinacms

repo_name: bshackelford/tinacms


text:
[![Build Status](https://travis-ci.com/pmav99/ansible-role-addme.svg?branch=master)](https://travis-ci.com/pmav99/ansible-role-addme)

addme
=====

This role setup a linux user account with my dotfiles etc.

It shouldn't be useful to anyone else (except maybe as inspiration)

Quickstart
----------

    curl -Ssl https://raw.githubusercontent.com/pmav99/ansible-role-addme/master/quickstart.sh | bash

Install the role
----------------

You can install the role by using:

    ansible-galaxy install pmav99.addme

Role Variables
--------------

    addme_username: pmav99
    addme_github_username: pmav99

Example Playbook
----------------

    - hosts: '<IP_ADDRESS>'
      connection: 'local'
      vars:
        addme_username: 'pmav99'
        addme_directory 'zsh_remote'
      roles:
        - role: 'pmav99.addme'

License
-------

MIT