text:
# installing a [Linux] system
## [Ubuntu-based] systems

To install updates, use `sudo apt update && sudo apt full-upgrade && sudo apt autoremove`.

To install officially supported programs, use `sudo apt install audacity autokey-gtk bless brasero bzr cheese codeblocks curl duc easytag espeak-ng-espeak exfat-fuse exfat-utils exiftool extundelete eyed3 festival filelight filezilla flac focuswriter gedit gimp git-cola gnome-disk-utility gnome-terminal gnumeric gparted gprename graphviz grsync gsmartcontrol idle imagemagick inkscape jekyll jq kcharselect kmag krename lftp lolcat lynx mediainfo meld mercurial moreutils ncdu net-tools pngcrush qtqr recode recoll retext searchmonkey simplescreenrecorder sox surf tesseract-ocr testdisk texlive-fonts-recommended thunderbird tracker transmission-qt trash-cli tree uget unar units unoconv unrar unrtf vlc vnstat zbar-tools -y`.

Also install additional programs using more specific instructions and installation methods:

- [Go](instlGo.md)
- [Node.js and npm with nvm](inNjspv.md)
- [pip](instpip.md)
- [Ruby Version Manager](insRVMr.md)

- [VirtualBox](instVBx.md)
- [youtube-dl](insytdl.md)

### dpkg
- [Atom text editor](insAtom.md) (64-bit systems only)
- [Google Chrome](insGCrm.md) (64-bit systems only)
- Pandoc [from the latest GitHub software release](islGHsr.md)
- [VSCodium](inVSCdm.md)

