text:
---
layout: tutpage
axis: doc-nock
categories: tut
sort: 2
title: II - Nock Is Easy
---

> You get used to it. I don't even see the code. All I see is blonde, brunette, redhead.
> - The Matrix

##Fundamentals##

Now that we have all the tools, let's learn Nock from scratch.
Here are all the rules defining `*`:

    23 ::    *[a [b c] d]     [*[a b c] *[a d]]
    24 ::
    25 ::    *[a 0 b]         /[b a]
    26 ::    *[a 1 b]         b
    27 ::    *[a 2 b c]       *[*[a b] *[a c]]
    28 ::    *[a 3 b]         ?*[a b]
    29 ::    *[a 4 b]         +*[a b]
    30 ::    *[a 5 b]         =*[a b]
    31 ::
    32 ::    *[a 6 b c d]     *[a 2 [0 1] 2 [1 c d] [1 0] 2 [1 2 3] [1 0] 4 4 b]
    33 ::    *[a 7 b c]       *[a 2 b 1 c]
    34 ::    *[a 8 b c]       *[a 7 [[7 [0 1] b] 0 1] c]
    35 ::    *[a 9 b c]       *[a 7 c 2 [0 1] 0 b]
    36 ::    *[a 10 [b c] d]  *[a 8 c 7 [0 3] d]
    37 ::    *[a 10 b c]      *[a c]
    38 ::
    39 ::    *a               *a

As we saw in the last chapter, when `a` is an atom, `*a` is
always an error.  So Nock proper is a function of a cell.
Informally, that cell is always described as a pair

    [subject formula]

where `subject` is the data and `formula` is the program.  Notice
that `a` in the rules above, except 39, is always the subject.
So: let's learn how to write a Nock formula.

##Autocons##

We observe from the rules above that a formula, too, is always a
cell.  But when we look inside that cell, we see two basic kinds
of formulas:

    [operator operands]
    [formula formula]

An operator is always an atom (`0` through `10`).  A formula is
always a cell.  Line 23 distinguishes these forms:

    23 ::    *[a [b c] d]     [*[a b c] *[a d]]

Suppose you have two formulas `f` and `g`, each of which computes
some function of the subject `s`.  You can then construct the
formula `h` as `[f g]`; and `h(s)` equals `[f(s) g(s)]`.

For instance, recall our computation from the last chapter:

    *[[19 42] [0 3] 0 2]

`s` is `[19 42]`, `f` is `[0 3]`, `g` is `[0 2]`, `h` is `[[0 3] 0
2]`.  `f(s)` is `42`; `g(s)` is `19`; so `h(s)` is `[42 19]`.

Why?  We could have an operator `11`, `cons` to a Lisp veteran,
with the operands `f` and `g` - so instead of writing

    [[0 3] 0 2]

we'd say

    [11 [0 3] 0 2]

But not only is this less elegant, it's less convenient.  Of
course, convenience at the Nock level matters little, but we
repeat this pattern at the Hoon level - where it's often more
pleasant to say `[a b]` than `(cons a b)`.

##Basic operators##

Nock is small, but it could be smaller.  If we didn't care at all
about the efficiency of the interpreter - in other words, if Nock
was a theoretical exercise rather than a practical tool - we
could make do with just the first six operators:

    25 ::    *[a 0 b]         /[b a]
    26 ::    *[a 1 b]         b
    27 ::    *[a 2 b c]       *[*[a b] *[a c]]
    28 ::    *[a 3 b]         ?*[a b]
    29 ::    *[a 4 b]         +*[a b]
    30 ::    *[a 5 b]         =*[a b]

Let's run through them one by one.

###`0`###

`0` just applies the `/` function:

    25 ::    *[a 0 b]         /[b a]

For any subject `a`, the formula `[0 b]` produces `/[b a]`, which
is why

    *[[19 42] 0 3]

is `/[3 19 42]`, which is `42`.

###`1`###

`1` just ignores its subject and produces its operand:

    26 ::    *[a 1 b]         b

###`2`###

`2` is the only interesting basic operator:

    27 ::    *[a 2 b c]       *[*[a b] *[a c]]

Here we generate a calculation to perform.  Given the formula `[2
b c]`, `b` is a formula for generating the new subject; `c` is a
formula for generating the new formula.  To compute `*[a 2 b c]`,
we evaluate both `b` and `c` against the current subject `a`.

###`3`, `4`, `5`###

`3`, `4`, and `5` just apply `?`, `+` and `=` respectively -
that is, cell/atom, increment, and equals.

    28 ::    *[a 3 b]         ?*[a b]
    29 ::    *[a 4 b]         +*[a b]
    30 ::    *[a 5 b]         =*[a b]

##Macros##

Operators `6` through `10` are all essentially macros:

    32 ::    *[a 6 b c d]     *[a 2 [0 1] 2 [1 c d] [1 0] 2 [1 2 3] [1 0] 4 4 b]
    33 ::    *[a 7 b c]       *[a 2 b 1 c]
    34 ::    *[a 8 b c]       *[a 7 [[7 [0 1] b] 0 1] c]
    35 ::    *[a 9 b c]       *[a 7 c 2 [0 1] 0 b]
    36 ::    *[a 10 [b c] d]  *[a 8 c 7 [0 3] d]
    37 ::    *[a 10 b c]      *[a c]

Each of these cases just resolves to another Nock computation, in
which each pattern matched on the left appears no more than once
on the right.  I.e., it's a macro.  But what do the macros do?
Let's work through them, from easiest to hardest.

###`10` (37)###

The second case of 10 is so easy it's puzzling:

    37 ::    *[a 10 b c]      *[a c]

For any `b`, the formula `[10 b c]` seems to be perfectly
equivalent to the formula `c`.  But why?  Why would we say
`[10 b c]` when we could just say `c`?

The answer is that `10` is a hint to the interpreter.  It's true
that `[10 b c]` has to be *semantically* equivalent to `c`, but
it doesn't have to be *practically* equivalent.  Since whatever
information is in `b` is discarded, a practical interpreter is
free to ignore it, or to use it in any way that does not affect
the results of the computation.

###`7`###

`7` is our next easiest macro:

    33 ::    *[a 7 b c]       *[a 2 b 1 c]

Informally, the formula `[7 b c]` composes the formulas `b` and
`c`.  To use a bit of math notation, if `d` is `[7 b c]`,

    d(a) == c(b(a))

Let's see how this works by applying some reductions to the
definition of `7`, and producing a simpler definition that
doesn't look like a macro:

    *[a 2 b 1 c]

        <<27 ::    *[a 2 b c]       *[*[a b] *[a c]]>>

    *[*[a b] *[a 1 c]]

        <<26 ::    *[a 1 b]         b>>

    *[*[a b] c]

So we can write a revised line 33, perhaps slightly clearer:

    33r::    *[a 7 b c]       *[*[a b] c]

###`8`###

`8` looks slightly horrible but you shouldn't fear it at all:

    34 ::    *[a 8 b c]       *[a 7 [[7 [0 1] b] 0 1] c]

What does this even mean?  Let's go through the same process
of reducing it.

    *[a 7 [[7 [0 1] b] 0 1] c]

      <<33r::    *[a 7 b c]       *[*[a b] c]>>

    *[*[a [7 [0 1] b] 0 1] c]

      <<23 ::    *[a [b c] d]     [*[a b c] *[a d]]>>

    *[[*[a 7 [0 1] b] *[a 0 1]] c]

      <<33r::    *[a 7 b c]       *[*[a b] c]>>

    *[[*[*[a 0 1] b] *[a 0 1]] c]

      <<25 ::    *[a 0 b]         /[b a]>>

    *[[*[a b] a] c]

So our revised rule 34:

    34r::    *[a 8 b c]       *[[*[a b] a] c]

What does this actually do?  Well, look at it.  It evaluates the
formula `c` with the cell of `*[a b]` and the original subject
`a`.  In other words, in math notation, if `d` is `[8 b c]`,

    d(a) == c([b(a) a])

But why?  Suppose, for the purposes of `c`, we need not just `a`,
but some intermediate noun computed from `a` that will be useful
in `c`'s calculation.  We apply `c` with a new subject that's a
cell of the intermediate value and the old subject - not at all
unlike pushing a new variable on the stack.

For extra credit, a good question to ask yourself: why do we
need to write `[7 [0 1] b]` and not just `b`?

###`10` (36)###

We now understand all the moving parts we need to figure out the
other reduction of `10`:

    36 ::    *[a 10 [b c] d]  *[a 8 c 7 [0 3] d]

Reducing:

    *[a 8 c 7 [0 3] d]

      <<34r::    *[a 8 b c]       *[[*[a b] a] c]>>

    *[[*[a c] a] [7 [0 3] d]]

      <<33r::    *[a 7 b c]       *[*[a b] c]>>

    *[*[[*[a c] a] 0 3] d]

If you've assimilated a bit of Nock already, you may feel the
temptation to reduce this to

    *[a d]

since it would be very reasonable to think that

    *[[*[a c] a] 0 3]

is just `a`.  And it seems to be - given the semantics of 8 as
we've explained them.

But there's a problem, which is that `c` might not terminate.
If `c` terminates, this reduction is correct.  Otherwise it's not.
So the best we can do is:

    36r::    *[a 10 [b c] d]  *[*[[*[a c] a] 0 3] d]

Why?  `10` in either case is a hint.  If `x` in `[10 x y]` is an
atom, we reduce line 37 and `x` is simply discarded.  Otherwise,
`x` is a cell `[b c]`; `b` is discarded, but `c` is computed as a
formula and its result is discarded.

Effectively, this mechanism lets us feed both static and dynamic
information into the interpreter's hint mechanism.

###`6`###

`6` certainly looks intimidating:

    32 ::    *[a 6 b c d]     *[a 2 [0 1] 2 [1 c d] [1 0] 2 [1 2 3] [1 0] 4 4 b]

We could explain `6` as a reduction sequence.  But it's a long
one.  Instead, let's invent another operator which makes `6` easy:

       ::    $[0 b c]         b
       ::    $[1 b c]         c

Then we can restate `6` quite compactly:

    32r::    *[a 6 b c d]     *[a $[*[a b] c d]]

`6` stands revealed as the humble if-then-else.  Nock *is* easy.

This excuse for an explanation may not satisfy everyone.  A good
exercise is to check that `6` as defined *actually* has these
properties - and can't be simplified.

###`9`###

`9` is an audacious mystery:

    35 ::    *[a 9 b c]       *[a 7 c 2 [0 1] 0 b]

We'll reduce `9` but not explain it.  When we use it in an
example, it'll be obvious what it is.

    *[a 7 c 2 [0 1] 0 b]]

      <<33r::    *[a 7 b c]       *[*[a b] c]>>

    *[*[a c] 2 [0 1] 0 b]]

      <<27 ::    *[a 2 b c]       *[*[a b] *[a c]]>>

    *[*[*[a c] [0 1]] *[*[a c] 0 b]]

      <<25 ::    *[a 0 b]         /[b a]>>

    *[*[a c] *[*[a c] 0 b]]

So we have:

    35r::    *[a 9 b c]       *[*[a c] *[*[a c] 0 b]]

If you have a really fine instinctive sense of Nock, you might
understand what `9` is for.  Otherwise, don't worry for now.

gha_language: CSS


text:
# Changelog
All notable changes to this project will be documented in this file.

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

## [Unreleased (2.0.0)]
### Added
- `SizeAlignedByteData` trait for `ByteData` types that are guaranteed to
  provide proper alignment for storage of `usize` and `isize` values.
- `SizeAlignedBuffer` trait for `Buffer` types that are guaranteed to provide
  proper alignment for storage of `usize` and `isize` values.

### Changed
- Separate out `alloc` library support from the "unstable" crate feature into
  its own "alloc" feature.
- Only implement `Tracking` for `SizeAlignedBuffer` types (implemented by
  default for arrays and slices of `usize`, `isize`, and `CacheAligned`
  elements), and use normal (aligned) reads and writes in the associated
  `Tracking::get()` and `Tracking::set()` implementations, avoiding the
  performance penalties associated with supporting unaligned reads and writes.
- Declare the `IntoMutSliceLikePtr::into_mut_slice_like_ptr()` trait method as
  `unsafe` to indicate that it may read from the given pointer.

## [Unreleased (1.x)]
### Changed
- Updated Travis CI configuration to use `clippy` and `rustfmt` from the
  stable toolchain, and updated the code accordingly (based on the 1.32.0
  toolchain versions).
- Minor API documentation improvements.

## [1.2.0] - 2018-07-07
### Added
- `CStr` allocation support, including conversion of `CStr` allocations to
  `[u8]` allocations.
