text:
##  AP Register Listing (APREG.R1)

<PageHeader />

**Form Details**
[ Form Details ](APREG-R1-1/README.md)

**Purpose**
The APREG.R1 procedure is used to print a listing of all Accounts Payable
register transactions for a period. This report can be run either in detail or
summary, for all or selected account numbers.

**Frequency of Use**
This report should be run as a period end audit report of the tran- sactions
which will be posted to General Ledger. It can be run as required to audit
progress through the period.

**Prerequisites**
Accounts Payable register transactions are created automatically by the system through the [ AP.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/AP-E) , [ CHECKS.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/AP-E/CHECKS-E) , [ RECEIPTS.P1 ](RECEIPTS-P1/README.md) and [ APR.P1 ](../../../../rover/AP-OVERVIEW/AP-PROCESS/APR-P1) procedures.

**Data Fields**

**Acct Number** The General Ledger account number.
**Vendor Number** The number of the vendor from the AP record.
**Vendor Name** The name of the vendor, as read from the Vendor file.
**Check Notes** Miscellaneous notes from the Check file, if the register was
the result of a check transaction.
**Invoice Number** The invoice number from the AP item, if the regis- ters was
the result of an AP transaction.
**Record Date** The date of the record which created this register record.
**Apreg ID** The record id of the APREG entry.
**Apreg Date** The date for which the register entry was made.
**Apreg Amount** The total amount of the register record.
**Procedure Name** The procedure which caused this register record to occur (e.g. [ AP.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/AP-E) , [ CHECKS.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/AP-E/CHECKS-E) , etc.).
**Record Id** The record id which caused this register record to occur (e.g.
AP id, Check number, etc.).
**Post Date** The date this register was posted to General Legder.
***** An asterisk will print in the right-most column if the register date
differs from the record date.

<badge text= "Version 8.10.57" vertical="middle" />

<PageFooter />

repository: zumasys/docs

repo_name: zumasys/docs


text:
---
layout: post
title:  "Foundations: Day II"
date:   2019-09-27
tags: [foundations, bike, push, squat, barbell, wod]
---

*(Written retrospectively, so honestly probably forgot something)*

Today was moving around the barbell off of the rack. This was good stuff
because my shoulders and upper body are **weak as fuck**.

<!--more-->

### Assault Bike
- Seat height: 4
- Pretty straight forward, but remember that you can use the handle bars to
  push and pull - It's not completely legs

### Pushes

