text:
## 2018-09-13

#### python
* [TheAlgorithms / Python](https://github.com/TheAlgorithms/Python):All Algorithms implemented in Python
* [donnemartin / system-design-primer](https://github.com/donnemartin/system-design-primer):Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.
* [mwouts / jupytext](https://github.com/mwouts/jupytext):Jupyter notebooks as Markdown documents, Julia, Python or R scripts
* [tensorflow / models](https://github.com/tensorflow/models):Models and examples built with TensorFlow
* [tensorflow / tensorboard](https://github.com/tensorflow/tensorboard):TensorFlow's Visualization Toolkit
* [vinta / awesome-python](https://github.com/vinta/awesome-python):A curated list of awesome Python frameworks, libraries, software and resources
* [django / django](https://github.com/django/django):The Web framework for perfectionists with deadlines.
* [everhide / everbug](https://github.com/everhide/everbug):Django debug tool for browser
* [KamitaniLab / DeepImageReconstruction](https://github.com/KamitaniLab/DeepImageReconstruction):Data and demo codes for Shen, Horikawa, Majima, and Kamitani, "Deep image reconstruction from human brain activity".
* [junfu1115 / DANet](https://github.com/junfu1115/DANet):Dual Attention Network for Scene Segmentation
* [keras-team / keras](https://github.com/keras-team/keras):Deep Learning for humans
* [rg3 / youtube-dl](https://github.com/rg3/youtube-dl):Command-line program to download videos from YouTube.com and other video sites
* [python / cpython](https://github.com/python/cpython):The Python programming language
* [toddmotto / public-apis](https://github.com/toddmotto/public-apis):A collective list of public JSON APIs for use in web development.
* [soimort / you-get](https://github.com/soimort/you-get):⏬
Dumb downloader that scrapes the web
* [encode / apistar](https://github.com/encode/apistar):A smart Web API framework, for Python 3.
🌟
* [ansible / ansible](https://github.com/ansible/ansible):Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications — automate in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com/ansible/
* [pallets / flask](https://github.com/pallets/flask):The Python micro framework for building web applications.
* [howie6879 / aspider](https://github.com/howie6879/aspider):aspider - An async web scraping micro-framework based on asyncio.
* [home-assistant / home-assistant](https://github.com/home-assistant/home-assistant):🏡
Open source home automation that puts local control and privacy first
* [facebookincubator / python-nubia](https://github.com/facebookincubator/python-nubia):A command-line and interactive shell framework.
* [scikit-learn / scikit-learn](https://github.com/scikit-learn/scikit-learn):scikit-learn: machine learning in Python
* [imhuay / Algorithm_Interview_Notes-Chinese](https://github.com/imhuay/Algorithm_Interview_Notes-Chinese):2018/2019/校招/春招/秋招/算法/机器学习(Machine Learning)/深度学习(Deep Learning)/自然语言处理(NLP)/C/C++/Python/面试笔记
* [KonstantinSchubert / zero](https://github.com/KonstantinSchubert/zero):Local file system transparently swapping to the cloud
* [requests / requests](https://github.com/requests/requests):Python HTTP Requests for Humans™
✨
🍰
✨

#### swift
* [eBay / HeadGazeLib](https://github.com/eBay/HeadGazeLib):A library to empower iOS app control through head gaze without a finger touch
* [pointfreeco / swift-html](https://github.com/pointfreeco/swift-html):🗺
A Swift DSL for type-safe, extensible, and transformable HTML documents.
* [fastred / Optimizing-Swift-Build-Times](https://github.com/fastred/Optimizing-Swift-Build-Times):Collection of advice on optimizing compile times of Swift projects.
* [daomoer / XMLYFM](https://github.com/daomoer/XMLYFM):swift高仿喜马拉雅App，采用MVC+MVVM设计模式，Moya+SwiftyJSON+HandyJSON网络框架和数据解析。数据来源抓包及部分本地json文件
* [malcommac / ImageSizeFetcher](https://github.com/malcommac/ImageSizeFetcher):Finds the type/size of an image given its URL by fetching as little data as needed
* [Mark-Ma-1988 / PhotoSolution](https://github.com/Mark-Ma-1988/PhotoSolution):PhotoSolution is an all-in-one photo solution for your iOS app, the UI is similar to WeChat.
* [lhc70000 / iina](https://github.com/lhc70000/iina):The modern video player for macOS.
* [serhii-londar / open-source-mac-os-apps](https://github.com/serhii-londar/open-source-mac-os-apps):🚀
Awesome list of open source applications for macOS.
* [vsouza / awesome-ios](https://github.com/vsouza/awesome-ios):A curated list of awesome iOS ecosystem, including Objective-C and Swift Projects
* [ishkawa / DataSourceKit](https://github.com/ishkawa/DataSourceKit):Declarative, testable data source of UICollectionView and UITableView.
* [danielgindi / Charts](https://github.com/danielgindi/Charts):Beautiful charts for iOS/tvOS/OSX! The Apple side of the crossplatform MPAndroidChart.
* [shadowsocks / ShadowsocksX-NG](https://github.com/shadowsocks/ShadowsocksX-NG):Next Generation of ShadowsocksX
* [zalando / SwiftMonkey](https://github.com/zalando/SwiftMonkey):A framework for doing randomised UI testing of iOS apps
* [ReactiveX / RxSwift](https://github.com/ReactiveX/RxSwift):Reactive Programming in Swift
* [vapor / vapor](https://github.com/vapor/vapor):💧
A server-side Swift web framework.
* [matteocrippa / awesome-swift](https://github.com/matteocrippa/awesome-swift):A collaborative list of awesome Swift libraries and resources. Feel free to contribute!
* [raywenderlich / swift-algorithm-club](https://github.com/raywenderlich/swift-algorithm-club):Algorithms and data structures in Swift, with explanations!
* [NJHu / swiftProject](https://github.com/NJHu/swiftProject):🌲
swift,组件化,直播,MVVM,NowShow,DouYu,Mediator,Swift4,component,video,player,ijkplayer,videoplayer,swift项目,pod,视频播放,弹幕,推流,拉流,liveshow,liveroom,playerroom,
📝
,滚动播放,拖拽播放,离线下载,即时通讯,打印 ios 日志,主流视频播放器,视频播放,图片浏览器,photoBrowser,通用链接配置,通用链接,各类知识点总结,运行时,贝塞尔曲线,水纹,粒子发射器,核心动画,二维码,照片上传,照片上传有进度,列表倒计时,H5和原生交互,自定义各种弹框,常见表单类型,列表加载图片,列表拖拽,日历操作,导航条渐变,指纹解锁,物理仿真,控制器生命周期,流水…
* [realm / SwiftLint](https://github.com/realm/SwiftLint):A tool to enforce Swift style and conventions.
* [Alamofire / Alamofire](https://github.com/Alamofire/Alamofire):Elegant HTTP Networking in Swift
* [JohnSundell / Splash](https://github.com/JohnSundell/Splash):A fast, lightweight and flexible Swift syntax highlighter for blogs, tools and fun!
* [apple / swift-syntax](https://github.com/apple/swift-syntax):SwiftPM package for SwiftSyntax library.
* [jianstm / Schedule](https://github.com/jianstm/Schedule):⏳
Lightweight timed task scheduler for Swift. (A modern alternative to Timer)
* [app-developers / top](https://github.com/app-developers/top):Top App Developers
* [mxcl / PromiseKit](https://github.com/mxcl/PromiseKit):Promises for Swift & ObjC

#### javascript
* [you-dont-need / You-Dont-Need-Momentjs](https://github.com/you-dont-need/You-Dont-Need-Momentjs):List of date-fns or native functions which you can use to replace moment.js + ESLint Plugin
* [Nozbe / WatermelonDB](https://github.com/Nozbe/WatermelonDB):🍉
Next-gen database for powerful React and React Native apps that scales to 10,000s of records and remains fast
⚡
* [thedaviddias / Front-End-Checklist](https://github.com/thedaviddias/Front-End-Checklist):🗂
The perfect Front-End Checklist for modern websites and meticulous developers
* [dawnlabs / carbon](https://github.com/dawnlabs/carbon):🎨
Create and share beautiful images of your source code
* [mariusandra / pigeon-maps](https://github.com/mariusandra/pigeon-maps):ReactJS Maps without external dependencies
* [date-fns / date-fns](https://github.com/date-fns/date-fns):⏳
Modern JavaScript date utility library
⌛
* [sindresorhus / ky](https://github.com/sindresorhus/ky):Tiny and elegant HTTP client based on the browser Fetch API
* [rwv / chinese-dos-games](https://github.com/rwv/chinese-dos-games):🎮
Chinese DOS games in browser.
* [vuejs / vue](https://github.com/vuejs/vue):🖖
A progressive, incrementally-adoptable JavaScript framework for building UI on the web.
* [trekhleb / javascript-algorithms](https://github.com/trekhleb/javascript-algorithms):Algorithms and data structures implemented in JavaScript with explanations and links to further readings
* [getgauge / taiko](https://github.com/getgauge/taiko):A node.js library to automate chrome/chromium browser
* [mweststrate / immer](https://github.com/mweststrate/immer):Create the next immutable state by mutating the current one
* [facebook / react](https://github.com/facebook/react):A declarative, efficient, and flexible JavaScript library for building user interfaces.
* [facebook / create-react-app](https://github.com/facebook/create-react-app):Create React apps with no build configuration.
* [justjavac / free-programming-books-zh_CN](https://github.com/justjavac/free-programming-books-zh_CN):📚
免费的计算机编程类中文书籍，欢迎投稿
* [storybooks / storybook](https://github.com/storybooks/storybook):Interactive UI component dev & test: React, React Native, Vue, Angular
* [wilk / microjob](https://github.com/wilk/microjob):A tiny wrapper for turning Node.js worker threads into easy-to-use routines for heavy CPU loads.
* [axa-group / nlp.js](https://github.com/axa-group/nlp.js):An NLP library built in node over Natural, with entity extraction, sentiment analysis, automatic language identify, and so more
* [felixrieseberg / windows95](https://github.com/felixrieseberg/windows95):💩
🚀
Windows 95 in Electron. Runs on macOS, Linux, and Windows.
* [sctb / lumen](https://github.com/sctb/lumen):A Lisp for Lua and JavaScript
* [AurelienLourot / ghuser.io](https://github.com/AurelienLourot/ghuser.io):Better GitHub profiles
* [netgusto / nodebook](https://github.com/netgusto/nodebook):Nodebook - Multi-Language REPL with Web UI
* [GoogleChrome / puppeteer](https://github.com/GoogleChrome/puppeteer):Headless Chrome Node API
* [alibaba / ice](https://github.com/alibaba/ice):🚀
飞冰 - 让前端开发简单而友好，海量可复用物料，配套桌面工具极速构建前端应用，效率提升 100%
* [airbnb / javascript](https://github.com/airbnb/javascript):JavaScript Style Guide

#### go
* [GoogleCloudPlatform / open-match](https://github.com/GoogleCloudPlatform/open-match):Flexible, extensible, and scalable video game matchmaking.
* [xmge / gonote](https://github.com/xmge/gonote):欢迎各位gopher一起来完善这份笔记，让更多的人能够了解go，学习go，使用go，热爱go.
👍
* [pingcap / tidb](https://github.com/pingcap/tidb):TiDB is a distributed HTAP database compatible with the MySQL protocol
* [kubernetes / kubernetes](https://github.com/kubernetes/kubernetes):Production-Grade Container Scheduling and Management
* [github / smimesign](https://github.com/github/smimesign):An S/MIME signing utility for use with Git
* [golang / go](https://github.com/golang/go):The Go programming language
* [avelino / awesome-go](https://github.com/avelino/awesome-go):A curated list of awesome Go frameworks, libraries and software
* [jesseduffield / lazygit](https://github.com/jesseduffield/lazygit):simple terminal UI for git commands
* [istio / istio](https://github.com/istio/istio):Connect, secure, control, and observe services.
* [chai2010 / advanced-go-programming-book](https://github.com/chai2010/advanced-go-programming-book):📚
《Go语言高级编程》开源图书，涵盖CGO、Go汇编语言、RPC实现、Protobuf插件实现、Web框架实现、分布式系统等高阶主题
* [gin-gonic / gin](https://github.com/gin-gonic/gin):Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
* [skatiyar / pacman](https://github.com/skatiyar/pacman):Classic pacman with procedurally generated maze, written in Golang
* [b3log / pipe](https://github.com/b3log/pipe):🎷
A small and beautiful blogging platform. 小而美的博客平台。
* [fatedier / frp](https://github.com/fatedier/frp):A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
* [prometheus / prometheus](https://github.com/prometheus/prometheus):The Prometheus monitoring system and time series database.
* [tsenart / vegeta](https://github.com/tsenart/vegeta):HTTP load testing tool and library. It's over 9000!
* [kgretzky / evilginx2](https://github.com/kgretzky/evilginx2):Standalone man-in-the-middle attack framework used for phishing login credentials along with session cookies, allowing for the bypass of 2-factor authentication
* [iikira / BaiduPCS-Go](https://github.com/iikira/BaiduPCS-Go):百度网盘客户端 - Go语言编写
* [ethereum / go-ethereum](https://github.com/ethereum/go-ethereum):Official Go implementation of the Ethereum protocol
* [gohugoio / hugo](https://github.com/gohugoio/hugo):The world’s fastest framework for building websites.
* [helm / helm](https://github.com/helm/helm):The Kubernetes Package Manager
* [v2ray / v2ray-core](https://github.com/v2ray/v2ray-core):A platform for building proxies to bypass network restrictions.
* [phasersec / san-go](https://github.com/phasersec/san-go):SAN parser for Go & CLI
* [go-kit / kit](https://github.com/go-kit/kit):A standard library for microservices.
* [etcd-io / etcd](https://github.com/etcd-io/etcd):Distributed reliable key-value store for the most critical data of a distributed system

repository: bonfy/github-trending

repo_name: bonfy/github-trending


text:
## Minimal Example

    require('uiautomation-runner').build_and_test {
      build_dir:            "#{__dirname}/build/xcode"
      results_dir:          "#{__dirname}/results/#{strftime.strftimeUTC('...')}"
      script_path:          "#{__dirname}/all-the-tests.js"
      xcode_workspace:      "#{__dirname}/../MyAwesomeProduct.xcworkspace"
      xcode_scheme:         'myawesomeproduct'
      xcode_configuration:  'Test'
      app_filename:         'My Awesome Product.app'
      delete_simulator_apps: true
    }

## Some Optional Settings

    # default: Xcode's Automation.tracetemplate
    tracetemplate: ".../Foo.tracetemplate"

## [TODO] Running on a physical device

    {
      ...
      bundle_id: 'com.example.foo'
      device_udid: '...'
    }

- This requires `fruitstrap` to be on your `PATH`

## Trusting custom CA certs

    {
      ...
      trust_ca_cert_paths: [
        "#{__dirname}/ssl/demoCA/cacert.pem"
      ]
    }

## Charles

Suppose you want to man-in-the-middle HTTPS requests whose host matches `*foo*` and proxy them to `:3001`

    {
      ...
      charles: {
        mim_https_to_local: {
          foo: 3001
        }
        headless: false     # Default: true
      }
      trust_charles: true   # Works for the simulator -- for physical devices, you'll need to manually trust the cert
    }

- This will
  - create a config file at `"#{build_dir}/charles.config"`
  - run Charles while the tests are running
- You need a registered copy of Charles
- It needs to be at `/Applications/Charles.app`

license: MIT

repository: uxalytics/uiautomation-runner

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: uxalytics/uiautomation-runner


text:
# ServerScalingService
The ServerScalingService controls the deployment of more servers of specific types, to ensure there is always enough capacity. Right now it communicates only with the kubernetes backend but it may start to communicate with Openshift as well to deploy more nodes.

## Endpoints

### /games/register [POST]:
#### Updates a game type

**Request**:

The name should must the gameId!

```json
{
"name": "mg_gw",
"image": "exorath/mg_gw:0.0.1",
"terminationGracePeriodSeconds": 1000,
"env": {
  "key1": "value1",
  "key2": "value2"
},
"labels": {}
}
```

**Response**:
```json
{
"success": true
}
```

### /bungee [POST]:
#### Updates the bungee spec
#### NOTICE: THE BUNGEE ENDPOINT IS CURRENTLY NOT IN USE!!!
**Request**:
```json
{
"image": "exorath/bungee:0.0.1",
"terminationGracePeriodSeconds": 1000,
"env": {
  "key1": "value1",
  "key2": "value2"
},
"labels": {}
}
```

**Response**:
```json
{
"success": true
}
```

## Environment
| Name | Value |
| --------- | --- |
| MONGO_URI | {mongo_uri} |
| DB_NAME | {db name to store data} |
| CONNECTOR_SERVICE_ADDRESS | {ConnectorService ip:port} |
| KUBERNETES_ADDRESS | {Kubernetes url} |

repository: Exorath/ServerScalingService

repo_name: Exorath/ServerScalingService


text:
---
title:  "Delegation Token Framework: Obtain, Distribute and Use Temporary Credentials Automatically"
date: "2023-01-20T08:00:00.000Z"
authors:
- gaborgsomogyi:
  name: "Gabor Somogyi"
- mbalassi:
  name: "Marton Balassi"
  twitter: "MartonBalassi"
aliases:
- /news/2023/01/20/delegation-token-framework.html
---

The Apache Flink Community is pleased to announce that the upcoming minor version of Flink (1.17) includes
the Delegation Token Framework proposed in [FLIP-272](https://cwiki.apache.org/confluence/display/FLINK/FLIP-272%3A+Generalized+delegation+token+support).
This enables Flink to authenticate to external services at a central location (JobManager) and distribute authentication
tokens to the TaskManagers.

## Introduction

Authentication in distributed systems is not an easy task. Previously all worker nodes (TaskManagers) reading from or
writing to an external system needed to authenticate on their own. In such a case several things can go wrong, including but not limited to:

* Too many authentication requests (potentially resulting in rejected requests)
* Large number of retries on authentication failures
* Re-occurring propagation/update of temporary credentials in a timely manner
* Dependency issues when external system libraries are having the same dependency with different versions
* Each authentication/temporary credentials are different making standardization challenging
* ...

The aim of Delegation Token Framework is to solve the above challenges. The framework is authentication protocol agnostic and pluggable.
The primary design concept is that authentication happens only at a single location (JobManager), the obtained temporary
credentials propagated automatically to all the task managers where they can be used. The token re-obtain process is also handled
in the JobManager.

New authentication providers can be added with small amount of code which is going to be loaded by Flink automatically.
At the moment the following external systems are supported:

* Hadoop filesystems
* HBase
* S3

Planned, but not yet implemented/contributed:

* Kafka
* Hive

The design and implementation approach has already been proven in [Apache Spark](https://spark.apache.org/docs/latest/security.html#kerberos).
Gabor is a Spark committer, he championed this feature in the Spark community. The most notable improvement we achieved compared to the
current state in Spark is that the framework in Flink is already authentication protocol agnostic (and not bound to Kerberos).

## Documentation

For more details please refer to the following documentation:

* [Delegation Tokens In General](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/security/security-delegation-token/)
* [How to use Kerberos delegation tokens](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/security/security-kerberos/#using-delegation-tokens)

## Development details

Major tickets where the framework has been added:

* [FLINK-21232](https://issues.apache.org/jira/browse/FLINK-21232) Kerberos delegation token framework
* [FLINK-29918](https://issues.apache.org/jira/browse/FLINK-29918) Generalized delegation token support
* [FLINK-30704](https://issues.apache.org/jira/browse/FLINK-30704) Add S3 delegation token support

## Example implementation

Adding a new authentication protocol is relatively straight-forward:

* Check out the [example implementation](https://github.com/gaborgsomogyi/flink-test-java-delegation-token-provider)
* Change `FlinkTestJavaDelegationTokenProvider.obtainDelegationTokens` to obtain a custom token from any external service
* Change `FlinkTestJavaDelegationTokenReceiver.onNewTokensObtained` to receive the previously obtained tokens on all task managers
* Use the tokens for external service authentication
* Compile the project and put it into the classpath (adding it inside a plugin also supported)
* Enjoy that Flink does all the heavy lifting behind the scenes :-)

## Example implementation testing

The existing providers are tested with the [Flink Kubernetes Operator](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/)
but one can use any other supported deployment model, because the framework is not bound to any of them.
We choose the Kubernetes Operator so that we could provide a completely containerized and easily reproducible test environment.

An example tutorial can be found [here](https://gist.github.com/gaborgsomogyi/ac4f71ead8494da2f5c35265bcb1e885) on
external system authentication.

## Summary

The Delegation Token Framework is feature complete on the master branch and is becoming generally available on the release of
Flink 1.17. The framework obtains authentication tokens at a central location and propagates them to all workers on a re-occurring basis.

Any connector to an external system which supports authentication can be a potential user of this framework.
To support authentication in your connector we encourage you to implement your own `DelegationTokenProvider/DelegationTokenReceiver` pair.

repository: apache/flink-web

branch_name: refs/heads/asf-site

gha_language: HTML

repo_name: apache/flink-web


text:
# Pet-Match

Anyone looking to adopt a pet in their area this is the website for you. You can create a secure login from which you can search for dogs, cats, a parrot, or even exotic animals like monkeys or snakes. Which type of breed you would like. How big of pet you are looking for and more. The application will tell you where these pets are located and provides contact information so you can call directly or click the link to the pet's profile for further details about this specific animal.

## User Story

I AM looking to adopt an animal.
I CAN create a personal account with a secure password.
WHEN I filter for a certain animal,
I AM presented with results from PetFinder.com.
I AM presented with multiple pets that meet my criteria.
WHEN deciding,
I CAN call the shelter directly from the page to inquire about the pet.
I CAN jot down information I would like to keep in mind.

## Installation
If you are installing to your local machine please remember to add a .env file
replace password with your local host password.

![img](public\assets\img\env.png)

[Deployed Website](https://sheltered-refuge-68768.herokuapp.com/)

## App Images
login Page
![Img-1](public\assets\img\WvuCWqr28A.png)

Members Page
![Img-2](public\assets\img\vSkyqdERvQ.png)

Team Members Page
![IMG-3](public\assets\img\kxmGESAyuK.png)

## Library, Frameworks & Tools
* Framework- Bootstrap
* Express
* handlebars
* Dotenv
* Mysql2
* Sequelize
* Bcryptjs
* Passport
* JavaScript
* CSS
* Git
* Third Party API
* Twilio

## Future Development

Moving forward we would like to add to the application by including functionality allowing us to search the area and get a response with available animals in our area.
Adding an exotic animal's search option to the application would really give it a unique touch.
Adding the ability for a user to delete their notes.
Working through the technical difficulties we encountered with Twilio

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

Please make sure to update tests as appropriate.

## Contributors

Nardin Lachowski, Adriana Valdiglesias, Bruce Farmer, Drew Bridgman

## License

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

branch_name: refs/heads/main

gha_language: JavaScript


text:
# Boletus carpini (R. Schulz) A. Pearson, 1947 SPECIES

#### Status
SYNONYM

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

#### Published in
Naturalist 96 (1947)

#### Original name
Boletus scaber var. carpini R. Schulz, 1924

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Boletales/Boletaceae/Leccinum/Leccinum pseudoscabrum/ Syn. Boletus carpini/README.md

repo_name: mdoering/backbone


text:
# WhatsApp has just made a big change for every Android user

Published at: **2019-11-01T07:38:32+00:00**

Author: **James Rodger, https://www.facebook.com/jamesrodgerjournalist**

Original: [birminghammail](https://www.birminghammail.co.uk/news/midlands-news/whatsapp-just-made-big-change-17182201)

WhatsApp users on Android can now lock the messaging app using their fingerprint.
The Facebook-owned messaging service announced it will allow users to add the extra layer of security, which will require the device owner's fingerprint to be confirmed before the app opens fully.
A similar feature was added to Apple's iOS platform earlier this year, which only unlocks the app when the fingerprint or face scan associated with the device is logged using Apple's Touch ID or Face ID biometric security features.
WhatsApp did not mention a facial recognition unlock for Android in its announcement, meaning owners of devices such as Google's Pixel 4 - which uses facial recognition rather than a fingerprint scanner as its biometric security - will not be able to use the feature.
The feature is being rolled out to WhatsApp users worldwide who have a fingerprint-scanning capable Android smartphone, the company confirmed.
Once active, it can be reached through the Settings section of WhatsApp, with users able to specify when their device asks for the biometric unlock - immediately, after one minute or after 30 minutes.
The messaging service has more than one billion monthly active users.

license: Unlicense

repository: dsadlollioygjmzvcxv/tdc-exported

repo_name: dsadlollioygjmzvcxv/tdc-exported


text:
# Slackers_Platform
Want instant communication with the Dev team? Join our
[Discord Channel](https://discord.gg/VN7ZuWR)!
## Release 6.05
##  Changes
  - Renamed README.md to changelog.md
  - Added -coverage option to command line.  This will set all speed values to 1 for a fast playing game.
  - runCoverage.sh will now actually perform coverage testing on the game files using tests in the  tests (src/functional) folder.
  - Changed testing binary names to reflect style of tests.
  - Additional make options added:
    - make tests - creates the testing binaries in the main program folder
    - make clean-tests - cleans up testing
# FIXES
  - Fixed problem with CI script looking for old testing binary names.
  - Fixed problem with tanks folder not being created on a fresh pull and make.

## Release 6.03
##  Changes
  - Added -quiet command line option to remove a lot of output text
  - Added -demo command line option to increase game size for a 1080p screen
  - Fixed speed mode
    - Changing ANIMATION_SPEED, TANK_SPEED, PROJECTILE_SPEED to 0 should greatly decrease total game time.
## Release 6.02
## Changes
  - Changed output to results.txt file to improve human readablility.
    - The new format will list what turn the game ended on, the winner if there was one.  And then list each tank that participated in the match.  For each tank, their kills, hits, shots, AP, Max/Current Health, Max/Current Ammo, and final position is listed.

## Release 6.01
## Fixes
  - Fixed issue with Object map not always updating on a tank move command
  - Fixed issue with max_turns not being correctly enforced

## Release 6.00
## Fixes
  - Fixed projectiles turning into torpedos
  - Prevented rocks from regrowing on top of tanks
## Changes
  - Changed the default settings for the animation configuration.  The lower the number the faster the actor will move.
## Balancing
- New Min and Max stat values:
             min       max      setAttribute
  - Damage    0   |     8     |   8
  - Health    0   |     8     |   8
  - AP        0   |     6     |   6
  - Radar     0   | Map Width | Map Width
  - Range     0   |    10     |   10
  - Ammo      0   |    10     |   -
  - Special   0   |    20     |   10
    - min - The minimum is the minimum value that can be set in the configuration file or assigned to your tank.
      * Warning - If you do not add status to your tank when 0 is set, they will stay at 0, nothing will be automatically increased.
    - max - The maximum value that can be set in the config file
    - setAttribute - The max a stat can end at.  If this value is exceed the stat will be clamped down to the value in the chart.

## Release 5.01
## Fixes
- Non-Disappearing objects from obstacle and health map
  - Trees, Rocks, and (Future)Bushes will now disappear from the obstacle map when destroyed.
- Tree/Rock Regrowth (And future bushes)
  - These objects will now regrow after 4 turns back to their original health.
  - They will also reappear back on the Obstacle and Health maps.
- Crates
  - Crates now properly get removed from the obstacle and health maps when they are destroyed.
  - They do NOT regrow.
- Health Adustments:
  - Trees: 3
  - Rocks: 5
  - Crates: 1
  - Bushes: 9999
- Regrow Rates:
  - Currently everything that can regrow regrows at the following rates:
    - Trees: 3
    - Rocks: 5
    - Crates: Never
    - Bushes: 1
    - Water: 0
## Release 5.00
## New
-	Adjustable Tank Speed config file setting
	- You can now adjust the speed of the tanks independently from the projectiles
- Adjustable Projectile speed in config file
	- You can now adjust the speed of the projectiles independently from the tanks
- Animations
	- Tanks and Projectiles will now try and move smoothly across the battle field
	- The number of samples used to smooth out movement can be set in the configuration file
- Turn Counter
	- A turn counter now appears in the top right corner
- AI Speed
	- This setting will now affect individual AI turns instead of just the game turn
-	Special Effects
	- Tanks will now visibily show signs of damage
		- minor damge smoke
		- medium damage more smoke
		- critical damage fire
	- Projectiles now have trails
  - Explosions are no longer a single static sprite
- Memory Management
	- Switched some heavily used objects to smart pointers to ensure quicker memory cleanup.
- Projectile stacking
  - Projectiles from the same tank will no longer be allowed to stack.  Instead if two projectiles are fired by the same tank on 1 turn, the two projectils will merge leaving a single projectile with double health, double damage, and 40% increased size.  (These will increase additively for the amount of projectiles fired)
  - Note with a tank tha does nothing but constantly fires, large amount of ammo, and moderate to a lot of AP the size of the projectile can get extremely large.
  - This also has the added benefit that when checking the health map you now know which area 'more' projectiles are coming from because the health stat will be larger for combined projectiles.
## Fixes
-	Tree's will now regrow properly. (4 turns).
- Rock's will now appear again. (4 turns).
- If a tree is destroyed on top of a tank, the tank will now take the appropriate amount of damage (1).
- Fixed an issue with some tanks moving sideways instead of turning.
- Potential bug with destroyed create still appearing on health map.
  - Doubly fixed the bug
## Changes
- Removed bushes from dispaying a health in the health map.  Since they are not destructible there is currently no need to send their health.

## Release 4.03
## Fixed
- Issue where when running moves the user was not updated with the current AP.
- Minor optimization issues.
## New
- Brand new scoreboard
  - Noone asked for it, but we delivered it anyway.  There is now a single scoreboard that displays the current tank's information allowing for stat tracking of more than 4 tanks at a time.
  - We also added a spinning image of the current tank to help identify which tank is yours.
## Release 4.02
## Fixed
- Modified max radar range to be allowed up to map width.
- Changed undestructible object sprite so it no longer looks like destructible objects
- Fixed ramming algorithm.    If a tank has more than 1 health and the ramming damage would kill them, there health is instead set to 1.
- Added support for maps down to 5x5.  Sizes below 15x9 will fill in missing squares with unpassible objects.
- Remove the tree hiding feature.  The hidden object implementation was unfinished before the feature freeze, but the hidding while in a tree made it through.  This has been corrected and removed.
- Default images for tanks.  If a tank does not provide any images it will instead use a default set of images.
- Default config file. If a config.txt file is not detected, the game will attempt to write a new one and prompt the user to add their tanks to the new configuration file.
- Fixed problem generating libCTF properly.
- UI Refresh 3.0
  - With the support for more tanks, the GUI was redrawn now to display the information for the tank whose turn it is including a small representation of the tank.
- New Configuration Options
  - Added MAXTURNS option into the config file
    - This will allow the user to override the default value set.
  - Added DISABLUEGUI option into the config file
    - While the OpenGL window will load, the game will not be constantly redrawn reducing overall game time.  During testing reduced average game time from 45s to 15s.

## Release 4.01
## Fixed
- Range now properly scales the distance a projectile can travel. Previously, they were stuck at 6.
- baseStats are now properly passed to tanks during setAttributes.  Previously, a freshly initalized variable was passed resulting in all 0's.
- Default values have been set:
  - Health = 3   - The amount of health a tank starts with
  - Damage = 1   - The amount of damage a tank's projectile does
  - AP = 2       - The amount of Action points a tank starts with.
  - Ammo = 6     - The amount of ammo a tank starts with before needing to reload
  - Radar = 4    - How far a tanks Radar expands to
  - Range = 4    - How many spaces a projectile travels per turn
  - Shots = 0    - This is a counter, no matter how many points you put here, it will stay 0.
- Reduced size of program.
## Release 4.00
## What's new?
- Updated Scoreboard
  - The scoreboard now lists more interesting facts about the tanks and has support for a draw.
- Reloading
  - Tanks now have a limited number of ammunition.  After they reach the limit they will have to reload.
  - A tank can reload by sending back action number 4 or the tank will automatically reload if it has no ammo and it attempts to fire.
- Water
  - New title type added that cannot be passed by tanks.  Projectiles on the other hand of no problem flying above the water.
- Health Map
  - When a tank is sent a map object there is now an additional map called the health map.  It will list the health of all the objects the tank can see.
- Attributes
  - Tanks now recieve a copy of there base stats when asked for their choice of special point spending.
- MaxTurns
  - The number of max turns can now be set in the config file.
- New formula for calculating field size display.
- Behind the scene caps for special points when dealing with a large special amount

## Fixed
- Damage
  - Fixed some inconsistencies between tank and projectile damages.
- SimpleAI
  - SimpleAI will now move even when it can't see the whole map.
  - Fixed incorrect header prototype.

## Release 3.10
## What's new?
- Scoreboard
  - At the end of the game a list of the top 3 players will be displayed.
- Crate_o_Fun
  - A new crate was added that has a surprise for anyone that shoots it.
- Tanks
  - Additional tank colors have been added to the map.
- Maps
  - All maps have been updated with destructible objects so that they can now be
- Default Map
  - The default map has been updated to support up to 10 Tanks.
- SimpleAI
  - Adjusted SimpleAI so that it will no longer refuse to play the game if it can't see.

## Release 3.01
### What's new?
- Object health
	- If you arn't a fan of the new objects, now you can do something about it.  Trees and rocks can both be destroyed with enough projectile hits.
	-Warning: You still cannot drive over rocks and will take damage if you try.  After they are destroyed you can safely move over them.
	- If you were tired of the paint on your tank fading, you can now sit under the shade of a tree.  This has the added benefit of taking a few hits from projectiles for you.
	- With the new objects means the obstacle map has been changed.  It is no longer a boolean array with simply occupied or not.  It now tells you if it's empty 0, a tree T or a rock R.
	- Previous code will still work with empty = false and everything else = true, however your tank won't know to hide in a tree if you don't update it's routines.
	- NOTE: The map can still be setup to use old style obstacles which will appear on the GUI using the new images, but retain the original properties: Infinite health, unpassible, and damaging when trying to move.  In this mode they will appear as a 1 in the obstacle map.
- New Map System
	- Maps can now be parse from the config file as shown in the config.sample
	- Valid map symbols: R - Rock, T - Tree, B - Bush, O - Obstacle, and a space for empty
	- The width and height parameters are now mandatory so the config file parser knows how big to search
  - A smaller sample map has been included in the src folder.
- Updated loading messages so if something fails you know where. Maybe.
- Makefile update
	- The makefile was updated to allow the use of the structres found in the header files found in the src directory.  This means you can make your own mapData structure to save data instead of relying soley on the one provided each turn.
- Results.txt
	- The results.txt will now be created on a first run of the platform.  It will log all the players added to the map, and the winner of the game.  And append to the file if it exists.

### Fixes
- Fixed a bug where dead actors were causing a delay in turn processing.
- Partially, optimized turn checks for a small speed increase.

## Release 2.04
### New Features
- The same boring objects are a thing of the past.  The game will now choose a random obstacle category when generating the map.  In addition to a random category, a random style will also be selected.

## Release 2.03
### New Features
- Added a new config.sample file that gives a template for how to setup a map file.
- If the makefile detects that no configuration file is present, it will automatically generate one from the config.sample file.
### Changes:
- The repository no longer stores a config.txt file.  This is to prevent a developers local copy from getting overwritten and to avoid merge conflicts.  This means that on a first clone the user will need to run 'make' once to generate a config.txt file if it does not exist.

## Release 2.02
### Fixes
- Problem with freshly made tanks not being able to find the constructor
- The game will display a message to console and exit when no config file is found
- Changed development pipeline to push to a pre-release branch before merging with master release

## Release 2.01
### What needs to change:
- All config.txt files will need to be updated with new image files.  The format is now:
	AI <AI Name> <x> <y> <Up Image> <Right Image> <Down Image> <Left Image> <Bullet Image>
	All images follow this format:
	images/<color>/tank<ColorLetter>_<direction>.png
	images/<color>/bullet<ColorLetter>.png
	For the blue tank:
		images/Blue/tankB_U.png
		images/Blue/tankB_R.png
		images/Blue/tankB_D.png
		images/Blue/tankB_L.png
		images/Blue/bulletB.png

### What's New?
- Radar
	- The Radar stat is what determines how far around the tank it can see.  If you
		have a Radar stat of 2, you will only be able to see objects 2 spaces away from
		you.
- Random Objects
	- The platform will now select from a pool of objects during object placement on
		the map.  The current two options are:  Tree, or Rock.
- Map Scaling
	- The map size can now be changed in the configuration settings between 15x9 to
		40 x 20
- Idle Speed Adjustment
	- The idle speed can be changed within the configuration file.  Currently, this will
		only affect the time between turns.
- Restructuring of Images
	- Added two new colors for tanks and projectiles.  And restructured them based on their
	affiliated color.
	- Restructured Objects into folders based on type

### Fixes
- Deconstructor is now called for custom tanks instead of relying on the parent.
- Changed configuration file to account for Radar instead of Range.
- Tanks are now limited to only pending the allowed number of attribute points.
- You will no longer get a message for an incorrect number of attribute points spent
	if you were within the limit.

## Release 1.04
### Whats New?
- Added checks for tanks cheating and adding too many attributes points to their
stats

## Release 1.03
### What's New?
- A new example tank has been added to show the basics of movment and shooting
- Fixed Bugs associated to parsing the config file,
    - The config file can now load up to 4 tanks
    - The config file also now error checking so invalid options are ignored and
set to defaults
- Improved the effeciency of the game manager so tank moves process faster

repository: EatMoreCookies/SDSMT

repo_name: EatMoreCookies/SDSMT


text:
# Best Practices

The Deployment Manager (DM) templates aim to configure Couchbase according to our recommended best practices on Google Compute Engine (GCE).

## Compute

GCE offers both standard compute types and custom types.  Machine sizes depend on workload.  While one core machines will deploy successfully, [we recommend machines with 4 or more cores](https://developer.couchbase.com/documentation/server/current/install/pre-install.html) for production applications.

Machines with 16 cores and more will have higher I/O limits than machines with fewer cores.  For this reason we recommend 16 core machines for most applications.

We recommend deploying GCE nodes via an Instance Group Manager (IGM) as it improves reliability and simplifies the addition and removal of nodes.

### Memory Allocation

Couchbase recommends allocating 85% of system memory to the database. When using MDS this can be tuned between data, query, etc. The templates currently allocate 50% for data and 15% for index. This can be adjusted after deployment.

### Fault Tolerance and High Availability

The IGM in the templates places nodes across AZs in a round robin fashion.  For most installs this will be sufficient.

Ideally you may want to configure Couchbase Server Groups to map to Availability Zones.  The templates do not set this up.

## Storage

Google offers numerous storage options for IaaS.  When running Couchbase, three are viable:

* pd-ssd
* SSD Ephemeral Drive
* RAM Disk

For the vast majority of applications, pd-ssd is preferable.  It often outperforms the ephemeral as it is network bound and offers persistence that the ephemeral does not.  pd-ssd does all this at an attractive price point.

As of 6/28/17, I/O for pd-ssd caps out at 1.7TB  This is not currently reflected in Google's documentation.

## Network

The Google network is globally flat.  This is amazing for running a geographically distributed database like Couchbase.  Private IPs can be routed around the world without need for VPN or leased line solutions.  When connecting with another cloud or an on-premises cluster in a hybrid scenario, VPN or leased lines are still required.

GCP also provides convenient setup of a VPN from your laptop to a GCP project, making it simple to connect applications to the cloud as you develop them.

## Security

The template automatically sets up a username and password for the Couchbase Web Administrator.  By default the template opens 8091 to internet traffic.  You may want to consider closing this.

The template does not currently configure SSL. We recommend setting it up for production applications.

These templates open Sync Gateway access to the internet over ports 4984 and 4985.  We typically recommend securing the admin interface for access from `<IP_ADDRESS>` only.  That can be done by editing the `/home/sync_gateway/sync_gateway.json` file.


text:
###Introduction
We will create a simple ruby script that listens to the status of airtime requests rent to the Africa’s Talking Airtime API.

####Prerequisites
* We assume that you have gone through the Setup guide. If not, kindly take a look at it here [link!].
* You are registered on the sandbox[link!] and have access to either the web app or the android app.
* You have generated the API key here: https://account.sandbox.africastalking.com/settings/apikey.

We also expect that you either have a virtual machine online, or ar using a localhost tunneling service
like ngrok, to expose your local host to the web.

To set up on ngrok on your localhost, register for free and refer to the getting started documentation
on https://dashboard.ngrok.com/get-started.

###Accessing a USSD Menu
* When the Africa's Talking API receives an Airtime sending request, The API pushes the request to the telco for the number to be topped up.
Immediately, a HTTP POST is sent to your web address where your script is listening out for the post. This is your callback URL or webhook[link!]

*This Post indicates the state of your request for the sent airtime, as received from the Telco.

*Create the call back URL/ruby script 'airtimestatus.rb'

For Windows
```sh

>cd\
>cd User
>cd YourUsername
>cd  rubyapp
>echo "require './AfricasTalkingGateway' " > airtimestatus.rb

```

For Ubuntu
```sh

$ cd
$ cd rubyapp
$ touch airtimestatus.rb

```

* Once the file is created, we can write the lines of code we need to listen for HTTP POSTS from the API:
```ruby

require './AfricasTalkingGateway'

post '/airtimestatus' do
  @status  = params[:status]
  @requestId = params[:requestId]

  #write the data to db

end

```

* Running the ruby server should allow the script to be accessible on the URL: http://youripaddress:port/airtimestatus

repository: mikedeace/Outreach

repo_name: mikedeace/Outreach


text:
# Salaries of State Agencies FY 2016

## Dataset

| Name | Value |
| :--- | :---- |
| Catalog | [Link](https://catalog.data.gov/dataset/salaries-of-state-agencies-fy-2016) |
| Metadata | [Link](https://data.oregon.gov/api/views/25mj-qtvj) |
| Data: JSON | [100 Rows](https://data.oregon.gov/api/views/25mj-qtvj/rows.json?max_rows=100) |
| Data: CSV | [100 Rows](https://data.oregon.gov/api/views/25mj-qtvj/rows.csv?max_rows=100) |
| Host | data.oregon.gov |
| Id | 25mj-qtvj |
| Name | Salaries of State Agencies FY 2016 |
| Category | Revenue & Expense |
| Tags | 2016, salaries, state employees, salaries of state employees, wages, salaries 2016 |
| Created | 2016-11-24T08:23:20Z |
| Publication Date | 2016-11-24T08:30:31Z |

## Description

Salaries of state work force sorted by agency - 2016. For more information go to http://www.oregon.gov/transparency/Pages/state_workforce.aspx

## Columns

```ls
| Included | Schema Type    | Field Name     | Name           | Data Type | Render Type |
| ======== | ============== | ============== | ============== | ========= | =========== |
| Yes      | time           | fiscal_year    | FISCAL YEAR    | number    | number      |
| Yes      | series tag     | agency         | AGENCY #       | text      | text        |
| Yes      | series tag     | agency_title   | AGENCY TITLE   | text      | text        |
| Yes      | series tag     | classification | CLASSIFICATION | text      | text        |
| Yes      | series tag     | service_type   | SERVICE TYPE   | text      | text        |
| Yes      | series tag     | full_part_time | FULL/PART TIME | text      | text        |
| Yes      | numeric metric | annual_salary  | ANNUAL SALARY  | money     | money       |
```

## Time Field

```ls
Value = fiscal_year
Format & Zone = yyyy
```

## Data Commands

```ls
series e:25mj-qtvj d:2016-01-01T00:00:00.000Z t:service_type="AGENCY HEAD" t:full_part_time=FULL-TIME t:agency=12000 t:agency_title="ACCOUNTANCY, OREGON BOARD OF" t:classification="PRINCIPAL EXECUTIVE/MANAGER D" m:annual_salary=96036

series e:25mj-qtvj d:2016-01-01T00:00:00.000Z t:service_type=UNREPRESENTED t:full_part_time=FULL-TIME t:agency=12000 t:agency_title="ACCOUNTANCY, OREGON BOARD OF" t:classification="OFFICE SPECIALIST 1" m:annual_salary=38712

series e:25mj-qtvj d:2016-01-01T00:00:00.000Z t:service_type=UNREPRESENTED t:full_part_time=FULL-TIME t:agency=12000 t:agency_title="ACCOUNTANCY, OREGON BOARD OF" t:classification="ADMINISTRATIVE SPECIALIST 1" m:annual_salary=35268
```

## Meta Commands

```ls
metric m:annual_salary p:double l:"ANNUAL SALARY" t:dataTypeName=money

entity e:25mj-qtvj l:"Salaries of State Agencies FY 2016" t:url=https://data.oregon.gov/api/views/25mj-qtvj

property e:25mj-qtvj t:meta.view d:2017-09-25T07:29:33.362Z v:averageRating=0 v:name="Salaries of State Agencies FY 2016" v:id=25mj-qtvj v:category="Revenue & Expense"

property e:25mj-qtvj t:meta.view.owner d:2017-09-25T07:29:33.362Z v:displayName="Paula N." v:lastNotificationSeenAt=1500509429 v:id=d6zz-js5q v:screenName="Paula N."

property e:25mj-qtvj t:meta.view.tableauthor d:2017-09-25T07:29:33.362Z v:displayName="Paula N." v:lastNotificationSeenAt=1500509429 v:roleName=administrator v:id=d6zz-js5q v:screenName="Paula N."
```

## Top Records

```ls
| fiscal_year | agency | agency_title                 | classification                | service_type  | full_part_time | annual_salary |
| =========== | ====== | ============================ | ============================= | ============= | ============== | ============= |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | PRINCIPAL EXECUTIVE/MANAGER D | AGENCY HEAD   | FULL-TIME      | 96036.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | OFFICE SPECIALIST 1           | UNREPRESENTED | FULL-TIME      | 38712.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | ADMINISTRATIVE SPECIALIST 1   | UNREPRESENTED | FULL-TIME      | 35268.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | ADMINISTRATIVE SPECIALIST 1   | UNREPRESENTED | FULL-TIME      | 35268.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | ADMINISTRATIVE SPECIALIST 1   | UNREPRESENTED | FULL-TIME      | 33816.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | ADMINISTRATIVE SPECIALIST 2   | UNREPRESENTED | FULL-TIME      | 51181.20      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | PROGRAM ANALYST 1             | UNREPRESENTED | FULL-TIME      | 61727.40      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | FINANCIAL INVESTIGATOR 1      | UNREPRESENTED | FULL-TIME      | 67848.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | FINANCIAL INVESTIGATOR 1      | UNREPRESENTED | PART-TIME      | 67848.00      |
| 2016        | 12000  | ACCOUNTANCY, OREGON BOARD OF | FINANCIAL INVESTIGATOR 1      | UNREPRESENTED | FULL-TIME      | 67861.20      |
```

repository: SpellarBot/open-data-catalog

repo_name: SpellarBot/open-data-catalog


text:
# UCN Latex Templates

 Unofficial and not affiliated with University College Nordjylland

An easily customisable and structured [LaTeX](https://www.latex-project.org/) template for [UCN](https://ucn.dk) reports, papers, and assignments.

## The UCN Report Template
 Many students use LaTeX for typesetting their reports. Although LaTeX is very powerful and able to create beautiful documents, the learning curve for LaTeX novices may be quite steep. Especially the management of the layout may be hard.

This report template is an attempt to give these LaTeX novices a gentle start. The template takes care of loading the most common packages in the preamble, creating a front page, an English and a Danish UCN title page, a preface with signatures, and a simple folder structure for organising the tex-files.

In english for [an example/the documentation](https://github.com/Adrast/UCN-Latex-Templates/blob/master/UCNReportTemplate-en/UCNReportTemplate_en.pdf) and in Danish for [an example/the documentation](https://github.com/Adrast/UCN-Latex-Templates/blob/master/UCNReportTemplate-dk/UCN_Latex_Templates_master_dk.pdf).

## Credits

All credit should go to [@jkjaer](https://github.com/jkjaer)'s original [aauReportTemplate](https://github.com/jkjaer/aauLatexTemplates) which I forked and modified.

## License

[The 3-Clause BSD License](LICENSE)

repository: Adrast/UCN-Latex-Templates

repo_name: Adrast/UCN-Latex-Templates


text:
An extension to describe the general availability of a location. Similar to the availability attributes found in the practitionerRole resource.

Consists of:
* availableTime - indicates the times the location is available
  * availableTime.daysOfWeek - indicates the day(s) of the week the location is available
  * availableTime.allDay - indicates the location is always available
  * availableTime.availableStartTime - indicates when the location opens
  * availableTime.availableEndTime - indicates when the location closes
* notAvailable - indicates why a location is not available at a particular time
  * notAvailable.description - describes the reason the location is not available
  * notAvailable.during - indicates a period for which the location is not available
* availabilityExceptions - describes any exceptions to when this location is typically available

repository: dchaput/providerdirectory-ig

repo_name: dchaput/providerdirectory-ig


text:
Amazehing
=========

Initially hosted on bitbuket, it's a project from 2015.
It's basically a game that generate random mazes with monsters and you have to find the exit.

Usage
--------

To run it you will need to manually install the mensadb dependency found at [mensadb](https://github.com/KyuBlade/mensadb)

Set the permissions :

	sudo chmod +x gradlew

Run on desktop :

	gradlew desktop:run

repository: KyuBlade/Amazehing

repo_name: KyuBlade/Amazehing


text:
Tekton CLI RPM Build
====================

This is a Tekton task to run an rpm build on copr.

It only supports the latest release as released on GitHub. It queries the GitHub
api to get the latest release.

It uses the docker image from `quay.io/chmouel/rpmbuild`. The Dockerfile is located in
this directory.

The task uploads the release to
`https://copr.fedorainfracloud.org/coprs/chmouel/tektoncd-cli/`. The distros
supported are:

* Epel for CentOS 7
* Fedora 30/31
* RHEL8

You simply have to run this to get it installed:

```
dnf copr enable chmouel/tektoncd-cli
dnf install tektoncd-cli
```

USAGE
=====

Same as when you use the [release.pipeline.yaml](../release-pipeline.yml), you
need to have a PipelineResource for your git repository. See
[here](../release-pipeline-run.yml) for an example.

* You need to have your user added to the `https://copr.fedorainfracloud.org/coprs/chmouel/tektoncd-cli/` request it by going [here](https://copr.fedorainfracloud.org/coprs/chmouel/tektoncd-cli/permissions/) and asking for admin access.

* You need to get your API file from https://copr.fedorainfracloud.org/api/ and have it saved to `~/.config/copr`. You will need to change the
`username` field to `chmouel` since the copr repo is currently `/chmouel/tektoncd-cli/`.

* Make sure you have the GitHub token set as documented in [RELEASE_PROCESS.md](../../RELEASE_PROCESS.md). You can also just add the `--namespace` option to all `kubectl` and `tkn` commands below and specify the namespace where you ran the release (by default, the namespace used in `release.sh` is `release`).

* You create the secret from that copr config file:

```
kubectl create secret generic copr-cli-config --from-file=copr=${HOME}/.config/copr
```

* Make sure you already have git-clone Task installed. To verify, run the command:

```
tkn task list | grep "git-clone"
```

If the above command doesn't return anything then you can install using:

```
tkn hub install task git-clone
```

* You should be able create the task with:

```
kubectl create -f rpmbuild.yml
```

And run it with:

```
kubectl create -f rpmbuild-run.yml
```

* Use `tkn pr desc rpmbuild-pipelinerun` to make sure the `PipelineRun` didn't fail on validation

And use the following command to get the logs of the `PipelineRun`:

```
tkn pr logs rpmbuild-pipelinerun -f
```

repository: tektoncd/cli

gha_language: Go

repo_name: tektoncd/cli


text:
# Image Search Application

Simple image search application which uses [unsplash.com API](https://unsplash.com/documentation#search).
This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Before Start

Here are a few steps to use Unsplash API features in this app:

You need to create **.env** file in the project directory and add 3 variables:
 - Unsplash demo app API Access Key as REACT_APP_API_ACCESS_KEY
 - Unsplash demo app API Secret Key as REACT_APP_API_SECRET_KEY
 - Unsplash demo app Redirect Uri as REACT_APP_AUTH_REDIRECT_URL

In order to create these variables you need to create free developer account from [unsplash.com/developers](https://unsplash.com/developers) and then add new application from **your apps** tab.

In your newly created application:

You can get **Access Key** and **Secret Key** from Keys Section.
![Screen Shot 2021-10-31 at 8 45 24 PM](https://user-images.githubusercontent.com/34595361/139595601-69aeaf6d-485c-4db7-a2d6-cebee6720444.png)

In Redirect URI & Permissions Section
 - You need to change your **Redirect URI** to complete authentication, for local tests change it to http://localhost:3000.
 - Check the **Write likes access** checkbox to use like/unlike photo feature of app. (The **Public access** checkbox is checked by default).
![Screen Shot 2021-10-31 at 8 45 06 PM](https://user-images.githubusercontent.com/34595361/139595611-5c966c6d-a501-45a4-8042-6442e0ab269b.png)

After operations above your **.env** file should look like below:
```
REACT_APP_API_ACCESS_KEY = IH9l4pLo5tydtmPDF3XR3e3MtlDYEYQO5}Jh^.M
REACT_APP_API_SECRET_KEY = wTcWxdF6HVVQ7RF9U8PxcaAM7noN2wzBIOQ9uAi
REACT_APP_AUTH_REDIRECT_URL = http://localhost:3000
```

## Source Folders

### `apiService`

##### `index.js`
API requests of the application

##### `axios/interceptors.js`
Axios API client interceptors which responsible for token configuration and error handling.

### `components`

##### `partials`
Represents partial components of application. In this app it just contains single photo item component.

##### `sections`
Represents sections of the application (Search Field, Search Results, Header and Footer).

### `context`

Contains context creation for authentication. I used [React Context API](https://reactjs.org/docs/context.html) for sharing and controlling auth state information through the app.
Redux or Mobx can be also used if you have large scaling app. Moreover, if you have a larger app, router or navigation layers will be better place for controlling authentication.
As an example check out my other repo [React Fluffzy Auth](https://github.com/EgeAytin/react-fluffzy-auth) boilerplate authentication infrastructure for React applications.

### `views`

Represents pages and user interfaces. In this app it just contains Home page.

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

 The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Additional Notes

### Design
I took care to keep the design of the application very simple and understandable. This is a testing application that focuses more on functionality, so I would like to point out that it does not have production level design quality.

### 3rd Party Libraries
- I used [bootsrap](https://getbootstrap.com/) for the design layout and most of the components.

- I've used [react-infinite-scroll-component](https://github.com/ankeetmaini/react-infinite-scroll-component) for pagination. A simple Load More button would do the same here. However, I prefer infinite scrolling rather than clicking.

- I used [react-masonry-component](https://github.com/eiriklv/react-masonry-component) to display the search results in the grid layout structure like unsplash.com.

## Author

> Ege Aytın

><EMAIL_ADDRESS>
## License

MIT License

Copyright (c) 2021 Ege Aytın

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

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

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

repository: EgeAytin/react-image-search-application

repo_name: EgeAytin/react-image-search-application


text:
# Vamp Workflows
A collection of usable workflows for Vamp

## Workflows

- [retention](breeds/retention.js) - Set retention on one or more Elasticsearch indices

repository: vlesierse/vamp-workflows

repo_name: vlesierse/vamp-workflows


text:
# vue-scroll-sync

A Vue component that syncronize containers scroll positions

## Installation

```js
npm i --save vue-scroll-sync
```

### Browser

Include the script file, then install the component with `Vue.use(ScrollSync);` e.g.:

```html
<script type="text/javascript" src="node_modules/vue/dist/vue.min.js"></script>
<script type="text/javascript" src="node_modules/vue-scroll-sync/dist/scroll-sync.min.js"></script>
<script type="text/javascript">
  Vue.use(ScrollSync);
</script>
```

### Module

```js
import ScrollSync from 'vue-scroll-sync';
```

## Usage

Once installed, it can be used in a template as simply as:

```html
<scroll-sync>
    Content
</scroll-sync>
```

[Demo and Code Example](https://metawin-m.github.io/vue-scroll-sync)

## SSR

Create the `plugins/vue-scroll-sync.js` :

```javascript
import Vue from 'vue'
import ScrollSync from 'vue-scroll-sync'

Vue.component('scroll-sync', ScrollSync)
```

Include plugin in your `nuxt.config.js` file:

```javascript
module.exports = {
  plugins: ['~plugins/vue-scroll-sync']
}
```

## License

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

## Acknowledgments

* [react-scroll-sync](https://github.com/okonet/react-scroll-sync) for the scrolling position calculation and the method to prevent the event echo

repository: iletica/vue-scroll-sync

repo_name: iletica/vue-scroll-sync


text:
# Design Tokens

## What are design tokens?

Design tokens are all the values needed to construct and maintain a design system. They define and have the greatest overall impact on the system as a whole. These can represent anything defined by design: a CSS font stack, a colour as an RGB value, a spacing unit expressed in ems, an opacity as a decimal number, an animation timing function as Bezier coordinates. They’re used in place of hard-coded values to ensure flexibility and unity across all product experiences.

Design tokens are directly integrated into our component libraries and UI kits. They cover the various options of platform scales, colour themes, component states, and more.

## Colour

Colour usage guidelines go here.

## Typography

Typography guidelines go here.

## Spacing

Spacing guidelines go here.

## Layout

Layout guidelines go here.

## Images

Image guidelines go here.

repository: brendansparrow/nest-ui-system

gha_language: CSS

gha_license_id: MIT

repo_name: brendansparrow/nest-ui-system


text:
## About

I'm just your ordinary geek, hope you find some interesting things here.

## Projects

-   [start page](/startpage.html) - My homepage for the internet
-   [cube](/cube.html) - My method for solving a rubik\'s cube
-   [SitChess](/chess.html) - Rules my own chess variant
-   [Github](https://github.com/TeaSkittle/) - My projects which are hosted on Github
-   [The Cabin](/cabin.html) - A simple choose your own adventure game wirtten in python using ncurses
-   [HolyC](/holyc.html) - My basic work with the language HolyC by Terry A. Davis(December 15, 1969 -- August 11, 2018)

## Links

Various blogs and personal websites that I follow and enjoy.

-   [iswc.pw](https://iswc.pw/)
-   [mythreed.com](https://mythreed.com)
-   [z3bra.org](http://z3bra.org/)
-   [christine.website](https://christine.website/)
-   [casey.muratori](https://caseymuratori.com/nexus)
-   [deviant.ollam](https://deviating.net/)
-   [fabien.sanglard](http://fabiensanglard.net/)

repository: TeaSkittle/website

repo_name: TeaSkittle/website


text:
# Language Details

---

The following is a fairly extensive introduction to the *grama* language. This
is (admittedly) not a great place to start learning how to *use* `py_grama`, but
is instead provided as a reference.

*grama* is a conceptual language, and `py_grama` is a code implementation of
that concept. This page is a description of both the concept and its
implementation.

## Running example

We'll use a running example throughout this page; the built-in `py_grama` Cantilever Beam model.

```python
import grama as gr
from grama.models import make_cantilever_beam

md_beam = make_cantilever_beam()
md_beam.printpretty()
```

```bash
model: Cantilever Beam

  inputs:
    var_det:
      w: [2, 4]
      t: [2, 4]
    var_rand:
      H: (+1) norm, {'loc': 500.0, 'scale': 100.0}
      V: (+1) norm, {'loc': 1000.0, 'scale': 100.0}
      E: (+0) norm, {'loc': 29000000.0, 'scale': 1450000.0}
      Y: (-1) norm, {'loc': 40000.0, 'scale': 2000.0}
  functions:
    cross-sectional area: ['w', 't'] -> ['c_area']
    limit state: stress: ['w', 't', 'H', 'V', 'E', 'Y'] -> ['g_stress']
    limit state: displacement: ['w', 't', 'H', 'V', 'E', 'Y'] -> ['g_disp']
```

## Objects

*grama* focuses on two categories of objects:

- **data** (`df`): observations on various quantities, implemented by the Python package [Pandas](https://pandas.pydata.org/)
- **models** (`md`): functions and a complete description of their inputs, implemented by [py_grama](https://github.com/zdelrosario/py_grama)

For readability, we suggest using prefixes `df_` and `md_` when naming DataFrames and models.

### Data

Data are observations on some quantities. Data often come from the real world,
but data are also used to inform models, and models can be used to generate new
data. `py_grama` uses the Pandas `DataFrame` implementation to represent data.
Since data operations are already well-handled by Pandas, `py_grama` uses the
existing Pandas infrastructure and focuses on providing tools to handle models
and their interface with data.

### Models

Models in *grama* have both functions and inputs. `py_grama` implements models
in the `Model` class, which in turn have three primary objects:

- `Domain`: Defines bounds on variables
- `Density`: Defines a joint density for variables
- List of`Function`s: Maps variables to outputs

#### Domain

The domain of the model defines bounds for all the variables. If a variable is
not included in the domain object, it is assumed to be unbounded. The model
above has bounds on `t, w`, both of which are `[2, 4]`.

#### Density

The density of the model defines a joint density for the *random* variables. If
a variable is included in the density it is random, otherwise it is
*deterministic*. The model above has a joint density on `H, V, E, Y`.
The model summary gives details on each marginal distribution.

#### Functions

A function has a set of variables, which map to a set of outputs; for instance,
the `cross-sectional area` function above maps `['w', 't'] -> ['c_area']`. The
other functions take more variables, all of which map to their respective
outputs.

#### Inputs

The full set of model inputs are organized into:

|            | Deterministic                         | Random     |
| ---------- | ------------------------------------- | ---------- |
| Variables  | `md.var_det`                          | `md.var_rand` |
| Parameters | `md.density.marginals[var].d_param`   | (Future*)  |

- **Variables** are inputs to the model's functions
  + **Deterministic** variables are chosen by the user; the model above has `w, t`
  + **Random** variables are not controlled; the model above has `H, V, E, Y`
- **Parameters** are inputs to the model's density
  + **Deterministic** parameters are currently implemented; these are listed under `var_rand` with their associated random variable
  + **Random** parameters* are not yet implemented

The full set of *variables* is determined by the domain, density, and functions.
Formally, the full set of variables is given (in pseudocode) by `domain.var +
[f.var for f in functions]`. The set of random variables is then given by
`domain.var + [f.var for f in functions] - density.marginals.keys()`, while the
deterministic variables are the remainder `var_det = var_full - var_rand`.

## Verbs

Verbs are used to take action on different *grama* objects. We use verbs to
generate data from models, build new models from data, and ultimately make sense
of the two.

The following table summarizes the categories of `py_grama` verbs. Verbs take
either data (`df`) or a model (`md`), and may return either object type. The
prefix of a verb immediately tells one both the input and output types. The
short prefix is used to denote the *pipe-enabled version* of a verb.

| Verb Type | Prefix (Short)  | In   | Out   |
| --------- | --------------- | ---- | ----- |
| Evaluate  | `eval_` (`ev_`) | `md` | `df`  |
| Fit       | `fit_`  (`ft_`) | `df` | `md`  |
| Transform | `tran_` (`tf_`) | `df` | `df`  |
| Compose   | `comp_` (`cp_`) | `md` | `md`  |
| Plot      | `plot_` (`pt_`) | `df` | (Plot) |

Since `py_grama` is focused on models, the majority of functions lie in the
Evaluate, Fit, and Compose categories, with only a few original Transform
utilities provided. Some shortcut plotting utilities are also provided
for covenience.

`py_grama` verbs are used to both *build* and *analyze* models.

### Model Building

The *recommended* way to build `py_grama` models is with *composition calls*.
Calling `Model()` creates an "empty" model, to which one can add.

```python
md = gr.Model()
md.printpretty()
```

```bash
model: None

  inputs:
    var_det:
    var_rand:
  functions:
```

We can then use Compose functions to build up a complete model step-by step. We
recommend starting with the functions, as those highlight the required
variables.

```python
md = gr.Model("Test") >> \
     gr.cp_function(
         fun=lambda x: [x[0], x[1]],
         var=["x0", "x1"],
         out=2,
         name="Identity"
     )
md.printpretty()
```

```bash
model: Test

  inputs:
    var_det:
      x0: (unbounded)
      x1: (unbounded)
    var_rand:
  functions:
    Identity: ['x0', 'x1'] -> ['y0', 'y1']
```

Note that by default all of the variables are assumed to be deterministic. We
can override this by adding marginal distributions for one or more of the
variables.

```python
md = gr.Model("Test") >> \
     gr.cp_function(
         fun=lambda x: [x[0], x[1]],
         var=["x0", "x1"],
         out=2,
         name="Identity"
     ) >> \
     gr.cp_marginals(
         x1=dict(dist="norm", loc=0, scale=1)
     )
md.printpretty()
```

```bash
model: Test

  inputs:
    var_det:
      x0: (unbounded)
    var_rand:
      x1: (+0) norm, {'loc': 0, 'scale': 1}
  functions:
    Identity: ['x0', 'x1'] -> ['y0', 'y1']
```

The marginals are implemented in terms of the Scipy [continuous
distributions](https://docs.scipy.org/doc/scipy/reference/stats.html); see the
variable `gr.valid_dist.keys()` for a list of implemented marginals. When
calling `gr.comp_marginals()`, we provide the target variable name as a keyword
argument, and the marginal information via dictionary. The marginal shape is
specified with the "dist" keyword; all distributions require the `loc, scale`
parameters, but some require additional keywords. See `gr.param_dist` for a
dictionary mapping between distributions and parameters.

Once we have constructed our model, we can analyze it with a number of tools.

### Model Analysis

One question in model analysis is to what degree the random variables affect the
outputs. A way to quantify this is with *Sobol' indices* (Sobol', 1999). We
can estimate Sobol' indices in `py_grama` with the following code.

```python
df_sobol = \
    md_beam >> \
    gr.ev_hybrid(n=1e3, df_det="nom", seed=101) >> \
    gr.tf_sobol()
print(df_sobol)
```

```bash
eval_hybrid() is rounding n...
     w    t  c_area     g_stress  g_disp  ind
0  NaN  NaN     NaN        -0.03    0.28  S_E
0  NaN  NaN     NaN         0.35    0.21  S_H
0  NaN  NaN     NaN         0.33    0.64  S_V
0  NaN  NaN     NaN         0.31    0.02  S_Y
0  0.0  0.0     0.0   -345263.39    0.01  T_E
0  0.0  0.0     0.0   4867712.30    0.01  T_H
0  0.0  0.0     0.0   4577175.85    0.02  T_V
0  0.0  0.0     0.0   4224965.01    0.00  T_Y
0  0.0  0.0     0.0  13758547.04    0.04  var
```

The normalized Sobol' indices are reported with `S_[var]` labels; they indicate
that `g_stress` is affected roughly equally by the inputs `H,V,Y`, while
`g_disp` is affected about twice as much by `V` as by `E` or `H`. Note that the
Sobol' indices are *only* defined for the random variables---since Sobol'
indices are defined in terms of fractional variances, they are only formally
valid for quantifying contributions from sources of randomness.

Under the hood `gr.eval_hybrid()` attaches metadata to its resulting DataFrame,
which `gr.tran_sobol()` detects and uses in post-processing the data.

`py_grama` also provides tools for constructing visual summaries of models. We
can construct a *sinew plot* with a couple lines of code. First we inspect the
design:

```python
md_beam >> \
    gr.ev_sinews(n_density=50, n_sweeps=10, df_det="nom", skip=True) >> \
    gr.pt_auto()
```

![beam sinew results](../images/ex_beam_sinews_doe.png)

The "sinews" are sweeps across random variable space which start at random
locations, and continue parallel to the variable axes. Evaluating these
samples allows us to construct a sinew plot:

```python
md_beam >> \
    gr.ev_sinews(n_density=50, n_sweeps=10, df_det="nom", skip=False) >> \
    gr.pt_auto()
```

![beam sinew results](../images/ex_beam_sinews_res.png)

Here we can see that inputs `H,E` tend to saturate in their effects on `g_disp`,
while `V` is linear over its domain. This may explain the difference in
contributed variance seen above via Sobol' indices.

By providing tools to quickly perform different analyses, one can quickly get a
sense of model behavior using `py_grama`.

## Layers and Defaults

`py_grama` is built around *layers and defaults*. As much as is possible
`py_grama` is designed to provide sensible defaults "out-of-the-box". We saw the
concept of *layers* above in the model building example. The following example
shows defaults in action.

### Example Defaults: `gr.eval_monte_carlo()`

Attempting to provide no arguments to `gr.eval_monte_carlo()` yields the
following error:

```python
df_res = md_beam >> gr.ev_monte_carlo()
```

```bash
...
ValueError: df_det must be DataFrame or 'nom'
```

One can sample over the random variables given their joint density, but this
tells us nothing about how to treat the deterministic variables. The error
message above tells us that we have to define the deterministic variable levels
through `df_det`. To perform simple studies, we can explicitly limit attention
to the nominal conditions.

```python
df_res = md_beam >> gr.ev_monte_carlo(df_det="nom")
print(df_res.describe())
```

```bash
                H           V             E  ...  c_area    g_stress    g_disp
count    1.000000    1.000000  1.000000e+00  ...     1.0     1.00000  1.000000
mean   505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044
std           NaN         NaN           NaN  ...     NaN         NaN       NaN
min    505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044
25%    505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044
50%    505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044
75%    505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044
max    505.743982  906.946892  2.824652e+07  ...     9.0  9758.06826  0.438044

[8 rows x 9 columns]
```

By default `gr.eval_monte_carlo()` will draw a single sample; this leads to the
`NaN` standard deviation (`std`) results. We can override this default behavior
by providing the `n` keyword.

```python
df_res = md_beam >> gr.ev_monte_carlo(df_det="nom", n=1e3)
print(df_res.describe())
```

```bash
eval_monte_carlo() is rounding n...
                 H            V             E  ...  c_area      g_stress       g_disp
count  1000.000000  1000.000000  1.000000e+03  ...  1000.0   1000.000000  1000.000000
mean    499.776481  1001.908814  2.899238e+07  ...     9.0   6589.731053     0.333387
std     100.878972   102.929434  1.523033e+06  ...     0.0   3807.292688     0.199576
min     168.466610   635.220875  2.427615e+07  ...     9.0  -5830.363269    -0.339594
25%     433.466349   933.698938  2.799035e+07  ...     9.0   3921.581411     0.200657
50%     500.201964  1002.514072  2.896188e+07  ...     9.0   6633.083925     0.339702
75%     569.159912  1065.489928  2.993924e+07  ...     9.0   9161.066426     0.465231
max     798.543698  1327.618914  3.378264e+07  ...     9.0  18682.531892     1.045742

[8 rows x 9 columns]
```

Formally `1e3` is a float, which is not a valid iteration count. The routine
`gr.eval_monte_carlo()` informs us that it first rounds the given value before
proceeding. Here we can see some variation in the inputs and outputs, though
`c_area` is clearly unaffected by the randomness.

We can also provide an explicit DataFrame to the `df_det` argument. The
`gr.eval_monte_carlo()` routine will automatically take an *outer product* of
the deterministic settings with the random samples; this will lead to a
multiplication in sample size of `df_det.shape[0] * n`. Since this can get quite
large, we should reduce `n` before proceeding. We can also *delay evaluation*
first with the `skip` keyword, and inspect the design first before evaluating
it.

```python
df_det = pd.DataFrame(dict(
    w=[3] * 10,
    t=[2.5 + i/10 for i in range(10)]
))

df_design = md_beam >> gr.ev_monte_carlo(df_det=df_det, n=1e2, skip=True)
print(df_design.describe())
```

```bash
eval_monte_carlo() is rounding n...
                 H            V             E             Y       w            t
count  1000.000000  1000.000000  1.000000e+03   1000.000000  1000.0  1000.000000
mean    485.021539   989.376268  2.890355e+07  40135.172902     3.0     2.950000
std     112.546373    92.381768  1.462286e+06   2135.788506     0.0     0.287372
min     137.606474   764.764234  2.586955e+07  33320.789307     3.0     2.500000
25%     411.652958   927.448139  2.763002e+07  39104.255172     3.0     2.700000
50%     490.765903  1002.513232  2.903287e+07  40121.853496     3.0     2.950000
75%     561.317283  1046.038620  2.994359e+07  41279.345157     3.0     3.200000
max     726.351812  1239.473097  3.176696e+07  45753.627265     3.0     3.400000
```

If we are happy with the design (possibly after visual inspection), we can
pass the input DataFrame to the straight evaluation routine

```python
df_res = md_beam >> gr.ev_df(df=df_design)
print(df_res.describe())
```

```bash
                 H            V             E  ...       c_area      g_stress       g_
disp
count  1000.000000  1000.000000  1.000000e+03  ...  1000.000000   1000.000000  1000.00
0000
mean    510.457048  1003.972079  2.887534e+07  ...     8.850000   4555.508097     0.12
0805
std     105.566743    91.443354  1.486829e+06  ...     0.862116   7027.137049     0.59
9538
min     269.102628   830.234813  2.553299e+07  ...     7.500000 -18370.732185    -1.84
8058
25%     437.342719   939.490354  2.794973e+07  ...     8.100000   -385.620306    -0.29
7274
50%     515.387982   995.468715  2.868415e+07  ...     8.850000   5347.337598     0.23
2133
75%     584.899669  1054.815972  2.982724e+07  ...     9.600000   9824.615141     0.60
9096
max     775.221819  1257.095025  3.369872e+07  ...    10.200000  21238.954122     1.23
6387

[8 rows x 9 columns]
```

## Functional Programming (Pipes)

[Functional programming](https://en.wikipedia.org/wiki/Functional_programming)
touches both the practical and conceptual aspects of the language. `py_grama`
provides tools to use functional programming patterns. Short-stem versions of
`py_grama` functions are *pipe-enabled*, meaning they can be used in functional
programming form with the pipe operator `>>`. These pipe-enabled functions are
simply aliases for the base functions, as demonstrated below:

```python
df_base = gr.eval_nominal(md_beam, df_det="nom")
df_functional = md_beam >> gr.ev_nominal(df_det="nom")

df_base.equals(df_functional)
```

```bash
True
```

Functional patterns enable chaining multiple commands, as demonstrated in the
following Sobol' index analysis. In nested form using base functions, this would
be:

```python
df_sobol = gr.tran_sobol(gr.eval_hybrid(md_beam, n=1e3, df_det="nom", seed=101))
```

From the code above, it is difficult to see that we first consider `md_beam`, perform a hybrid-point evaluation, then use those data to estimate Sobol' indices. With more chained functions, this only becomes more difficult. One could make the code significantly more readable by introducing intermediate variables:

```python
df_samples = gr.eval_hybrid(md_beam, n=1e3, df_det="nom", seed=101)
df_sobol = gr.tran_sobol(df_samples)
```

Conceptually, using *pipe-enabled* functions allows one to skip assigning intermediate variables, and instead pass results along to the next function. The pipe operator `>>` inserts the results of one function as the first argument of the next function. A pipe-enabled version of the code above would be:

```python
df_sobol = \
    md_beam >> \
    gr.ev_hybrid(n=1e3, df_det="nom", seed=101) >> \
    gr.tf_sobol()
```

## References

- I.M. Sobol', "Sensitivity Estimates for Nonlinear Mathematical Models" (1999) MMCE, Vol 1.

gha_language: Jupyter Notebook


text:
---
section: help
lead: true
title: Full-text search API
authors:
- Neil Ashton
---
OpenSpending supports full-text search as a research tool for
everyone who wants to investigate the spending information kept
in our database.

It is important to note, however, that search is always performed
on individual entries. More abstract concepts (e.g. "all
health spending in a country over a given year") would mostly be the
result of adding up many individual entries. If your use case
requires that you access such concepts, you may want to look at
the [aggregation API](../aggregate) instead.

#### Basic call and parameters

    GET /api/2/search?q=<query>

Calls will return a set of fully JSON serialized entries, query
statistics, and, depending on the other parameters, other data such as
facets.

The following parameters are recognized:

* ``q``
  Query string. Will usually search a composite text field but can
  be limited to a specific field (i.e. a dimension, attribute, or measure)
  with ``field:value``. Boolean operators such as OR, AND, and ±term can also be used.

* ``dataset``
  Specifies a dataset name to search in. While searching across multiple
  datasets is supported, this parameter can be used to limit the scope and
  increase performance. It can be used multiple times or multiple
  dataset names can be separated with pipe symbols.

* ``category``
  The dataset category can be used to filter datasets by their type,
  e.g. limiting the output to only transactional expenditure (and
  excluding any budget items). Valid values include ``budget``,
  ``spending``, and ``other``.

* ``stats``
  Includes solr statistics on measures, namely the average, mean, and
  standard deviations. This is generated through the indexed data and
   can differ marginally from the
  results of the aggregator due to floating point inaccuracies.
  Note that aggregations
  across datasets with different currencies (or even the same currency
  across different years) are possible but must be avoided.

* ``filter``
  Apply a simple filter of the format ``field:value``. Multiple filters
  can be joined through pipes, e.g. ``fieldA:value|fieldB:value``.

* ``page``
  Page number for paginated results. Defaults to ``1``.

* ``pagesize``
  Size of a page for paginated results. Defaults to ``10000``.

* ``facet_field``
  A field to facet the search by, i.e. give all the distinct values of
  the field in the result set with the count of how often each occurred.

* ``facet_page``, ``facet_pagesize``
  Works analogously to the ``page`` and ``pagesize`` parameters but applies
  to facets instead.

* ``expand_facet_dimensions``
  When a compound dimension name is used for a facet, this will return a
  full representation of this dimension value for each value.

If an error is detected, the system will return a simple JSON response
with a list of ``errors`` describing the fault.

### Solr query syntax

OpenSpending uses Apache Solr for full-text indexing. Some search
parameters are passed directly to Solr:

    GET /api/2/search?q=money%20measure:[min%20TO%20max]&fq=dimension:value

Some useful resources to explore the query language of Solr include:

* [Solr Common Query Parameters](http://wiki.apache.org/solr/CommonQueryParameters)
* [Lucene Query Parser Syntax](http://lucene.apache.org/java/3_4_0/queryparsersyntax.html)
* [Solr Query Syntax](http://wiki.apache.org/solr/SolrQuerySyntax) (Advanced)

**Up**: [OpenSpending API](../)

branch_name: refs/heads/gh-pages


text:
[![Build Status](https://travis-ci.org/pozil/salesforce-node-client.svg?branch=master)](https://travis-ci.org/pozil/salesforce-node-client)

# Salesforce Node Client

**Table of Content**
- [About](#about)
- [Installation](#installation)
- [Documentation](#documentation)
	- Declaring your application in Salesforce
	- Configuring and instantiating the client
	- Authenticating
	- Interacting with Force.com data
	- Interacting with Apex REST resources

# About
Node.js client library for Salesforce Force.com services.

This library provides access to 2 main Force.com services:
- Authentication through OAuth 2.0
- Data through Force.com REST APIs

This client is provided “as is“ without any warranty or support. Salesforce does not officially endorse it.

**Credit**

The authentication service of this project is largely inspired by [cangencer's project](https://github.com/cangencer/salesforce-oauth2).

**Sample application**

A sample React.js application that integrates with Salesforce using this client can be found in [this repository](https://github.com/pozil/salesforce-react-integration).

Even if you are not familiar with React.js, the Node.js backend code is worth looking at.

## Installation
This project can be installed through NPM:
```sh
$ npm install salesforce-node-client --save
```

## Documentation

### Declaring your application in Salesforce

Before being able to interact with Force.com with your application, you will have to declare it as a connected application:

1. Log in your Salesforce administrator account
2. Access Setup
3. Type 'App' in the quick find box and navigate to Build > Create > Apps
4. Scroll down and click 'New' in the 'Connected Apps' section
5. Fill in the required fields in the 'Basic Information' section
6. Check 'Enable OAuth Settings', this will open some additional settings
7. Provide a callback URL (this is an endpoint belonging to your application that should match `auth.callbackUrl` specified in the client configuration later)
8. Select your OAuth scope(s) ('api' is a good start)
9. Save your settings

### Configuring and  instantiating the client
The first thing that you need to do to use this project is to set its configuration and create a client instance.

To do so, create a configuration object with this structure:
```js
// Salesforce client settings for Force.com connection
var sfdcConfig = {
  // OAuth2 service
  auth : {
    // OAuth authentication domain
    // For production or DE use
    domain : 'https://login.salesforce.com',
    // For sandbox use
    //domain : 'https://test.salesforce.com',

    // URL called by Force.com after authorization and used to extract an authorization code.
    // This should point to your app and match the value configured in your App in SFDC setup)
    callbackUrl : 'http://localhost:3000/auth/callback',

    // Set of secret keys that allow your app to authenticate with Force.com
    // These values are retrieved from your App configuration in SFDC setup.
    // NEVER share them with a client.
    consumerKey : 'your consumer key',
    consumerSecret : 'your consumer secret key',
  },
  // Data service
  data : {
    // Force.com API version
    apiVersion : 'v37.0'
  }
};
```

Then, create an instance of the service with the following code:
```js
var SalesforceClient = require('salesforce-node-client');

// Instantiate Salesforce client with configuration
var sfdc = new SalesforceClient(sfdcConfig);
```

Once this is done, you may access the underlying client services with these properties:
- `auth` for the authentication service
- `data` for the data service

### Authenticating
Prior to performing any operation, you will need to authenticate with Force.com.

There are two authentication methods available:
- Standard user authentication (requires a browser).
- Password authentication for non-browser operations such as programmatic access.

#### Standard user authentication mode
The first step in standard user authentication is to generate the authorization URL with your OAuth scope(s) (API only in in this example) and redirect the user to it:
```js
// Redirect to Salesforce login/authorization page
var uri = sfdc.auth.getAuthorizationUrl({scope: 'api'});
return response.redirect(uri);
```

The user will authorize your application to connect to Salesforce and will be redirected to the `auth.callbackUrl` URL you specified in the client configuration.

**Important:** the callback URL you specified in the client configuration MUST match your connected applications settings in Salesforce.

The user will be redirected to that call back URL with an authorization code passed as a query parameter.

The Node client library will use that code (`request.query.code` in the following example) to authenticate with Force.com.
The, once the authentication is completed:
1. persist the response payload in a server-side session (you will need this for all further operations)
2. redirect the user to your application's home page

```js
// Authenticate with Force.com
sfdc.auth.authenticate({'code': request.query.code}, function(error, payload) {
	// Store the payload content in a server-side session
	// Redirect your user to your app's home page
}
```

The `authenticate` response `payload` is an object with the following format:

| Attribute     | Description |
| ------------- |-------------|
| id            | URL that represents logged in user |
| issued_at     | Timestamp of token creation |
| refresh_token | Long-lived token that may be used to obtain a fresh access token on expiry of the access token |
| instance_url  | URL that identifies the Salesforce instance to which API calls should be sent |
| access_token  | Short-lived access token |
| signature     | Hash used to sign requests sent to Force.com (the client library will take care of that for you) |

#### Password authentication mode
In order to perform password authentication, use the following:
```js
// Authenticate with Force.com
sfdc.auth.password({
	'username': 'the user name',
	'password': 'the user password',
}, function(error, payload) {
	// Store the payload content in a server-side session
	// Do something
}
```

#### Logging out
You may log out a user of your application by revoking his access token `accessToken` with the following code:
```js
// Revokes your user's access to Force.com
sfdc.auth.revoke({'token': accessToken}, function(error) {
	// Do something
}
```
**Important:** revoking a user's access token logs the user out of your application but not Salesforce.

### Interacting with Force.com data
Once you have authenticated, you may perform various operations on Force.com.

For all operations, you will need the response payload of `auth.authenticate` or `auth.password`.
We will refer to it as `sfdcSession`.

#### Interacting with Force.com data
Interactions with Force.com data performed with this client handled with REST APIs in two steps.

First, prepare the request options and sign it with the client by calling `data.createDataRequest`.
To do so, you will need to provide two paramters:
- `sfdcSession` the session information
- `resourceUrlSuffix` a string containing the location of the REST resource you wish to interact with (you may use the [REST Explorer](https://workbench.developerforce.com/restExplorer.php) from the Workbench to get the right URL).

Finally, send the request with the HTTP verb of your choice and process the response.

```js
// Prepare Force.com request options with a SOQL query that lists users
var query = encodeURI('SELECT Id, Name FROM User LIMIT 10');
var apiRequestOptions = sfdc.data.createDataRequest(sfdcSession, 'query?q='+ query);
// Send an HTTP GET request with our options
httpClient.get(apiRequestOptions, function (error, payload) {
	// Do something
}
```

#### Retrieving the currently logged user
As a convenience, you can retrieve the currently logged in user with this call:
```js
// Request logged user info
sfdc.data.getLoggedUser(sfdcSession, function (error, userData) {
	// Do something
}
```

### Interacting with Apex REST resources
Apex REST resources can be called in the following way:
```js
// Builds a REST query to a custom Apex resource
var apiRequestOptions = sfdc.apex.createApexRequest(sfdcSession, 'MyCustomApexResource/001B000000RS9WWIA1');
// Send an HTTP GET request with our options
httpClient.get(apiRequestOptions, function (error, payload) {
	// Do something
}
```

repository: FontevaRecruiting/DAS

repo_name: FontevaRecruiting/DAS