- Implementation of
  [`StableDeref`](https://crates.io/crates/stable_deref_trait) for
  `Allocation`, allowing allocations to be used with other crates that support
  the trait such as
  [`owning_ref`](https://crates.io/crates/owning_ref) and
  [`rental`](https://crates.io/crates/rental).

### Fixed
- Minor documentation fixes.

## [1.1.0] - 2018-06-16
### Added
- `Scratchpad::static_new_in_place()` for initializing a `Scratchpad` within
  a block of uninitialized memory for `Scratchpad` types that use only static
  arrays for backing memory, bypassing potential call stack use for parameters
  and return values that may exceed the amount of space available on the
  stack.

## [1.0.1] - 2018-06-07
### Fixed
- Use unaligned reads and writes in `Tracking::get()` and `Tracking::set()`
  implementations for `Buffer` types to avoid potential issues with marker
  tracking buffers that are not aligned to at least the same alignment as
  `usize`, as `Buffer` doesn't guarantee any specific alignment, and some CPU
  architectures do not allow unaligned access. This can impact performance,
  but retains compatibility with code that may be using tracking buffers with
  lower alignment requirements.

## [1.0.0] - 2018-06-04
### Added
- `IntoMutSliceLikePtr` trait for reinterpreting pointer types to compatible
  `SliceLike` pointers. This replaces the `IntoSliceLikeAllocation` trait for
  determining which `Allocation` types can be converted to slices and
  slice-like types.
- Missing support for converting `str` allocations to `[u8]` allocations.

### Changed
- Moved `into_slice_like_allocation()` away from the `IntoSliceLikeAllocation`
  trait into a method of `Allocation` itself, allowing it to be called
  directly on any allocation without having to import any special traits.
- Rewrote much of the crate-level documentation to be more useful as well as
  better reflect the changes made since the initial release.

### Removed
- `IntoSliceLikeAllocation` trait (superseded by
  `Allocation::into_slice_like_allocation()` and `IntoMutSliceLikePtr` trait).

## [1.0.0-beta.2] - 2018-05-31
### Added
- `SliceSource` trait for providing slice data to `Marker` functions from
  various source data types.
- `SliceMoveSource` subtrait of `SliceSource` that allows for taking ownership
  of the contents of a slice.
- `SliceSourceCollection` trait for abstracting collections of `SliceSource`
  objects.
- `SliceMoveSourceCollection` subtrait of `SliceSourceCollection` that allows
  for taking ownership of the slices provided by all `SliceSource` objects in
  a collection.
- `Marker::concat_slices()` function for concatenating slices by moving their
  contents into the new allocation.

### Changed
- Overhauled `Marker` functions that work with slices to take slice input
  using the new `SliceSource`, `SliceMoveSource`, `SliceSourceCollection`, and
  `SliceMoveSourceCollection` traits, allowing for more flexible input for
  slice data. Additionally, the inputs for these functions are now more
  consistent with one another.
- Renamed `IntoSliceAllocation` to `IntoSliceLikeAllocation` and updated its
  methods accordingly for consistency with other traits that work with
  `SliceLike` types.
- Unconditionally enable `i128` and `u128` implementations of `ByteData` if
  the `rustc` version detected at build time is 1.26 or later.

### Removed
- `OwnedSlice` trait (superseded by `SliceSource` and its related traits).
- Automatic coercion of scalar values (including boxed scalars) and boxed
  arrays into slices when used as arguments for `Marker::allocate_slice()`,
  `Marker::extend()`, and the related `MarkerFront` and `MarkerBack` wrappers.
  Support for scalars previously resulted in ambiguity when trying to
  determine whether an array or slice reference should be interpreted as a
  slice of its contents or a single-element slice containing either the array
  or slice reference, requiring explicit type annotations in such cases. On
  the other hand, support for boxed arrays simply becomes difficult to
  implement when using the newly added `Array` trait, so they've simply been
  removed in response. Both can still be used as input via explicit conversion
  into a supported type.
- Miscellaneous unnecessary generic parameters.

### Fixed
- Check for the correct feature ("unstable" versus "nightly") in the `cfg`
  attributes used to control whether `ByteData` implementations are generated
  for `i128` and `u128`.

## [1.0.0-beta.1] - 2018-05-25
### Added
- `Marker::allocate_slice()`, `Marker::allocate_slice_clone()`, and
  `Marker::allocate_slice_copy()` for creating slice allocations.
- `Allocation::concat()` and `Allocation::concat_unchecked()` for
  concatenating two adjacent allocations into a single slice allocation.
- `MarkerFront::append{,_clone,_copy}()` and
  `MarkerBack::prepend{,_clone,_copy}()` for extending existing allocations at
  the end of their respective stacks with new data. This functionality is also
  available through the `Marker` trait using the `extend{,_clone,_copy}()`
  methods (appending is always performed by front markers, and prepending is
  always performed by back markers).
- `IntoSliceAllocation` trait for safely coercing `Allocation` instances into
  allocations of slices. This is also used to determine what types can be used
  for allocation concatenation (`concat()` and `concat_unchecked()` allocation
  methods) and extension (`append*()` and `prepend*()` marker methods).
- `SliceLike` trait for performing conversions between DSTs that essentially
  wrap some primitive slice type and the underlying slice type (e.g. between
  `str` and `[u8]`), and `ConcatenateSlice` trait for marking `SliceLike`
  types that can be safely concatenated without any additional verification
  needed. This is used to allow for general use of such DSTs in allocations.
- Various unit tests for edge cases (e.g. allocation extension safety, ZST
  allocation support).

### Changed
- Replaced the simple `Error` enum with an `Error` struct that provides the
  error category (an `ErrorKind` enum variant based on the old `Error` enum)
  and any values whose ownership was intended to be passed to the callee. This
  allows the caller to reuse such values if an operation fails instead of
  simply throwing them away.
- Replaced `Marker::concat()` with `Marker::concat_slices_clone()` and
  `Marker::concat_slices_copy()`, which both work on general slices.
- Use `NonNull<T>` for internal storage of `Allocation` pointers, allowing for
  compiler optimizations such as reducing `Option<Allocation<'marker, T>>`
  size to that of a single pointer.

## [0.3.0] - 2018-04-30
### Added
- `Marker::concat()` for concatenating a series of strings into a single
  string slice allocated from the marker on which it is called.
- `#[inline]` attribute to most `Marker` allocation functions and the
  `uninitialized_boxed_slice*()` utility functions.

### Changed
- Replaced data reference in `Allocation` with a raw pointer, allowing the
  removal of the nebulous `'t` lifetime in the `Allocation` type and `Marker`
  methods (conceptually, an `Allocation` instance owns its data, and this
  helps clarify that ownership).

### Removed
- Reference to creating static instances of `Scratchpad` from README
  (overlooked when correcting the crate documentation for version 0.2.0).

## [0.2.0] - 2018-04-29
### Added
- `Scratchpad::static_new()` function for creating scratchpads backed by
  static arrays without having to pass array instances as function parameters.
- `StaticBuffer` trait for constraining `Scratchpad::static_new()` to
  scratchpads that use only static arrays for backing storage.
- `cache_aligned_zeroed!()`, `cache_aligned_zeroed_for_bytes!()`, and
  `cache_aligned_zeroed_for_markers!()` macros for shorthand creation of
  zeroed-out `CacheAligned` data.
- References to `MarkerFront` and `MarkerBack` in documentation for `Marker`.
- Run tests with both the `std` and `unstable` crate features enabled in
  Travis CI configuration.
- "data-structures" and "embedded" categories in `Cargo.toml` manifest.
- Documentation link in `Cargo.toml` manifest.
- Documentation and release nodes links in `README.md`.
- Changelog.

### Changed
- Clarified how the front and back allocation stacks operate independently in
  documentation.
- Use clearer wording in "Memory Overhead" documentation section.
- Minor documentation tweaks.

### Removed
- References to creating static instances of `Scratchpad` from documentation
  (static variables must implement `Sync`, but `Scratchpad` is not thread-safe
  by design).

### Fixed
- Incorrect "deque" term use internally.

## 0.1.0 - 2018-04-27
### Added
- Initial release.

[Unreleased (2.0.0)]: https://github.com/okready/scratchpad/compare/HEAD...2.0-dev
[Unreleased (1.x)]: https://github.com/okready/scratchpad/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/okready/scratchpad/compare/v1.1.0...v1.2.0
[1.1.0]: https://github.com/okready/scratchpad/compare/v1.0.1...v1.1.0
[1.0.1]: https://github.com/okready/scratchpad/compare/v1.0.0...v1.0.1
[1.0.0]: https://github.com/okready/scratchpad/compare/v1.0.0-beta.2...v1.0.0
[1.0.0-beta.2]: https://github.com/okready/scratchpad/compare/v1.0.0-beta.1...v1.0.0-beta.2
[1.0.0-beta.1]: https://github.com/okready/scratchpad/compare/0.3.0...v1.0.0-beta.1
[0.3.0]: https://github.com/okready/scratchpad/compare/0.2.0...0.3.0
[0.2.0]: https://github.com/okready/scratchpad/compare/0.1.0...0.2.0

repository: okready/scratchpad

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: okready/scratchpad


text:
# redux-components-legacy
Implementation of the `redux-components` 0.3.x API on top of the new 0.4.x infrastructure. Designed as an aid in porting old code that uses the 0.3.x API.

## Usage

- Install: `$ npm install --save redux-components-legacy`

- Replace `require('redux-components')` with `require('redux-components-legacy')`. The exports and API are the same as 0.3.x.

- `redux-components-legacy` passes all of the `redux-components` 0.3.x unit tests and should work as a drop in replacement. Please file an issue if this is not the case.

## Legacy Documentation

The `redux-components` 0.3.x API documentation [is available here](docs). This is for reference only; new code should be written to the 0.4 API and this documentation will not be updated in the future.

license: MIT

repository: wcjohnson/redux-components

gha_language: JavaScript

gha_license_id: MIT

repo_name: wcjohnson/redux-components


text:
# AmazonAppFlow

```text
aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow
```

```text
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')
```

| Illustration | AmazonAppFlow | AmazonAppFlowCard | AmazonAppFlowGroup |
| :---: | :---: | :---: | :---: |
| ![illustration for Illustration](../../../aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow.png) | ![illustration for AmazonAppFlow](../../../aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow.Local.png) | ![illustration for AmazonAppFlowCard](../../../aws-q2-2023/Architecture/AppIntegration/AmazonAppFlowCard.Local.png) | ![illustration for AmazonAppFlowGroup](../../../aws-q2-2023/Architecture/AppIntegration/AmazonAppFlowGroup.Local.png) |

## Sprites
The item provides the following sriptes:

- `<$AmazonAppFlowXs>`
- `<$AmazonAppFlowSm>`
- `<$AmazonAppFlowMd>`
- `<$AmazonAppFlowLg>`

## AmazonAppFlow

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlow
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlow('AmazonAppFlow', 'Amazon App Flow', 'an optional tech label', 'an optional description')
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlow
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlow('AmazonAppFlow', 'Amazon App Flow', 'an optional tech label', 'an optional description')
@enduml
```

## AmazonAppFlowCard

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlowCard
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlowCard('AmazonAppFlowCard', 'Amazon App Flow Card', 'an optional description')
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlowCard
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlowCard('AmazonAppFlowCard', 'Amazon App Flow Card', 'an optional description')
@enduml
```

## AmazonAppFlowGroup

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlowGroup
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlowGroup('AmazonAppFlowGroup', 'Amazon App Flow Group', 'an optional tech label') {
    note as note
        the content of the group
    end note
}
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('aws-q2-2023/bootstrap')

' loads the Item which embeds the element AmazonAppFlowGroup
include('aws-q2-2023/Architecture/AppIntegration/AmazonAppFlow')

' renders the element
AmazonAppFlowGroup('AmazonAppFlowGroup', 'Amazon App Flow Group', 'an optional tech label') {
    note as note
        the content of the group
    end note
}
@enduml
```

repository: tmorin/plantuml-libs

gha_language: TypeScript

repo_name: tmorin/plantuml-libs


text:
# Vault Plugin: Bitcoin Secrets Backend

This is a backend secrets plugin to be used with Hashicorp Vault. This plugin manages secret keys for the Bitcoin blockchain platform.

## Usage

Assuming you have Hashicorp Vault installed, `scripts/dev_start.sh` is a helper script to start up Vault in dev mode and mount this plugin.
Vault will be listening on localhost:8200.

Once the plugin is mounted, you can start writing secrets to it.

### Log In To Vault

```
export VAULT_ADDR=http://localhost:8200
vault login
```

The token is "root" if you've used dev_start.sh to start Vault.

### Creating an Account

`vault write bitcoin/accounts/MyAccountName`

This will create a new account called "MyAccountName".

### Viewing an Account

`vault read bitcoin/accounts/MyAccountName`

### Viewing All Account Names

`vault list bitcoin/accounts`

### Creating a Signed Payment Transaction

`vault write bitcoin/payments source=MySourceAccountName destination=MyDestinationAccountName amount=35 unsignedTx=01000...`

This will return a signed transaction.

## Running Tests

```
make test
```

Running tests with coverage:
```
make coverage
```

## License

Copyright (c) 2019 ChainFront LLC

Licensed under the Apache License, Version 2.0.

repository: ChainFront/vault-plugin-bitcoin

repo_name: ChainFront/vault-plugin-bitcoin


text:
#Grammar

This is the grammar of [clu](clu.md), expressed in the form in which it will, eventually, be compiled.

```text
       clu :  form* / EOF

      form :  unary* (_atom_ / _compound_) / _comment

     unary :  ","
           /  "~"
           /  "`"
           /  reader-macro

      atom :  symbol
           /  number
           /  keyword
           /  string

  compound :  expr
           /  hash
           /  vector
           /  type
           /  syntax

   symbol  :  latin !(forbidden) ANYTHING
   keyword :  ":" symbol

    xpr   :  "(" form* ")"
    hash   :  "{" (form$2)* "}"
    vector :  "[" form* "]"
    type   :  ":[" form* "]:"
    syntax :  "|" dispatch* "|"

  dispatch :  "--|" moonscript "|--"
           /  "--!" dispatch-string
           /  lun
       lun :  !"|" ANY    ;-) looks like lua!
moonscript :  !"|" ANY    ;-) looks like moonscript!

     latin :  ([A-Z] / [a-z])
 `comment` :  ";" !"\n" ANY "\n"
```

... I think that's it. I didn't specify what can't go into a symbol in much detail. None of the quoted literal forms, that's for certain. Actually, "--!" is the sole exception to this, that is a valid character string within a symbol.

repository: mnemnion/loon

repo_name: mnemnion/loon


text:
# Install using Carthage

To install **Whipcream UI**, using Carthage or Cocoapods is recommended.

## Prepare `Cartfile`

First, you need to create `Cartfile` in root dir of your project, unless you already created it.

Then, define or register **Whipcream**, your `Cartfile` like here

```
github "shotastage/whipped-cream" "master"
```

## Build framework

Then, you build *.framework* using Carthage. In shortest way of building framework, following command is easy.

```shell
$ carthage update whipped-cream
```

Sometimes, Carthage failed to fetch or build frameworks. If you face to such trouble, try following command.

```shell
$ carthage update --platform iOS --no-use-binaries --use-ssh --new-resolver whipped-cream
```

repository: shotastage/whipcream-swift

gha_language: Swift

repo_name: shotastage/whipcream-swift


text:
# Use Amazon RDS with MySQL engine for your Code Dx database

Code Dx recommends using an RDS database instance with the [MariaDB database engine](use-rds-for-code-dx-database.md), but these instructions are here to support those who are unable to use MariaDB.

>Note: Code Dx currently requires [MySQL version 8.0.x](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

1) Your new MySQL RDS database instance must use a configuration that's compatible with Code Dx. Follow the [Create a DB Parameter Group instructions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html#USER_WorkingWithParamGroups.Creating) to create a new DB Parameter Group named codedx-mysql-recommendation. Then edit the parameters of your new group by using the [Modifying Parameters in a DB Parameter Group instructions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html#USER_WorkingWithParamGroups.Modifying) to set the following parameter values:

- optimizer_search_depth=0
- character_set_server=utf8mb4
- collation_server=utf8mb4_general_ci
- lower_case_table_names=1
- log_bin_trust_function_creators=1

>Note: When editing a parameter value, the column to the right of the edit box shows the allowable values (not the current values).

The log_bin_trust_function_creators parameter is required when using replication, which is enabled by default with the AWS MySQL Production template.

2) Provision a new Amazon RDS MySQL database instance with the codedx-mysql-recommendation DB Parameter Group by following the [installation instructions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html).

3) Connect to your RDS MySQL database instance.

4) Create a database user for Code Dx. You can customize the following statement to create
   a Code Dx database user named codedx (remove 'REQUIRE SSL' when not using TLS).

   CREATE USER 'codedx'@'%' IDENTIFIED BY 'enter-a-password-here' REQUIRE SSL;

5) Create a Code Dx database. The following statement creates a Code Dx database named codedxdb.

   CREATE DATABASE codedxdb;

6) Grant required privileges on the Code Dx database to the database user you created. The
   following statements grant permissions to the codedx database user.

   GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, CREATE TEMPORARY TABLES, ALTER, REFERENCES, INDEX, DROP, TRIGGER ON codedxdb.* to 'codedx'@'%';
   FLUSH PRIVILEGES;

repository: codedx/codedx-kubernetes

gha_language: PowerShell

repo_name: codedx/codedx-kubernetes


text:
addDCSubjects
=

A simple shell script which uses [exiftool](http://www.sno.phy.queensu.ca/~phil/exiftool/) to add a list of
[XMP dc subjects](http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html) to all compatible files in a
directory.

## Requirements

You need to have [exiftool](http://www.sno.phy.queensu.ca/~phil/exiftool/) installed on your system.

## Install

#### NPM
```bash
$ npm install -g adddcsubjects
```

## Usage

```bash
$ addDcSubjects -t feeding,five,thousand ../crass
```

## License

  [MIT](LICENSE)

repository: kyusu/addDcSubjects

repo_name: kyusu/addDcSubjects


text:
# Park N' Go

This is our BostonHackathon project that we demoed. It give you the best places to park,
using data from Liberty Mutuals shine API. Also it overlays a heat map of the so called
'dangerous' places that have been classified as dangerous by a classifier we built using the
Crimes in Boston data we found on Kaggle.

Using the ease of the web and the power of Data Mining we combined the two in this project
to allow people live safer.

### Getting Started

There are two methods for getting started with this repo.

```
> git clone https://github.com/siddhantbenadikar/BostonHacks18.git
> cd BostonHacks18
> npm install
> npm start
```


text:
# Earthquake_Prediction
## About The Project

[\* This was an academic project.]

Our project data is from a laboratory prediction of earthquake occurrences. The scientists use a model like the picture shown below. They wrapped the rock sample by a sensor frame.

![Schematic diagram of experimental device](https://github.com/Runtao-Xue/Earthquake_Prediction/blob/main/Schematic%20diagram%20of%20experimental%20device.PNG)

The model will be putted in the high-temperature and high-pressure environment, just like the condition of crust movement of the Earth. Before they put the model into that environment, they added some ultrasonic transducer, which can recognize grain fault, around the wrapped cylinder.

Each time the grain occurs on the surface or within the sample, the ultrasonic transducer will reflect a signal. And the scientists regard those signals as the sample signal of every time the mini-earthquake happening.

Hence, we will get the acoustic signal data, which is the simulate sample of seismic signal, and the time to failure, the time interval between two mini-earthquake occurrences.

What we do is using these data to forecast the occurrence time of next mini-earthquake.

**Built With**

* [Numpy](https://numpy.org/)
* [Pandas](https://pandas.pydata.org/)
* [Seaborn](https://seaborn.pydata.org/)
* [Matplotlib](https://matplotlib.org/)

* [Scikit-learn](https://scikit-learn.org/stable/)

**Data Source**

[LANL Earthquake Prediction](https://www.kaggle.com/c/LANL-Earthquake-Prediction/) From [kaggle.com](https://www.kaggle.com/)

## Getting Started

**Installation**

1. Clone the repo

   ```
   git clone https://github.com/Runtao-Xue/Earthquake_Prediction
   ```

2. Install packages

   ```python
   # In Jupyter Notebook
   !pip install numpy
   !pip install pandas
   !pip install seaborn
   !pip install matplotlib
   !pip install scikit-learn
   ```

## Contact

Runtao Xue -<EMAIL_ADDRESS>
Project Link: https://github.com/Runtao-Xue/Earthquake_Prediction

## Acknowledgements

* Professor: Yingjie Zhang, PhD
* Group member: Tong Liu, Jiexuan Du

license: Unlicense

branch_name: refs/heads/main


text:
# CAPLibpp
C++ library to process NOAA CAP XML Files.
This library is designed to process NOAA CAP feeds as found at https://alerts.weather.gov/.

## Installation
It depends on Boost, curlpp, libcurl, and cmake.

```bash
mkdir build
cd build
cmake ..
make
```
## Tests
This project uses the Google Test framework.  Install that to run the tests.

```bash
mkdir build
cd build
cmake ..
make
cd tests
./caplibpp_unit_test
```

## Usage
See the main.cpp file under src.

## Contributing
Feel free! For anything major please open an issue first before issuing a pull

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

repository: briangmaddox/CAPLibpp

repo_name: briangmaddox/CAPLibpp


text:
# Hunger Free City
Connecting people to the needs of Community.

Hunger Free City provides easy way to find out what the needs of your local community are. Food Banks list top needed items, so that users, when they are shopping for donations items, can understand what the real needs are.

This forked repo is an alternative implementation implemented using freely accessible software using
Node.js + Mongodb server, iOS Swift, Android.

For the original Xamarin and .Net project, please go to  https://github.com/markradacz/HungerFreeCity

repository: mirchow/HungerFreeCity

repo_name: mirchow/HungerFreeCity


text:
# Charts For Grid

The Charts For Grid component displays line charts for the data at the grid with
specific latitude and longitude. In the application, this chart is displayed by
a button in the map popover.

##For developers

You can setup a map legend by importing `WaterStorageGridDiagram`:
.

```javascript
import WaterStorageGridDiagram from "../src/components/map/WaterStorageGridDiagram";

export const myCharts = () => {
    return (
        <div style={{padding: '20px', width:'600px', height:'500px'}}>
            <div style={{textAlign: 'center'}}>
                <h3>Charts for The Grid at (49.25, -19.25)</h3>
            </div>
            <WaterStorageGridDiagram
                latitude={49.25}
                longitude={-91.25}
            />
        </div>
    )
}
```

The map on the canvas was generated by using this code.


text:
# Automated API Test Suite
This Go-written API level test suite is an automated test where a list of test configurations in JSON format will be scanned automatically through single script, using [Gin as the framework](https://github.com/gin-gonic/gin).
## How to use
  1. Run the server: `go run main.go` (The port can be changed on the main.go file)
  2. Run the test: `go test .` (It will execute the test script located on the same level as main.go, in this case is main_test.go)
## Main Components
### Executor, Validator, and Response Handler
TestExecutor is a struct where request is created. It manages the URL, headers, body, and other request's contents. TestResponse is a container of the response retrieved, storing status code and response body (by default, any contents can be added if necessary). TestValidator is a module that check the response values whether those values match the expected ones.
### JSON Configuration
JSON file named `testConfig.json` is the script where all test cases are placed, stored in `/docs/json/test/`. All test cases must have the same format with each other, and each test case can have 1 or more jobs, in case there is a job that needs a values that must be retrieved by another job.
```
{
  "config_name": "",
  "hostname": "",
  "port": "",
  "schema": [
    {
      "test_title": "",
      "jobs": [
        {
          "test_name": "",
          "try": 0,
          "url": "",
          "method": "",
          "params": {},
          "header": {},
          "body": {},
          "save_keys": [],
          "expected": {
            "response_status": "",
            "body": {}
          }
        }
      ]
    }
  ]
}
```
The template above can also be found in `/docs/json/test/template.json`.

repository: joshiarheinier/automated-api-test-suite

repo_name: joshiarheinier/automated-api-test-suite


text:
---
layout: post
title:  "8_1_0_pre5"
date:   2017-10-07 22:24:56 +0200
categories: cmssw
relmajor: 8
relminor: 1
relsubminor: 0
relpre: _pre5
---

# CMSSW_8_1_0_pre5
#### Changes since CMSSW_8_1_0_pre4:

[compare to previous](https://github.com/cms-sw/cmssw/compare/CMSSW_8_1_0_pre4...CMSSW_8_1_0_pre5)

1. [14526](http://github.com/cms-sw/cmssw/pull/14526){:target="_blank"}  from **@kpedro88**: Fix setting the # of presamples for HcalUpgradeDataFrame. `simulation`  created: 2016-05-16T22:56:27Z merged: 2016-05-17T09:07:05Z

1. [14515](http://github.com/cms-sw/cmssw/pull/14515){:target="_blank"}  from **@Dr15Jones**: Changed global bool in TinyXML to be atomic `core`  created: 2016-05-16T15:36:26Z merged: 2016-05-17T07:59:35Z

1. [14504](http://github.com/cms-sw/cmssw/pull/14504){:target="_blank"}  from **@slava77**: numeric header include  for std::accumulate to fix gcc600 error `reconstruction`  created: 2016-05-14T10:25:47Z merged: 2016-05-15T20:07:35Z

1. [14503](http://github.com/cms-sw/cmssw/pull/14503){:target="_blank"}  from **@davidlt**: Ignore ICC specific flags (-ax_, -wd_) `comparison`  `db`  created: 2016-05-14T08:55:57Z merged: 2016-05-14T08:57:09Z

1. [14497](http://github.com/cms-sw/cmssw/pull/14497){:target="_blank"}  from **@Dr15Jones**: Special case for only one ProductResolver matching a blank Process re `core`  created: 2016-05-13T19:58:32Z merged: 2016-05-14T05:27:10Z

1. [14495](http://github.com/cms-sw/cmssw/pull/14495){:target="_blank"}  from **@cms-l1t-offline**: Update L1T Ntuples for l1t-tsg-v6-cand  `l1`  created: 2016-05-13T14:51:25Z merged: 2016-05-17T07:59:56Z

1. [14491](http://github.com/cms-sw/cmssw/pull/14491){:target="_blank"}  from **@vkhristenko**: HCAL DQM Updates. On top of 13805 `dqm`  created: 2016-05-13T10:52:24Z merged: 2016-05-13T15:20:36Z

1. [14490](http://github.com/cms-sw/cmssw/pull/14490){:target="_blank"}  from **@ahinzmann**: Cleanup unused pixel CPE code `reconstruction`  created: 2016-05-13T08:38:08Z merged: 2016-05-13T14:24:10Z

1. [14488](http://github.com/cms-sw/cmssw/pull/14488){:target="_blank"}  from **@bsunanda**: bsunanda:Phase2-hgx52 Enable single detector reconstruction (useful for TB) `geometry`  `reconstruction`  created: 2016-05-12T21:53:10Z merged: 2016-05-14T05:28:21Z

1. [14487](http://github.com/cms-sw/cmssw/pull/14487){:target="_blank"}  from **@cms-sw**: Fix wrong merge from 80X to 81X `hlt`  created: 2016-05-12T20:31:41Z merged: 2016-05-12T20:58:48Z

1. [14476](http://github.com/cms-sw/cmssw/pull/14476){:target="_blank"}  from **@fwyzard**: L1TGlobalProducer: migrate to stream module (81x) `l1`  created: 2016-05-12T13:59:52Z merged: 2016-05-13T07:11:16Z

1. [14475](http://github.com/cms-sw/cmssw/pull/14475){:target="_blank"}  from **@fwyzard**: HLT DQM: add protection for empty L1 uGT collection `dqm`  created: 2016-05-12T12:48:33Z merged: 2016-05-12T14:35:00Z

1. [14472](http://github.com/cms-sw/cmssw/pull/14472){:target="_blank"}  from **@makortel**: Fix SeedExtensionTrajectoryFilter when it is disabled `reconstruction`  created: 2016-05-12T10:49:51Z merged: 2016-05-15T20:07:46Z

1. [14468](http://github.com/cms-sw/cmssw/pull/14468){:target="_blank"}  from **@emiglior**: revert PixelDigitizerAlgorithm.DigitalReadout to False and CellsToKil `simulation`  created: 2016-05-12T07:49:46Z merged: 2016-05-12T17:22:35Z

1. [14466](http://github.com/cms-sw/cmssw/pull/14466){:target="_blank"}  from **@VinInn**: fix det search tolerances for Cosmics `reconstruction`  created: 2016-05-12T05:06:50Z merged: 2016-05-13T09:40:34Z

1. [14460](http://github.com/cms-sw/cmssw/pull/14460){:target="_blank"}  from **@Dr15Jones**:  Only construct tbb::task_scheduler_init once `core`  created: 2016-05-11T19:00:03Z merged: 2016-05-12T07:58:57Z

1. [14458](http://github.com/cms-sw/cmssw/pull/14458){:target="_blank"}  from **@cms-l1t-offline**: L1T Minimum Bias Trigger `l1`  created: 2016-05-11T18:25:02Z merged: 2016-05-12T14:38:09Z

1. [14455](http://github.com/cms-sw/cmssw/pull/14455){:target="_blank"}  from **@ianna**: Migrate GeomDetLess and GluedGeomDet to Geometry/CommonDetUnit `alca`  `analysis`  `dqm`  `fastsim`  `geometry`  `reconstruction`  created: 2016-05-11T14:48:28Z merged: 2016-05-14T18:10:04Z

1. [14452](http://github.com/cms-sw/cmssw/pull/14452){:target="_blank"}  from **@davidlt**: ReferenceCounted\* must always be the first in base class list `reconstruction`  `simulation`  created: 2016-05-11T12:27:49Z merged: 2016-05-14T18:10:34Z

1. [14450](http://github.com/cms-sw/cmssw/pull/14450){:target="_blank"}  from **@davidlt**: Move CaloTowerDetId selection rules to DataFormats/CaloTowers `reconstruction`  created: 2016-05-11T11:08:44Z merged: 2016-05-12T07:58:34Z

1. [14441](http://github.com/cms-sw/cmssw/pull/14441){:target="_blank"}  from **@lgray**: Fix ordering bug in reworked PFBlockAlgo `reconstruction`  created: 2016-05-10T19:16:29Z merged: 2016-05-12T17:23:18Z

1. [14439](http://github.com/cms-sw/cmssw/pull/14439){:target="_blank"}  from **@ianna**: Detector Description Include What You Use  `geometry`  created: 2016-05-10T16:36:37Z merged: 2016-05-13T14:24:34Z

1. [14438](http://github.com/cms-sw/cmssw/pull/14438){:target="_blank"}  from **@davidlt**: SIMDVec: enable USE_SSEVECT for __INTEL_COMPILER `reconstruction`  created: 2016-05-10T16:06:53Z merged: 2016-05-12T08:18:16Z

1. [14436](http://github.com/cms-sw/cmssw/pull/14436){:target="_blank"}  from **@ggovi**: Changes for O2O deployment and monitoring `db`  created: 2016-05-10T15:39:44Z merged: 2016-05-11T12:17:37Z

1. [14435](http://github.com/cms-sw/cmssw/pull/14435){:target="_blank"}  from **@davidlt**: Fix explicit GzInputStream::operator bool() const `comparison`  `l1`  created: 2016-05-10T13:09:52Z merged: 2016-05-11T17:36:50Z

1. [14434](http://github.com/cms-sw/cmssw/pull/14434){:target="_blank"}  from **@davidlt**: Fix explicit GzInputStream::operator bool() const `comparison`  `l1`  created: 2016-05-10T13:06:34Z merged: 2016-05-14T05:28:46Z

1. [14431](http://github.com/cms-sw/cmssw/pull/14431){:target="_blank"}  from **@cms-l1t-offline**: Bugfix of Giovanni Petrucciani for runaway combinatorics `l1`  created: 2016-05-10T10:04:26Z merged: 2016-05-10T10:05:51Z

1. [14429](http://github.com/cms-sw/cmssw/pull/14429){:target="_blank"}  from **@cms-sw**: Revert "L1TGlobalProducer: migrate to stream module (80x)" `comparison`  `l1`  created: 2016-05-10T09:35:17Z merged: 2016-05-10T09:36:06Z

1. [14428](http://github.com/cms-sw/cmssw/pull/14428){:target="_blank"}  from **@ianna**: Clean up clang warnings `geometry`  created: 2016-05-10T08:59:01Z merged: 2016-05-10T16:12:33Z

1. [14426](http://github.com/cms-sw/cmssw/pull/14426){:target="_blank"}  from **@avetisya**: Fixing L1 seed module name `hlt`  created: 2016-05-10T04:06:25Z merged: 2016-05-10T12:55:17Z

1. [14425](http://github.com/cms-sw/cmssw/pull/14425){:target="_blank"}  from **@avetisya**: Fixing L1 seed module name `hlt`  created: 2016-05-10T03:56:57Z merged: 2016-05-11T07:55:51Z

1. [14424](http://github.com/cms-sw/cmssw/pull/14424){:target="_blank"}  from **@calabria**: small bug fix me0 background `simulation`  created: 2016-05-10T00:13:48Z merged: 2016-05-10T16:11:28Z

1. [14423](http://github.com/cms-sw/cmssw/pull/14423){:target="_blank"}  from **@civanch**: fixed ZDC test `dqm`  `simulation`  created: 2016-05-09T17:37:29Z merged: 2016-05-13T08:12:35Z

1. [14418](http://github.com/cms-sw/cmssw/pull/14418){:target="_blank"}  from **@kpedro88**: Premixing for QIE10 `simulation`  created: 2016-05-09T16:25:42Z merged: 2016-05-10T16:11:15Z

1. [14416](http://github.com/cms-sw/cmssw/pull/14416){:target="_blank"}  from **@davidlt**: Add missing selection rules (GCC 6) `reconstruction`  created: 2016-05-09T13:42:37Z merged: 2016-05-10T12:54:57Z

1. [14414](http://github.com/cms-sw/cmssw/pull/14414){:target="_blank"}  from **@cms-l1t-offline**: Fix HLT-L1T seed index to be from begin BxVector `hlt`  created: 2016-05-09T13:25:43Z merged: 2016-05-09T14:03:11Z

1. [14413](http://github.com/cms-sw/cmssw/pull/14413){:target="_blank"}  from **@mtosi**: add track hit eff monitoring vs BX `dqm`  created: 2016-05-09T12:58:55Z merged: 2016-05-10T16:20:39Z

1. [14412](http://github.com/cms-sw/cmssw/pull/14412){:target="_blank"}  from **@archiron**: Electron validation 81X preshower `dqm`  created: 2016-05-09T12:42:15Z merged: 2016-05-10T12:54:44Z

1. [14408](http://github.com/cms-sw/cmssw/pull/14408){:target="_blank"}  from **@dmitrijus**: Add DQMStore::getElement whichs throws an exception instead of a nullptr (81x) `dqm`  created: 2016-05-09T08:18:10Z merged: 2016-05-10T12:51:48Z

1. [14407](http://github.com/cms-sw/cmssw/pull/14407){:target="_blank"}  from **@dmitrijus**: Add DQMStore::getElement whichs throws an exception instead of a nullptr (80x)  `dqm`  created: 2016-05-09T08:16:57Z merged: 2016-05-11T08:17:01Z

1. [14405](http://github.com/cms-sw/cmssw/pull/14405){:target="_blank"}  from **@civanch**: Clean-up Sim Exceptions `simulation`  created: 2016-05-07T19:38:34Z merged: 2016-05-09T07:19:51Z

1. [14404](http://github.com/cms-sw/cmssw/pull/14404){:target="_blank"}  from **@cippy**: Optimization of ECAL Pi0 stream timing `hlt`  created: 2016-05-07T16:16:04Z merged: 2016-05-09T07:14:56Z

1. [14401](http://github.com/cms-sw/cmssw/pull/14401){:target="_blank"}  from **@bsunanda**: bsunanda:Run2-hcx81 Correct the depth index for ieta=17 `geometry`  created: 2016-05-06T16:27:08Z merged: 2016-05-10T16:10:52Z

1. [14396](http://github.com/cms-sw/cmssw/pull/14396){:target="_blank"}  from **@Dr15Jones**: Added noexcept(false) to module destructors for gcc 6 `alca`  `analysis`  `core`  `db`  `dqm`  `generators`  `reconstruction`  `simulation`  `visualization`  created: 2016-05-06T15:01:53Z merged: 2016-05-12T07:56:24Z

1. [14392](http://github.com/cms-sw/cmssw/pull/14392){:target="_blank"}  from **@cms-l1t-offline**: L1REPAC 2016 2015 81x (clean history) `l1`  `operations`  created: 2016-05-06T10:23:17Z merged: 2016-05-07T15:27:00Z

1. [14391](http://github.com/cms-sw/cmssw/pull/14391){:target="_blank"}  from **@dildick**: Correctly configure CSC trigger primitive emulator for Run2 (81X) `l1`  created: 2016-05-05T21:58:40Z merged: 2016-05-14T18:12:09Z

1. [14387](http://github.com/cms-sw/cmssw/pull/14387){:target="_blank"}  from **@cms-l1t-offline**: L1REPACK 2016 2015 `l1`  `operations`  created: 2016-05-05T18:33:08Z merged: 2016-05-11T08:25:34Z

1. [14386](http://github.com/cms-sw/cmssw/pull/14386){:target="_blank"}  from **@bapavlov**: fixing Phase2 RPC local reco `reconstruction`  created: 2016-05-05T16:21:55Z merged: 2016-05-11T15:27:59Z

1. [14384](http://github.com/cms-sw/cmssw/pull/14384){:target="_blank"}  from **@kskovpen**: Keep muon parents in prunedGenParticles collection `analysis`  `reconstruction`  created: 2016-05-05T09:05:57Z merged: 2016-05-12T07:55:39Z

1. [14383](http://github.com/cms-sw/cmssw/pull/14383){:target="_blank"}  from **@igv4321**: Initial implementation of the pre-reco stage for the Phase 1 HF reco `reconstruction`  created: 2016-05-05T08:44:50Z merged: 2016-05-10T16:22:55Z

1. [14381](http://github.com/cms-sw/cmssw/pull/14381){:target="_blank"}  from **@barvic**: CSC Unpacker fixes for 2016 TMB/OTMB firmware updates (81X) `reconstruction`  created: 2016-05-04T17:54:43Z merged: 2016-05-10T12:51:33Z

1. [14380](http://github.com/cms-sw/cmssw/pull/14380){:target="_blank"}  from **@barvic**: CSC Unpacker fixes for 2016 TMB/OTMB firmware updates (80X) `reconstruction`  created: 2016-05-04T15:53:43Z merged: 2016-05-11T17:42:35Z

1. [14379](http://github.com/cms-sw/cmssw/pull/14379){:target="_blank"}  from **@fwyzard**: TriggerRatesMonitor: migrate to Stage 2 (81x) `dqm`  created: 2016-05-04T15:42:00Z merged: 2016-05-09T11:28:07Z

1. [14378](http://github.com/cms-sw/cmssw/pull/14378){:target="_blank"}  from **@fwyzard**: TriggerRatesMonitor: migrate to Stage 2 (80x) `dqm`  created: 2016-05-04T15:41:55Z merged: 2016-05-09T14:04:15Z

1. [14372](http://github.com/cms-sw/cmssw/pull/14372){:target="_blank"}  from **@makortel**: Update tracking MC validation scripts `dqm`  created: 2016-05-04T12:14:22Z merged: 2016-05-13T08:12:50Z

1. [14366](http://github.com/cms-sw/cmssw/pull/14366){:target="_blank"}  from **@thomaslenzi**: Fixed clusterizer for Threaded version of CMSSW `reconstruction`  created: 2016-05-04T08:33:18Z merged: 2016-05-06T08:44:21Z

1. [14364](http://github.com/cms-sw/cmssw/pull/14364){:target="_blank"}  from **@cms-l1t-offline**: Update L1T to l1t-tsg-v6-cand (81x) `l1`  created: 2016-05-04T02:07:25Z merged: 2016-05-13T14:30:57Z

1. [14363](http://github.com/cms-sw/cmssw/pull/14363){:target="_blank"}  from **@bsunanda**: bsunanda:Run2-hcx80 Get rid of parameter set HcalRelabel `geometry`  `simulation`  created: 2016-05-04T01:30:32Z merged: 2016-05-10T16:09:57Z

1. [14360](http://github.com/cms-sw/cmssw/pull/14360){:target="_blank"}  from **@wddgit**: Add new signal to ActivityRegistry around when a `core`  created: 2016-05-03T20:23:29Z merged: 2016-05-06T08:44:45Z

1. [14359](http://github.com/cms-sw/cmssw/pull/14359){:target="_blank"}  from **@cippy**: optimized CPU timing of ECAL Pi0 stream `hlt`  created: 2016-05-03T15:50:29Z merged: 2016-05-04T12:10:18Z

1. [14358](http://github.com/cms-sw/cmssw/pull/14358){:target="_blank"}  from **@cippy**: optimized CPU timing of ECAL Pi0 stream `hlt`  created: 2016-05-03T15:21:11Z merged: 2016-05-11T08:16:50Z

1. [14354](http://github.com/cms-sw/cmssw/pull/14354){:target="_blank"}  from **@JanFSchulte**: Change of StoN cut in hit selection for SiPixAli in PCL + 0T configs for the same `alca`  created: 2016-05-03T13:18:45Z merged: 2016-05-07T15:54:20Z

1. [14351](http://github.com/cms-sw/cmssw/pull/14351){:target="_blank"}  from **@fwyzard**: L1TGlobalProducer: migrate to stream module (80x) `l1`  created: 2016-05-03T13:04:50Z merged: 2016-05-07T16:10:21Z

1. [14350](http://github.com/cms-sw/cmssw/pull/14350){:target="_blank"}  from **@slava77**: sync with 80X and cleanup of obsolete T0 processing scenarios `alca`  `dqm`  `operations`  `reconstruction`  created: 2016-05-03T12:13:02Z merged: 2016-05-04T11:55:21Z

1. [14349](http://github.com/cms-sw/cmssw/pull/14349){:target="_blank"}  from **@fwyzard**: TriggerBxMonitor: migrate to Stage 2 (81x) `dqm`  created: 2016-05-03T12:11:18Z merged: 2016-05-04T13:24:54Z

1. [14348](http://github.com/cms-sw/cmssw/pull/14348){:target="_blank"}  from **@deguio**: fix EDMtoMEConverter for multiRun harvesting `dqm`  created: 2016-05-03T11:37:07Z merged: 2016-05-07T15:59:01Z

1. [14344](http://github.com/cms-sw/cmssw/pull/14344){:target="_blank"}  from **@VinInn**: avoid redundant computations in StripCPE `core`  `reconstruction`  created: 2016-05-03T10:13:49Z merged: 2016-05-07T15:29:40Z

1. [14341](http://github.com/cms-sw/cmssw/pull/14341){:target="_blank"}  from **@gpetruc**: SCEnergyCorrectorSemiParm: don't cache ES objects the wrong way `reconstruction`  created: 2016-05-03T09:16:25Z merged: 2016-05-04T12:15:05Z

1. [14340](http://github.com/cms-sw/cmssw/pull/14340){:target="_blank"}  from **@gpetruc**: SCEnergyCorrectorSemiParm: don't cache ES objects the wrong way `reconstruction`  created: 2016-05-03T09:15:02Z merged: 2016-05-07T15:42:54Z

1. [14338](http://github.com/cms-sw/cmssw/pull/14338){:target="_blank"}  from **@fwyzard**: TriggerBxMonitor: migrate to Stage 2 (80x) `dqm`  created: 2016-05-03T09:06:27Z merged: 2016-05-07T15:43:25Z

1. [14333](http://github.com/cms-sw/cmssw/pull/14333){:target="_blank"}  from **@kpedro88**: remove unneeded EE geometry from EcalRecHitWorkerRecover `reconstruction`  created: 2016-05-02T20:10:41Z merged: 2016-05-04T12:18:56Z

1. [14331](http://github.com/cms-sw/cmssw/pull/14331){:target="_blank"}  from **@lathomas**: Filling the fillDescription method of CaloRecHitsBeamHaloCleaned and  `reconstruction`  created: 2016-05-02T19:44:23Z merged: 2016-05-04T13:18:25Z

1. [14327](http://github.com/cms-sw/cmssw/pull/14327){:target="_blank"}  from **@makortel**: Improve low-pT performance of "quadruplets by propagation", and use it in phase1 tracking instead of "triplet merging" `reconstruction`  created: 2016-05-02T15:09:57Z merged: 2016-05-07T15:30:03Z

1. [14324](http://github.com/cms-sw/cmssw/pull/14324){:target="_blank"}  from **@cms-tsg-storm**: Towards the first hlt menu for 2016 - 81X `hlt`  created: 2016-05-02T14:51:08Z merged: 2016-05-09T07:16:43Z

1. [14323](http://github.com/cms-sw/cmssw/pull/14323){:target="_blank"}  from **@cms-l1t-offline**: Updates to L1T packer needed to simultaneously pack GT inputs and GMT/Calo ouputs `l1`  created: 2016-05-02T14:21:45Z merged: 2016-05-11T08:15:57Z

1. [14322](http://github.com/cms-sw/cmssw/pull/14322){:target="_blank"}  from **@schneiml**: SiPixelMonitorTrack invalid TSOS crash fix `alca`  `dqm`  created: 2016-05-02T13:58:58Z merged: 2016-05-07T15:43:56Z

1. [14320](http://github.com/cms-sw/cmssw/pull/14320){:target="_blank"}  from **@cms-l1t-offline**: Update L1Ntuples to l1t-tsg-v5, and address memory management problems. `l1`  created: 2016-05-02T11:50:08Z merged: 2016-05-11T08:15:17Z

1. [14318](http://github.com/cms-sw/cmssw/pull/14318){:target="_blank"}  from **@schneiml**: TrackerMonitorTrack: Fix side for TID so that TID/MINUS histograms appear. `dqm`  created: 2016-05-02T08:58:35Z merged: 2016-05-07T15:44:08Z

1. [14316](http://github.com/cms-sw/cmssw/pull/14316){:target="_blank"}  from **@sushilchauhan**: update of dqm  client config for online beam spot, running pixel trac `dqm`  created: 2016-04-30T20:18:52Z merged: 2016-05-07T15:35:38Z

1. [14315](http://github.com/cms-sw/cmssw/pull/14315){:target="_blank"}  from **@sushilchauhan**: update dqm  client config for online beam spot running pixel tracking `dqm`  created: 2016-04-30T20:14:30Z merged: 2016-05-11T08:14:57Z

1. [14313](http://github.com/cms-sw/cmssw/pull/14313){:target="_blank"}  from **@bsunanda**: bsunanda:Run2-hcx78 Correct access of HcalTopology `alca`  `db`  `geometry`  `l1`  created: 2016-04-30T13:58:26Z merged: 2016-05-12T10:52:05Z

1. [14306](http://github.com/cms-sw/cmssw/pull/14306){:target="_blank"}  from **@jshlee**: bug fix for Me0 segments `reconstruction`  created: 2016-04-29T15:50:42Z merged: 2016-05-10T12:42:04Z

1. [14305](http://github.com/cms-sw/cmssw/pull/14305){:target="_blank"}  from **@jshlee**: Gem Geometry fix for 81x `geometry`  `simulation`  created: 2016-04-29T15:20:57Z merged: 2016-05-04T12:19:12Z

1. [14295](http://github.com/cms-sw/cmssw/pull/14295){:target="_blank"}  from **@bsunanda**: bsunanda:Run2-alca41 Change the name of L1GTSeed (backport from 8_1_X) `alca`  created: 2016-04-28T22:27:37Z merged: 2016-05-02T06:04:00Z

1. [14287](http://github.com/cms-sw/cmssw/pull/14287){:target="_blank"}  from **@jruizvar**: Implement HLT_TkMu50_v into EXO DQM (80X) `dqm`  created: 2016-04-27T22:03:21Z merged: 2016-05-07T15:57:52Z

1. [14286](http://github.com/cms-sw/cmssw/pull/14286){:target="_blank"}  from **@jruizvar**: Implement HLT_TkMu50_v into EXO DQM (81X) `dqm`  created: 2016-04-27T22:03:11Z merged: 2016-05-04T11:54:15Z

1. [14285](http://github.com/cms-sw/cmssw/pull/14285){:target="_blank"}  from **@cms-l1t-offline**: Updates to L1TCaloLayer1 and unpacker (80X) `l1`  created: 2016-04-27T20:48:03Z merged: 2016-05-11T08:14:31Z

1. [14283](http://github.com/cms-sw/cmssw/pull/14283){:target="_blank"}  from **@davidsheffield**: Quietly return when producer fails to find input collection `hlt`  created: 2016-04-27T20:22:15Z merged: 2016-05-04T13:17:31Z

1. [14281](http://github.com/cms-sw/cmssw/pull/14281){:target="_blank"}  from **@mmusich**: Update Global Tag for Collisions2016_v1 L1T menu and splitting Ecal Pedestal tags `alca`  created: 2016-04-27T19:54:21Z merged: 2016-05-11T08:14:14Z

1. [14279](http://github.com/cms-sw/cmssw/pull/14279){:target="_blank"}  from **@duanders**: Jet ID and b-tag information for Scouting Calojets (80X) `core`  `hlt`  created: 2016-04-27T19:48:34Z merged: 2016-05-02T06:05:16Z

1. [14272](http://github.com/cms-sw/cmssw/pull/14272){:target="_blank"}  from **@silviodonato**:  Pixel PU jet update (backport of #14269 in 80X) `hlt`  created: 2016-04-27T15:55:02Z merged: 2016-05-02T07:12:43Z

1. [14267](http://github.com/cms-sw/cmssw/pull/14267){:target="_blank"}  from **@makortel**: Remove obsolete customiseForRunI `reconstruction`  `simulation`  created: 2016-04-27T09:10:36Z merged: 2016-05-09T11:37:26Z

1. [14260](http://github.com/cms-sw/cmssw/pull/14260){:target="_blank"}  from **@deguio**: fix DQMExample `dqm`  created: 2016-04-26T16:58:10Z merged: 2016-05-04T11:53:36Z

1. [14258](http://github.com/cms-sw/cmssw/pull/14258){:target="_blank"}  from **@acimmino**: RPC DQM ONLINE Patch for Active Channel Fraction `dqm`  created: 2016-04-26T16:53:14Z merged: 2016-05-07T15:47:55Z

1. [14249](http://github.com/cms-sw/cmssw/pull/14249){:target="_blank"}  from **@makortel**: Migrate tracking DQM to phase1 and enable it `dqm`  created: 2016-04-26T12:59:21Z merged: 2016-05-13T08:14:36Z

1. [14248](http://github.com/cms-sw/cmssw/pull/14248){:target="_blank"}  from **@makortel**: Add plots vs. seeding layer set to MultiTrackValidator `dqm`  `reconstruction`  created: 2016-04-26T11:58:48Z merged: 2016-05-04T11:52:31Z

1. [14218](http://github.com/cms-sw/cmssw/pull/14218){:target="_blank"}  from **@fioriNTU**: Add protection to consider only Strip hits `dqm`  created: 2016-04-22T19:21:04Z merged: 2016-05-07T15:47:39Z

1. [14217](http://github.com/cms-sw/cmssw/pull/14217){:target="_blank"}  from **@fioriNTU**: fix to fill properly the rec-hits Tracker maps 81X `dqm`  created: 2016-04-22T19:02:42Z merged: 2016-05-10T12:40:38Z

1. [14214](http://github.com/cms-sw/cmssw/pull/14214){:target="_blank"}  from **@jpazzini**: Fixes involving DQM/Physics for Exo `dqm`  created: 2016-04-22T16:14:03Z merged: 2016-05-09T11:37:45Z

1. [14210](http://github.com/cms-sw/cmssw/pull/14210){:target="_blank"}  from **@dimattia**: Calibration update 80 x `alca`  created: 2016-04-22T14:19:11Z merged: 2016-05-02T05:57:33Z

1. [14208](http://github.com/cms-sw/cmssw/pull/14208){:target="_blank"}  from **@mbandrews**: Add pulse max check parameter `dqm`  created: 2016-04-22T14:14:28Z merged: 2016-05-07T15:57:40Z

1. [14150](http://github.com/cms-sw/cmssw/pull/14150){:target="_blank"}  from **@rovere**: Enable OfflinePV and Beamspot in trackingLowPU era `dqm`  `reconstruction`  created: 2016-04-19T16:08:33Z merged: 2016-05-11T08:28:16Z

1. [14147](http://github.com/cms-sw/cmssw/pull/14147){:target="_blank"}  from **@sarafiorendi**: update muon validation plots to Stage2L1 + update HLT DQM plots (backport of #14146) `dqm`  created: 2016-04-19T13:29:14Z merged: 2016-05-11T08:14:02Z

1. [14145](http://github.com/cms-sw/cmssw/pull/14145){:target="_blank"}  from **@davidlt**: Misc. cleanup for CondFormats/HcalObjects (UNIX format & style) `alca`  `db`  created: 2016-04-19T12:12:51Z merged: 2016-05-14T05:30:17Z

1. [14136](http://github.com/cms-sw/cmssw/pull/14136){:target="_blank"}  from **@sarafiorendi**: modify L2MuonSeedGeneratorFromL1T to deal with possible L1 zero charge (backport) `reconstruction`  created: 2016-04-19T10:11:24Z merged: 2016-05-02T05:57:57Z

1. [14097](http://github.com/cms-sw/cmssw/pull/14097){:target="_blank"}  from **@jwwetzel**: HF Radiation Damage Simulation V2016 `alca`  `simulation`  created: 2016-04-15T17:23:16Z merged: 2016-05-10T12:40:26Z

1. [14008](http://github.com/cms-sw/cmssw/pull/14008){:target="_blank"}  from **@silviodonato**: Change of VBF Hbb HLT path names in DQM code (online,offline,relval) (backport of #13966 in 80X) `dqm`  created: 2016-04-10T10:23:32Z merged: 2016-05-02T05:59:53Z

1. [13993](http://github.com/cms-sw/cmssw/pull/13993){:target="_blank"}  from **@Dr15Jones**: Cleanup sim mergeable products `generators`  created: 2016-04-08T14:49:46Z merged: 2016-05-10T16:56:14Z

1. [13973](http://github.com/cms-sw/cmssw/pull/13973){:target="_blank"}  from **@fioriNTU**: improve TkMaps 81X `dqm`  created: 2016-04-07T12:50:45Z merged: 2016-05-11T14:06:05Z

1. [13951](http://github.com/cms-sw/cmssw/pull/13951){:target="_blank"}  from **@kirschen**: add L2L3Residual as know correction level to JetCorrector[Calculator] `analysis`  `db`  created: 2016-04-06T10:05:37Z merged: 2016-05-07T15:56:46Z

1. [13805](http://github.com/cms-sw/cmssw/pull/13805){:target="_blank"}  from **@vkhristenko**: Online HCAL DQM adding a new application `dqm`  created: 2016-03-22T21:21:58Z merged: 2016-05-11T13:23:46Z

1. [13759](http://github.com/cms-sw/cmssw/pull/13759){:target="_blank"}  from **@gouskos**: barrel vs ladder in roc level in 81x `dqm`  created: 2016-03-17T16:17:34Z merged: 2016-05-11T08:03:27Z

1. [13421](http://github.com/cms-sw/cmssw/pull/13421){:target="_blank"}  from **@mtosi**: update trajectory filters (minNumberOfHits --> minNumberOfHitsForLoopers) `hlt`  `reconstruction`  created: 2016-02-22T09:56:45Z merged: 2016-05-11T17:37:32Z

#### CMSDIST Changes between Tags REL/CMSSW_8_1_0_pre4/slc6_amd64_gcc530 and REL/CMSSW_8_1_0_pre5/slc6_amd64_gcc530:

[compare to previous](https://github.com/cms-sw/cmsdist/compare/REL/CMSSW_8_1_0_pre4/slc6_amd64_gcc530...REL/CMSSW_8_1_0_pre5/slc6_amd64_gcc530)

1. [2297](http://github.com/cms-sw/cmssw/pull/2297){:target="_blank"}  from **@degano**: Update SLHCUpgradeSimulations/Geometry data. created: 2014-02-04T19:56:59Z merged: 2014-02-04T19:59:01Z

1. [2288](http://github.com/cms-sw/cmssw/pull/2288){:target="_blank"}  from **@smuzaffar**: Updated root to tip e4b3d70 of v6-06-00 patches branch created: 2014-02-04T09:04:03Z merged: 2014-02-04T11:16:05Z

1. [2286](http://github.com/cms-sw/cmssw/pull/2286){:target="_blank"}  from **@degano**: Fix data files for SLHCUpgradeSimulations/Geometry created: 2014-02-04T08:13:42Z merged: None

1. [2282](http://github.com/cms-sw/cmssw/pull/2282){:target="_blank"}  from **@cms-sw**: Update utm to r45210-xsd310-patch created: 2014-02-03T19:20:00Z merged: 2014-02-04T15:09:13Z

1. [2281](http://github.com/cms-sw/cmssw/pull/2281){:target="_blank"}  from **@cms-sw**: Update data-L1Trigger-L1TCalorimeter.spec created: 2014-02-03T19:09:41Z merged: 2014-02-04T08:48:46Z

1. [2274](http://github.com/cms-sw/cmssw/pull/2274){:target="_blank"}  from **@smuzaffar**: Updated root to tip of 86c0d59 created: 2014-02-03T16:21:23Z merged: None

repository: rovere/ReleaseNotes

repo_name: rovere/ReleaseNotes


text:
---
layout: default
title: Projects
---
GitHub :sparkles:
Resume :thumbsup:
LinkedIn :laughing:
RIP StackOverflow CV :skull:

# Nick Christiny
## Software Development & Security
### Projects

### Watch This!
Film recommendation engine API built from scratch. Rails-API MongoDB backend and React frontend with Webpack. Testing Rspec, Guard and Mocha, Chai. Source code (back end). Source code (front end).

### Chord Explorer
Ruby on Rails single page app. Final group project for Dev Bootcamp, completed during 8 days in November 2015. Shows the user songs they are able to learn given a combination of known chords. Also suggests new chords to learn next. Source code.

### Catstream
Lightweight Sinatra app, fun with `instagram-ruby-gem` and Instagram API. This was deployed and hosted on Heroku until June 1 2016 Instagram API rule changes for media viewer type 3rd-party apps. Source code.

### Gaming: The System
Web app CRUD functionality. Built observing the 12-factor app methodology. Source code.

### Magic 8 Ball™ Simulator
Just for fun, a little Sinatra app that I made in my spare time to practice authentication, authorization, AJAX calls and RESTful routing. Source code.

gha_language: SCSS


text:
# React Starter Kit

The web's most popular Jamstack front-end template for building web applications with
[React](https://react.dev/).

## Features

- Optimized for serverless deployment to CDN edge locations (Cloudflare Workers)
- HTML page rendering (SSR) at CDN edge locations, all ~100 points on Lighthouse
- Hot module replacement during local development using React Refetch
- Pre-configured with CSS-in-JS styling using Emotion.js
- Pre-configured with code quality tools: ESLint, Prettier, TypeScript, Vitest, etc.
- Pre-configured with VSCode code snippets and other VSCode settings
- The ongoing design and development is supported by these wonderful companies:

---

This project was bootstrapped with [React Starter Kit](https://github.com/kriasoft/react-starter-kit).
Be sure to join our [Discord channel](https://discord.com/invite/2nKEnKq) for assistance.

## Directory Structure

`├──`[`.github`](.github) — GitHub configuration including CI/CD workflows

`├──`[`.vscode`](.vscode) — VSCode settings including code snippets, recommended extensions etc.

`├──`[`app`](./app) — Web application front-end built with [React](https://react.dev/) and [Material UI](https://mui.com/core/)

`├──`[`edge`](./edge) — Cloudflare Workers (CDN) edge endpoint

`├──`[`env`](./env) — Application settings, API keys, etc.

`├──`[`scripts`](./scripts) — Automation scripts such as `yarn deploy`

`├──`[`tsconfig.base.json`](./tsconfig.base.json) — The common/shared TypeScript configuration

`└──`[`tsconfig.json`](./tsconfig.json) — The root TypeScript configuration

## Tech Stack

- [React](https://react.dev/), [React Router](https://reactrouter.com/), [Recoil](https://recoiljs.org/), [Emotion](https://emotion.sh/), [Material UI](https://next.material-ui.com/), [Firebase Authentication](https://firebase.google.com/docs/auth)
- [Cloudflare Workers](https://workers.cloudflare.com/), [Vite](https://vitejs.dev/), [Vitest](https://vitejs.dev/),
  [TypeScript](https://www.typescriptlang.org/), [ESLint](https://eslint.org/), [Prettier](https://prettier.io/), [Yarn](https://yarnpkg.com/) with PnP

## Requirements

- [Node.js](https://nodejs.org/) v18+ with [Corepack](https://nodejs.org/api/corepack.html) (`$ corepack enable`)
- [VS Code](https://code.visualstudio.com/) editor with [recommended extensions](.vscode/extensions.json)
- Optionally [React Developer Tools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en)
  and [Reactime](https://chrome.google.com/webstore/detail/reactime/cgibknllccemdnfhfpmjhffpjfeidjga?hl=en) browser extensions

## Getting Started

[Generate](https://github.com/kriasoft/react-starter-kit/generate) a new project
from this template, clone it, install project dependencies, update the
environment variables found in [`env/*.env`](./env/), and start hacking:

```
$ git clone https://github.com/kriasoft/react-starter-kit.git example
$ cd ./example
$ yarn install
$ yarn start
```

The app will become available at [http://localhost:5173/](http://localhost:5173/) (press `q` key to exit).

**IMPORTANT**: Ensure that VSCode is using the workspace [version of TypeScript](https://code.visualstudio.com/docs/typescript/typescript-compiling#_using-newer-typescript-versions)
and ESLint.

![](https://files.tarkus.me/typescript-workspace.png)

## Scripts

- `yarn start` — Launches the app in development mode on [`http://localhost:5173/`](http://localhost:5173/)
- `yarn build` — Compiles and bundles the app for deployment
- `yarn lint` — Validate the code using ESLint
- `yarn tsc` — Validate the code using TypeScript compiler
- `yarn test` — Run unit tests with Vitest, Supertest
- `yarn edge deploy` — Deploys the app to Cloudflare

## How to Deploy

Ensure that all the environment variables for the target deployment environment
(`test`, `prod`) found in [`/env/*.env`](./env/) files are up-to-date.

If you haven't done it already, push any secret values you may need to CF Workers
environment by running `yarn workspace edge wrangler secret put <NAME> [--env #0]`.

Finally build and deploy the app by running:

```
$ yarn build
$ yarn deploy [--env #0] [--version #0]
```

Where `--env` argument is the target deployment area, e.g. `yarn deploy --env=prod`.

## How to Update

- `yarn set version latest` — Bump Yarn to the latest version
- `yarn upgrade-interactive` — Update Node.js modules (dependencies)
- `yarn dlx @yarnpkg/sdks vscode` — Update TypeScript, ESLint, and Prettier settings in VSCode

## Contributors 👨💻

## Backers 💰

## Related Projects

- [GraphQL API and Relay Starter Kit](https://github.com/kriasoft/graphql-starter) — monorepo template, pre-configured with GraphQL API, React, and Relay
- [Cloudflare Workers Starter Kit](https://github.com/kriasoft/cloudflare-starter-kit) — TypeScript project template for Cloudflare Workers
- [Node.js API Starter Kit](https://github.com/kriasoft/node-starter-kit) — project template, pre-configured with Node.js, GraphQL, and PostgreSQL

## How to Contribute

Anyone and everyone is welcome to [contribute](.github/CONTRIBUTING.md). Start
by checking out the list of [open issues](https://github.com/kriasoft/react-starter-kit/issues)
marked [help wanted](https://github.com/kriasoft/react-starter-kit/issues?q=label:"help+wanted").
However, if you decide to get involved, please take a moment to review the
[guidelines](.github/CONTRIBUTING.md).

## License

Copyright © 2014-present Kriasoft. This source code is licensed under the MIT license found in the
[LICENSE](https://github.com/kriasoft/react-starter-kit/blob/main/LICENSE) file.

---

Made with ♥ by Konstantin Tarkus ([@koistya](https://twitter.com/koistya), [blog](https://medium.com/@koistya))
and [contributors](https://github.com/kriasoft/react-starter-kit/graphs/contributors).

repository: kriasoft/react-starter-kit

repo_name: kriasoft/react-starter-kit


text:
# Todo

- [ ] Setup CopyBara to move code to olivr/\_stack:
  - Ignore .github/CODEOWNERS
- [ ] Bot should check if PR requester is codeowner and automatically approve PR on '/review' https://bionic.fullstory.com/taming-github-codeowners-with-bots/
- [ ] Implement /rebase on PR

repository: Olivr/oStack

gha_language: HCL

repo_name: Olivr/oStack


text:
##  Python API

The **Package Creator** can be embedded into your Python application to create packages programmatically.

#### Example

This uses the C_Library template to create a package /tmp/test/Foo/1.0 with the category set to "Libraries/Data":

    from ToolBOSCore.Packages.PackageCreator import PackageCreator_C_Library

    values = { 'category': 'Libraries/Data' }
    pc     = PackageCreator_C_Library( 'Foo', '1.0', values, '/tmp/test' )

    pc.run()

####  "values" documentation

values must be a Python dict containing any of the following keys:

|key 	          |datatype | 	description
|-----------------|---------|----------------
| buildRules      |	string  | Put this text verbatim in the CMakeLists.txt instead of the default build instructions. Note that if this key is specified then srcFilesPattern, exeFilesPattern, preBuildRules and postBuildRules have no effect.
| buildRules      |	string 	| Put this text verbatim in the CMakeLists.txt instead of the default build instructions. Note that if this key is specified then srcFilesPattern, exeFilesPattern, preBuildRules and postBuildRules have no effect.
| postBuildRules  |	string  | Put this text verbatim in the CMakeLists.txt right after the default build rules.
| srcFilesPattern |	string  | Glob-expression which shall be used for searching library source files (e.g. "src/A/*.c src/B/*.c"). Has no effect if buildRules is specified.
| exeFilesPattern |	string  | Glob-expression which shall be used for searching main program source files (e.g. "bin/*.c examples/*.c"). Has no effect if buildRules is specified.
| category        |	string  | SIT category of the package, such as "Libraries"
| category        |	string  | SIT category of the package, such as "Libraries"
| force           |	boolean | ignore certain safety checks, f.i. overwrite existing files

**See also**
    PackageCreator.py

repository: HRI-EU/ToolBOSCore

gha_language: Python

repo_name: HRI-EU/ToolBOSCore


text:
## Features

* Accurate & performance optimized detection for both Zawgyi-One (ဇော်ဂျီ) and standard Myanmar Unicode (မြန်မာ ယူနီကုဒ်)
* Intelligent chunk by chunk detection on mix-typed input (Mixed Zawgyi and Unicode)
* Fully tested with Myanmar Spelling Book (မြန်မာ စာလုံးပေါင်း သတ်ပုံကျမ်း) data
* Work with latest versions of Angular
* Compatible with Angular Universal (Server Side Rendering - SSR)

## Changes

* Fix bugs and improve detection

npm package is available on:

[@myanmartools/ng-zawgyi-detector](https://www.npmjs.com/package/@myanmartools/ng-zawgyi-detector)

repository: mmzliveid/ng-zawgyi-detector

repo_name: mmzliveid/ng-zawgyi-detector


text:
# Blood Bank Management System

This system is made to ease the handling of the recipient and the donor blood using an encrypted login system in C++.

## Requirements
##### To run the Executable, no pre-requisites are required, it will work on all Windows System
##### To Run the C++ Code, following are the requirements,
- g++ 9.2.0
- C++ 17
- Filesystem.h
- Json.hpp [Github](https://github.com/nlohmann/json)
- ```g++ -std=c++17 main.cpp && a.exe```

## Start-Up

On execution of the software, the following options are presented:
1. Admin Login
2. Patient Login
3. Exit

### Admin Login
This method takes in the admin password and sends it to a dynamic encryption hashing algorithm to encrypt the password while decrypting the original stored password and dynamically re-hashing it to match with the entered password.

![Login Encryption System](https://github.com/kartikeya72001/Blood-Bank-Management/blob/master/Images/AdminLogin.jpg?raw=true)

## Admin Functionality
- Check Blood Availability
- Search Patient by Name
- Display all Patients
- Generate a Combined Report for all Hospital Patients
- View and Accept/Reject Blood Requests
- Change Admin Password(Encrypted)

#### Check Blood Availability
This system function displays all the types of blood available with the hospital with their respective quantities.
#### Search Patient
It enables the admin to search for a patient by the first name. It returns all the patients matching the input first name string.
#### Display
This method displays all the donor and well all recipient patients registered with the portal.
#### Generate Hospital Report
This method exports a comma-separated file for all the registered patients in the hospital system.
### View Requests
This function enables the admin to manage all the recipient requests that are registered in the system. all the requests are displayed along with the available quantities of blood.
#### Change Admin Password
This method takes admin input via a private variable encrypts the input and stores the input into a file for future references.

![Password Reset](https://github.com/kartikeya72001/Blood-Bank-Management/blob/master/Images/ResetPwd.jpg?raw=true)

### Patient Menu
Patient Menu provides an option for the patient to either register as a new patient or instead log in to his/her account using his/her unique Patient Id.

- Donate
- Request
- Login

##### New Patient
Any new patient will be prompted to add his/her personal as well as medical details for donating or requesting blood. On successful completion of the request or donate menu, a unique patient Id will be generated signifying the addition of the patient into the hospital system.

##### Registered Patient
Any patient with a history with the hospital can use his earlier patient ID to log into the hospital system to request or donate blood without requiring to re-enter his/her personal details.

- Generate Report
- Request Blood
- Donate Blood

##### Generate Report
The patient can generate his/her report associated with the login id with all details exported to a comma-separated file.

##### Request/Donate Blood
The patient can Donate/Request more blood without having the need to re-enter all the personal details.

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


text:
---
Module Name: AutomatedLab.Recipe
Module Guid: 0c1fa63a-6982-48c3-bc12-c74806861b08
Download Help Link: {{ Update Download Link }}
Help Version: <IP_ADDRESS>
Locale: en-US
---

# AutomatedLab.Recipe Module
## Description
The AutomatedLab.Recipe module was intended to make simple labs even easier. Through a pseudo-DSL and a handful of cmdlets, you can deploy very simple labs like Domain with PKI on the go.
```powershell
LabRecipe SuperEasy {
    DeployRole = 'Domain', 'PKI'
} | Invoke-LabRecipe
```

## AutomatedLab.Recipe Cmdlets
### [Export-LabSnippet](Export-LabSnippet.md)
Export a snippet

### [Get-LabRecipe](Get-LabRecipe.md)
Get a lab recipe to invoke fresh or from the store

### [Get-LabSnippet](Get-LabSnippet.md)
Get a (filtered) list of lab code snippets

### [Invoke-LabRecipe](Invoke-LabRecipe.md)
Invoke a recipe

### [Invoke-LabSnippet](Invoke-LabSnippet.md)
Invoke one or more lab snippets

### [New-LabRecipe](New-LabRecipe.md)
Create and store a new lab recipe

### [New-LabSnippet](New-LabSnippet.md)
Create a new snippet, sample or custom role

### [Remove-LabRecipe](Remove-LabRecipe.md)
Remove a stored recipe

### [Remove-LabSnippet](Remove-LabSnippet.md)
Remove one or more snippets

### [Save-LabRecipe](Save-LabRecipe.md)
Save a lab recipe to disk

### [Set-LabSnippet](Set-LabSnippet.md)
Update a snippet

### [Update-LabSnippet](Update-LabSnippet.md)
Update the list of lab snippets

repository: AutomatedLab/AutomatedLab

branch_name: refs/heads/develop

repo_name: AutomatedLab/AutomatedLab


text:
# paye-registration-frontend

[ ![Download](https://api.bintray.com/packages/hmrc/releases/paye-registration-frontend/images/download.svg) ](https://bintray.com/hmrc/releases/paye-registration-frontend/_latestVersion)

Source code for the PAYE Registration frontend microservice, part of the SCRS journey.

## Running the Application

In order to run the microservice, you must have SBT installed. You should then be able to start the application using:

```sbt "run 9870 -Dapplication.router=testOnlyDoNotUseInAppConf.Routes"```

To run the tests for the application, you can run: ```sbt test it:test```

or ```sbt coverage test it:test coverageReport```

###  License

This code is open source software licensed under the [Apache 2.0 License]("http://www.apache.org/licenses/LICENSE-2.0.html")

repository: jezd-hmrc/paye-registration-frontend

repo_name: jezd-hmrc/paye-registration-frontend


text:
# Angular Practice Assignment
How to use the repo :

1.Clone the project to your machine :
    git clone https://github.com/Prashanth-Arralli/Anuglar-Assgn.git

2.After cloning go into project folder:
    cd Angular-Assgn
3.Install npm packages using below command:
    npm install ;
4.Run the project:
    npm start

repository: Prashanth-Arralli/Anuglar-Assgn

repo_name: Prashanth-Arralli/Anuglar-Assgn


text:
# Lab 7

## Admissions

So, unfortunately for prospective students, my analysis turned up no obvious
factors that seem to lead to admission, at least not at a significant level.
However, there did seem to be some strong predictors of *not* being admitted.
Particularly, if you had a rank of 4, which was the lowest possible ranking, you
weren't very likely to be admitted. Furthermore, having a bad GRE score seemed
to be fairly detrimental, even if you had a decent rank. Particularly, a score
below 600 was iffy.

Here are some nifty plots:

![Plot 1](/images/admissions_plot_1.png)
![Plot 2](/images/admissions_plot_2.png)
![Plot 3](/images/admissions_plot_3.png)
![Plot 4](/images/admissions_plot_4.png)
![Plot 5](/images/admissions_graph_5.png)

## Electoral Data

There's not a whole lot of data for this, and I had to discretize it first
before I could do anything useful. The most interesting thing that I found
through this analysis was consistently that a low number of total votes cast
implies that Bush won by a relatively high margin in that state. Given what I
know about American politics, this seems reasonable. Interestingly, I would
expect the opposite association as well, but that didn't really materialize.

## Top Movies

Here are some things I've learned about movies:

- From 1981 - 1996, most movies were in the bottom quintile in terms of
  money made.
- 1996 - 2010 was similar, although the trend was slightly less pronounced.
- Movies that come out in the spring seem to make less money.
- From 1996 to 2010, more movies came out in the fall (30%) than would be
  expected by random chance. (25%)
- Incidentally, movies that come out in the fall seem highly likely to fall into
  the bottom fifth in terms of money made.


text:
# ![Thinodium](https://thinodium.github.io/img/logo.svg)

[![Build Status](https://travis-ci.org/thinodium/thinodium.svg?branch=master)](http://travis-ci.org/thinodium/thinodium)
[![npm](https://img.shields.io/npm/v/thinodium.svg?maxAge=2592000)](https://www.npmjs.com/package/thinodium)
[![Join the chat at https://discord.gg/bYt4tWB](https://img.shields.io/badge/discord-join%20chat-738bd7.svg?style=flat-square)](https://discord.gg/bYt4tWB)
[![Follow on Twitter](https://img.shields.io/twitter/url/http/shields.io.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/hiddentao)

A "thin ODM" which is less opinionated and tries to give you query flexibility
whilst still providing helpful document handling.

Features:

* ES6-ready with Promises, no callbacks
* Allows you to handle connections yourself
* Add virtual fields to documents
* Fully pluggable - easy to add support for your DB of choice
* Listen to before and after events on internal asynchronous methods
* Schema validation ([sjv](https://github.com/hiddentao/sjv)).

Read the [documentation](https://thinodium.github.io/) for more.

## Installation

**This package requires Node 4 or above**

```bash
$ npm install thinodium
```

This package provides the core infrastructure. To actually access a particular
database you will need to additionally install one of the following adapters:

* [thinodium-mongodb](https://github.com/thinodium/thinodium-rethinkdb) - MongoDB
* [thinodium-rethinkdb](https://github.com/thinodium/thinodium-rethinkdb) - RethinkDB
* [thinodium-knex](https://github.com/thinodium/thinodium-knex) - Knex (Postgres, Sqlite, etc)

_NOTE: Please raise a PR if you want me to add your adapter to the above list_.

## Basic usage

Let's first create a database connection:

```js
// thinodium instance
const Thinodium = require('thinodium');

// create the connection
const db = yield Thinodium.connect('rethinkdb', {
  db: 'mydb',
});
```

Thinodium will try to load an NPM module called `thinodium-rethinkdb` (which
is our intention in this example). If not
available it will try to load a module called `rethinkdb`. Once loaded it will
instantiate a database connection through that module, passing in the second
parameter to `connect()`.

If we wished to add a custom adapter but not as an NPM module we could simply
provide its path to `connect()`:

```js
// connect using custom adatper
const db = yield Thinodium.connect('path/to/custom/adapter', {
  db: 'mydb',
});

```

**Models**

Once we have our database connection setup we can access models (i.e. tables)
within the database:

```js
// get the model
const model = yield db.model('User');

// insert a new user
let user = yield model.insert({
  name: 'john'
});

// change the name
user.name = 'mark';
yield user.save();

// load user with id
let user2 = yield model.get(user.id);

console.log(user2.name); /* mark */
```

Both `get()` and `insert()` return `Thinodium.Document` instances.
These internally call through to the methods prefixed with `raw` - methods
which you can also use directly if you do not wish to deal with `Document`s.
These are documented in the [API docs](https://hiddentao.github.io/thinodium).

**Document customization**

Model documents (each representing a row in the table) can be customized. We
can add virtual fields and additional methods:

```js
// create the model
const model = yield db.model('User', {
  docMethods: {
    padName: function(str) {
      this.name += str;
    }
  },
  docVirtuals: {
    fullName: {
      get: function() {
        return this.name + ' smith';
      }
    }
  }
});

// insert a new user
let user = yield model.insert({
  name: 'john'
});

console.log(user2.fullName); /* mark smith */

user.padName('test');

console.log(user2.fullName); /* marktest smith */
```

Note that you can access the parent model for a document using `getModel()`:

```js
let user = yield model.insert({
  name: 'john'
});

console.log( user.getModel() === model ) /* true */
```

**Schema validation**

Schema validation is performed by [simple-nosql-schema](https://github.com/hiddentao/simple-nosql-schema), and is used if a schema is provided in the initial model config:

```js
// create the model
const model = yield db.model('User', {
  // tell Thinodium to validate all updates and inserts against the given schema
  schema: {
    age: {
      type: Number,
      required: true,
    },
  }
});

// insert a new user
let user1 = yield model.insert({ name: 'john', }); /* throws Error since age is missing */

let user2 = yield model.insert({
  name: 'john',
  age: 23,
});
user2.age = 'test';

yield user2.save();  /* throws Error since age must be a number */
```

Note that schema validation is partial. If the insert or update contains a
key that is not mentioned within the schema then that key gets passed through
without any checks. This allows for flexibility - you only need to vaildate
the parts of a model's schema you're interested in.

## API

Check out the [API docs](https://hiddentao.github.io/thinodium) for information on supported methods.

## Creating an Adapter

An adapter has to extend the base `Database` and `Model` classes and
override the necessary internal methods:

```js
"use strict";

const Thinodium = require('thinodium');

class Database extends Thinodium.Database {
  _connect (options) {
    return new Promise((resolve, reject) => {
      // do what's needed for connection here and save into "connection" var
      resolve(connection);
    });
  }

  _disconnect (connection) {
    return new Promise((resolve, reject) => {
      // disconnect connection
      resolve();
    });
  }

  _model (connection, name, config) {
    return new Model(connection, name, config);
  }
}

class Model extends thinodium.Model {
  rawQry() {
    // return object for doing raw querying
  }

  rawGet (id) {
    return new Promise((resolve, reject) => {
      // fetch doc with given id
      resolve(doc);
    });
  }

  rawGetAll (id) {
    return new Promise((resolve, reject) => {
      // fetch all docs
      resolve(docs);
    });
  }

  rawInsert (attrs) {
    return new Promise((resolve, reject) => {
      // insert doc
      resolve(doc);
    });
  }

  rawUpdate (id, changes, document) {
    return new Promise((resolve, reject) => {
      // update doc
      resolve();
    });
  }

  rawRemove (id) {
    return new Promise((resolve, reject) => {
      // remove doc with id
      resolve();
    });
  }
}

module.exports = Database;
```

## Building

To run the tests:

    $ npm install
    $ npm test

## Contributing

Contributions are welcome! Please see [CONTRIBUTING.md](https://github.com/thinodium/thinodium/blob/master/CONTRIBUTING.md).

## License

MIT - see [LICENSE.md](https://github.com/thinodium/thinodium/blob/master/LICENSE.md)

repository: thinodium/thinodium

repo_name: thinodium/thinodium


text:
productive-you
==============

A chrome extension which is aimed at increasing the productivity of the user.

###Features
* Tracks the time you have spent on various websites.
* Displays the top 10 websites on which you have spent your time.

###TODO:
* Find all the events on which the activeTabUrl needs to be updated
* Check if the currentWindow is in focus or not while updating the timeSpent
* Reset the timeMap everyday at some time
* Store the data using the chrome.storage api
* Persist user preferences

repository: sathishbaskar/productive-you

repo_name: sathishbaskar/productive-you


text:
---
title: The Lua Programming Language
layout: default
last-modified: 2018-11-05
tags: [lua]
authors:
  - the_renegade_coder
---

As usual, I’m not super familiar with the language we’re working with today,
so let’s consult [Wikipedia][1].

Like many of the languages we’ve touched on already, Lua is a scripting language.
Unlike many of the scripting languages we’ve covered, Lua is extremely lightweight,
so it shines in embedded applications.

Perhaps the oddest featured of Lua is the fact that it’s compiled, but this is
not readily apparent to the user. That’s because the compilation occurs at
run-time where the bytecode is then interpreted. However, it’s possible to
precompile Lua to save a few CPU cycles during runtime.

Because Lua is built for embedded applications, it has its own C API which can
be used to write Lua code in C. Personally, I don’t find the API to be that
user-friendly, but it does eliminate the need for reference management, so I
can’t really complain.

Due to its lightweight and embedded nature, Lua has also found a home in the
gaming community. How have I never used it?[^1]

## Articles

{% include article_list.md collection=site.tags.lua %}

---

#### References

[^1]: J. Grifski, “Hello World in Lua,” The Renegade Coder, 28-Jul-2018. [Online]. Available: <https://therenegadecoder.com/code/hello-world-in-lua/>. [Accessed: 31-Oct-2018].

[1]: https://en.wikipedia.org/wiki/Lua_(programming_language)


text:
# Biowire
Monorepo for the Biowire blog. Code, designs and documentation are split into microservices.

| Item   |      Code-base      |  Description |
|----------|:-------------:|------:|
| Design's |  ```/designs``` | Contains files, components & mockups |
| Backend & Crawler |    ```/website```   |   Backend with SSR made with next-js |
| Documentation |  ```/docs``` | Contains Documentation for codebase and project structure |
| Scraper's |  ```/scraper``` | Crawlers to scrape data off of websites |
| Machine Learning |  ```/machine-learning``` | Contains ML API with models for classification and clustering |


text:
# GroupMeeting4   - sat, October 26

## Goal:
We want to assign the tasks for next project checkpoint and discuss the how to connect others in firestore

## Result:
We assign the tasks based on the backlog.
We need to learn more about firestore.

repository: ArcherUz/Umood

repo_name: ArcherUz/Umood


text:
# Quick RPG Encounters.

Instantly turn any battlemap in to a playable encounter! Setup and run your TTRPG encounters via video chat in minutes.

Try it now at:
https://thybag.github.io/rpg-quick-encounter/

![Screenshot of tool in use](https://user-images.githubusercontent.com/887397/126874584-9fa924a0-9c1a-4272-806c-170701449d7a.png)

### How to use it
* **Any map** - Grab the map url, paste it in and your on your way. Plenty of great ones are shared on [reddit](https://www.reddit.com/r/dndmaps/) every day.
* **Players** - Click a player to spawn them on the map, then drag them around as need be. Double click to rename & right click to remove.
* **Spawn NPC's** - Select a name and icon from spawn menu & get them added.
* **Fog** - Click to clear an area of fog, right click to re-add it. You can control fog opacity, clearing size or just turn it off in the fog menu.
* **Auto save** - Every action is saved to your local storage so you can quickly resume a game at your leisure. All saves are shown on the wizard.
* **Player bar** - Click a player to spawn or focus on them plus reorder freely to match your turn order.
* **Custom icons** - Just drag them in to the image picker and they will be available for all your encounters.
* **URL options** - Create maps using links,  use `map` for the image and `players` with a comma separated list users.
* **Local storage sync** - Allowing you to setup ambushes off screen by opening a second copy of the map on another window.

### Planned features
* Add more features to getting started.
* Import/Export - so people can share reconfigured encounters or just move them around.
* Ability to add overlays for injured or dead NPC's.
* More default NPC options.
* Set the icon size so they fit your tile system.

## Credits
Released by Carl Saggs under the MIT license.

Made possible by the great work in;
* [Leaflet.js](https://leafletjs.com/) - Powering the maps themselves.
* [Rollup.js](https://rollupjs.org/) - Build tooling
* [turf.js](https://turfjs.org/) - Clever GeoJson tools.
* [Kenny's](https://www.kenney.nl/) - Awesome free assets.
* [Lump.js](https://github.com/thybag/lump.js) - Because this is a hobby project, so why not attempt to roll my own js framework.
* [CatnipCarta](https://www.patreon.com/CatnipCarta) - Creating the map used in the screenshots.
* Github - Hosting

repository: thybag/rpg-quick-encounter

repo_name: thybag/rpg-quick-encounter


text:
---
title: devspace list
---

The command lists the following configurations:

* Installed Packages/Charts (package)
* Sync paths (sync)
* Forwarded ports (port)

```
Usage:
  devspace list [command]

Available Commands:
  package     Lists all added packages
  port        Lists port forwarding configuration
  sync        Lists sync configuration

Flags:
  -h, --help   help for list

Use "devspace list [command] --help" for more information about a command.
```


text:
[![GitHub license](https://img.shields.io/github/license/jwellone/custom-camera-inspector.svg?style=plastic)](https://github.com/jwellone/custom-camera-inspector/blob/main/LICENSE)
[![GitHub Release](https://img.shields.io/github/v/release/jwellone/custom-camera-inspector.svg?style=plastic)](https://GitHub.com/jwellone/custom-camera-inspector/releases/latest)
[![Github All Releases](https://img.shields.io/github/downloads/jwellone/custom-camera-inspector/total?color=blue&style=plastic)](https://GitHub.com/jwellone/custom-camera-inspector/releases)
![GitHub repo size](https://img.shields.io/github/repo-size/jwellone/custom-camera-inspector?label=size&style=plastic)
![C#](https://img.shields.io/badge/C%23-239120?logo=c-sharp&style=plastic)
[![Unity](https://img.shields.io/badge/Unity-100000?logo=unity&style=plastic)](https://unity.com)

# custom-camera-inspector
Extend inspector of camera component as follows:
- Add preview that camera in the Scene view always sync.
- Move and rotate by the mouse.
- Take screenshots.

This feature is one of the "j1Tech" developed by jwellone Inc for Unity.

## Getting Started
- Import the package.
- Select a camera object in the hierarchy.
- Additional features appear in the Inspector.

![custom-camera-inspector](https://user-images.githubusercontent.com/85072161/127937689-153c0f82-0a45-42fa-973a-cbe976b3f890.gif)

## Authors
Developer:[Yasuhiko Usui.](https://github.com/UsuiYasuhiko-jw1)

[![GitHub watchers](https://img.shields.io/github/watchers/jwellone/custom-camera-inspector.svg?style=social&label=Watch)](https://GitHub.com/jwellone/custom-camera-inspector/watchers/)
[![GitHub stars](https://img.shields.io/github/stars/jwellone/custom-camera-inspector.svg?style=social&label=Stars)](https://GitHub.com/jwellone/custom-camera-inspector/stargazers)
[![GitHub fork](https://img.shields.io/github/forks/jwellone/custom-camera-inspector.svg?style=social&label=Fork)](https://GitHub.com/jwellone/custom-camera-inspector/network/members)
[![Twitter](https://img.shields.io/twitter/follow/jwellone?label=Twitter&logo=twitter&style=social)](http://twitter.com/jwellone)
[![Facebook](https://img.shields.io/badge/Facebook-1877F2?style=for-the-badge&logo=facebook&logoColor=white&style=plastic)](https://www.facebook.com/jwellone)

repository: jwellone/custom-camera-inspector

repo_name: jwellone/custom-camera-inspector