### npm
- [Lloyd Brookes's renamer](inLBrnm.md)

### pip
- [beets](insbeet.md)
- [MkDocs](insMkDc.md)
- [sqlitebiter](inqbitr.md)

### PPA
- [DB Browser for SQLite](inDBSQL.md)
- [Git](instGit.md)
- [Krita](insKrta.md)
- [qBittorrent](insqBtr.md)

### RubyGems
- [Linguist](insLngst.md)

For Lubuntu, install additional packages using `sudo apt install dolphin kate openjdk-8-jre`.

??? info "Personal experience"
    Tested in Lubuntu 18.04.1.

## explanation

!!! note

    This is an incomplete explanation.

| package name                   | program name                                             | program category                                     | [interface]    | licensing                                                            | predominant programming language
|:-------------------------------|:---------------------------------------------------------|:-----------------------------------------------------|:---------------|:---------------------------------------------------------------------|:-
| `audacity`                     | [Audacity]                                               | [audio editing]                                      | [GUI]          | [GNU GPL v2.0] [^insLnxS6]                                           | [C]
| `autokey-gtk`                  | [AutoKey]                                                | [automation]                                         | [GUI]          | [GNU GPL v3.0] [^insLnxS86]                                          | [Python]
| `bless`                        | [Bless]                                                  | [hex editing]                                        | [GUI]          | [GNU GPL v2.0] [^insLnxS2]                                           | [C#]
| `brasero`                      | [Brasero]                                                | [optical disc authoring]                             | [GUI]          | [GNU GPL v2.0] [^insLnxS88]                                          | [C]
| `bzr`                          | [Bazaar]                                                 | [version control]                                    | [CLI]          | [GNU GPL v2.0] [^insLnxS81] or later [^insLnxS82]                    | [Python]
| `cheese`                       | [Cheese]                                                 | [webcam] recording                                   | [GUI]          | [GNU GPL v2.0] [^insLnxS7]                                           | [C]
| `codeblocks`                   | [Code::Blocks]                                           | [IDE]                                                | [GUI]          | [GNU GPL v3.0] [^insLnxS8] [^insLnxS67]                              | [C++]
| `curl`                         | [Curl]                                                   | [data transmission]                                  | [CLI]          | MIT/X-inspired license[^insLnxS10] [^insLnxS68]                      | [C]
| `duc`                          | [Duc]                                                    | [computer data storage] analysis                     | [CLI] or [GUI] | [GNU GPL v3.0] [^insLnxS47]                                          | [C]
| `easytag`                      | [EasyTag]                                                | [tag editing]                                        | [GUI]          | [GNU GPL v2.0] or later[^insLnxS14]                                  | [C]
| `espeak-ng-espeak`             | [eSpeak NG]                                              | [speech synthesis]                                   | [CLI]          | [GNU GPL v3.0] [^insLnxS23]                                          | [C]
| `exfat-fuse` and `exfat-utils` | [exfat]                                                  | implementation of [exFAT] [file system]              |                | [GNU GPL v2.0] [^insLnxS15]                                          | [C]
| `exiftool`                     | [ExifTool]                                               | [tag editing]                                        | [CLI]          | [GNU GPL v1.0] or later[^insLnxS16] [^insLnxS69]                     | [Perl]
| `extundelete`                  | [extundelete]                                            | [undeletion]                                         | [CLI]          | [GNU GPL v2.0] [^insLnxS17]                                          | [C++]
| `eyed3`                        | [eyeD3]                                                  | [tag editing]                                        | [GUI]          | [GNU GPL v3.0] [^insLnxS18]                                          | [Python]
| `festival`                     | [Festival Speech Synthesis System]                       | [speech synthesis]                                   | [CLI]          | MIT-like license[^insLnxS11]                                         | [C++]
| `filelight`                    | [Filelight]                                              | [computer data storage] analysis                     | [GUI]          | [GNU GPL v2.0] [^insLnxS19]                                          | [C++]
| `filezilla`                    | [FileZilla]                                              | [data transmission] for [FTP]                        | [GUI]          | [GNU GPL v2.0] [^insLnxS70] or later[^insLnxS20]                     | [C++]
| `flac`                         | [FLAC]                                                   | [lossless] [audio] compression [codec]               | [CLI]          | [GNU GPL] [^insLnxS21] [^insLnxS72]                                  | [C]
| `focuswriter`                  | [FocusWriter]                                            | [word processing]                                    | [GUI]          | [GNU GPL v3.0] [^insLnxS22]                                          | [C++]
| `gedit`                        | [gedit]                                                  | [text editing]                                       | [GUI]          | [GNU GPL v2.0] [^insLnxS24]                                          | [C]
| `gimp`                         | [GIMP]                                                   | [image editing] for [raster graphics]                | [GUI]          | [GNU GPL v3.0] [^insLnxS25] [^insLnxS73]                             | [C]
| `git-cola`                     | [Git Cola]                                               | [version control] for [Git]                          | [GUI]          | [GNU GPL v2.0] [^insLnxS9]                                           | [Python]
| `gnome-disk-utility`           | [gnome-disk-utility]                                     | [disk utility] package                               | [GUI]          | [GNU GPL v2.0] [^insLnxS26]                                          | [C]
| `gnome-terminal`               | [GNOME Terminal]                                         | [terminal emulation]                                 | [GUI]          | [GNU GPL v3.0] [^insLnxS27]                                          | [C]
| `gnumeric`                     | [Gnumeric]                                               | [spreadsheet]                                        | [GUI]          | [GNU GPL v3.0] [^insLnxS28]                                          | [C]
| `gparted`                      | [GParted]                                                | [partition editing]                                  | [GUI]          | [GNU GPL v2.0] [^insLnxS29]                                          | [C++]
| `gprename`                     | [GPRename]                                               | [batch renaming]                                     | [GUI]          | [GNU GPL v3.0] [^insLnxS4]                                           | [Perl]
| `graphviz`                     | [Graphviz]                                               | [graph visualization]                                | [CLI]          | [Eclipse Public License 1.0] [^insLnxS30] [^insLnxS31]               | [C]
| `grsync`                       | [Grsync]                                                 | [file synchronization]                               | [GUI]          | [GNU GPL v2.0] [^insLnxS32]                                          | [C]
| `gsmartcontrol`                | [GSmartControl]                                          | [computer data storage] analysis                     | [GUI]          | [GNU GPL v2.0] or [GNU GPL v3.0] [^insLnxS48] [^insLnxS74]           | [C++]
| `idle`                         | [IDLE]                                                   | [IDE]                                                | [GUI]          | [PSFL] [^insLnxS33]                                                  | [Python]
| `imagemagick`                  | [ImageMagick]                                            | [image editing]                                      | [CLI]          | [ImageMagick License] [^insLnxS34]                                   | [C]
| `inkscape`                     | [Inkscape]                                               | [image editing] for [vector graphics]                | [GUI]          | [GNU GPL v3.0] or later[^insLnxS35]                                  | [C++]
| `jekyll`                       | [Jekyll]                                                 | [static site generation]                             | [CLI]          | [MIT License] [^insLnxS36]                                           | [Ruby]
| `jq`                           | [jq]                                                     | [JSON] processing                                    | [CLI]          | [MIT License] for code and [CC BY 3.0] for documentation[^insLnxS37] | [C]
| `kcharselect`                  | [KCharSelect]                                            | [character] selection                                | [GUI]          | various licenses[^insLnxS85]                                         | [C++]
| `kmag`                         | [KMag]                                                   | [screen magnification]                               | [GUI]          | [GNU GPL v2.0] [^insLnxS60]                                          | [C++]
| `krename`                      | [KRename]                                                | [batch renaming]                                     | [GUI]          | [GNU GPL v2.0] [^insLnxS5]                                           | [C++]
| `lftp`                         | [LFTP]                                                   | [file transferring]                                  | [CLI]          | [GNU GPL v3.0] [^insLnxS38]                                          | [C++]
| `lolcat`                       | [lolcat]                                                 | text colorization ([toy program])                    | [CLI]          | unknown license[^insLnxS39]                                          | [Ruby]
| `lynx`                         | [Lynx]                                                   | [text-based web browsing]                            | [CLI]          | [GNU GPL v2.0] [^insLnxS40]                                          | [C]
| `mediainfo`                    | [MediaInfo]                                              | video file and audio file metadata displaying        | [CLI]          | [BSD 2-Clause license] [^insLnxS41] [^insLnxS42]                     | [Pascal]
| `meld`                         | [Meld]                                                   | [file comparison]                                    | [GUI]          | [GNU GPL v2.0] [^insLnxS43]                                          | [Python]
| `mercurial`                    | [Mercurial]                                              | [version control]                                    | [CLI]          | [GNU GPL v2.0] [^insLnxS79]
| `moreutils`                    | sponge, part of [moreutils]                              | [standard stream] manipulation                       | [CLI]          | various licenses (sponge is licensed [GNU GPL v2.0] [^insLnxS44])
| `ncdu`                         | [Ncdu]                                                   | [computer data storage] analysis                     | [CLI]          | [MIT License] [^insLnxS45]                                           | [C]
| `net-tools`                    | [ifconfig], part of [net-tools]                          | [networking] configuration                           | [CLI]          | [GNU GPL v2.0] [^insLnxS3]                                           | [C]
| `openjdk-8-jre`[^insLnxS1]     | the [Open Java Development Kit] Java Runtime Environment
| `pngcrush`                     | [pngcrush]                                               | [PNG] image optimization                             | [CLI]          | libpng-like license [^insLnxS75]                                     | [C]
| `qtqr`                         | QtQR (part of [QR Tools])                                | [QR code] encoding and decoding                      | [GUI]          | [GNU GPL v3.0] (for [QR Tools]) [^insLnxS49] [^insLnxS77]            | [Python]
| `recode`                       | [recode]                                                 | [character encoding] conversion                      | [CLI]          | [GNU GPL v2.0] [^insLnxS50]                                          | [C]
| `recoll`                       | [Recoll]                                                 | [desktop searching]                                  | [GUI]          | [GNU GPL v2.0] [^insLnxS46]                                          | [C++]
| `retext`                       | [ReText]                                                 | [text editing] for [Markdown] and [reStructuredText] | [GUI]          | [GNU GPL v3.0] [^insLnxS51]                                          | [Python]
| `searchmonkey`                 | [Searchmonkey] ([gSearchmonkey])                         | [desktop searching]                                  | [GUI]          | [GNU LGPL v2.1] [^insLnxS52]                                         | [C]
| `simplescreenrecorder`         | [SimpleScreenRecorder]                                   | [screen recording]                                   | [GUI]          | [GNU GPL v3.0] [^insLnxS54] [^insLnxS55]                             | [C++]
| `sox`                          | [SoX]                                                    | [audio editing]                                      | [CLI]          | [GNU GPL v2.0] [^insLnxS78] or later[^insLnxS12]                     | [C]
| `subversion`                   | [Apache Subversion]                                      | [version control]                                    | [CLI]          | [Apache License 2.0] [^insLnxS71]                                    | [C]
| `surf`                         | [surf]                                                   | [web browsing]                                       | [GUI]          | [MIT License] [^insLnxS56]                                           | [C]
| `tesseract-ocr`                | [Tesseract]                                              | [optical character recognition]                      | [CLI]          | [Apache License 2.0] [^insLnxS13]                                    | [C++]
| `testdisk`                     | [TestDisk]                                               | [data recovery]                                      | [CLI]          | [GNU GPL v2.0] [^insLnxS53]
| `texlive-fonts-recommended`    | recommended fonts for [TeX Live]                         |                                                      |                | [GNU GPL v2.0] [^insLnxS57]
| `thunderbird`                  | [Mozilla Thunderbird]                                    | [email]                                              | [GUI]          | [MPL 2.0] [^insLnxS84]
| `tracker`                      | [Tracker]                                                | [desktop searching]                                  | [CLI]          | [GNU LGPL v2.1] or later, [BSD 3-Clause license], and [GNU GPL v2.0] or later [^insLnxS76] | [C]
| `transmission-qt`              | [Transmission]                                           | [file sharing] for [BitTorrent]                      | [GUI] ([Qt])   | [GNU GPL v2.0] or [GNU GPL v3.0] [^insLnxS58]                        | [C]
| `trash-cli`                    | [trash-cli]                                              | [trashing]                                           | [CLI]          | [GNU GPL v2.0] [^insLnxS59]                                          | [Python]
| `tree`                         | [tree]                                                   | [computer data storage] analysis                     | [CLI]          | [GNU GPL v2.0]                                                       | [C]
| `uget`                         | [uGet]                                                   | [download management]                                | [GUI]          | [GNU LGPL v2.1] [^insLnxS83]                                         | [C]
| `unar`                         | [The Unarchiver]                                         | [archive file] unarchiving                           | [CLI]          | [GNU LGPL v2.1] [^insLnxS80]                                         | [C]
| `units`                        | [GNU Units]                                              | [unit conversion]                                    | [CLI]          | [GNU GPL v3.0] or later[^insLnxS87]                                  | [C]
| `unoconv`                      | [unoconv]                                                | [file format] conversion                             | [CLI]          | [GNU GPL v2.0] [^insLnxS61]                                          | [Python]
| `unrar`                        | [UnRAR]                                                  | [RAR] unarchiving                                    | [CLI]          | [trialware]
| `unrtf`                        | [UnRTF]                                                  | [RTF] conversion                                     | [CLI]          | [GNU GPL v3.0] [^insLnxS62]                                          | [C]
| `vlc`                          | [VLC media player]                                       | [media playback]                                     | [GUI]          | [GNU LGPL v2.1] [^insLnxS63] or later [^insLnxS64]                   | [C]
| `vnstat`                       | [vnStat]                                                 | [networking] analysis                                | [CLI]          | [GNU GPL v2.0] [^insLnxS65]                                          | [C]
| `zbar-tools`                   | [ZBar bar code reader]                                   | [barcode reading]                                    | [CLI] or [GUI] | [GNU LGPL v2.1] or later [^insLnxS66]                                | [C]

## licensing
**No rights reserved: [CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/).**

## prior work
- The method of installing GPRename was introduced to me by [an answer on Ask Ubuntu by karel](https://askubuntu.com/questions/1030996/how-can-i-install-pyrenamer-for-bionic/1031003#1031003).
- The method of installing updates was introduced to me by [a post on Reddit by MyNameIsRichardCS54](https://www.reddit.com/r/Kubuntu/comments/99jfb5/every_new_install_of_kubuntu_1804_freezes_up_when/e4qsx0a/).

repository: oronymzy/tips

repo_name: oronymzy/tips


text:
# WIP: work in progress

# Ansible role: fscrypt
File-based encryption on existing ext4 filesystem

## Requirements
Ext4 filesystem and recent kernel with `CONFIG_FS_ENCRYPTION`.
Only tested on Debian stable, for now.

## Role Variables
+ `fscrypt_dirs`: list of paths on which to enable encryption.
  Must be empty prior to encrypting.

## Playbooks
+ `main.yml`: apply role
+ `uninstall.yml`: remove. Run prior to removing host from inventory group.

## Dependencies
None.

## License
+ Ansible role licensed [MIT](LICENSE)

## Author Information
+ Ansible role by [Sean Ho](https://github.com/ho-ansible/)

license: MIT

repository: ho-ansible/fscrypt

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: ho-ansible/fscrypt


text:
A `main` method must be `public`, `static`, and return `void` (see
[JLS §12.1.4]).

For example, the following method is confusing, because it is an overload of a
valid `main` method (it has the same name and signature), but is not a valid
`main` method:

```java
class Test {
  static void main(String[] args) {
    System.err.println("hello world");
  }
}
```

```
$ java T.java
error: 'main' method is not declared 'public static'
```

[JLS §12.1.4]: https://docs.oracle.com/javase/specs/jls/se11/html/jls-12.html#jls-12.1.4

TIP: If you're declaring a method that isn't intended to be used as the main
method of your program, prefer to use a name other than `main`. It's confusing
to humans and static analysis to see methods like `private int main(String[]
args)`.

repository: PicnicSupermarket/error-prone

gha_language: Java

repo_name: PicnicSupermarket/error-prone


text:
---
title: "An Autobiographical Novel"
subtitle:
date: 1991-11-01T06:00:07.000Z
series:
genre: "nonfiction"
subgenre:
  - "memoir"
language:
authors:
  - author/kenneth-rexroth.md
translators:

editors:

contributors:

editions:
  - binding: paperback
    isbn:<PHONE_NUMBER>796
    date: 1991-11-01T06:00:07.000Z
    description: ""
    trim_size: ""
    page_count: ""
    sales_data:
      forsale: false
      saleprice:
      shipping_weight:
      price_us: 23.95
      price_cn:
    contributors:
    cover_image: "/An_Autobiographical_Novel.jpg"
featured_image:
  file:
draft: false
_slug: an-autobiographical-novel
---

When the poet Kenneth Rexroth died in 1982, he left behind a sequel to _An Autobiographical Novel_ (1966). His published memoir––all 365 pages of it––stopped at 1927, when the twenty-two-year-old writer and his first wife, Andrée, were about to settle in California. Now revised and expanded, _An Autobiographical Novel_ includes reminiscences that cover another twenty years of literary life and two more marriages. Linda Hamalian, author of _A Life of Kenneth Rexroth_ (W. W. Norton, 1991), sifted through more than 300 pages of raw tape transcriptions. Weighing fact against fictions (Rexroth loved a tall tale and relished gossip), Hamalian has prepared a valuable index that identifies obscure allusions and the real people who figured in Rexroth’s emotionally tumultuous life. "It adds up to a very good read," she says. "I am willing to bet a nice chunk of money that readers will wish Rexroth had been able to go on and on loosening his talk-tapes."

repository: theNewDynamic/hugo-controllers-panic

repo_name: theNewDynamic/hugo-controllers-panic


text:
# MovieTweetings
## Some stats

Metric | Value
--- | ---
Total number of ratings                 | 721,993
Number of unique users                  | 54,423
Number of unique items                  | 31,543
These stats were last autocalculated on Tue Aug 7 00:48:32 CEST 2018  ([more stats here](./stats.md))

repository: vnekv/MovieTweetings

repo_name: vnekv/MovieTweetings


text:
# Examples
## Run _E. coli_ Example
### Commands
1. Go to a directory to store fmlrc and clone this repository:
```bash
git clone https://github.com/holtjma/fmlrc.git
```
2. Change into the fmlrc example directory:
```bash
cd fmlrc/example
```
3. Run the examples script.  This will automatically install ropebwt2 to a local path, download short- and long-read _E. coli_ data, build the multi-string BWT using ropebwt2 and fmlrc-convert, and lastly run use fmlrc to correct the first 400 reads in the long-read data:
```bash
./run_example.sh
```

### Outputs
1. `./ecoli_comp_msbwt.npy` - this contains the run-length encoded multi-string BWT using the same encoding as the [msbwt](https://github.com/holtjma/msbwt) python package.  Note: if you wish to use this with msbwt, it will need to be placed in it's own directory and renamed to `comp_msbwt.npy` in that directory.  For more information, please refer to the msbwt wiki pages.
2. `./corrected_final.fa` - this contains the first 400 long reads after correction using fmlrc.

repository: wenmm/fmlrc

repo_name: wenmm/fmlrc


text:
ZLHistogramAudioPlot
====================

A hardware-accelerated audio visualization view using EZAudio, inspired by [AudioCopy](https://itunes.apple.com/us/app/audiocopy/id719137307?mt=8). ZLHistogramAudioPlot was originally developed for [Murmur](http://zhxnlai.github.io/#/murmur).

Preview
---

###Buffer
![preview buffer](Previews/ZLHistogramAudioPlotBuffer.gif)

###Rolling
![preview rolling](Previews/ZLHistogramAudioPlotRolling.gif)

CocoaPods
---
You can install `ZLHistogramAudioPlot` through CocoaPods adding the following to your Podfile:

    pod 'ZLHistogramAudioPlot'

Usage
---
Checkout the [demo app](https://github.com/zhxnlai/ZLHistogramAudioPlot/tree/master/EZAudioRecordExample) for an example.

Customizable attributes:
~~~objective-c
/// The upper bound of the frequency range the audio plot will display. Default:
/// 10000Hz
@property (nonatomic) float maxFrequency;

/// The lower bound of the frequency range the audio plot will display. Default:
/// 1200Hz
@property (nonatomic) float minFrequency;

/// The number of bins in the audio plot. Default: 30
@property (nonatomic) NSUInteger numOfBins;

/// The padding of each bin in percent width. Default: 0.1
@property (nonatomic) CGFloat padding;

/// The gain applied to the height of each bin. Default: 10
@property (nonatomic) CGFloat gain;

/// A float that specifies the vertical gravitational acceleration applied to
/// each bin. Default: 10 pixel/sec^2
@property (nonatomic) float gravity;

/// The color of all bins in the audio plot.
@property (strong, nonatomic) UIColor *color;

/// An array of color objects defining the color of each bin in the audio plot.
/// If not set, the color attribute will be used instead. Currently only
/// supported by plot type EZPlotTypeBuffer.
@property (strong, nonatomic) NSArray *colors;
~~~

Dependencies
---
- `ZLHistogramAudioPlot` is a subclass of `EZAudioPlot`. It requires [EZAudio](https://github.com/syedhali/EZAudio).
- It also requires [Accelerate](https://developer.apple.com/library/ios/documentation/Accelerate/Reference/AccelerateFWRef/_index.html) framework for hardware acceleration.

Compatibilty
---
`ZLHistogramAudioPlot` uses the following interface provided by [EZAudio](https://github.com/syedhali/EZAudio) to get audio data:
~~~objective-c
- (void)updateBuffer:(float *)buffer withBufferSize:(UInt32)bufferSize;
~~~
It can be easily modified to work with [Audio Unit](https://developer.apple.com/library/mac/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/Introduction/Introduction.html) and [Core Audio](https://developer.apple.com/library/mac/documentation/MusicAudio/Conceptual/CoreAudioOverview/Introduction/Introduction.html).

Requirements
---
- iOS 6 or higher.
- Automatic Reference Counting (ARC).

License
---
ZLHistogramAudioPlot is available under the MIT license. See the LICENSE file for more info.

repository: Nikhil-Advoco/ZLHistogramAudioPlot

gha_license_id: MIT

repo_name: Nikhil-Advoco/ZLHistogramAudioPlot


text:
# rubato

An audio sample rate conversion library for Rust.

This library provides resamplers to process audio in chunks.

The ratio between input and output sample rates is completely free.
Implementations are available that accept a fixed length input
while returning a variable length output, and vice versa.

### Asynchronous resampling
The resampling is based on band-limited interpolation using sinc
interpolation filters. The sinc interpolation upsamples by an adjustable factor,
and then the new sample points are calculated by interpolating between these points.
The resampling ratio can be updated at any time.

### Synchronous resampling
Synchronous resampling is implemented via FFT. The data is FFT:ed, the spectrum modified,
and then inverse FFT:ed to get the resampled data.
This type of resampler is considerably faster but doesn't support changing the resampling ratio.

### SIMD acceleration
The asynchronous resampler is designed to benefit from auto-vectorization, meaning that the Rust compiler
can recognize calculations that can be done in parallel. It will then use SIMD instructions for those.
This works quite well, but there is still room for improvement.
On x86_64 it will always use SSE3 if available. The speed benefit compared to auto-vectorization
depends on the CPU, but tends to be in the range 20-30% for 64-bit data, and 50-100% for 32-bit data.

### Cargo features
##### `avx`: AVX on x86_64
The `avx` feature is enabled by default, and enables the use of AVX when it's available.
The speed increase compared to SSE depends on the CPU, and tends to range from zero to 50%.
On other architectures than x86_64 the `avx` feature does nothing.

##### `neon`: Experimental Neon support on aarch64
Experimental support for Neon is available for aarch64 (64-bit Arm) by enabling the `neon` feature.
This requires the use of a nightly compiler, as the Neon support in Rust is still experimental.
On a Raspberry Pi 4, this gives a boost of about 10% for 64-bit floats and 50% for 32-bit floats when
compared to the auto-vectorized implementation.
Note that this only works on a full 64-bit operating system.

### Documentation

The full documentation can be generated by rustdoc. To generate and view it run:
```
cargo doc --open
```

### Example
Resample a single chunk of a dummy audio file from 44100 to 48000 Hz.
See also the "fixedin64" example that can be used to process a file from disk.
```rust
use rubato::{Resampler, SincFixedIn, InterpolationType, InterpolationParameters, WindowFunction};
let params = InterpolationParameters {
    sinc_len: 256,
    f_cutoff: 0.95,
    interpolation: InterpolationType::Nearest,
    oversampling_factor: 160,
    window: WindowFunction::BlackmanHarris2,
};
let mut resampler = SincFixedIn::<f64>::new(
    48000 as f64 / 44100 as f64,
    params,
    1024,
    2,
);

let waves_in = vec![vec![0.0f64; 1024];2];
let waves_out = resampler.process(&waves_in).unwrap();
```

### Compatibility

The `rubato` crate requires rustc version 1.40 or newer.

License: MIT

repository: JoNil/rubato

repo_name: JoNil/rubato


text:
[![CircleCI](https://circleci.com/gh/jbelyeu/unfazed/tree/master.svg?style=svg)](https://circleci.com/gh/jbelyeu/unfazed/tree/master)
[![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/unfazed/README.html)

# Unfazed: phasing tool for _de novo_ SNVs and SVs
Unfazed identifies the parent of origin for _de novo_ variants, accepting input from either a vcf file or bed file of variant information. Unfazed works for point mutations (SNVs and INDELs) as well as larger structural mutations. Also see (and cite) our Bioinformatics paper at https://academic.oup.com/bioinformatics/article/37/24/4860/6306405.

## How it works
### Extended read-backed phasing (SNV/INDEL/DEL/DUP/INV)
Unfazed identifies 'informative sites' upstream or downstream from a _de novo_ variant, using a VCF/BCF of SNVs for the trio (the child and both parents). These informative sites are variants inherited from the parents that allow identification of the origin of the read (maternal or paternal).

Informative sites must be HET in the child and discernibly different in parents, specifically HOM_REF|HOM_ALT, HET|HOM_ALT, or HET|HOM_REF. These patterns allow identification of the parent of origin for the allele found at that site in each read spanning the region.

Extended read-backed phasing adds sensitivity by chaining reads together using mutually overlapped heterozygous sites, i.e. if two reads have the same allele for a given het site, those reads must come from the same parent. This allows the search distance from a given de novo variant to extend farther than possible with a single read pair.

Caveat: unfazed is not a variant validation tool, and assumes variants to phase are accurate _de novo_ calls.

### Allele-balance CNV phasing (DUP/DEL)
Unfazed also applies an additional phasing technique to copy-number variants (CNVs), by using the allele balance of heterozygous sites are found **inside** the copy-altered region.
* In a deletion, the allele of the _de novo_ CNV's origin parent disappears and therefore the site should appear to be HOM_REF for the other parent's allele (although actually hemizygous).
* In a duplication, the allele balance of the _de novo_ CNV's origin parent should be about double in proportion to the allele from the other parent. If parents share no alleles, this is fairly simple: if the allele balance of the alelle from parent A increases relatively, that is the origin parent. If the parents share one allele (one parent being HET, the other HOMREF or HOMALT) the DUP can only be phased if the non-shared allele is duplicated, as an increase in allele balance of the shared allele could come from a duplication in either parent. Unfazed requires an allele-balance of 0.66 in favor of the duplicated allele for each informative site.

### Sex-chromosome autophasing
Variants which lie on the X chromosome in male samples can generally be automatically phased to the mother and those from the Y can be phased to the father. The pseudoautosomal region (PAR) is the exception, where the X and Y are indistinguishable. Unfazed will therefore perform read-based or allele-balance phasing for PAR variants but will automatically phase other sex chromosome variants in males. This requires genome build information which is specified via the `--build` parameter. Build defaults to build 38 and works for HG38 and GRCh38. Note that only human genome builds 19/37 and 38 are supported for special sex-chromosome phasing.

## How to use it
Unfazed is available for install from conda. Requires at least Python 3.5.

`conda install -c bioconda unfazed `

  Unfazed options:

  ```

UNFAZED v1.0.2
usage: unfazed [-h] [-v] -d DNMS -s SITES -p PED [-b BAM_DIR] [--bam-pairs [BAM_PAIRS [BAM_PAIRS ...]]] [-t THREADS] [-o {vcf,bed}] [--include-ambiguous] [--verbose]
               [--outfile OUTFILE] [-r REFERENCE] -g {37,38,na} [--no-extended] [--multiread-proc-min MULTIREAD_PROC_MIN] [-q] [--min-gt-qual MIN_GT_QUAL]
               [--min-depth MIN_DEPTH] [--ab-homref AB_HOMREF] [--ab-homalt AB_HOMALT] [--ab-het AB_HET] [--evidence-min-ratio EVIDENCE_MIN_RATIO]
               [--search-dist SEARCH_DIST] [--insert-size-max-sample INSERT_SIZE_MAX_SAMPLE] [--min-map-qual MIN_MAP_QUAL] [--stdevs STDEVS] [--readlen READLEN]
               [--split-error-margin SPLIT_ERROR_MARGIN] [--max-reads MAX_READS]

optional arguments:
  -h, --help            show this help message and exit
  -v, --version         Installed version (1.0.2)
  -d DNMS, --dnms DNMS  valid VCF OR BED file of the DNMs of interest> If BED, must contain chrom, start, end, kid_id, var_type columns (default: None)
  -s SITES, --sites SITES
                        sorted/bgzipped/indexed VCF/BCF file of SNVs to identify informative sites. Must contain each kid and both parents (default: None)
  -p PED, --ped PED     ped file including the kid and both parent IDs (default: None)
  -b BAM_DIR, --bam-dir BAM_DIR
                        directory where bam/cram files (named {sample_id}.bam or {sample_id}.cram) are stored for offspring. If not included, --bam-pairs must be set
                        (default: None)
  --bam-pairs [BAM_PAIRS [BAM_PAIRS ...]]
                        space-delimited list of pairs in the format {sample_id}:{bam_path} where {sample_id} matches an offspring id from the dnm file. Can be used with
                        --bam-dir arg, must be used in its absence (default: None)
  -t THREADS, --threads THREADS
                        number of threads to use (default: 2)
  -o {vcf,bed}, --output-type {vcf,bed}
                        choose output type. If --dnms is not a VCF/BCF, output must be to BED format. Defaults to match --dnms input file (default: None)
  --include-ambiguous   include ambiguous phasing results (default: False)
  --verbose             print verbose output including sites and reads used for phasing. Only applies to BED output (default: False)
  --outfile OUTFILE     name for output file. Defaults to stdout (default: /dev/stdout)
  -r REFERENCE, --reference REFERENCE
                        reference fasta file (required for crams) (default: None)
  -g {37,38,na}, --build {37,38,na}
                        human genome build, used to determine sex chromosome pseudoautosomal regions. If `na` option is chosen, sex chromosomes will not be auto-phased.
                        HG19/GRCh37 interchangeable (default: None)
  --no-extended         do not perform extended read-based phasing (default True) (default: False)
  --multiread-proc-min MULTIREAD_PROC_MIN
                        min number of variants required to perform multiple parallel reads of the sites file (default: 1000)
  -q, --quiet           no logging of variant processing data (default: False)
  --min-gt-qual MIN_GT_QUAL
                        min genotype and base quality for informative sites (default: 20)
  --min-depth MIN_DEPTH
                        min coverage for informative sites (default: 10)
  --ab-homref AB_HOMREF
                        allele balance range for homozygous reference informative sites (default: 0.0:0.2)
  --ab-homalt AB_HOMALT
                        allele balance range for homozygous alternate informative sites (default: 0.8:1.0)
  --ab-het AB_HET       allele balance range for heterozygous informative sites (default: 0.2:0.8)
  --evidence-min-ratio EVIDENCE_MIN_RATIO
                        minimum ratio of evidence for a parent to provide an unambiguous call. Default 10:1 (default: 10)
  --search-dist SEARCH_DIST
                        maximum search distance from variant for informative sites (in bases) (default: 5000)
  --insert-size-max-sample INSERT_SIZE_MAX_SAMPLE
                        maximum number of read inserts to sample in order to estimate concordant read insert size (default: 1000000)
  --min-map-qual MIN_MAP_QUAL
                        minimum map quality for reads (default: 1)
  --stdevs STDEVS       number of standard deviations from the mean insert length to define a discordant read (default: 3)
  --readlen READLEN     expected length of input reads (default: 151)
  --split-error-margin SPLIT_ERROR_MARGIN
                        margin of error for the location of split read clipping in bases (default: 5)
  --max-reads MAX_READS
                        maximum number of reads to collect for phasing a single variant (default: 100)
```

Many of the above optional arguments consist of options for user-defined deviation from tested defaults. For example, the `--stdevs` options allow a user to alter the definition of a discordant read. By default, it is defined as a paired-end read in which the insert size is greater than 3 standard deviations above the mean, and where mean is calculated from the first million reads in an alignment file, excluding the top 0.5%. A user can decide to alter the number of standard deviations for greater or lesser sensitivity to discordant pairs, but the set defaults are used for all testing and are generally recommended.

### A simple use case is:

```
unfazed\
  -d mydenovos.vcf.gz\
  -s sites.vcf.gz\
  -p myped.ped\
  -g 38 \
  --bam-pairs a_sample:a_sample.bam
```
This will print an annotated vcf file of phased variants. Note that unfazed requires each input VCF to have the `GT`, `AD`, and `GQ` fields.

### Unfazed will also accept a bed file as input:

```
unfazed\
  -d mydenovos.bed\
  -s sites.vcf.gz\
  -p myped.ped\
  -g 38 \
  --bam-pairs a_sample:a_sample.bam
```

This will print a bed file of phased variants. The input bed file must have the following tab-separated columns: chrom, start, end, kid_id, var_type, where var_type is SNV, INDEL, POINT, DEL, DUP, INV, INS, MEI, or BND.

## Unfazed input and output
Unfazed will accept as input either a valid VCF file of _de novo_ variants or a BED file with fields described below. Output can be either an annotated VCF or a BED file.

### VCF annotations
Unfazed adds two tags to the FORMAT field of the VCF.
* UOPS: support for the UOP call (count of informative sites)
* UET: evidence type(s) for the UOP call, which may be 0 (readbacked), 1 (allele-balance, for CNVs only), 2 (both readbacked and allele-balance), 3 (ambiguous-
readbacked), 4 (ambiguous-allele-balance), 5 (ambiguous-both), -1 (missing).

#### Important notes:
* Unfazed replaces `/` with `|` in the GT tag for phased variants to indicate phasing, following the phase order paternal|maternal.

* VCF output is only possible when `--dnms` is a VCF file.

* Unfazed is not effective for SV types that have neither clear discordant pair evidence nor a copy-number impact. Thus, it does not work for insertion variants (INS) or breakends (BNDs).

#### VCF lines before annotation with unfazed:

```
22	16256430	.	A	G	453874	PASS	AC=3;AF=0.495;AN=6	GT:AD:DP:GQ:PL	0/1:17,12:29:99:267,0,418	0/1:11,9:20:99:206,0,266	0/1:17,15:32:99:347,0,410
22	16256512	.	T	C	834865	PASS	AC=3;AF=0.494;AN=6  GT:AD:DP:GQ:PL	0/1:10,14:24:99:343,0,224	0/1:13,11:24:99:254,0,312	0/1:26,20:46:99:478,0,660
22	30857373	.	A	C	939637	PASS	AC=3;AF=0.63;AN=6	GT:AD:DP:GQ:PL	0/1:47,47:94:99:1478,0,1355	0/1:48,38:86:99:1166,0,1416	0/1:72,73:145:99:2241,0,1931
22	30857448	.	A	G	815602	PASS	AC=3;AF=0.606;AN=6	GT:AD:DP:GQ:PL	0/1:32,31:63:99:861,0,932	0/1:33,40:73:99:1058,0,876	0/1:60,66:126:99:1904,0,1635
```
#### After:

22	16256430	.	A	G	453874	PASS	AC=3;AF=0.495;AN=6	GT:AD:DP:GQ:PL:UOPS:UET	0/1:17,12:29:99:267,0,418:-1:-1	0/1:11,9:20:99:206,0,266:-1:-1	0/1:17,15:32:99:347,0,410:-1:-1
22	16256512	.	T	C	834865	PASS	AC=3;AF=0.494;AN=6	GT:AD:DP:GQ:PL:UOPS:UET	0/1:10,14:24:99:343,0,224:-1:-1	0/1:13,11:24:99:254,0,312:-1:-1	0/1:26,20:46:99:478,0,660:-1:-1
22	30857373	.	A	C	939637	PASS	AC=3;AF=0.63;AN=6	GT:AD:DP:GQ:PL:UOPS:UET	1|0:47,47:94:99:1478,0,1355:2:0	0/1:48,38:86:99:1166,0,1416:-1:-1	0/1:72,73:145:99:2241,0,1931:-1:-1
22	30857448	.	A	G	815602	PASS	AC=3;AF=0.606;AN=6	GT:AD:DP:GQ:PL:UOPS:UET	1|0:32,31:63:99:861,0,932:2:0	0/1:33,40:73:99:1058,0,876:-1:-1	0/1:60,66:126:99:1904,0,1635:-1:-1

The GT alleles are separated with `|` for phased variants (where FORMAT fields are __bold__). The added UOPS and UET tags are added to each record, with -1 for variants/samples that were not phased.

### BED output
Either VCF or BED input can produce a BED as output, with the following columns:
```
chrom	start	end	vartype	kid	origin_parent	other_parent	evidence_count	evidence_types
```

Additional information can be included by using the `--verbose` option, which will append the following columns

```
chrom	start	end	vartype	kid	origin_parent	other_parent	evidence_count	evidence_types	origin_parent_sites	origin_parent_reads	other_parent_sites	other_parent_reads
```

Evidence counts and types in BED output match those in VCF output.

#### BED input
```
#chrom	start	end	kid_id	var_type
22	16256429	16256430	NA12878	POINT
22	16256511	16256512	NA12878	POINT
22	16266919	16266920	NA12878	POINT
22	16277851	16277852	NA12878	POINT
22	18571007	18571008	NA12878	POINT
22	18844941	18844942	NA12878	POINT
22	21088145	21088146	NA12878	POINT
22	21141299	21141300	NA12878	POINT
22	30857372	30857373	NA12878	POINT
22	30857447	30857448	NA12878	POINT

```
#### BED output (no entries for variants that cannot be phased)
```
#chrom	start	end	vartype	kid	origin_parent	other_parent	evidence_count	evidence_types
22	18844941	18844942	POINT	NA12878	NA12892	NA12891	1	READBACKED
22	21088145	21088146	POINT	NA12878	NA12892	NA12891	1	READBACKED
22	21141299	21141300	POINT	NA12878	NA12892	NA12891	2	READBACKED
22	30857372	30857373	POINT	NA12878	NA12891	NA12892	2	READBACKED
22	30857447	30857448	POINT	NA12878	NA12891	NA12892	2	READBACKED

```

**Ambiguous results** derive from inconsistent phasing (different parent of origin indicated by different informative sites or reads. These may indicate sequencing errors or mosaic events and will *not* be reported unless the `--include-ambiguous` argument is included.

## Performance
Many variants lack informative sites and are therefore can't be phased. Unfazed also makes no attempt to phase multiallelic sites (which should be very rare among _de novo_ calls). Generally a little under 30% of _de novo_ SNVs/INDELs are phaseable via unfazed, and about 50% of CNV/SV variants. These results may very by quite a bit, depending on the factors like the types of variants. For example, INDELs caused by short tandem repeats are less likely to accurately phase than other INDELs. Large CNVs are also more likely to phase than other SV types, as they are more likely to contain usable informative sites for allele-balance phasing. Unfazed has also been exclusively texted with relatively deep sequencing data (30x coverage or more) and will be less effective with lower depth sequencing.

The runtime of unfazed is highly dependent on the size of the sites VCF, as well as the number of variants and coverage depth. A multithreaded approach is used to improve runtime; however, as the operations are bound by file IO, using more than 2 threads yields diminishing returns (and can even cause a slowdown due to race conditions). Running with 2 threads (default option) is therefore recommended. (Expert note: running with 1 thread can often produce more informative error messages in the case of a silent failure).

Unfazed was tested on a set of 29,029 _de novo_ SNVs/INDELs for a set of 603 samples in the CEPH-Utah cohort, with a set of 19,905,682 variants in the `--sites` vcf. This very large input set finished in 58.6 hours with two process threads, a total of 111.5 hours of runtime with 13.8 seconds per input variant.

repository: jbelyeu/unfazed

repo_name: jbelyeu/unfazed


text:
# Stockify

_An innovative platform to trade stocks and manage your portfolio._

This is an update and improvement over my original [StockTradr](http://stocktradrapp.herokuapp.com/) app.
Link: _coming soon!_

<!-- Deployed Link: [Stockify](http://stocktradrapp.herokuapp.com/) -->

## Stockify Features

* Purchase and Sell Stocks
  * Ticker Dropdown Autocomplete
* View All Transactions
  Transaction information includes: Date, Type, Symbol, Shares, Price, and Total

* View Portfolio
  Portfolio details include Total Value, Symbol, Shares, Change, and Current Value

* Current Cash Balance

## Screenshots

_coming soon_

<!-- ![Image of Login](/images/login.png)
![Image of Portfolio](/images/portfolio.png)
![Image of Transactions](/images/transactions.png) -->

## Technologies

HTML, CSS, JavaScript, React, Redux, PostgreSQL, Sequelize, Node.js, Express, IEX Cloud Api,

repository: chrischindev/Stockify

gha_language: JavaScript

repo_name: chrischindev/Stockify


text:
**History Commands**
If [user] is omitted, these commands default to you.
**Look up someone's schedule history** `+hist [user] [page]`
**Look up someone's full schedule history** `+histfull [user] [page]`
Full history does not merge any attempts and shows indices.
You need these indices to edit past schedules.

All dates must be in `yyyy-mm-dd` format, such as `2020-04-07`
**Add a schedule in the past** `+histadd [schedule-name] [start-date]`
**Remove a schedule in the past** `+histdel [index]`

__Moderators only__
**Add a schedule to someone's history** `+histadd [schedule-name] [start-date] [user]`
**Remove a schedule from someone's history** `+histdel [index] [user]`
**Set adapted to someone in the past** `+histadapt [index] [adapted-date] [user]`
**Verify someone's history** `+histverify [user]`
Editing history will automatically unverify the user's schedule. This protects the integrity of the database from being maliciously modified.
The purpose of these commands is to ensure the accuracy of the database to allow global scheduling statistics, such as success rate for each schedule and schedule popularity.


text:
# Installers from packages

## Centos 7

To build the package (if needed or if you want to make some changes) get the rpmbuild-imzabbix-1.0-Centos7.tar.gz, uncompress it and run the next command from the rpmbuild directory:

```sh
rpmbuild -v -bb --clean SPECS/imzabbix-agent.spec
```

Check into RPMS/x86_64/ that imzabbix-agent-1.0-1.el7.centos.x86_64.rpm is generated.

To install the package run:

```sh
rpm -ivh imzabbix-agent-1.0-1.el7.centos.x86_64.rpm
```

The software will be installed at /opt/imzabbix-agent-1.0

The file get-access-token.sh is a useful tool to get an access_token and a token_refresh from IAM, giving the user and password for IAM, and client ID/client secret credentials; this can be done with the grant type password. Replace the label with the respective value into the script.

```sh
IAM_USER='__IAM_USER__'
IAM_PASSWORD='__IAM_PASSWORD__'

client_secret='__CLIENT_SECRET__'
client_id='__CLIENT_ID__'
```

Then launch it.

```sh
sh get-access-token.sh
```

You can obtain a response like it follows:
```
{"access_token":"eyJraWQiOiJy...c2qXq_Vo","token_type":"Bearer","refresh_token":"eyJhbGci...Tc2N2YifQ.",
"expires_in":3599,"scope":"address phone openid email profile offline_access","id_token":"eyJraWQi...vmYH_o"}
```
The main script to execute the imzabbix agent is probeim.py. This script needs some information to communicate with IAM, with Infrastructure Manager (IM) and with Zabbix.

Assuming that your zabbix user is "Admin" and password is "zabbix", from shell you can execute the agent like it follows:

```sh
python probeim.py -i $CLIENT_ID -s $CLIENT_SECRET -t $TOKEN -r $REFRESH -u Admin -p zabbix -v $ZABBIX_SERVER -a $ZABBIX_API_URL
```

For an easy use, the script setimzabbixvar.sh sets this variables and launch the command, so you can configure this script by replacing the labels by the respective values.

```sh
CLIENT_ID=__CLIENT_ID__
CLIENT_SECRET=__CLIENT_SECRET__
TOKEN=__IAM_TOKEN__
REFRESH=__REFRESH_TOKEN__
ZABBIX_SERVER=__ZABBIX_SERVER_IP__
ZABBIX_API_URL=http://__ZABBIX_WEB_IP__/api_jsonrpc.php
```

repository: indigo-dc/Monitoring

repo_name: indigo-dc/Monitoring


text:
# Introduction

This document specifies the implementation of the Software Trace
Module. The purpose of this module is to allow software running on a
processor core to emit trace events. The trace events tuples of and
identifier `ID` and a `value`. The trace events are further annotated
with a timestamp. By that the developer can use software tracing for a
variety of purposes, for example:

- Annotate the source code to perform timing measurements

- Correlate software execution of different cores

- Simply as a replacement for printf-debugging

- Transfer small data amounts between the software and a debug tool

Software tracing is minimally intrusive, meaning it does only consume
a few processor cycles. Hence it generally allows to keep a minimal
set of trace debug information in productive code.

## License

This work is licensed under the Creative Commons
Attribution-ShareAlike 4.0 International License. To view a copy of
this license, visit
[http://creativecommons.org/licenses/by-sa/4.0/](http://creativecommons.org/licenses/by-sa/4.0/)
or send a letter to Creative Commons, PO Box 1866, Mountain View, CA
94042, USA.

You are free to share and adapt this work for any purpose as long as
you follow the following terms: (i) Attribution: You must give
appropriate credit and indicate if changes were made, (ii) ShareAlike:
If you modify or derive from this work, you must distribute it under
the same license as the original.

## Authors

Stefan Wallentowitz

Fill in your name here!

# Core Interface: Software Trace Port

The software trace port is a simple data port with an `enable`
signal. There is no backpressure as the debug infrastructure is not
supposed to influence the processor execution.

The interface is defined as:

 Name     | Width       | Description
 -------- | ----------- | -----------
 `id`     | 16          | Trace identifier
 `value`  | `REG_WIDTH` | Trace value, width of CPU general purpose registers
 `enable` | 1           | Trace an event this cycle

# Memory Map

The basic memory map of control and status applies. Beside this there
are currently no registers available.

# Trace Primitives

Generally, the trace primitives are divided in a groups:

 Identifiers         | Group | Description
 ------------------- | ----- | -----------
 `0x0000`            | N/A   | Not used
 `0x0001` - `0x3fff` | USER  | User-defined trace events
 `0x4000` - `0x7fff` | COM   | Commonly defined trace events
 `0x8000` - `0xbfff` | N/A   | Reserved
 `0xc000` - `0xffff` | SYS   | System-generated trace events

The implementation of all trace events is optional, both for software
and for hardware.

## User-defined trace events (USER)

Trace events from this group are generated from software
execution. There are many possibilities to implement them in hardware,
but from the ABI there are generally two data items that a software
writes to emit a trace event: first it writes the `value` and then it
writes the `id`.

As those are two memory accesses in two distinct operations the
following properties must hold:

 - Sequential consistency: The write to the second data item must
   occur after the first data item. This property is usually enforced
   with memory fences.

 - Atomicity: The first data item must not be changed in multithreaded
   systems or by interrupt processing in general.

For more details see the section *Trace Generation* in the following.

## Commonly defined trace events (COM)

Those are trace events identical to the user-defined trace events, but
that have a commonly defined semantic meaning. Their semantic meaning
is therefore still transparent to the hardware module, but common to
all platforms. This eases implementation of trace debugger tools.

You can find a list of events at the end of this specification.

## System-generated trace events (SYS)

This group of trace events are generated by the hardware or by the
operating/runtime system. For the latter the same method as
user-defined trace events is used. For hardware-generated events the
method of emitting the trace event is core-specific and examples are
described in the the section *Trace Generation*.

# Trace generation

The method of emitting a trace event depends on the
micro-architecture. Examples for existing processor core architectures
are given in the following.

## Software Trace Port: OpenRISC

In OpenRISC an interesting property of the instruction set is used:
The no-operation `l.nop` has a parameter `K` of 16 bit width. The
specification defines this parameter to be used for simulation
purposes, and it is here used to emit the trace value.

We use this operation for the trace identifier. As the compiler emits
`l.nop 0x0`, the user-defined value of `0x0000` is not available in
this specification.

The trace value is defined to be written to the general purpose
register `r3` with the properties described before. As a general
purpose register is restored after interrupts, the atomicity property
holds. Finally, the register `r3` is the first function parameter
register in the ABI which eases efficient implementation of library
functions for trace events.

In the hardware implementation the writeback stage must be observed
and whenever a write to register `r3` is observed, the same value is
stored into the register `value`. When completion of an `l.nop`
operation is observed, the opeand `K` (if not equal to 0) and the
`value` are emitted on the trace port for one cycle.

Finally, the following extension is required to support the trace
event `THREAD_SWITCH`: All writes to register `r10` must be tracked
and if a value is written, the trace event is emitted. The register is
historically reserved and in the Linux port used as thread-local
storage (TLS), which is unique for concurrently executed threads.

## Software Trace Port: RISC-V

In RISC-V an additional control register is added to emit a trace
event (non-standard for the moment). A write to this register triggers
the emission of the trace event for one cycle.

Beside this, the general purpose register `x10` (`a0`) is tracked for
updates as the trace event value, identical to the reasoning for
OpenRISC.

Finally the register `x4` (`tp`) may also be tracked and a
`THREAD_SWICH` trace event is emitted on updates to the register.

## Software Trace Port: Other cores

The method described for the RISC-V microarchitecture should be
applicable to a variety of RISC cores.

## Software Trace Port: Out-of-Order

With out-of-order cores it is important to track the accesses to the
two data items properly, which can be enforced by a memory fence.

In an out-of-order implementation the software trace port may be
implemented more efficiently at stages where the trace event may still
be canceled. If that is the case, the software trace port should hold
back the value until it can be safely emitted or aborted beforehand.

# List of Trace events

## Commonly defined (COM group)

 Identifier | Name          | Description
 ---------- | ------------- | -----------
 `0x4000`   | `THREAD_NAME` | Emit a thread name, emitted repeatedly

## System-generated (SYS group)

 Identifier | Name            | Description
 ---------- | --------------- | -----------
 `0x8000`   | `THREAD_SWITCH` | Unique value of the scheduled thread


text:
---
tags: perl
layout: post
title: "Overview of work to do for Perl 6"
---

Re: Perl 6 timeline? - This seemed like a good overview from Larry. I haven't been paying attention at all except for glancing at Piers's summaries from time to time. Don't want to get my hopes up too soon...

gha_language: CSS


text:
# Semantic Git Hooks

This repository contains implementation of git hooks as pure bash scripts.
Goal of implemented hooks is to support idea of semantic releases. So it
restricts developer from doing meaningless, improper formatted commits. As a
result it would allow automate tracking changes just in git and provides
an ability to automate changelog creation on releases.

Currently it provides the following hooks:

  - `commit-msg` This hook checks for the correct message format and performs
    spell-checking of the commit message.
  - `pre-commit` Verifies that committed changes is correctly spelled

Spell checking is based on external tools. Currently it supports `hunspell` and
`aspell`. On some systems you may be required to install one of these tools
manually.

## Installing

You may install this repository as a submodule of your repo or simply clone it
to your repo and remove `.git` directory from the cloned repo:

### Install As Submodule

~~~bash
cd ./my/project/workdir
git submodule add https://github.com/Mikhus/.git-hooks.git
./.git-hooks/scripts/init
git commit -am "chore: added .git-hooks as submodule to qualify commits"
git push
~~~

Now anyone would be able to pull `.git-hooks` from your repo. If you want to
rely on your personal hooks implementation, feel free to fork it and submodule
from your own or organization fork, so you would be able to manage your own
changes and still will have possibility to merge from a source repo if needed.

When anyone is cloning your repository first, make sure adding `--recursive`
option to clone command, as:

~~~bash
git clone --recursive [your_repo_url]
~~~

### Installing As Part of Your Repo

~~~bash
cd ./my/project/workdir
git clone git@github.com:Mikhus/.git-hooks.git
rm -rf .git-hooks/.git
./.git-hooks/scripts/init
git commit -am "chore: added .git-hooks as submodule to qualify commits"
git push
~~~

Now you may commit and `.git-hooks` to your project repo to share it between
teammates.

## Enabling/Disabling

As simple as:

~~~bash
cd ./my/project/workdir

# Enabling
./.git-hooks/scripts/init
# or, if you want to enable only specific hooks
./.git-hooks/scripts/init commit-msg

# Disabling
./.git-hooks/scripts/reset
~~~

You may want to automatically enable hooks for everyone in your team. There is
no other way to do it only by imploding the `init` command, for example in your
install or build tool, so whenever someone will run install or build the hooks
will be automatically initialized. For example in your `Makefile`:

~~~Makefile
SCRIPT_ROOT = .git-hooks/scripts

all: init
.PHONY: all

init:
	@$(SCRIPT_ROOT)/init
.PHONY: init
~~~

Or in your `package.json`

~~~json
{
  "name": "my-cool-project",
  "version": "1.0.0",
  "scripts": {
    "start": "./.git-hooks/scripts/init ; /usr/bin/env node ./index.js",
    "install": "./.git-hooks/scripts/init"
  }
}
~~~

I guess you've caught an idea :)...

Of course it does not give a 100% warranty that improper commits will be
published, but that may be achieved only with installing server-side hooks and
that option is not always available, so having at least this kind of protection
is better than nothing.

## Scripts

This is not only hooks repo. There are couple of other useful scripts delivered
under `script` directory

  - `init/reset` - already described, them are used to disable/enable hooks
  - `spell` - mostly used to perform spell-checking of the given input. Accepts
    two arguments - string (or multiline string) input and verification type.
    Second one is optional, but relies on a git work directory, so will try
    to find all the places where misspelled words in a current commit diff.
    With a single argument would treat it as a commit message, but who prevents
    of using it in other ways, or in another hooks? Examples:
    ~~~bash
    ./.git-hooks/scripts/spell "Wht wng with you?"
    ./.git-hooks/scripts/spell "$(git diff --cached | grep -e "^+[^+]")" "git"
    ~~~
  - `version` - assumes your git repository uses semantic version tagging
    for your releases. If so, may help to determine semantic version of
    current commit or to build the next release version tag, for example:
    ~~~bash
    # get current version
    ./.git-hooks/scripts/version
    # get next prerelease version
    ./.git-hooks/scripts/version prerelease
    # get next patch version
    ./.git-hooks/scripts/version patch
    # get next minor version
    ./.git-hooks/scripts/version minor
    # get next major version
    ./.git-hooks/scripts/version major
    ~~~
    It is safe to run as it does not modify your repository. This could be
    useless on NPM based developments, but can be dramatically helpful in many
    other cases.

## License

[ISC](https://rawgit.com/Mikhus/.git-hooks/master/LICENSE)

Happy Coding!

license: ISC


text:
# Germslitospora savoryi (C. Booth) Lodha, 1978 SPECIES

#### Status
SYNONYM

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

#### Published in
Taxonomy of Fungi (Proc. int. Symp. Madras, 1973), Pt 1 250 (1978)

#### Original name
Thielavia savoryi C. Booth, 1961

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Ascomycota/Sordariomycetes/Coniochaetales/Coniochaetaceae/Coniochaeta/Coniochaeta savoryi/ Syn. Germslitospora savoryi/README.md

repo_name: mdoering/backbone


text:
# Orleans.Sagas
A distributed saga implementation for Orleans

[![.NET Core](https://github.com/OrleansContrib/Orleans.Sagas/workflows/.NET%20Core/badge.svg)](https://github.com/OrleansContrib/Orleans.Sagas/actions?query=workflow%3A%22.NET+Core%22)
[![NuGet](https://img.shields.io/nuget/v/Orleans.Sagas.svg?style=flat)](https://www.nuget.org/packages/Orleans.Sagas)
[![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/OrleansContrib/Orleans.Sagas?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)

# Project Status
The library is currently in user acceptance testing with its first major consumer and is therefore **not recommended for production use** yet and will likely require subsequent API changes prior to a supported release.

The [NuGet package](https://www.nuget.org/packages/Orleans.Sagas) is available as a preview, and in the absence of detailed documentation, the [gitter chat](https://gitter.im/OrleansContrib/Orleans.Sagas) is a good place to start.

# Usage

## Installing
Install the [NuGet package](https://www.nuget.org/packages/Orleans.Sagas) with a package manager.

## Configuring Orleans for sagas
Add the following statements to your Orleans silo builder, and don't forget **you'll need reminders and a default storage provider** configured for durability.
```csharp
.UseOrleans(siloBuilder =>
{
    siloBuilder
        .UseSagas()
        .ConfigureApplicationParts(parts =>
        {
            parts.AddSagaParts();
        })
        ...
}
```

## Designing activity configs
```csharp
public class BookHireCarConfig
{
    public bool IsClownCar { get; set; }
    public int HireCarModel { get; set; }
    public Guid HireCarRequestGuid { get; set; }
}
```

## Designing activities
```csharp
public class BookHireCarActivity : Activity<BookHireCarConfig>
{
    public override async Task Execute()
    {
        // idempotently request a hire car from a hire car service.
        await HireCarService.Book(Config.HireCarRequestGuid, Config.IsClownCar);
    }

    public override async Task Compensate()
    {
        // idempotently cancel a hire car request from a hire car service.
        await HireCarService.Cancel(Config.HireCarRequestGuid);
    }
}
```

## Executing a saga
```csharp
// create a saga builder.
var sagaBuilder = GrainFactory.CreateSaga();

// add activities to your saga, and optional associated configuration.
sagaBuilder
    .AddActivity<BookHireCarActivity, BookHireCarConfig>(x => x.HireCarModel = 1)
    .AddActivity<BookHotelActivity>()
    .AddActivity<BookPlaneActivity>()

// execute the saga (idempotent).
var saga = await sagaBuilder.ExecuteSaga();

// abort the saga (idempotent).
await saga.RequestAbort();
```


text:
# P2P network between browsers

The main goal of this project is to create an overlay network formed by browsers.

The connection is made with WebRTC with the help of a server only for signaling that is mandatory in WebRTC, for the initial bootstrap and to keep an up to date list of all connected peers for our project. Everything else is browser's duty.

## Application

To test our overlay network we implemented a chat room that allows messages between everyone or a direct message system that allows messaging or file transfer. All this is done without any direct connections if both peers aren't directly connected. All data is routed through the overlay network.

## Signaling

The mentioned signaling is only used when two peers want to establish a connection.
In order to to establish the connection both ends should know that will. To make that happen the signaling server does it's job, deliver the *Offer*.
That *Offer* is an SDP packet that contains all the parameters about the connection that can be established. A peer that receives an *Offer* answers with an *Answer* with the same thing but for his connection.

When an *Answer* arrives the connection between those two peers is established and ready to be used for both data transfer, for audio and/or video transfer or for both.

## API

The file *webrtc.js* provides an API for sending messages or files.

The functions `sendMessage()` and `sendFile()` allow us to send a message or a file between any two peers in the network thanks to a process of *Route Discovery*.

### Messages

They have a specific format that is important to keep so that their processing goes well.

----------
`sendMessage(Type, Destination, Message)`

The field *Type* can be set has `broadcast` or `direct`. The first one sends a message to all peers in the network with controlled flooding. The second one sends a message directly to the peer set in *Destination*.
The field *Message* needs to have the following format:
- `Date;Source;TextMessage`

When sending files it should be sent a message first with the information of the file. The message should have the following format:
- `Destination;Date;Source;FileName;FileSize;FileType`

Keeping this all messages should flow correctly.

--------

`sendFile(Destination, File)`

In this function the only thing to keep in mind is to pass the file from the `<input>` and not the input itself.

----------

It is kept a global `Map messages` that contains all messages sent and received. Doing `messages.get("broadcast")` we get all messages which destination is everyone, `messages.get(User)` gets the messages from the requested *User*. This last one comes in form of a javascript object `{type: Type, message: Msg}`, with Type being either *text* or *file*. Messages of type *text* comes with the format `Date;Username:Message` and the *file* type `Date;Username:FileName`.

## Route Discovery Mechanism

When a peer wants to send a file or a message to another it is verified if a route to that peer is known, using `connections` and `reachable`.

*Connections* keeps all the above for the directly connected peers.

`Connections :: Map`
`Key :: Peer Username (String)`
`Value :: Object {name::String, connection::RTCPeerConnection, channel::RTCDataChannel}`

*Reachable* keeps all level two neighbours (neighbours of directly connected peers) and requested peers. The value is the username of a directly connected peer.

`Reachable :: Map`
`Key :: Destination Peer Username (String)`
`Value :: Neighbour (String)`

If the peer isn't in none of the maps a *RouteRequest* is sent with controlled flooding. The first node to receive the request answers with a *RouteReply* through the same path that the *RouteReply* came, refreshing the *reachable* Map on the way back.

## Requirements

[fif]: https://www.mozilla.org/en-US/firefox/new/
[op]: https://www.opera.com/download
[ch]: https://www.google.com/chrome/index.html
[njs]: https://nodejs.org/en/download/

- [Node.js][njs]
- [Google Chrome][ch], [Opera][op] or [Mozilla Firefox][fif]

## How to install and run

1. Go to folder that contains the files
2. Run `npm install` to install all the dependencies
3. Go to client folder
4. Run `static -a <IP address for webserver> -p <port> &`
5. Return to main folder and execute `node server.js &`

repository: mrcsilva/lei

repo_name: mrcsilva/lei


text:
# dump_it

Simple tool for easy database dumping(only postgresql is supported yet).

## How to?

* Clone this repository

`git clone https://github.com/DevAlone/dump_it`

* Go to `dump_it` dir

`cd dump_it`

* Create configs

```bash
cp default.conf.py.example default.conf.py
cp example.conf.py.example example.conf.py
```

Default config is config with global settings, each of which can be overridden in config for database. Example of config for database is example.conf.py.example. You can create as many configs as many databases you have

* Create cron rule

`sudo crontab -e`

```
* * * * * PATH_TO_REPOSITORY/dump.py -c PATH_TO_REPOSITORY >> /var/log/dump_it.stdout.log 2>> /var/log/dump_it.stderr.log
```

And don't forget to change PATH_TO_REPOSITORY to actual path of where you cloned it. So program will be running every minute, getting configs from repository dir and writing logs to /var/log/dump_it.stdout.log and /var/log/dump_it.stderr.log

Happy dumping!


text:
![MyGUI logo](http://mygui.info/images/MyGUI_Logo.png)

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

MyGUI is a cross-platform library for creating graphical user interfaces (GUIs) for games and 3D applications.

* Website: http://mygui.info/

* There you can find basic information about how to build MyGUI:
	http://www.ogre3d.org/tikiwiki/MyGUI+Compiling

* Note: support for Ogre3D 2.0 is currently in beta state and available in a separate [branch](https://github.com/MyGUI/mygui/tree/ogre2).

repository: paroj/mygui

repo_name: paroj/mygui


text:
# HypDiff

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

HypDiff compares HTML snippets. It generates a diff between two input snippets. The diff is a new HTML snippet that highlights textual changes. The tag structure and formatting of the input snippets is preserved. The generated diff snippet is valid, well-formed HTML and suitable for presentation inside a WYSIWYG environment.

## Basic Usage

Compare two HTML snippets:

    HypDiff.compare("
byebye world
", "
hello world
")
    => '
byebyehello world
'

## Why another diff tool?

Many existing tools simply create a diff of the html source code. Unfortunately a diff of the source code can only be viewed as source code. It cannot be viewed in a browser. While that is fine for developers, it is not suitable for an audience that prefers not to be exposed to HTML source code, for example users of WYSIWYG editors.

There are other tools that try to generate an HTML diff that is can be rendered by a browser. But many tools simply try to "work around" the HTML document structure by use of regular expressions. This simplistic approach only works for a small subset of HTML snippets. These tools often output incomprehensible diffs or even invalid HTML.

## How is HypDiff different?

HypDiff takes two HTML snippets and generates a comparison that is again a valid HTML snippet that can be viewed inside a browser.

HypDiff does not rely on regular expressions, but actually parses the input snippets using Nokogiri. It extracts the textual content of the documents and compares them with a state-of-the-art diff algorithm provided by the diff-lcs gem. It then inserts `<ins>` and `<del>` tags into the HTML snippet to highlight changes, but leaves all other HTML tags intact.

## Limitations

HypDiff does not perform a comparison of the html source code or the DOM tree, but compares changes to visible text. It does not care about changes that do not involve visible text.

## Advanced Usage

    # use custom markup by providing callbacks for rendering insertions and deletions
    HypDiff.compare("
byebye world
", "
hello world
",
      render_insertion: proc { |html| "#{html}" },
      render_deletion: proc { |html| "#{html}" }
    )
    # '
byebyehello world
 '

    # choose which markup should be the basis for the results:
    HypDiff.compare("
byebye world
", "
hello world
", markup_from: "before")
    # => '
byebyehello world
 '
    HypDiff.compare("
byebye world
", "
hello world
", markup_from: "after")
    # => '
byebyehello world
 '

For more examples, take a look at the [specs](https://github.com/krishan/hyp_diff/blob/master/spec/hyp_diff_spec.rb).

## Installation

Add this line to your application's Gemfile:

    gem 'hyp_diff'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install hyp_diff

## Contributing

1. Fork it ( http://github.com/krishan/hyp_diff/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

Copyright 2014 Kristian Hanekamp

gha_language: Ruby


text:
# 0.11.0

  * Gracefully shuts down WebSocket when something bad happens
  * Fixes a bug calling the root route over a WebSocket
  * Fixes a bug causing join events to be fired before the connection is registered
  * Fixes a bug causing session to not be serialized in redis
  * Fixes a bug causing redis subscriptions to never unsubscribe
  * Properly disconnects from redis as necessary to avoid eating up connections
  * Moves everything into the Pakyow namespace
  * Improves subscriber management in production environments
  * Fixes a memory leak caused by converting channel names to symbols
  * Replaces `websocket_parser` gem with `websocket`
  * Fixes a bug causing websocket failures in Internet Explorer

# 0.10.2 / 2015-11-15

  * Adds ability to return only a partial in call-route response
  * Fixes several bugs with the redis registry / subscriptions
  * Fixes a bug causing qualifications to not match when using redis
  * Bumps concurrent-ruby version to 1.0

# 0.10.0 / 2015-10-19

  * Initial release

repository: erlandsona/pakyow

repo_name: erlandsona/pakyow


text:
# audio-lambda
Small RESTful API used to toggle audio playback

# Howto
### Setup your passphrase, music directory, and base volume in `config.py`...
```python
# Password included in every POST request to audio-lambda
PASSPHRASE = 'my_passphrase'

# Directory to store music files
MUSIC_DIR = '/var/music/'

# Base volume (0.0 to 1.0)
VOLUME = 0.4
```

### POST to /toggle with your passphrase
```
curl -H "Content-Type: application/json" -X POST -d '{"passphrase": "my_passphrase"}' http://localhost:5000/toggle
```

### ♫♪♫ (=´ω｀=) ♫♪♫

repository: OzuYatamutsu/audio-lambda

repo_name: OzuYatamutsu/audio-lambda


text:
# Interactive Conversation Archive [![Build Status][travis_img]][travis_url] [![Codacy Badge][codacy_img]][codacy_url]

## Dependencies

- Apache
- PHP ^5.4
- MySQL ^5.5

Development dependencies please check in [`package.json`](package.json).

## Setting Up

- Install development dependencies: `npm install`

- Make a copy of [`app/.htaccess.example`](app/.htaccess.example) as `app/.htaccess` in the same directory.

  Then replace `<http-host>` with the local host, e.g. `localhost`, if the website is hosted on `http://localhost/*`.

- Make a copy of [`app/config.oauth2.php.example`](app/config.oauth2.php.example) as `app/config.oauth2.php` in the same directory.

  Then replace `<http-host>` with the local host same as above, e.g. `localhost`, if the website is hosted on `http://localhost/*`.

  Currently, the login mechanism utilizes [OAuth 2](https://oauth.net/2/) at `https://accounts.mintkit.net/`. `OAUTH2_CLIENT_ID` and `OAUTH2_CLIENT_SECRET` may be updated if necessary. Please contact<EMAIL_ADDRESS>for custom client id and secret.

- Make a copy of [`app/config.php.example`](app/config.php.example) as `app/config.php` in the same directory.

  Then replace `<http-host>` with the local host same as above, e.g. `localhost`, if the website is hosted on `http://localhost/*`.

  Then replace `<mysql-host>`, `<mysql-database>`, `<mysql-user>` and `<mysql-password>` with the corresponding database information.

  A database seed is available at `db/seed.sql`.

- Make a copy of [`config.json.example`](config.json.example) as `config.json` in the same directory.

  Then replace `<server-proxy>` with the url to the locally hosted website, e.g. `http://localhost/`, under which is the `app/` contents.

- Make a copy of [`app/config.algolia.php.example`](app/config.algolia.php.example) as `app/config.algolia.php` in the same directory.

  Then replace `<algolia-app-id>`, `<algolia-api-key>` and `<algolia-index>` with the corresponding values from Algolia.

- Front-end build: `gulp build`.

  Or start the front-end build and watch for changes: `gulp` or `gulp proxy`.

## Notes on Architecture

- [`Component`](scripts/component/): A syntactical sugar for the JavaScript class.

[travis_img]: https://travis-ci.org/many-to-many/ica.svg?branch=master
[travis_url]: https://travis-ci.org/many-to-many/ica
[codacy_img]: https://api.codacy.com/project/badge/Grade/be3257310544477d87a24c2f17cdfc09
[codacy_url]: https://www.codacy.com/app/sethlu/ica

repository: many-to-many/ica

repo_name: many-to-many/ica


text:
# :coffee: Lemon Utils

The settings I use for development

## IDLE Plugins

 - [Visual Studio Code](https://github.com/leticiamrosa/lemonconfig/blob/master/VSCODE.md)

## Operating System

How to prepare the development environment for each operating system

 - Ubuntu
 - Windows
 - OSX

## Frameworks

 - [React-Native](https://github.com/leticiamrosa/lemonconfig/blob/master/REACTNATIVE.md)
 - React
 - AngularJs

repository: leticiamrosa/lemonconfig

repo_name: leticiamrosa/lemonconfig


text:
# Spring Boot 2 Security

## Runtime Environment
- [Java 8](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)
- [Spring Framework 5.1.3.RELEASE](https://spring.io/projects/spring-framework)
- [Spring Boot 2.1.1.RELEASE](https://spring.io/projects/spring-boot)
- [Spring Security 5.1.2.RELEASE](https://spring.io/projects/spring-security)
- [HttpClient 4.5.3](https://hc.apache.org/downloads.cgi)
- [Spring Session 2.1.1.RELEASE](https://spring.io/projects/spring-session)
- [Redis 3.2.9](https://redis.io/download)

gha_language: HTML


text:
# PERSONAL TEACHING - REACT FRONTEND
> This project is a front-end website that consumes a Ruby On Rails API. The chosen topic is a system for booking appointments with personal teachers.

## Screenshots

![screenshot-1](https://user-images.githubusercontent.com/36812672/103248197-9f535680-4937-11eb-860a-acc48e7e5537.png)
![screenshot-2](https://user-images.githubusercontent.com/36812672/103248198-9febed00-4937-11eb-9106-ade0d7d8db7d.png)
![screenshot-3](https://user-images.githubusercontent.com/36812672/103248199-a0848380-4937-11eb-9a5f-ee669dcb36b9.png)
![screenshot-4](https://user-images.githubusercontent.com/36812672/103248201-a0848380-4937-11eb-989e-b974e9b53434.png)
![screenshot-5](https://user-images.githubusercontent.com/36812672/103248298-0c66ec00-4938-11eb-97b4-81ed1d45f2b3.png)

## Features

- Sign Up / Sign In
- Register teachers
- List of teachers
- Teacher details and reserve
- List of user's appointments
- List of teacher's commitments

## Built With

- Javascript
- React & Redux
- Hooks
- CSS Modules
- Netlify
- API from: [Personal Teaching Repository](https://github.com/sergiomauz/RoR-Personal-Teaching)
- API live demo root: [Personal Teaching Repository](https://ror-personal-teaching-backend.herokuapp.com/api/v1/)

## Live Demo

Click -> [Personal Teaching!](https://react-personal-teaching.netlify.app/)

## How to Install

- Install Node JS in your system. To install Node JS, you can read the [documentation](https://nodejs.org/en/docs/).
- Clone it using **git clone** command and move to the project directory.
- Run in your terminal **npm install**.

## Tests

- This project uses **React Testing Library** for testing classes.
- All files are in **src/test** directory.
- OPTIONAL: Put your public and secret keys before to test, it will help to add testing for consuming the Pet Finder API.
- In order to run the tests, in terminal type: ```npm test```.
- More than 60 tests:

![screenshot-10](https://user-images.githubusercontent.com/36812672/103628232-b2a08c00-4f0c-11eb-85ec-af2725d49e60.png)

## Author

👤 **Sergio Zambrano**

- Portfolio: [Sergio Zambrano](https://www.szetapp.com/)
- Github: [@sergiomauz](https://github.com/sergiomauz)
- Twitter: [@sergiomauz](https://twitter.com/sergiomauz)
- Linkedin: [Sergio Zambrano](https://www.linkedin.com/in/sergiomauz/)

## 🤝 Contributing

Contributions, issues and feature requests are welcome!. Feel free to check the [issues page](../../issues/).

## Show your support

Give a ⭐ if you like this project!

## Credits

- The user interface [Vespa Responsive Redesign](https://www.behance.net/gallery/26425031/Vespa-Responsive-Redesign) was designed by [Murat Korkmaz](https://www.behance.net/muratk).

## 📝 License

This project is [MIT](./LICENSE) licensed.

repository: sergiomauz/React-Personal-Teaching

branch_name: refs/heads/development

repo_name: sergiomauz/React-Personal-Teaching


text:
# Week4_MS

Data Investigation with Pandas, Python Data Cleaning & Analysis, and SQL Analysis

In addition, during this week’s independent project, I got to test my understanding of the following learning outcomes:

1. Recall the basics of Python programming for data science.
2. Obtain and manipulate data from various types of databases using the SQL language.
3. Write code and document your workflow in a programming environment.
4. Understand mechanisms for missing data, outliers and analytic implications.
5. Evaluate the integrity of data by making decisions on data quality issues.
6. Perform the extraction, querying, and aggregation of data for analysis in multiple projects through common techniques and tools.

In this week's independent project, I was working as a data scientist working for an electric car-sharing service company. I have been tasked to process stations data to understand electric car usage over time by solving for the following research question: Identify the most popular hour of the day for picking up a shared electric car (Bluecar) in the city of Paris over the month of April 2018.

branch_name: refs/heads/main


text:
# dicom-decoder-ring

## Transfer Syntaxes

A DICOM file's [Transfer Syntax UID (0002,0010)][transfer-syntax-uid] helps us identify how it's [Pixel Data (7FE0,0010)][pixel-data] is encoded. It, along with a few other choice fields, help us identify how to decode the image and access it's raw pixel data.

This library aims to support decoding the following DICOM standard representations

| Transfer Syntax        | Name                                                        | Codec                |
| ---------------------- | ----------------------------------------------------------- | -------------------- |
| _Uncompressed_         |                                                             |                      |
| 1.2.840.10008.1.2      | Implicit VR Endian (Default transfer syntax for DICOM)      | N/A                  |
| 1.2.840.10<IP_ADDRESS>    | Explicit VR Little Endian                                   | N/A                  |
| 1.2.840.10<IP_ADDRESS>.99 | Deflated Explicit VR Little Endian                          | N/A                  |
| 1.2.840.10<IP_ADDRESS>    | Explicit VR Big Endian                                      | N/A                  |
| _Compressed_           |                                                             |                      |
| 1.2.840.10<IP_ADDRESS>.50 | JPEG Baseline (Process 1 - 8 bit)                           | [jpeg-js][jpeg-js]   |
| 1.2.840.10<IP_ADDRESS>.51 | JPEG Baseline (Processes 2 & 4 - 12 bit)                    | [jpeg-js][jpeg-js]   |
| 1.2.840.10<IP_ADDRESS>.57 | JPEG Lossless, Nonhierarchical (Processes 14)               | Jpeg Lossless        |
| 1.2.840.10<IP_ADDRESS>.70 | JPEG Lossless, Nonhierarchical (Processes 14 [Selection 1]) | Jpeg Lossless        |
| 1.2.840.10<IP_ADDRESS>.80 | JPEG-LS Lossless Image Compression                          | [CharLS][charls]     |
| 1.2.840.10<IP_ADDRESS>.81 | JPEG-LS Lossy (Near-Lossless) Image Compression             | [CharLS][charls]     |
| 1.2.840.10<IP_ADDRESS>.90 | JPEG 2000 Image Compression (Lossless Only)                 | [OpenJPEG][openjpeg] |
| 1.2.840.10<IP_ADDRESS>.91 | JPEG 2000 Image Compression                                 | [OpenJPEG][openjpeg] |
| 1.2.840.10<IP_ADDRESS>.92 | JPEG 2000 Part 2 Multicomponent (Lossless Only)             | [OpenJPEG][openjpeg] |
| 1.2.840.10<IP_ADDRESS>.93 | JPEG 2000 Part 2 Multicomponent (Lossy)                     | [OpenJPEG][openjpeg] |
| 1.2.840.10<IP_ADDRESS>    | RLE Lossless                                                | RLE                  |

Note: The standard includes additional transfer syntaxes, some of which are retired. You can find a [full list here][transfer-syntax-list]. The OpenJPEG codec may also be able to decode retired syntaxes `*.4.92` and `*.4.93`.

### Codecs

| Name               | Description                                | License            | Source            |
| ------------------ | ------------------------------------------ | ------------------ | ----------------- |
| [jpeg-js][jpeg-js] | Pure javascript JPEG encoder and decoder\* | Apache 2.0 / Adobe | [GitHub][jpeg-js] |

\* - Faster, non-blocking, alternatives exist if you have access to the DOM ([canvas API][canvas-api]) or are using node ([sharp][sharp]). We use `jpeg-js` because it works in a Web Worker.

## Photometric Interpretations

-   MONOCHROME1
-   MONOCHROME2
-   RGB (pixel and planar configurations)
-   PALETTE COLOR
-   YBR_FULL
-   YBR_FULL_422
-   YBR_RCT
-   YBR_ICT

## Resources

-   [Webpack: TypeScript](https://webpack.js.org/guides/typescript/)
    -   [tsconfig.json](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
    -   [Using third party libraries](https://webpack.js.org/guides/typescript/#using-third-party-libraries)

<!-- prettier-ignore-start -->

<!--
    LINKS
-->

[transfer-syntax-uid]: http://dicom.nema.org/dicom/2013/output/chtml/part10/chapter_7.html
[pixel-data]: http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.7.6.3.html#sect_C.<IP_ADDRESS>.4
[charls]: https://github.com/team-charls/charls
[openjpeg]: https://github.com/uclouvain/openjpeg
[jpeg-js]: https://github.com/eugeneware/jpeg-js
[canvas-api]: https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API
[sharp]: https://www.npmjs.com/package/sharp
[transfer-syntax-list]: https://www.dicomlibrary.com/dicom/transfer-syntax/

repository: VoxelMed/dicom-decoder-ring

repo_name: VoxelMed/dicom-decoder-ring


text:
# Microsoft Graph Excel ASP.NET donations sample

This sample shows how to read and write into an Excel document stored in your OneDrive for Business account by using the Excel REST APIs.

## Prerequisites

To use the Microsoft Graph Excel ASP.NET donations sample, you need the following:
* Visual Studio 2015 installed and working on your development computer.

     > Note: This sample is written using Visual Studio 2015. If you're using Visual Studio 2013, make sure to change the compiler language version to 5 in the Web.config file:  **compilerOptions="/langversion:5**
* A Microsoft Office 365 account. You can sign up for [an Office 365 Developer subscription](https://aka.ms/devprogramsignup) that includes the resources that you need to start building apps.

     > Note: If you already have a subscription, the previous link sends you to a page with the message *Sorry, you can’t add that to your current account*. In that case, use an account from your current Office 365 subscription.
* A Microsoft Azure Tenant to register your application. Azure Active Directory (AD) provides identity services that applications use for authentication and authorization. A trial subscription can be acquired here: [Microsoft Azure](https://account.windowsazure.com/SignUp).

     > Important: You also need to make sure your Azure subscription is bound to your Office 365 tenant. To do this, see the Active Directory team's blog post, [Creating and Managing Multiple Windows Azure Active Directories](http://blogs.technet.com/b/ad/archive/2013/11/08/creating-and-managing-multiple-windows-azure-active-directories.aspx). The section **Adding a new directory** will explain how to do this. You can also see [Set up your Office 365 development environment](https://msdn.microsoft.com/office/office365/howto/setup-development-environment#bk_CreateAzureSubscription) and the section **Associate your Office 365 account with Azure AD to create and manage apps** for more information.
* The client ID and redirect URI values of an application registered in Azure. This sample application must be granted the **Have full access to user files and files shared with user** permission for **Microsoft Graph**. [Add a web application in Azure](https://msdn.microsoft.com/office/office365/HowTo/add-common-consent-manually#bk_RegisterWebApp) and grant the proper permissions to it:
	* In the [Azure Management Portal](https://manage.windowsazure.com/), select the **Active Directory** tab and an Office 365 tenant.
	* Select the **Applications** tab and choose the application that you want to configure.
	* In the **permissions to other applications** section, add the **Microsoft Graph** application.
	* For the **Microsoft Graph** application, add the following delegated permissions: **Have full access to user files and files shared with user**.
	* Save the changes.

     > Note: During the app registration process, make sure to specify **http://localhost:21942** as the **Sign-on URL**.

## Configure the app
1. Open **Microsoft-Graph-ASPNET-Excel-Donations.sln** file.
2. In Solution Explorer, open the **Web.config** file.
3. Replace *ENTER_YOUR_CLIENT_ID* with the client ID of your registered Azure application.
4. Replace *ENTER_YOUR_SECRET* with the key of your registered Azure application.
5. Upload the **WoodGroveBankExpenseTrendsWorkbook.xlsx** file included in this repo to the root OneDrive directory of your Office 365 tenant. The app won't work without this workbook, which stores the data in your donations list.

## Run the app

1. Press F5 to build and debug. Run the solution and sign in with your organizational account. The application launches on your local host and shows the starter page.
![WoodGrove Companion App start page](images/ExcelApp.jpg)

     > Note: Copy and paste the start page URL address **http://localhost:21942/home/index** to a different browser if you get the following error during sign in:**AADSTS70001: Application with identifier ad533dcf-ccad-469a-abed-acd1c8cc0d7d was not found in the directory**.
2. Select the `Get Started` button.
3. The application displays the donations page. Select the `Add New' link to add a new task. Fill in the form with the donation details.
4. After you add a donation, the app shows the updated donations list. If the newly added donation isn't updated, choose the `Refresh` link after a few moments.
![Donations list](images/Donations.jpg)

## Contributing ##

If you'd like to contribute to this sample, see [CONTRIBUTING.MD](/CONTRIBUTING.md).

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode<EMAIL_ADDRESS>with any additional questions or comments.

## Questions and comments

We'd love to get your feedback about the Microsoft Graph Excel REST API ASP.NET Donations sample. You can send your questions and suggestions to us in the [Issues](https://github.com/microsoftgraph/aspnet-donations-rest-sample/issues) section of this repository.

Questions about Office 365 development in general should be posted to [Stack Overflow](http://stackoverflow.com/questions/tagged/MicrosoftGraph). Make sure that your questions or comments are tagged with [MicrosoftGraph].

## Additional resources

* [Microsoft Graph documentation](http://graph.microsoft.io)
* [Microsoft Graph API References](http://graph.microsoft.io/docs/api-reference/v1.0)

## Copyright
Copyright (c) 2016 Microsoft. All rights reserved.

repository: sacitc/aspnet-donations-rest-sample

repo_name: sacitc/aspnet-donations-rest-sample