- Bunch of different types of pushes, but each one is just a step different
  than the previous. I figure writing them out and seeing them in a line will
  help me remember the differences:
    - [Strict Shoulder Press](https://www.youtube.com/watch?v=xe19t2_6yis)
        - Hip-width stance
        - Full grip, outside of shoulders
        - Elbows forward
        - It seems like the full grip limits elbow mobility, preventing far
          elbows like in a [front rack]() position
    - [Push Press](https://www.youtube.com/watch?v=iaBVSJm78ko)
        - Similar to strict, but bending legs to position self a little bit
          under the barbell to distribute the weight into your legs
        - The coach taught this to me in three steps:
            - Slightly squatting with bar
            - Getting onto toes, bar should reach face-height
            - Catch bar at the top with both legs and arms extended
    - [Push Jerk](https://www.youtube.com/watch?v=V-hKuAfWNUw)
        - Similar to push press, but you jerk under the bar in the third step,
          catching the bar with arms extended but legs squatting (jumping into
          slightly wider squat with toes slightly outward)
    - [Split Jerk](https://www.youtube.com/watch?v=PsiO8lZTU2I)
        - Similar to push jerk, but instead of jerking into a slightly wider
          squat, you jump into a lunge
        - The rep is complete when you stand up from the lunge
        - Standing up after the lunge looks so ugly, so I hate the split jerk

### Squats

- [Overhead squat](https://www.youtube.com/watch?v=RD_vUnqwqqI)
    - Shoulder-width stance
    - Wide full grip
- [Front rack squat](https://www.youtube.com/watch?v=m4ytaCJZpl0)
    - Shoulder-width stance
    - Hands outside of shoulders, loose fingertip grip
        - I don't think my wrists are flexible enough for this, despite how
          much I work on my wrists
- [Back squat](https://www.youtube.com/watch?v=ultWZbUMPL8)
    - Shoulder-width stance
    - Hands comfortably outside of shoulders at a full-grip

### Broad Strokes

Remember to activate all of your muscles. You're naturally a sedentary being
and forget to use muscles that you have.

## WOD

For Time:
- 200m Run
- 6 Push Presses
- 7 Front Squats
- 8 Burpees

I actually don't know how long this took me. This was really taxing for me. I
remember the few days after my lats were so sore.

license: MIT

branch_name: refs/heads/master

extension: md

gha_language: CSS

gha_license_id: MIT

license_type: permissive


text:
---
layout: default
---

# 1997-04-23 - www.wow-com.com

## Header Data

From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: 9ea5774ec283c18bc404c5384b535240207d6ab326568c6b36d25bdf9cf16a1f

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1997-04-23 01:23:38 UTC

Raw Date: Tue, 22 Apr 1997 18:23:38 -0700 (PDT)

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>Date: Tue, 22 Apr 1997 18:23:38 -0700 (PDT)
To<EMAIL_ADDRESS>Subject: www.wow-com.com
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

Dear WOW-COM Reader:

WOW-COM continues to provide the knowledge wireless professionals need to stay ahead in a fast-paced environment.  Our news, CTIA-sponsored research and  regular updates on the top issues affecting wireless, make WOW-COM the site for industry professionals.

Daily use of the wireless industry's Web hub continues to grow because we constantly add new features and information.  Here is what's new:

**Searchable Database on Antenna Moratoria Across America**

This segment of WOW-COM provides the information on every effort by localities to thwart development of wireless infrastructure by limiting tower development.  This analysis is of great value to all wireless professionals attempting to navigate the tower siting issue successfully.

To reach the Moratoria Database, click on http://www.WOW-COM.com/professional/siting/index.cfm

**Career Center**

WOW-COM's Career Center continues to grow rapidly.  New listings by Motorola, Iridium LLC, Sony Wireless Telecommunications, AirTouch Cellular, Lucent Technologies, and others have made this the on-line job center for wireless.  Recruiters are also now linked to the center, making it possible for you to reach them easily.

To reach the Career Center, simply logon to WOW-COM and click on the Career Center.

**Week In Review**

The Week In Review, authored by CTIA political and regulatory experts, is available every Friday on WOW-COM -- three days before its scheduled Monday release.

We are always adding additional services, analysis and research for WOW-COM readers.  Please let us know what you think about WOW-COM and how we can serve you better!

Sincerely,
Team WOW-COM
<EMAIL_ADDRESS>www.wow-com.com

We hope you found this email useful and informative.  If you didn't, we sincerely apologize.  If you do not wish to receive our notices, please reply to<EMAIL_ADDRESS>

{% endraw %}
```

## Thread

+ Return to [April 1997](/archive/1997/04)

+ Return to "[wcreply@ctia.org](/authors/wcreply_at_ctia_org)"

+ 1997-04-23 (Tue, 22 Apr 1997 18:23:38 -0700 (PDT)) - www.wow-com.com -<EMAIL_ADDRESS>


text:
---
title: "God"
author: glennji
date: 2019-05-06T00:12:11+10:00
draft: false
type: note
crosslink: "true"
aliases:
  - /lexicon/goddess
  - /lexicon/deity
categories:
  - Anthropology
  - Theosophy
---
In religion, a powerful, immortal entity that may exist outside of space-time (but still have an effect on "reality"). Different religions may have one or many gods and goddesses: in a monotheistic religion (like Judaism, Christianity to a degree and Islam) they will not acknowledge foreign gods as "real", and are likely to instead associate them with the devil.

In Abrahamic religions there are many names for god, including those below; generally god is named using platitudes ("most high", "lord above all", et cetera):

  * Y-H-W-H, "yahweh"
  * "El" or "Allah"

I'm not at all convinced there is such a thing: while the lack of evidence suggests there isn't, there's plenty of "reality" that we don't know about (yet). I do sometimes feel something "spiritual", but that could be either part of my own internal psychology or even just how the Universe "works" (without any need for an anthropomorphic "personality" imposed upon the system). At the end of the day, I don't find an all-powerful deity likely or (more importantly) necessary. Call it "pragmatic atheism" or "atheistic pragmatism".

Besides, I don't want to be associated with the nut-cases that call themselves "religious" -- so it is much more sensible to side with the atheists.

repository: glennji/website

gha_language: HTML

repo_name: glennji/website


text:
# Java-Project
A barebones project structure that serves as the basis of an assignment

How to run.

1)Open project with Intellij
2)Create a database called PersadoProject
3)Change username and password at application.properties file
4)add mysql.connector jar file at project structure
5)Run the project in order to create tables
6)Run the data.sql script
7)Run project again :)
8)Connect to http://localhost:8093


text:
# cros-sdk docker image

Docker image for [Chromium OS](http://www.chromium.org/chromium-os) SDK.

## Building

```
# build `cros-sdk` and `cros-sdk:beaglebone` images
./build
# re-use depots sources cache from previous build
CACHE_OPTS= ./build
# build for multiple boards
BOARD="x86-generic arm-generic beaglebone" ./build
```

## Usage

```
# start a cros-sdk shell
docker run --privileged -ti cros-sdk
# run a cros-sdk command
docker run --privileged cros-sdk -- ./setup_board --board=beaglebone)
# use beaglebone image variant
docker run --privileged -ti cros-sdk:beaglebone
```

## Disclaimer

This is not an official Google product.

repository: proppy/cros-sdk-docker

repo_name: proppy/cros-sdk-docker


text:
# FPGA Development

There may be needs to change the FPGA image. The following explains how this can be done.

## Preparation

If you want to make changes to the FPGA design, you need to install [Vivado 2021.2](https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html). More infos for setting up a development machine we refer to the following [resource](http://pavel-demin.github.io/red-pitaya-notes/development-machine/) and [here](installation.md#linux-image-and-fpga-images).

After following the installation steps, you need to clone the repository into a directory of your choice and then regenerate the IP cores and the project by running

`make daq_bitfiles`.

Afterwards you can start Vivado and open the recreated project in `./build/fpga/<xc7z010clg400-1,xc7z020clg400-1>/firmware/RedPitayaDAQServer.xpr`. Apply the changes you need and then create the bitfile by using 'Flow -> Generate Bitstream'. This runs the synthesis and implementation steps and output the Bitfile to `./build/fpga/firmware/RedPitayaDAQServer.runs/impl_1/system_wrapper.bit`.

After creating the respective bitfile you need to copy it to your Red Pitayas. You can use

`scp ./build/fpga/<xc7z010clg400-1,xc7z020clg400-1>/firmware/RedPitayaDAQServer.runs/impl_1/system_wrapper.bit root@<IP>:/root/RedPitayaDAQServer/bitfiles/daq_<xc7z010clg400-1,xc7z020clg400-1>.bit`

for this. Set your IP and FPGA version accordingly. Another option is to fully regenerate the Linux image with `make all` and copy it to the SD card.

Since using git with Vivado can be annoying here are some hints how you can make your changes ready for git:

* If you only changed some stuff in the blockdesign, you just have to export the blockdesign to `./src/fpga/bd/bd.tcl` by using 'File -> Export -> Export Block Design' in Vivado.
* Changes to the project settings have to be done in `./src/fpga/build.tcl` in order to not lose the ability to recreate your changed project.
* For your own IP cores, just create a new directory in `./src/fpga/cores` and copy and adapt the `core_config.tcl` of another core. Afterwards re-run `make cores`.

repository: tknopp/RedPitayaDAQServer

gha_language: C

gha_license_id: NOASSERTION

repo_name: tknopp/RedPitayaDAQServer


text:
 Undergrad-Project-Tools

----
- [Overview](#overview)
- [General suggestions](#general-suggestions)
- [Cross Platform App Development](#cross-platform-app-development)
- [Web Development](#web-development)
- [Backend](#backend)
- [Design](#design)
- [Project Management](#project-management)
- [Contributing](#contributing)
- [License](#license)

## Overview

This is just a page that intends to provide useful suggestions for undergraduate students who want to work on out-of-class projects. The suggestions listed here are mostly based on my personal project development experience in my undergrad years.

## General suggestions

There are lots of available languages, tools, frameworks for you to do out-of-class projects. Cross-Platform and Web apps are typically easier for deployment so you can get a taste of building your own products and share with others. Don't be afraid of learning new languages or frameworks as long as they have good documentations and active communities. StackOverflow and Google are always your best teachers/friends ~

## Cross Platform App Development

[Flutter](https://flutter.dev)

* Developed by Google, based on Dart
* Cross-platform (Android, iOS, React Native, web)
* Use its own UI component "Widget" (similar to React Native's View)
* Rich documentations and helpful guides
* Hot-reload for easy-debugging and fast development

[React Native](https://reactnative.dev/docs/0.60/getting-started)

* Developed by Facebook, based on JavaScript
* Cross-platform (Android, iOS, React Native, web)
* Hot-reload for easy-debugging and fast development
* Helpful tutorials and active communities
* [Expo](https://expo.io) is highly recommended for conveninet tests on mobile platforms

[Apache Cordova](https://cordova.apache.org)

* Cross-platform (web, iOS, Android)
* 0 extra knowledge required other than basic HTML/CSS/JS
* Basically a browser to open your web app on mobile platforms
* Needs to do extra work on the styling

Unity* (for games)

* Unity is probably the most popular game engine.
* Available on Windows/OSX/Linux
* Can be deployed to multiple platforms easily
* Resource-consuming but powerful
* Helpful community and abundant available resources for learning and developing games (Youtube videos, templates, assets, packages)

## Web Development

JavaScript

* The next step after basic HTML/CSS for static web dev
* Handle logics in web dev and make your web pages move ~
* Used both for client-side and server-side
* Various good frameworks based on JS, such as React.js, Vue.js, Angular.js
* Probably the *most* important language to learn for web/app development

[React JS](https://reactjs.org)

* One of the most popular JS frameworks developed by Facebook
* Easy to learn after you get familiar with JS
* Declarative programming to abstract away from [DOM](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction)
* Component-Based with states (similar to an object in Java [?](https://stackoverflow.com/questions/35764800/is-reactjs-based-on-object-orient-concept))

[Node.js](https://nodejs.org/en/about/)

* Backend JS environment
* Can be understood as "compiler/intepreter" for JS locally
* A necessary dependency for web dev (such as [npm](https://www.npmjs.com/get-npm), a package manager to install JS libraries, including React JS)

[Bootstrap](https://getbootstrap.com) (also available for [React](https://react-bootstrap.github.io))

* Good for general web design
* Useful templates to replace non-trivial CSS style setups
* Organize the website layouts quickly and easily
* Provide prebuilt components for webs and also icons
* Can be installed with npm or just add two lines for CSS and JS at the top of HTML

[Gatsby](https://getbootstrap.com)

* Provide templates to build tutorials
* Can convert MDX to web pages directly
* Powerful to enable non-experts to build web pages

## Backend

[Firebase](https://firebase.google.com)

* Developed by Google
* Free for small apps
* Support apps on multiple platforms (Android, iOS, Unity, Web)
* High-level backend management with a GUI
* Super good for people to develop apps w/o backend knowledge
* Various functions, including hosting web, storaging, relational DB
* Easy connections with other google's products, such as Flutter and Google Cloud Platform
* Not quite an active community (at least 2 years ago), hard to find hacky solutions in some special cases

[Heroku](https://www.heroku.com)

* Probably the most commonly used free server
* Provides "hooks" to Github so that your web app will be updated automatically if you push changes to github
* Various third-party apps, such as MangoDB, for backend development

## Design

[invision](https://www.invisionapp.com)

* Free trial available
* Easy to draw nice-looking low-fidelity prototypes

[Figma](https://www.figma.com)

* Allow collaboration
* Free for 3 projects and 2 editors
* Can be used to build nice-looking low-fidelity prototypes

Keynote/PowerPoints

* Probably the most accessible design tools (?)
* Easy to use and present to others
* Can be used to build interactive high-fidelity prototypes by using links that can lead to other pages on elements.

## Project Management

Github

* Probably the most popular platform to hold your team projects. It's pretty important to make sure your team members are familiar with Github's features, such as branches.
* With a good habit of version control, it can make your team confident enough to keep pushing forward with a safe option to roll back to stable previous versions.
* With multiple branching, you can have members work on different features of the project at the same time on different branches. Then, let the project leader to review and merge branches to the main/dev branch weekly.

[GitKraken](https://www.gitkraken.com)

* By far my personal favorite git GUI.
* Colorful UI.
* Friendly to people who are new to Git/Github.
* Easy to manipulate branches (by just drag branches around).

## Contributing

**Contributions are all welcome!**

## License

Licensed under the [MIT license](LICENSE.txt).

license: Unlicense,MIT

branch_name: refs/heads/main

detected_licenses: Unlicense MIT


text:
**Life cycle dataset, source publication references. Lists sources of
data for ICE life cycle analysis dataset, including title, author(s),
year of publicaiton and ISBN**

## Summary

The [Inventory of Carbon & Energy (ICE),
version 2.0](Embodied_Inventory_of_carbon_and_energy_ICE) is a life
cycle dataset featuring a wide range of construction materials, produced
in conjunction with the University of Bath. This dataset describes the
sources upon which the dataset is based.

-----

## The Dataset

Each of the sources of ICE data are individually itemised, and are
differentiated by their **reference** number or *index*. Each reference
is represented by the following data:

  - *Title*
  - *Author(s)*
  - *Year of publication*
  - *Publisher*
  - *Internation Standard Book Number (ISBN)*

-----

## Related methodologies

These references related to several life-cycle methodologies sourced
from the ICE database.

The bulk of the ICE database represents several hundred distinct
materials, the embodied emissions and energy of which can be calculated
on the basis of [mass](ICE_v2_by_mass) or [area](ICE_v2_by_area).

In addition, there exist several methodologies which provide data and
calculations specific to particular types of materials:
[concrete](ICE_v2_concrete), [timber](ICE_v2_timber) (including biogenic
CO2 emissions) and [windows](ICE_v2_windows).

repository: thegreenwebfoundation/datasets

gha_language: JavaScript

repo_name: thegreenwebfoundation/datasets


text:
ieee_tec_2014_rtea
==================

Matlab code for the rolling-tide evolutionary algorithm described in the IEEE Transactions on Evolutionary Computation paper:
"The Rolling Tide Evolutionary Algorithm:  A Multi-Objective Optimiser for Noisy Optimisation Problems"
by Jonathan E. Fieldsend and Richard M. Everson

The paper is in press and has been available online via the IEEE Explore site since Feb 2014 (issue number in physical copy of IEEE Transactions on Evolutionary Computation TBC).

https://ore.exeter.ac.uk/repository/handle/10871/17063
https://doi.org/10.1109/TEVC.2014.2304415

Code additionally requires the single link guardian data structure in my gecco_2014_changing_objectives repository to run (specifically the single_link_guardian_iterative.m file)

Please run "help RTEA" in the matlab terminal for details of inputs and use.

Example usage:

```matlab
num_obj = 2; % two objectives
num_var=30; % 30 design variables
mut_width = 0.2; % mutation width
cross_prob = 0.8; % crossover probability

% set up variable ranges and bounds for use in algorithm
func_arg.range = ones(1,num_var);
func_arg.upb = ones(1,num_var);
func_arg.lwb = zeros(1,num_var);
% set up noise width to apply to decorated test function
func_arg.noise = ones(1,num_obj)*0.1;

[I_dom, X, Y_mo, Y_n, Y_dom] = ...
RTEA(10000,'cost_dtlz2_noise','check_dtlz_legality',num_var,num_obj,mut_width,cross_prob,func_arg);
```


text:
# Migrating from a local database to S3

If you're running your own instance of docs.rs for personal development, and you'd like to test out the S3 integration, there are a couple steps involved. It's mostly straightforward, but there's at least one major caveat that should be taken into account.

## Requirements

Since docs.rs uses a fixed bucket name to upload files, you'll need to set up an independent server that implements the Amazon S3 API. [Minio](https://min.io/) is an example of a server you can set up. Instructions for installing and configuring Minio (or any S3-compliant provider) are beyond the scope of this article.

## Configuring your docs.rs instance

Once you have your server and credentials set up, you need to tell the docs.rs server to use it. You'll need to add some extra environment variables to the environment file you use to configure docs.rs. It uses the `S3_ENDPOINT` variable to determine where to call, and the other variables to configure its access privileges. The available environment variables are documented in `rusoto`'s [`EnvironmentProvider`](https://docs.rs/rusoto_credential/0.40.0/rusoto_credential/struct.EnvironmentProvider.html).

```text
AWS_ACCESS_KEY_ID=<access key>
AWS_SECRET_ACCESS_KEY=<access secret>
S3_ENDPOINT=<endpoint url>
```

## Migrating files out of the database

Before you restart the process to load the new credentials, the files that are currently in the local database need to be migrated out to S3. Once docs.rs sees that it has AWS credentials in its environment, it will stop reading from the `files` table entirely. Therefore, to properly transition to using the new file storage, you need to run an extra command to upload them. It's helpful to lock the build queue while this is happening, so that no new files will sneak in while the migration happens.

```sh
cratesfyi build lock
# edit the environment file with the above variables if you haven't already
cratesfyi database move-to-s3 # this will take a while, depending on the size of your database
sudo systemctl restart cratesfyi # or however you manage your docs.rs service
# verify that files are loading from S3/Minio/etc
cratesfyi build unlock
```

Once this is done, new crate builds will upload files directly to your file storage service rather than into the database. The `move-to-s3` command will remove rows from the `files` table in the database as it uploads them, so once you're done, you can compact the database to shrink its on-disk size.

repository: XAMPPRocky/rust-forge

gha_language: Rust

repo_name: XAMPPRocky/rust-forge


text:
# ABC - Afterburner CMS
------

[![Code Climate](https://codeclimate.com/github/grounded/afterburnercms.png)](https://codeclimate.com/github/grounded/afterburnercms)

## We make building sites as easy as 1-2-3.

### 1. Install the gem.

Fetch it directly from Github:

```ruby
gem 'abc', github: 'grounded/afterburnercms'
```

### 2. ???

TODO: Fill this in

### 3. Profit!

![Please!](http://i2.kym-cdn.com/photos/images/newsfeed/000/264/200/acb.jpg)

## Using it with Rails
You need to mount both the backend (administrative section) and the frontend (user-facing section) in your rails app.  This can be accomplished by adding the following to your `config/routes.rb`:

```ruby
mount Abc::Backend::Engine  => '/admin'
mount Abc::Frontend::Engine => '/'
```

*NOTE:* Do not use the `:as` option when mounting the Afterburner engines.  This will yield unfavorable results / all manner of brokenness.

## Development
To run the tests inside a subproject (i.e. `/core`):

```shell
bundle
bundle exec rspec spec
```

To run all tests:

```shell
script/rspec
```

To bundle install for all the projects:
```shell
script/bundle
```

To run some command in all sub-projects:
```shell
script/run somecommand
```

To list out the sub-projects:
```shell
script/projects
```

repository: grounded/afterburnercms

gha_language: Ruby

repo_name: grounded/afterburnercms


text:
# Interested in making Tahi better? Awesome :)

Please email us and say hello: TODO

## Contributing

When creating a new pull request, please paste in the following rubric. Please
**delete todo list items that** you feel **do not apply** to your pull request
/ review.

**If you are a first-time contributor you can ignore this rubric; your reviewer
 will help you along**

    ## Pull Request Checklist
    - [ ] ask yourself: is this PR complicated enough that you should write
          integration tests?
    - [ ] do tests pass at every commit? (to preserve ease of `git-bisect`)
    - [ ] ask yourself: do you feel that things are well abstracted?
    - [ ] do a self code review (read through `git diff` or the github UI)
    - [ ] complete all relevant todos in your code
    - [ ] self QA (make sure the app still works, along with your change)
    - [ ] get review from a team-member with knowledge of this codebase area
    - [ ] **team-member said ship it! (:ship: it)**
    - [ ] self QA again Chrome
    - [ ] self QA again Firefox
    - [ ] self QA again Safari
    - [ ] self QA again IE
    - [ ] do any changes need to be made to prod before a deploy? List them in
          the `deployer checklist`
    - [ ] the tests are passing for this branch on semaphore
    - [ ] merge! Celebrate your success!

    ## Reviewer Checklist
    - [ ] is syntax consistent with rest of code-base?
    - [ ] are database access patterns relatively efficient?
    - [ ] are client-side access patterns
    - [ ] ember style

    ## Deployer Checklist
    Changes to Tahi are deployed automatically to staging whenever tests for
    the `master` branch are passing. These items really only apply for deploys
    to `currents`, and `demo` (we don't have a production yet).
    - [ ] **>>list changes here that need to be made to prod before a deploy<<**
    - [ ] ideally these changes can be made by running a rake task or script
    - [ ] you are deploying in the morning
    - [ ] you are deploying on Monday, Tuesday, Wednesday, or Thursday.
    - [ ] you are deploying your own code
    - [ ] did the deploy
    - [ ] you are watching the BugSnag slack channel and/or `heroku logs --tail`
    - [ ] you announced the deploy with a few words summary to chatrooms
    - [ ] you have opened https://dashboard.heroku.com/apps for rollback

At some point we may consider adding this bullet point to the list:

    - [ ] changelog has been updated

codeofconduct
=============

####Tahi's Code of Conduct

*[borrowed from Code for America][cfa]*
[cfa]:https://github.com/codeforamerica/codeofconduct

The Tahi community expects that Tahi network activities, events, and digital forums:

1. Are a safe and respectful environment for all participants.
2. Are a place where people are free to fully express their identities.
3. Presume the value of others. Everyone’s ideas, skills, and contributions have
  value.
4. Don’t assume everyone has the same context, and encourage questions.
5. Find a way for people to be productive with their skills (technical and not)
  and energy. Use language such as “yes/and”, not “no/but.”
6. Encourage members and participants to listen as much as they speak.
7. Strive to build tools that are open and free technology for public use. Activities that aim to foster public use, not private gain, are prioritized.
9. Work to ensure that the community is well-represented in the planning,
  design, and implementation of academic tech. This includes encouraging
  participation  from women, minorities, and traditionally marginalized groups.
10. Actively involve community groups and those with subject matter expertise in
  the decision-making process.
11. Ensure that the relationships and conversations between community members,
  academia, and community partners remain respectful, participatory, and
  productive.
12. Provide an environment where people are free from discrimination or
  harassment.

Tahi reserves the right to ask anyone in violation of these policies not to participate in Tahi network activities, events, and digital forums.

####Tahi's Anti-Harassment Policy

This anti-harassment policy is based on the
example policy from the Geek Feminism wiki, created by the Ada Initiative
and other volunteers.

This policy is based on several other policies, including the Ohio LinuxFest
anti-harassment policy, written by Esther Filderman and Beth Lynn Eicher, and
the Con Anti-Harassment Project. Mary Gardiner, Valerie Aurora, Sarah Smith, and
Donna Benjamin generalized the policies and added supporting material. Many
members of LinuxChix, Geek Feminism and other groups contributed to this work.

---

All Tahi network activities, events, and digital forums and their staff,
presenters, and participants are held to an anti-harassment policy, included
below.

Tahi is dedicated to providing a harassment-free experience for everyone
regardless of gender, gender identity and expression, sexual orientation,
disability, physical appearance, body size, race, age, or religion. We do not
tolerate harassment of staff, presenters, and participants in any form. Sexual
language and imagery is not appropriate for any Tahi event or network activity,
including talks. Anyone in violation of these policies may expelled from Tahi
network activities, events, and digital forums, at the discretion of the event
organizer or forum administrator.

If a participant engages in harassing behavior, the organizers may take any
action they deem appropriate, including warning the offender or expulsion from
Tahi network activities, events, and digital forums.

If you are being harassed, notice that someone else is being harassed, or have
any other concerns, please contact a member of the event staff or forum
administrator immediately. You can contact them at [EVENT ORGANIZER/FORUM
ADMINISTRATOR EMAIL AND PHONE NUMBER]. Event staff or forum administrators will
be happy to help participants contact hotel/venue security or local law
enforcement, provide escorts, or otherwise assist those experiencing harassment
to feel safe for the duration of the event.

If you cannot reach an event organizer or forum administrator and/or it is an
emergency, please call 911 and/or remove yourself from the situation.

You can also contact Tahi about harassment at mike.mazur å† neo.com and feel
free to use the email template below. Tahi staff acknowledge that we are not
always in a position to evaluate a given situation due to the number of events
and the fact that our team is not always present. However, we are hopeful that
by providing these guidelines we are establishing a community that jointly
adheres to these values and can provide an environment that is welcoming to all.

We value your attendance and hope that by communicating these expectations
widely we can all enjoy a harassment-free environment.

####Email Template for Anti-Harassment Reporting

SUBJECT: Safe Space alert at [EVENT NAME]

I am writing because of harassment at a Tahi Communities event, (NAME, PLACE,
DATE OF EVENT).

You can reach me at (CONTACT INFO). Thank you.

repository: johan--/tahi

repo_name: johan--/tahi


text:
---
hrs_structure:
  division: '1'
  volume: '2'
  title: '7'
  chapter: '90'
  section: 90-3
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0090-0003
    parent: HRS0090
    name: '90-3 Rights, responsibilities, and expectations in volunteer relationships'
weight: 50015
title: 'Rights, responsibilities, and expectations in volunteer relationships'
full_title: '90-3 Rights, responsibilities, and expectations in volunteer relationships'
---
**§90-3 Rights, responsibilities, and expectations in volunteer relationships.** (a) Every person regardless of his present economic condition, race, color, ancestry, political affiliation, religious affiliation, sex, age, physical or mental handicap, or marital status has the right to volunteer his services to an agency. An agency has the right to decline any voluntary offer of services, or if accepted, to release subsequently the volunteer who is no longer needed or who is found to be unacceptable.

(b) A volunteer providing services to an agency may expect:

(1) That he will be assigned a job that is worthwhile and challenging, and which permits him the freedom to use existing skills or develop new ones.

(2) That he will be trusted with information that will help him carry out the assignment.

(3) That he will be kept informed about what is going on in the specific volunteer areas.

(4) That he will be provided orientation, training, and supervision for the job he accepts so he will know why he is being asked to do a particular task.

(5) That his time will not be wasted by lack of planning, coordination, and cooperation within the organization.

(6) That he will receive feedback as to whether his work is effective and how it can be improved.

(7) That he will be reimbursed for out-of-pocket costs if it is the only way he can volunteer.

(8) That he will receive letters of recommendation and reference from his supervisor upon request.

(9) That he will be given appropriate recognition for his volunteer services.

(10) That he will be provided a designated supervisor.

(c) A volunteer providing services to an agency has the responsibility to:

(1) Accept assignments given to him.

(2) Fulfill his commitment or notify the designated person of his change of plans.

(3) Follow guidelines and policies established by the agency.

(4) Respect the values and beliefs of others.

(5) Use time wisely and not interfere with the job performance of others.

(6) Provide feedback, suggestions, and recommendations to his supervisor regarding the program.

(7) Be considerate, respect competencies, and work as a member of a team with staff and other volunteers.

(d) The agency utilizing the services of volunteers may expect:

(1) That the volunteer will fulfill his assignment as agreed upon or will notify staff sufficiently in advance if he cannot complete it.

(2) That the volunteer will not go beyond his competencies and authority.

(3) That the volunteer will submit feedback, suggestions, and recommendations about the program to his supervisor.

(4) That the volunteer will maintain confidentiality and will respect and treat the recipients of volunteer services with dignity.

(e) The agency utilizing the services of volunteers has the responsibility to:

(1) Use volunteers to extend services without displacing paid employees.

(2) Provide each volunteer with a designated supervisor.

(3) Provide staff orientation and training in the use and supervision of volunteers.

(4) Define volunteer jobs that are meaningful to the volunteer and commensurate with his abilities.

(5) Be alert to assignments for handicapped or disabled volunteers.

(6) Make it possible for a volunteer to serve on a trial or probationary basis for a specified period.

(7) Provide orientation and training to improve the volunteer's skills.

(8) Provide volunteers with clear instructions and an adequate work space.

(9) Accept the volunteer as part of the team, including him in training and staff meetings that pertain to his work.

(10) Establish and communicate clearly defined lines of supervision so that the volunteer knows to whom he is responsible.

(11) Provide appropriate recognition and appreciation to the volunteer.

(12) Provide written guidelines governing the recruitment, screening, utilization, and supervision of volunteers.

(13) Recognize an applicant's prior volunteer service in evaluating fulfillment of training and experience requirements for state employment pursuant to rules adopted by the department of human resources development, the judiciary, and the board of regents of the University of Hawaii.

(14) Provide funds for volunteer benefits as specified in section 90-4.

(15) Provide recognition of paid staff for support and supervision of volunteers. [L 1978, c 10, pt of §2; am L 1994, c 56, §21]

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# openl-studio-container

Containerised Openl war for running on a local development environment.
http://openl-tablets.org/

# Building
Download the latest war, drop it into the current folder.
run: docker build -t shaneneilwalsh/openl-studio-local .

# Running
docker container run -it --publish 8685:8080 shaneneilwalsh/openl-studio-local

# Usage
Open the browser on the war file name as the url. e.g localhost:8685/openl-tablets-webstudio-5.24.5

repository: ShaneWalsh/openl-studio-container

repo_name: ShaneWalsh/openl-studio-container


text:
# **OpenGL Shader Project**

This project was part of a lecturing/tutorial for a computer graphics class at university.

It consists of most of the OpenGL shader basics needed for further and more complex projects like Pathtracing and SSAO.

With this kind of example-project I would have saved myself lots of hours some years ago.

## **Knowledge Requirement**

If you are completely new to OpenGL or new to programming this is not the tutorial for you!
What you need is a basic understanding of OpenGL and the rendering pipeline.
Also you know how to initialize buffers, allocate memory and generally handle and write C-code.

So if you already build some smaller stuff with OpenGL and want to step your game up with some
 shaders - this is for you!

## **This is what you get**

You can toggle between five different modes. Each mode is very shortly explained on the screen itself,
so you know what you are looking at.

- **Simple coloring of areas**. The fragment shader is used to color your object in just one color. This is
    the simplest shader you can get.

    ![One color](https://github.com/MauriceGit/Simple_GLSL_Shader_Example/blob/master/Screenshots/simple_color.png "Shader with one color")

- **Take the coordinates as color**. The fragment shader interprets the interpolated coordinates as RGB-color and colors your object
    with that color.

    ![Coord color](https://github.com/MauriceGit/Simple_GLSL_Shader_Example/blob/master/Screenshots/coord_color.png "Shader with coordinate-color")

- **Texture**. A texture is loaded and mapped onto the object.

    ![Texture](https://github.com/MauriceGit/Simple_GLSL_Shader_Example/blob/master/Screenshots/texture.png "Shader with texture")

- **Framebuffer-Texture**. The scene is rendered into a framebuffer object which is bound to a texture-object. The resulting texture is then
    mapped onto the object.

    ![fbo-texture](https://github.com/MauriceGit/Simple_GLSL_Shader_Example/blob/master/Screenshots/fbo_texture.png "Shader with framebuffer-object")

- **Framebuffer-Depth-Texture**. The scene is rendered into a framebuffer object which is bound to a depth-buffer-texture. The texture-values
    are then linearized and mapped onto the object. Showing grey values corresponding to the depth of the scene.

    ![fbo-depth-texture](https://github.com/MauriceGit/Simple_GLSL_Shader_Example/blob/master/Screenshots/depthbuffer_texture.png "Shader with framebuffer-object (depth)")

## **Install && Run**

I tested this simulation on a debian-based Linux OS (Ubuntu, Mint, ...). It should run on other machines as well but is not
tested.

### **Requirements**

The following system-attributes are required for running this simulation:

- A graphics card supporting OpenGL version 3.3 (For the shaders).

- Unix-Libraries: xorg-dev, freeglut3-dev and mesa-common-dev

### **Running**

Compiling and running is pretty straight forward.

- ./compile.sh

- ./shaderDemo

While the simulation runs, you can move around (always looking to the center!) with your mouse (left-klick and move).

To toggle the different modes, press 's'.

Pressing 'h' at any point will give you help and all possible mouse/key assignments.

Good luck and have fun!

license: ISC


text:
# mousepage
use your phone as a mouse for your computer!  also configure custom shortcut buttons for specific apps.

configs for various apps are in configs/

you can create an (unformatted) example prefs file with `mousepage --writeprefs <filename>`.

currently there's an audacity config, a vlc config, and a plain mouse config.

start the server with `mousepage <config file>`, navigate to the page with your phone or tablet, there you go.

As of now, this works best in Chrome, with firefox you might need to prompt a resize event somehow or other.

**example ui**

In addition to the mouse controls, the vlc config has various buttons that cause mousepage to issue shortcut key presses.

![](images/vlc-half.jpg)

**prefs**

Prefs are in s-expression format.  Here's the example prefs with some explanatory comments.

```Scheme
((prefs (xmult . 1000.0)  ; prefs section for port and some mouse feel params.
        (ymult . 1000.0)
        (max_tap_duration . 100)
        (show_press_duration . #f)  ; use #t and #f for true/false
        (scroll_threshold . 10)
        (html_port . 8001)
        (websocket_port . 9001)
        )
 (gui  ; gui section has 'title' and 'control'.
        (title . "example")  ; title bar of the web page.
        (control Sizer  ; top control is typically a Sizer.
                        ; Sizer has orientation (Horizontal/Vertical)
                        ; controls (list of controls)
                        ; proportion (number indicating relative size of a control
                        ;             compared to others in a list.)
                  (orientation . Vertical)
                  (controls (Sizer (orientation . Horizontal)
                                    ; labels just show static text.
                                   (controls (Label (label . "label1")
                                                    (proportion)
                                                    )
                                               (Label (label . "label2")
                                                      (proportion)
                                                      )
                                             )
                                   (proportion 0.10000000149011612)
                                   )
                             (Sizer (orientation . Horizontal)
                                    ; for MouseButton 'button' values look in buildlisp.rs
                                    (controls (MouseButton (label "L")
                                                           (button . LeftButton)
                                                           (proportion)
                                                           )
                                       ; holding scroll button down cause the mousexy
                                       ; area to be in scroll mode.
                                              (ScrollButton (label "Scroll")
                                                            (proportion)
                                                            )
                                              (MouseButton (label "R")
                                                           (button . RightButton)
                                                           (proportion)
                                                           )
                                              )
                                    (proportion 0.10000000149011612)
                                    )
                            ; MouseXy moves the mouse around like a touchpad.
                             (MouseXy (label)
                                      (proportion 0.5)
                                      )
                             (Sizer (orientation . Horizontal)
                                    (controls
                              ; key controls contain a list of keys.
                              ; see buildlisp.rs for a list of valid key symbols to
                              ; use here.  For multiple keys (like ctrl-shift-z) you can
                              ; do: (key LControlKey LShiftKey ZKey)
                              ; keys are pressed from left to right, and released right to left.
                                            (Key (label "Enter Key")
                                                 (keys EnterKey)
                                                 (proportion 0.10000000149011612)
                                                 )
                                            )
                                    (proportion) ; empty proportion is optional
                                    )
                            )
                  (proportion)
                 )
       )
  ; see buildlisp.rs for a list of valid 'color' symbols.
  (colors (((color . Text)
             (hexstring . "FF0000")
            )))
 )
```

repository: bburdette/mousepage

repo_name: bburdette/mousepage


text:
# consider-using-in (R1714)
*Consider merging these comparisons with \"in\" to %r* To check if a
variable is equal to one of many values,combine the values into a tuple
and check if the variable is contained \"in\" it instead of checking for
equality against each of the values.This is faster and less verbose.

gha_language: Python


text:
---
title: Getting MathJax to Work
layout: post
use_code: true
use_toc: true
last_updated: 2020-05-04
tags: [web dev]
excerpt: Re-formatting a LaTeX document for use as a blog post took more work than expected. MathJax only supports the LaTeX math-mode commands, and there are additional formatting considerations as well. Here are some tools that I found to make the transition easier.
---

## Converting LaTeX to Markdown/MathJax

1. Replace all `\textbf{abc}` with `**abc**`, and similarly for italics
- Find What: `\\textbf{([^}]+)}`
- Replace With: `**$1**`

2. Replace `\begin{enumerate} ... \end{enumerate}` with actual numbering

3. Replace `\href{link}{text}` with `[text](link)`
- Find What: `\\href{(.+)}{(.+)}`
- Replace With: `\[$2\]\($1\)`

4. Make sure all `$$ ... $$` equations have a newline above and below. This prevents these equations from being treated as inline equations.

5. Replace all `$ ... $` with `$$ ... $$`. (This assumes that single dollar signs have not been configured as delimiters for inline math.)
- Find What: `([^$])\$([^$]+)\$([^$])`
- Replace With: `$1\$\$$2\$\$$3`

6. Surround all LaTeX math-mode blocks (such as `\begin{align} ... \end{align}`) with `$$ ... $$`. This apparently tells the kramdown processor to avoid treating underscores `_` within math equations as italics.

## MathJax Configuration Options

MathJax can be configured to enable optional behavior, including automatic line breaks and support for additional inline math delimiters. These are options that I have played with, but I am wary of their drawbacks and therefore have decided to hold off on enabling them. The automatic line breaks do not account for equation formatting, so they tend to be ugly. Also, using single dollar signs for inline math would require escaping normal dollar signs when writing about currency. However, I am including the following code block for future reference, should I decide to enable these options. The code block would need to come *before* the `<script>` tag that links to the actual MathJax `.js` file.

```html
<script type="text/x-mathjax-config">
  MathJax.Hub.Config({
    // enable automatic line breaks (might look ugly)
    CommonHTML: { linebreaks: { automatic: true } },
    "HTML-CSS": { linebreaks: { automatic: true } },
    SVG: { linebreaks: { automatic: true } },

    // enable $ for inline math -> use \$ for ordinary dollar-sign
    tex2jax: {
      inlineMath: [['$','$'], ['\\(','\\)']],
      processEscapes: true
    },
  });
</script>
```

Additionally, MathJax's accessibility extension [MathJax-a11y](https://mathjax.github.io/MathJax-a11y/) is supposed to support "smart" auto-collapsing equations. I tried to follow the [documentation](https://mathjax.github.io/MathJax-a11y/docs/) but was unsuccessful.

## Other Resources

[Supported LaTeX Commands in MathJax](http://docs.mathjax.org/en/latest/tex.html)


text:
# docker-java-shaded

Shaded/Shadow/Uber/Fat/All version of the [docker-java](https://github.com/docker-java/docker-java) library

## Status

| Questions | CI | Release |
| :---: | :---: | :---: |
| [![Stack Overflow](https://img.shields.io/badge/stack-overflow-4183C4.svg)](https://stackoverflow.com/questions/tagged/docker-java-shaded) | [![Build Status](https://travis-ci.org/project-aries/docker-java-shaded.svg?branch=master)](https://travis-ci.org/project-aries/docker-java-shaded) | [![docker-java-shaded](https://api.bintray.com/packages/project-aries/libs-release-local/docker-java-shaded/images/download.svg) ](https://bintray.com/project-aries/libs-release-local/docker-java-shaded/_latestVersion) |

## Motivation

As the current maintainer of the [gradle-docker-plugin](https://github.com/bmuschko/gradle-docker-plugin) project we had a need to use a shaded version of `docker-java` to get around various `buildscript` clobberring issues. As the folks at the `docker-java` project are busy with other things, and can't immediately make this happen, I decided to go ahead and code something myself until they have the free time in which to do so.

If a new release of `docker-java` happens that I miss, and you'd like a new version of this library spun up based on it, just open an ISSUE and ask.

If a security vulnerability arises, and an internal dependency needs to be bumped, and assuming the `docker-java` can't be easily updated, then just open an ISSUE and note the library and we can spin a new point release to accommadate you and the greater community.

## Latest Release

Can be sourced from jcenter like so:
```
<dependency>
    <groupId>com.aries</groupId>
    <artifactId>docker-java-shaded</artifactId>
    <version>X.Y.Z</version>
</dependency>
```

## Additional Resources

* [Release Process](https://github.com/project-aries/docker-java-shaded/blob/master/docs/RELEASE_PROCESS.md)

repository: project-aries/docker-java-shaded

gha_language: Java

repo_name: project-aries/docker-java-shaded


text:
# Lecture **11**

## Enroute Picker

The first of (the final) four lectures to cover topics for students to use in their final projects.  Picker.  Introduction of the Enroute demo code-base.

url: https://raw.githubusercontent.com/wxpasta/SwiftUI-learning/84b1fa372f7f76fa40396c2df591bffa0acba3ff/Stanford CS193p - Developing Apps for iOS（2020）/Lecture 11/README.md

repository: wxpasta/SwiftUI-learning

repo_name: wxpasta/SwiftUI-learning


text:
## AI Driven Visual Inspection of Wind Turbines based on Drones Pictures

This repository provides the example SAM (Serverless Application Model) template and two AWS Lambda functions disucussed in the blog post AI Driven Visual Inspection of Wind Turbines based on Drones Pictures <link>.

This is an example business logic. Not intended for production.

## Security

See [CONTRIBUTING](CONTRIBUTING.md#security-issue-notifications) for more information.

## License

This library is licensed under the MIT-0 License. See the LICENSE file.


text:
## Note  terraform 0.13 required
### This module creates user groups and adds users to your PostgresSQL database

### Please copy paste the following code to your tfvars file

```
region                      = "us-east-1"
db_host                     = ""
port                        = 5432
database                    = "postgres"
postgres_username           = "postgres"
password                    = ""
group_name                  = "datascience"

user_names = [
    "nargiz",
    "test2",
    "newUser",
    "farrukh"
]
```

### Create a new file called module.tf
```
module "rds" {
    source = "./module"
    user_names = var.user_names
    region = var.region
    db_host = var.db_host
    port = var.port
    postgres_username = var.postgres_username
    password = var.password
    database = var.database
    group_name = var.group_name
}
```

### Create variables.

```
variable "user_names" {
  type = list
}
variable "region" {}
variable "db_host" {}
variable "port" {}
variable "database" {}
variable "postgres_username" {}
variable "password" {}
variable "group_name" {}
```
### Run The following command

```
terraform init
terraform apply -var-file=main.tfvars
```

repository: Murodbey/Terraform-project

repo_name: Murodbey/Terraform-project


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.3.28](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.27<EMAIL_ADDRESS>(2020-03-31)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.27](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.26<EMAIL_ADDRESS>(2020-01-17)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.26](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.25<EMAIL_ADDRESS>(2019-11-25)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.25](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.24<EMAIL_ADDRESS>(2019-11-06)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.24](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.23<EMAIL_ADDRESS>(2019-11-06)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.23](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.22<EMAIL_ADDRESS>(2019-10-10)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.22](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.21<EMAIL_ADDRESS>(2019-10-10)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.21](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.20<EMAIL_ADDRESS>(2019-10-08)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.20](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.19<EMAIL_ADDRESS>(2019-10-08)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.19](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.18<EMAIL_ADDRESS>(2019-10-08)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.18](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.17<EMAIL_ADDRESS>(2019-09-05)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.17](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.16<EMAIL_ADDRESS>(2019-08-15)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.16](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.15<EMAIL_ADDRESS>(2019-07-24)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.15](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.14<EMAIL_ADDRESS>(2019-05-24)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.14](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.13<EMAIL_ADDRESS>(2019-05-21)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.13](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.12<EMAIL_ADDRESS>(2019-05-06)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.12](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.11<EMAIL_ADDRESS>(2019-02-04)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.11](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.10<EMAIL_ADDRESS>(2018-12-13)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.10](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.9<EMAIL_ADDRESS>(2018-11-26)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.9](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.8<EMAIL_ADDRESS>(2018-11-08)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.8](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.7<EMAIL_ADDRESS>(2018-10-17)

### Bug Fixes

* Update deps ([2d509bc](https://github.com/OpenChemistry/oc-web-components/commit/2d509bc))

## [0.3.7](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.6<EMAIL_ADDRESS>(2018-09-24)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.6](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.5<EMAIL_ADDRESS>(2018-09-17)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.5](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.4<EMAIL_ADDRESS>(2018-09-13)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.4](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.3<EMAIL_ADDRESS>(2018-09-05)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.3.3](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.1<EMAIL_ADDRESS>(2018-08-01)

### Bug Fixes

* Update deps to latest versions ([56c5b28](https://github.com/OpenChemistry/oc-web-components/commit/56c5b28))

## [0.3.1](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.3.0<EMAIL_ADDRESS>(2018-07-05)

**Note:** Version bump only for package @openchemistry/sample-data

# [0.3.0](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.5<EMAIL_ADDRESS>(2018-06-19)

### Features

* Add animation of a molecule's normal modes ([f4517f7](https://github.com/OpenChemistry/oc-web-components/commit/f4517f7))

# [0.2.0](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.5<EMAIL_ADDRESS>(2018-06-19)

### Features

* Add animation of a molecule's normal modes ([f4517f7](https://github.com/OpenChemistry/oc-web-components/commit/f4517f7))

# [0.1.0](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.5<EMAIL_ADDRESS>(2018-06-19)

### Features

* Add animation of a molecule's normal modes ([f4517f7](https://github.com/OpenChemistry/oc-web-components/commit/f4517f7))

## [0.0.5](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.4<EMAIL_ADDRESS>(2018-06-17)

### Bug Fixes

* Add caffeine to the sample data ([cd2c74a](https://github.com/OpenChemistry/oc-web-components/commit/cd2c74a))

## [0.0.4](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.3<EMAIL_ADDRESS>(2018-06-17)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.0.3](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.2<EMAIL_ADDRESS>(2018-06-16)

**Note:** Version bump only for package @openchemistry/sample-data

## [0.0.2](https://github.com/OpenChemistry/oc-web-components/compare/@openchemistry/sample-data@0.0.1<EMAIL_ADDRESS>(2018-06-16)

**Note:** Version bump only for package @openchemistry/sample-data

## 0.0.1 (2018-06-16)

### Bug Fixes

* Add a new package with sample cjson data ([aab6353](https://github.com/OpenChemistry/oc-web-components/commit/aab6353))

repository: OpenChemistry/oc-web-components

repo_name: OpenChemistry/oc-web-components


text:
## [1.1.5](https://github.com/json-schema-tools/playground/compare/1.1.4...1.1.5) (2022-10-26)

### Bug Fixes

* bump node ([b03eaef](https://github.com/json-schema-tools/playground/commit/b03eaef9fb0f9338a5f8febfb487345e6a1a4318))
* force npm install more ([05b10aa](https://github.com/json-schema-tools/playground/commit/05b10aa70c9942e38003b5beaadd254c6626a0b2))
* gotta force install ([4025e94](https://github.com/json-schema-tools/playground/commit/4025e944a68f66cf221a1b193f48f06be3f74565))

## [1.1.4](https://github.com/json-schema-tools/playground/compare/1.1.3...1.1.4) (2021-07-30)

### Bug Fixes

* update transpiler to latest with type array fixes ([1dda1aa](https://github.com/json-schema-tools/playground/commit/1dda1aaffa1fdeb3905adf0795561ecad29feb6d))

## [1.1.3](https://github.com/json-schema-tools/playground/compare/1.1.2...1.1.3) (2021-07-30)

### Bug Fixes

* update dereffer + transpiler to latest ([335a85c](https://github.com/json-schema-tools/playground/commit/335a85cd84f37738c5d4b615f4c264aa6c46c476))

## [1.1.2](https://github.com/json-schema-tools/playground/compare/1.1.1...1.1.2) (2020-10-28)

### Bug Fixes

* update dereffer again ([1609490](https://github.com/json-schema-tools/playground/commit/1609490b70f1e03f8df61ae95b8a2356cd9ddac8))

## [1.1.1](https://github.com/json-schema-tools/playground/compare/1.1.0...1.1.1) (2020-10-27)

### Bug Fixes

* add dereferencing and a ref to the example ([bef7782](https://github.com/json-schema-tools/playground/commit/bef7782284df98c60ef02d344fbf794130d360cd))
* make link to to root org ([a9cb349](https://github.com/json-schema-tools/playground/commit/a9cb349069a92f1741f2e4513e276ce2e59d225b))
* update example ([6fce070](https://github.com/json-schema-tools/playground/commit/6fce0701b26ea618cc1c3bb459f9285942907ead))
* use context for release ([6a5a6cb](https://github.com/json-schema-tools/playground/commit/6a5a6cba0356873e6700ea466dfc75d40b992cc0))

# [1.1.0](https://github.com/json-schema-tools/playground/compare/1.0.4...1.1.0) (2020-10-27)

### Bug Fixes

* update readme ([f064cf9](https://github.com/json-schema-tools/playground/commit/f064cf98c764e41ea30f1c853078aeade559e961))

### Features

* switch to transpiler ([6efb220](https://github.com/json-schema-tools/playground/commit/6efb220219a1d95c1aba9da5180e06b0bd64111f))

## [1.0.4](https://github.com/json-schema-tools/playground/compare/1.0.3...1.0.4) (2020-02-25)

### Bug Fixes

* **README:** description + add github code button ([d97e046](https://github.com/json-schema-tools/playground/commit/d97e0463984c8dbc1fb02a190e2ce73449458e97))
* **README:** make json-schema.tools link ([9cdd89d](https://github.com/json-schema-tools/playground/commit/9cdd89dfdd90c229a5c5b97dd04aae8dfbceb8a2))
* **README:** tool => tools ([d93676e](https://github.com/json-schema-tools/playground/commit/d93676e02b39690728698c021e286758237e7b74))
* **README:** update description ([e1a7f5a](https://github.com/json-schema-tools/playground/commit/e1a7f5aaf07520a6eea08eb27fce01974d36c459))
* typo ([9bd98de](https://github.com/json-schema-tools/playground/commit/9bd98de3bc8b0eea62b2993a7ce433319f75b201))

## [1.0.3](https://github.com/json-schema-tools/playground/compare/1.0.2...1.0.3) (2020-02-25)

### Bug Fixes

* whitespace in defaultValue ([ec10186](https://github.com/json-schema-tools/playground/commit/ec101865a2e88064e1fe6260db2bd56fee66468e))

## [1.0.2](https://github.com/json-schema-tools/playground/compare/1.0.1...1.0.2) (2020-02-25)

### Bug Fixes

* add json schema 7 metaschema editor support ([6e69ea7](https://github.com/json-schema-tools/playground/commit/6e69ea798a96c53b305d7601fbe7a3ec2d738ff0))

## [1.0.1](https://github.com/json-schema-tools/playground/compare/1.0.0...1.0.1) (2020-02-25)

### Bug Fixes

* add CNAME ([2eb1c48](https://github.com/json-schema-tools/playground/commit/2eb1c486d30fe9a3442b0bb960d363eada2c9a91))
* toggle editor theme + add gif ([0eec7ba](https://github.com/json-schema-tools/playground/commit/0eec7ba1464a41af626732a5a375de716db1e5bc))

# 1.0.0 (2020-02-25)

### Bug Fixes

* **README:** add initial README ([cc1a8ce](https://github.com/json-schema-tools/playground/commit/cc1a8ceb6de2b31b5e861e7492ae423b471f06d9))
* linting ([5005a34](https://github.com/json-schema-tools/playground/commit/5005a34f812b8b17782c9bcc165472813f889ec2))

### Features

* initial commit ([5d4b87f](https://github.com/json-schema-tools/playground/commit/5d4b87f36e4bcdc510d55e98d2a6c3cd49fa02e7))

## [1.0.1](https://github.com/etclabscore/pristine-typescript-react-material-ui-monaco-playground/compare/1.0.0...1.0.1) (2019-11-27)

### Bug Fixes

* **package.json:** homepage link ([e854587](https://github.com/etclabscore/pristine-typescript-react-material-ui-monaco-playground/commit/e8545870e57ac00078e0ae9cf7c0e9ca777d7a45))

# 1.0.0 (2019-11-27)

### Bug Fixes

* linting ([c651584](https://github.com/etclabscore/pristine-typescript-react-material-ui-monaco-playground/commit/c651584e4cea12bddcc8bc1d4e29a8d60d9fd28f))
* **README:** update content to monaco playground ([f6b83bb](https://github.com/etclabscore/pristine-typescript-react-material-ui-monaco-playground/commit/f6b83bb24da1be50d1d05a214098b838820771ee))
* remove unused variables ([946ff9d](https://github.com/etclabscore/pristine-typescript-react-material-ui-monaco-playground/commit/946ff9d04b4cfeb3fd1763b272d7db0fca5b1675))

# 1.0.0 (2019-10-24)

### Bug Fixes

* add demo gif to README ([a1e0ce6](https://github.com/etclabscore/pristine-typescript-react-material-ui/commit/a1e0ce6dd7c0d44e46e41faaf52b7e45b8623ce9))
* add viewport meta ([6843410](https://github.com/etclabscore/pristine-typescript-react-material-ui/commit/68434105895ea915c3aa4204c8827801d3a5d7bc))
* linting ([27c26d6](https://github.com/etclabscore/pristine-typescript-react-material-ui/commit/27c26d6fa744910a0c53789b0f020a7870053925))

## [1.0.2](https://github.com/etclabscore/pristine-typescript-react/compare/1.0.1...1.0.2) (2019-07-02)

### Bug Fixes

* add homepage to fix gh-pages ([dcb2099](https://github.com/etclabscore/pristine-typescript-react/commit/dcb2099))

## [1.0.1](https://github.com/etclabscore/pristine-typescript-react/compare/1.0.0...1.0.1) (2019-07-02)

### Bug Fixes

* **.releaserc:** remove npm publish ([2ee1fce](https://github.com/etclabscore/pristine-typescript-react/commit/2ee1fce))

# 1.0.0 (2019-07-02)

### Bug Fixes

* **jest:** use passWithNoTests ([f7fdd6c](https://github.com/etclabscore/pristine-typescript-react/commit/f7fdd6c))

### Features

* initial commit ([2cf2f38](https://github.com/etclabscore/pristine-typescript-react/commit/2cf2f38))

repository: json-schema-tools/playground

gha_language: TypeScript

repo_name: json-schema-tools/playground


text:
## About this example

This is a visualization of the 2D particle environment.

## Requirements

 * Simple DirectMedia Layer (version 2)
 * FreeGLUT (version 3)
 * See install-dependencies-ubuntu.sh

##  Compile
Open a terminal and type:
```bash
sh run.sh
```

##  Output
You will see an animation.


text:
# Built-In Build Types

The default Build Type for new jobs is controlled through the "Configure
Jenkins" screen. In addition you can override the setting for a specific
job on its configuration page to use a different Build Type. The build
types are:

* [docker_compose](DockerCompose.md)
* [install_packages](InstallPackages.md)

repository: jkrems/DotCi

repo_name: jkrems/DotCi


text:
Draw Over All Apps plugin for Cordova
===============================

Android Cordova Plugin that uses draw over all apps feature to display a HTML Web view

This plugin was successfully tested on Android 5.1 , also on Marshmallow (Android 6.0).

## Install  ##

	cordova plugin add cordova-plugin-drawoverapps
It is also possible to install via repo url directly

    cordova plugin add https://github.com/ahmedwahba/cordova-plugin-drawoverapps

## Functions

 - window.overApps.checkPermission
 - window.overApps.startOverApp
 - window.overApps.closeOverApp

### window.overApps.checkPermission
This to check draw-over-apps permession and open system permission window to be granted

      window.overApps.checkPermission(function(msg){
             console.log(msg);
      });

|                                    |                                     |
| ---------------------------------  | --------------------------------    |
|| |

### window.overApps.startOverApp

start service function display the over-all head or the web view according to options. If successful the `success` is called,
otherwise the `failed` is called instead.

    window.overApps.startOverApp(options, success, failed);

#### Options

 - **path**: file path to display as view content, this file should be located in  `WWW` root folder.
 - **hasHead**: display over app head image which open the view up on click , by default true.
 - **dragToSide**: enable auto move of head to screen side after dragging stop , by default true.
 - **enableBackBtn**: enable hardware back button to close view, by default true.

    should be disabled to be able to use keyboard.
 - **enableCloseBtn**: whether to show native close btn or to hide it , by default true
 - **verticalPosition**: set vertical alignment of view , values are top - center - bottom , by default center.
 - **horizontalPosition**: set horizontal alignment of view , values are right - center - left , by default center.

#### Example

    var options = {
          path: "test.html",          // file path to display as view content.
          hasHead: true,              // display over app head image which open the view up on click.
          dragToSide: false,          // enable auto move of head to screen side after dragging stop.
          enableBackBtn: false,       // enable hardware back button to close view.
          enableCloseBtn: true,      //  whether to show native close btn or to hide it.
          verticalPosition: "top",    // set vertical alignment of view.
          horizontalPosition: "left"  // set horizontal alignment of view.
     };

     window.overApps.startOverApp(options,function (success){
       		console.log(success);
     },function (err){
       		console.log(err);
     });

|                                    |                                     |                                    |
| ---------------------------------  | --------------------------------    | -----------------------------------|
||  ||

### window.overApps.closeOverApp

It closes over app web view , called inside app itself only .

    window.overApps.closeOverApp();

## Control overApp WebView

### Close WebView

It closes over app webview from one of the webview UI or event

    OverApps.closeWebView();

## Licence ##

Copyright (c) 2017	Ahmed Wahba & Mohamed Sayed

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

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

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

repository: cedkim/waketag

repo_name: cedkim/waketag


text:
# Linear Pipelines

In MLJ a *pipeline* is a composite model in which models are chained
together in a linear (non-branching) chain. Pipelines can include
learned or static target transformations, if one of the models is
supervised.

To illustrate basic construction of a pipeline, consider the following
toy data:

```@setup 7
using MLJ
MLJ.color_off()
```

```@example 7
using MLJ
X = (age    = [23, 45, 34, 25, 67],
	 gender = categorical(['m', 'm', 'f', 'm', 'f']));
height = [67.0, 81.5, 55.6, 90.0, 61.1]
nothing # hide
```

The code below defines a new model type, and an *instance* of that
ype called `pipe`, for performing the following operations:

- standardize the target variable `:height` to have mean zero and
  standard deviation one
- coerce the `:age` field to have `Continuous` scitype
- one-hot encode the categorical feature `:gender`
- train a K-nearest neighbor model on the transformed inputs and
  transformed target
- restore the predictions of the KNN model to the original `:height`
  scale (i.e., invert the standardization)

```@setup 7
const KNNRegressor = @load KNNRegressor pkg=NearestNeighborModels
```

```julia>
KNNRegressor = @load KNNRegressor
pipe = @pipeline(X -> coerce(X, :age=>Continuous),
				 OneHotEncoder,
				 KNNRegressor(K=3),
				 target = Standardizer())

Pipeline326(
	one_hot_encoder = OneHotEncoder(
			features = Symbol[],
			drop_last = false,
			ordered_factor = true,
			ignore = false),
	knn_regressor = KNNRegressor(
			K = 3,
			algorithm = :kdtree,
			metric = Distances.Euclidean(0.0),
			leafsize = 10,
			reorder = true,
			weights = :uniform),
	target = Standardizer(
			features = Symbol[],
			ignore = false,
			ordered_factor = false,
			count = false)) @287
```

Notice that field names for the composite are automatically generated
based on the component model type names. The automatically generated
name of the new model composite model type, `Pipeline406`, can be
replaced with a user-defined one by specifying, say,
`name=MyPipe`. **If you are planning on serializing (saving) a
pipeline-machine, you will need to specify a name.**.

The new model can be used just like any other non-composite model:

```julia
pipe.knn_regressor.K = 2
pipe.one_hot_encoder.drop_last = true
evaluate(pipe, X, height, resampling=Holdout(), measure=l2, verbosity=2)

[ Info: Training Machine{Pipeline406} @959.
[ Info: Training Machine{UnivariateStandardizer} @422.
[ Info: Training Machine{OneHotEncoder} @745.
[ Info: Spawning 1 sub-features to one-hot encode feature :gender.
[ Info: Training Machine{KNNRegressor} @005.
┌───────────┬───────────────┬────────────┐
│ _.measure │ _.measurement │ _.per_fold │
├───────────┼───────────────┼────────────┤
│ l2        │ 55.5          │ [55.5]     │
└───────────┴───────────────┴────────────┘
_.per_observation = [[[55.502499999999934]]]

```

For important details on including target transformations, see below.

```@docs
@pipeline
```