text:
Features
--------

- Make your tables responsive easily
- Select columns/headings you want to show or not
- Set a custom heading for rows in responsive mode based on templates
- Control responsive behavior based on viewport width
- Based on the Chirs Coyier responsive tables approach described here
- Lightweigth plugin ~< 2kb

Usage
-----

- jQuery is required
- Download the plugin magic-tables.min.js js file
- Download the plugin magic-tables.min.css css file

Include both files in your project and simply call the magicTable plugin over a table:

`````javascript

<script type="text/javascript">
    jQuery('.mytable').magicTable();
</script>

`````

Options
-------

You can pass a diferent options to customize responsive behavior

- responsiveWidth default: 1024

Set the min viewport width that enables responsive behavior.

- skipColumns default: []

Array with columns index you want to skip in responsive mode, starting from 0.

i.e. if you want to hide the first and third column you have to pass [0,2]

- displayLabels default: true

Controls column heading display for all rows

- skipLabels default: []

Array with columns heads you want to skip in responsive mode, starting from 0.

- customTitle default: ''

A html template to create custom heading for each row.

If is set, a new column will be added and the beginning of each row using the specfic template.

You can define simple templates like

`````html
<b>{0}</b>.
`````

{0} will be replace for the column 0 value.

You can reference any column, no matter if that column are in the skipColumns array.
In fact, you may want to use this feature in combination with skipColumns to create custom heading for each row in responsive mode and hide referenced columns.

See custom title example in demo page to give a better idea.

- labelSeparator default: ':'

Set separator between column heading and column value in responsive mode.

Demo
----

See some demos here

repository: rreimi/responsible-tables

repo_name: rreimi/responsible-tables


text:
# GamesCatalogue :video_game:
[![MIT](https://img.shields.io/badge/license-MIT-green.svg)](https://opensource.org/licenses/MIT)

React web application to view latest Games and Trailers

## Installing

1) Clone this repository on your local machine.
2) Run `npm install` to install all the dependencies.
3) Run `npm start` to start dev server.
4) GamesCatalogue will be avaialbe at [http://localhost:8080/](http://localhost:8080/)

## API format

```
[
   {
      "api_rate_limit":50000
   },
   {
      "title":"LittleBigPlanet PS Vita",
      "platform":"PlayStation Vita",
      "score":9.0,
      "genre":"Platformer",
      "editors_choice":"Y"
   },
   {
      "title":"LittleBigPlanet PS Vita -- Marvel Super Hero Edition",
      "platform":"PlayStation Vita",
      "score":9.0,
      "genre":"Platformer",
      "editors_choice":"Y"
   },
   .
   .
   .
```

## Screenshot

![Games Catalogue](https://raw.githubusercontent.com/ChaitanyaKaranam/GamesCatalogue/master/Screenshot/Games.PNG "Games Catalogue")

license: MIT

repository: ChaitanyaKaranam/GamesCatalogue

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: ChaitanyaKaranam/GamesCatalogue


text:
  MultiHack

Real-Time Editor, Web Host, Voice Chat, and Social Network.

Tired of struggling to set up remote collaboration with your team? multihack.co

###Collaborate in Real Time
Code is synchronized in real time between everyone on your team.
Work on complex projects with a large number of files.
All data is sent over an encrypted websockets connection.

###Integrated Voice Chat
Join a secure group call in one click with WebRTC.

###Deploy your Website Instantly
MultiHack uses HyperHost to deploy your web project to the web instantly.
Test designs with clients without ever needing to setup a server!

###Syntax Highlighting
Syntax highlighting for all web languages is supported.
MultiHack is built with CodeMirror, so adding new highlighting is a breeze!

###Network With Other Users
MultiHack allows you to see other users online and request to code with them, without any kind of account or URL needed.
It's great for programming interviews, tutoring, hackathons, or just meeting other developers!

###Export Your Project
Save your project as a ZIP archive and use it in your favourite native IDE.
If you want to stay in MultiHack, you can save your project to your browsers LocalStorage!

###Upload Existing Projects
Upload files, ZIP archives, and even pull from GitHub without leaving MultiHack!

###Works Offline
When your internet connection drops, MultiHack moves your code into your own private room.
You can keep working on your own version without interruptions.

###Works On Mobile
MultiHack works your phone! Even iOS Safari!

##Deploy To Heroku
Although MultiHack is meant to bring developers together, you can run your own instance if you need to.

repository: pro-to-tip/webrtc

repo_name: pro-to-tip/webrtc


text:
---
layout: post
title: EB5 regional center - 1300+ centers data driven statistics
date: 2017-5-20
tags: EB-5-visa regional-center
comments: true
description: 9000+ visas awarded annually to regional center EB-5 investors. Over $5 billion invested through the regional centers to generate over 150K full time jobs yearly. Top 5 states pull in 65% of the total investments.
---

## What is a regional center?
United States Citizenship and Immigration Services (USCIS) designates certain businesses as regional centers through which foreign investors can invest money to obtain legal permanent residency(LPR) commonly referred to as green card. These green cards or visas are granted through the employment based 5th category [EB-5 investor visa](/posts/eb-5/).

## Table Of Contents

- [EB-5 visa program and regional centers](#eb-5-visa-program-and-regional-centers)
- [EB-5 regional center program extension](#eb-5-regional-center-program-extension)
- [Eb-5 investor visa requirement](#eb-5-investor-visa-requirement)
- [EB-5 Regional center application and designation](#eb-5-regional-center-application-and-designation)
- [EB-5 Regional centers statistics](#eb-5-regional-centers-statistics)
- [EB-5 Regional center terminations](#regional-center-terminations)
- [Regional center risks](#regional-center-risks)
- [Create your regional center rankings](#create-your-regional-center-rankings)

## EB-5 visa program and regional centers

In the early 90s, the EB-5 visa program was amended to create the EB-5 regional center program.  An EB-5 Regional Center is a commercial
enterprise which can pool money from the foreign immigrants and make capital investment projects. Regional Centers are designated as
such by USCIS to promote economic growth and job creation.

Regional center investment is not a mandatory for the EB-5 visa, investors can also make direct investments. However, the primary advantage of the regional center is that the foreign immigrant can meet the visa requirements by counting the indirect jobs projected to be created through the center. In contrast, the direct investment EB-5 applicants can meet the requirements only through the jobs directly created. Regional centers helps the foreign investors who are more interested in obtaining LPR than directly investing or operating a business in the United States (U.S).

The EB-5 Regional Center (RC) is a for profit enterprise which connects the foreign investor to the developers of projects in need of capital. The regional centers typically create an investment fund pooled from foreign investors and sponsors one or more commercial businesses. Real estate is the most common investment avenue of the regional centers. Regional centers
sponsors projects like construction of luxury hotels, office spaces, apartment complexes, warehouses etc. While most regional centers are private enterprises, there are a few of govt created public entities too. The primary motive behind the regional center program is to increase economic growth, productivity, job creation.

## EB-5 regional center program extension

Congress initially created the regional center program for a period of 5 years. Since then it has been extended to subsequent 5 year periods for the last 25 years. Current approval of the regional center program runs until September 2017.

## EB-5 investor visa requirement

The EB-5 visa program in essence has 2 requirements, investments and job creation.
The foreign investor has to invest $1 million dollars in a regional center. The amount is reduced to half a million dollars if the regional center is located in areas of high unemployment and not within urban centers.

Such investments have to generate at least 10 direct or indirect full time jobs through the regional center.

The foreign investor can get a green card (LPR) for themselves and their immediate family members (spouse and minor children).

USCIS conditionally approves the green card for about 2 years

After 2 years, USCIS permanently approves the green card upon the investment meeting the job requirement and other EB5 program rules

EB-5 investor can live, study or work anywhere in the U.S. None of the activity needs to be associated to the geographical location of the regional center.

Eb-5 applicants need not have to be actively managing the projects through which they are seeking a green card. However, applicants seeking green card through direct investments typically
actively are involved in the operations of the enterprise.

## EB-5 Regional center application and designation

Developers makes an application to USCIS through form I-924 to designate a project as an EB-5 regional center. The application includes
information about the geographical area and the types of businesses the regional center plans to invest. The application can include
actual projects or hypothetical projects. Hypothetical project application should include supporting documents to demonstrate the job
creation of the proposed regional center. The application for an actual project requires a description of the nature of the business,
it's detailed business plan and details of employment generated.

## EB-5 regional centers statistics
Following are the interesting statistics from the regional centers,

### Types of common commercial activity undertaken by the regional center projects

- Various types of Wholesale trading business
- Nonresidential Building Construction
- Traveler Accommodation
- Architectural, Engineering, and Related Service

### EB-5 recipients by regional origin,
![EB-5 investors]({{ site.url }}assets/images/posts/eb5-country-demand.png)

### Highlights from the recently released analysis of the program by the U.S. Department of Commerce. Data were used from FY2012-2013.

Data pulled from the [report](http://www.esa.doc.gov/sites/default/files/estimating-the-investment-and-job-creation-impact-of-the-eb-5-program_0.pdf)

- $5.6 billion invested through the EB-5 investor program in a year.
- 35% of investments for the regional center project funding were contributed by foreign investors
- Around 170,000 estimated jobs were created through regional centers in a year
- California is the top destination for US investor visa program
- New York, Florida, Texas and Alabama are the top attractive destinations

### Spread of regional center projects as of now,

No. of regional centers | State/Territory
------------------- | --------------
13	| Alabama
1	| Alaska
10	| Arizona
6	| Arkansas
223	| California
18	| Colorado
5	| Commonwealth of Northern Marianas Islands
44	| Connecticut
11	| Delaware
23	| District of Columbia
84	| Florida
35	| Georgia
3	| Guam
15	| Hawaii
4	| Idaho
30	| Illinois
24	| Indiana
3	| Iowa
1	| Island of Guam
7	| Kansas
10	| Kentucky
17	| Louisiana
3	| Maine
31	| Maryland
21	| Massachusetts
11	| Michigan
7	| Minnesota
17	| Mississippi
10	| Missouri
2	| Montana
5	| Nebraska
24	| Nevada
10	| New Hampshire
85	| New Jersey
9	| New Mexico
107	| New York
21	| North Carolina
3	| North Dakota
18	| Ohio
12	| Oklahoma
21	| Oregon
68	| Pennsylvania
7	| Puerto Rico
10	| Rhode Island
15	| South Carolina
1	| South Dakota
14	| Tennessee
73	| Texas
3	| U.S. Virgin Islands (USVI)
7	| Utah
1	| Vermont
27	| Virginia
59	| Washington
11	| West Virginia
20	| Wisconsin
1	| Wyoming

USCIS, EB5 approved projects can be found on their [website ](https://www.uscis.gov/working-united-states/permanent-workers/employment-based-immigration-fifth-preference-eb-5/immigrant-investor-regional-centers)

### Number of terminated regional centers

- 98 regional centers have been [terminated](https://www.uscis.gov/working-united-states/permanent-workers/employment-based-immigration-fifth-preference-eb-5/eb-5-immigrant-investor-process/regional-center-terminations) by USCIS so far.

## Regional center terminations

USCIS terminates the EB-5 regional center designation to the projects for any of the following reasons,

* If the regional center does not provide sufficient information to USCIS
* Regional center is not able to generate required employment and economic growth.

USCIS gives the regional center 30 days to furnish sufficient information and avoid termination. However, USCIS termination only disqualifies the project from the immigrant investor program. Those projects can continue to operate otherwise. If the investors already have a conditional green card approved through the terminated regional center, they can still demonstrate the EB-5 requirement compliance and go on to have an approved permanent residency.

USCIS also provides avenues for the terminated regional centers to appeal and get re approved for a EB-5 regional center designation.

## Regional center risks

It's important to note that even though USCIS designates a regional center, it does not guarantee or endorse the activities of the center. It's also important to note that USCIS or any other government agency does not evaluate the quality of the projects. The responsibility for due diligence of the regional center lies with the immigrant investor.
Securities Exchange Commission (SEC) has in recent times expanded the monitoring the EB-5 program and they issued an active fraud alert warning to the investors.

In one example, SEC alleged that a regional center falsely promised certain return on investment for investors investing in the regional  center. The developers of the regional center
started collecting money for the EB-5 program before the center was designated as a regional center by USCIS. SEC also claimed that the promoters used the money raised for the program for their own personal use. According to SEC, the foreign immigrant investors who invested money on the regional center did not get the Eb-5 green card.

In another similar case, the SEC alleged that another regional center falsely claimed that the necessary approvals were obtained for construction in addition to falsely claiming several non existing backers for the project. In this case too, the promoters used the money for some personal use according to SEC.

In another case, SEC sued lawyers for taking a transaction based fee for promoting certain regional centers.

Any investment has risks and EB-5 is no different. In EB-5 program it's more complicated because the investors are primarily looking to obtain U.S green card in addition to a return on investment. Also, most times the investors are located in a foreign country and have to depend on agents that makes them vulnerable to scams.

## Create your regional center rankings

With recent explosion of regional centers, investors should be cautious about getting involved in bad regional centers. Investors can follow the SEC guidelines and create their own risk based regional center project rankings. Incorporate the following guidelines while evaluating the regional centers. rank and pick the best among them.

* Verify that the regional center is not listed by USCIS in the terminated list.
* Verify that the regional center is in the USCIS eb-5 regional center list. Even if the regional center is listed remember that USCIS doesn't guarantee the quality of investments
* A regional center files various documents to USCIS to seek and maintain approvals. This includes the form I-924 for initial approval and yearly form I-924A filings to furnish additional information. Obtain these copies from the regional center

* Evaluate the business plans and scrutinize the project details etc reported in those documents. Seek in writing any clarifications you need.
* Check the track record of previous EB-5 approvals of the regional center if it exists.
* Ask if the consultants, attorneys and other service agencies get paid for promoting or recommending certain regional center. Ask them in writing. Individuals and entities who get paid for selling an investment may have to be registered with SEC. Ask for SEC registration details.

* Cross verify the information that you gather from the developers, consultants and lawyers and make sure they are consistent. Verify any claims made by any of these parties. For example, cross verify building permits, property tax assessments in the area the project is located. Compare similar projects in the area to make sure nothing that is being offered in out of the line.

* Examine the balance sheet of the regional center, the budget of the projects, assets, the amount of debt, due dates etc.

* Make sure the developers of the regional center's incentives are aligned to the success of the project.

* Watch out for overtly out of the line promises/promotions like risk free returns, guaranteed permanent status, high return on investments etc.

If the EB-5 investment entity end up being fraudulent, you risk of not only failing to obtain LPR, but you might also loose the money. Hence, be extremely cautious and careful about your investment. If you suspect anything after the investment was made report to USCIS and SEC.

gha_language: CSS


text:
## Build

Now that all the dependencies are installed, we can continue to
build a documentation website using @toolio/docs and @toolio/proto-theme.

We're going to use @toolio/docs default options to quickly get our docs up and running.

1. Create a directory named "docs" in the directory root of your project.
```bash
mkdir docs
```

2. Populate the "docs" directory with some `.md` files (your documentation). You can
use [proto-theme's documentation](https://github.com/tooliojs/proto-theme/tree/master/docs)
as dummy data if you'd like. Your project structure should look similar to this.
```txt
docs/
    docs.md
    go.md
    here.md
    your.md
node_modules/
package.json
package-lock.json
```

3. Create a JavaScript file somewhere in your project directory. Inside that file we'll call the
docs.build() function to generate our documentation. Here's how.
```js
// yourfile.js
require('@toolio/docs').build('html', {
    theme: 'proto',
    order: [
        'your',
        'docs',
        'go',
        'here
    ]
})
```
The `order` should be an array of markdown file names. It's used to determine the top to bottom rendering
of the documentation menu. Simply pass in the names of your markdown files
excluding the extension (`.md`), and your docs will be built in that specific order.

4. Finally, run the script you created to generate your docs.
```bash
node yourfile.js
```
If you look in the "docs" direcotry, there should be a newly created directory called `__build__`. Congrats
on making it this far.
Your project now has documentation in Markdown and HTML! That's great. But wait, there's more. Check out
[Markdown](Markdown.html) for details on some features included with this theme.

### Report Issues

If you encountered an error, during the Build process, please submit a
[Bug Report](https://github.com/tooliojs/proto-theme/issues/new/choose). We
will try our best to fix the issue as quick as possible. On the other hand,
the project is open source. You always have the option to clone it, and
try and solve the issue yourself. We really appreciate all the help
we can get :heart:

repository: tooliojs/proto-theme

repo_name: tooliojs/proto-theme


text:
# Enforce the use of `Math.trunc` instead of bitwise operators

💼 This rule is enabled in the ✅ `recommended` [config](https://github.com/sindresorhus/eslint-plugin-unicorn#preset-configs).

🔧💡 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix) and manually fixable by [editor suggestions](https://eslint.org/docs/developer-guide/working-with-rules#providing-suggestions).

<!-- end auto-generated rule header -->
<!-- Do not manually modify this header. Run: `npm run fix:eslint-docs` -->

Enforces a convention of using [`Math.trunc()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/trunc) instead of bitwise operations for clarity and more reliable results.
It prevents the use of the following bitwise operations:

- `x | 0` ([`bitwise OR`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Bitwise_OR) with 0)
- `~~x` (two [`bitwise NOT`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Bitwise_NOT))
- `x >> 0` ([`Signed Right Shift`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Right_shift) with 0)
- `x << 0` ([`Left Shift`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Left_shift) with 0)
- `x ^ 0` ([`bitwise XOR Shift`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Bitwise_XOR) with 0)

These hacks help truncate numbers but they are not clear and do not work in [some cases](https://stackoverflow.com/a/34706108/11687747).

This rule is fixable, unless the left-hand side in assignment has side effect.

## Fail

```js
const foo = 37.4;
console.log(foo | 0);
```

```js
const foo = 37.4;
console.log(~~bar);
```

```js
let foo = 37.4;
foo |= 0;
```

```js
const foo = 37.4;
console.log(foo << 0);
```

```js
const foo = 37.4;
console.log(foo >> 0);
```

```js
const foo = {bar: 37.4};
console.log(foo.bar ^ 0);
```

## Pass

```js
const foo = 37.4;
console.log(Math.trunc(foo));
```

```js
const foo = 37.4;
console.log(foo | 3);
```

```js
let foo = 37.4;
foo = Math.trunc(foo);
```

```js
const foo = 37.4;
console.log(~foo);
```

```js
const foo = 37.4;
console.log(foo >> 3);
```

```js
const foo = 37.4;
console.log(foo << 3);
```

```js
const foo = 37.4;
console.log(foo ^ 3);
```

repository: sindresorhus/eslint-plugin-unicorn

branch_name: refs/heads/main

gha_language: JavaScript

gha_license_id: MIT

repo_name: sindresorhus/eslint-plugin-unicorn


text:
---
layout: post
title:  "weekly picks (May 2 week 2021)"
date:   2021-05-08 00:16:27
categories: 2021may
---

{% include image.html url="/images/2021may2weeks.png" caption="A WordCloud of 2021 May 2nd week collection" width=300 align="center" %}

<--! 1. **[]()** : -->

1. **[PhysRevB.103.L201107](https://link.aps.org/doi/10.1103/PhysRevB.103.L201107)** : Quantum thermal transport in the charged Sachdev-Ye-Kitaev model: Thermoelectric Coulomb blockade (thermal transport, PRB)

1. **[PhysRevB.103.205115](https://link.aps.org/doi/10.1103/PhysRevB.103.205115)** : Extrinsic phonon thermal Hall transport from Hall viscosity (Sachdev, PRB)

1. **[PhysRevB.103.205111](https://link.aps.org/doi/10.1103/PhysRevB.103.205111)** : Quantum oscillations in the field-induced ferromagnetic state of $\mathrm{Mn}{\mathrm{Bi}}_{2\ensuremath{-}x}{\mathrm{Sb}}_{x}{\mathrm{Te}}_{4}$ (MnBiSbTe, PRB)

1. **[PhysRevB.103.184407](https://link.aps.org/doi/10.1103/PhysRevB.103.184407)** : **Functional renormalization group study of the Kitaev-$\mathrm{\ensuremath{\Gamma}}$ model on the honeycomb lattice and emergent incommensurate magnetic correlations (YBKim, PRB)**

1. **[PhysRevB.103.184202](https://link.aps.org/doi/10.1103/PhysRevB.103.184202)** : **Subdiffusion in a one-dimensional Anderson insulator with random dephasing: Finite-size scaling, Griffiths effects, and possible implications for many-body localization (Griffiths, PRB)**

1. **[PhysRevB.103.174408](https://link.aps.org/doi/10.1103/PhysRevB.103.174408)** : **Current-induced dynamics of skyrmion tubes in synthetic antiferromagnetic multilayers (skyrmion, PRB)**

1. **[PhysRevB.103.174302](https://link.aps.org/doi/10.1103/PhysRevB.103.174302)** : Classical many-body chaos with and without quasiparticles (Moessner, PRB)

1. **[PhysRevB.103.195116](https://link.aps.org/doi/10.1103/PhysRevB.103.195116)** : Transport in the non-Fermi liquid phase of isotropic Luttinger semimetals (Luttinger semimetal, PRB)

1. **[PhysRevB.103.195115](https://link.aps.org/doi/10.1103/PhysRevB.103.195115)** : Weyl nodal-line surface half-metal in ${\mathrm{CaFeO}}_{3}$ (Weyl nodal-line, PRB)

1. **[PhysRevB.103.184103](https://link.aps.org/doi/10.1103/PhysRevB.103.184103)** : Local structure of Nb in superconducting Nb-doped ${\mathrm{Bi}}_{2}{\mathrm{Se}}_{3}$ (Bi2Se3, PRB)

1. **[PhysRevB.103.195114](https://link.aps.org/doi/10.1103/PhysRevB.103.195114)** : **Manipulation of the Rashba spin-orbit coupling of a distorted $1T\text{-phase}$ Janus WSSe monolayer: Dominant role of charge transfer and orbital components (Rashba, PRB)**

1. **[PhysRevLett.126.185303](https://link.aps.org/doi/10.1103/PhysRevLett.126.185303)** : Chiral Anomaly in Interacting Condensed Matter Systems (Burkov, PRL)

1. **[PhysRevX.11.021030](https://link.aps.org/doi/10.1103/PhysRevX.11.021030)** : Broadband Terahertz Probes of Anisotropic Magnetoresistance Disentangle Extrinsic and Intrinsic Contributions (THz, PRX)

1. **[2105.02673](http://arxiv.org/abs/2105.02673)** : Versatility of spiral spin liquid in frustrated van der Waals magnets (GangChen, arXiv)

1. **[2105.02411](http://arxiv.org/abs/2105.02411)** : Quantum Oscillation of Thermally Activated Conductivity in a Monolayer WTe$_2$-like Excitonic Insulator (PALee, arXiv)

1. **[2105.02791](http://arxiv.org/abs/2105.02791)** : Local and non-local quantum transport due to Andreev bound states in finite Rashba nanowires with superconducting and normal sections (DLoss, arXiv)

1. **[2105.02654](http://arxiv.org/abs/2105.02654)** : A strange metal in a bosonic system (strange metal, arXiv)

1. **[2105.02415](http://arxiv.org/abs/2105.02415)** : Spin-valley locked instabilities in moire transition metal dichalcogenides with conventional and higher-order Van Hove singularities (DasSarma, arXiv)

1. **[2105.02287](http://arxiv.org/abs/2105.02287)** : Boosting spintronics with superconductivity (spintronics, arXiv)

1. **[PhysRevB.103.L020504](https://link.aps.org/doi/10.1103/PhysRevB.103.L020504)** : **Tunable critical field in Rashba superconductor thin films (Rashba, PRB)**

1. **[2105.02235](http://arxiv.org/abs/2105.02235)** : Eliashberg study of superconductivity induced by interfacial coupling to antiferromagnets (Eliashberg, arXiv)

1. **[PhysRevB.103.205201](https://link.aps.org/doi/10.1103/PhysRevB.103.205201)** : Acoustic plasmons in type-I Weyl semimetals (Weyl, PRB)

1. **[PhysRevB.103.205109](https://link.aps.org/doi/10.1103/PhysRevB.103.205109)** : Separated transport relaxation scales and interband scattering in thin films of ${\mathrm{SrRuO}}_{3}$, ${\mathrm{CaRuO}}_{3}$, and ${\mathrm{Sr}}_{2}{\mathrm{RuO}}_{4}$ (transport relaxation scales, PRB)

1. **[PhysRevB.103.195407](https://link.aps.org/doi/10.1103/PhysRevB.103.195407)** : Quantized Majorana pump in semiconductor-superconductor heterostructures (majorana, PRB)

1. **[PhysRevB.103.195109](https://link.aps.org/doi/10.1103/PhysRevB.103.195109)** : Intershell interactions in correlated materials: A slave-rotor approach (silke, PRB)

1. **[PhysRevB.103.174504](https://link.aps.org/doi/10.1103/PhysRevB.103.174504)** : Conductance quantization in topological Josephson trijunctions (conductance quantization, PRB)

1. **[PhysRevLett.126.187001](https://link.aps.org/doi/10.1103/PhysRevLett.126.187001)** : **Berry Curvature Effects on Quasiparticle Dynamics in Superconductors (QNiu, PRL)**

1. **[PhysRevLett.126.186601](https://link.aps.org/doi/10.1103/PhysRevLett.126.186601)** : Non-Fermi Liquids in Conducting Two-Dimensional Networks (GYCho, PRL)

1. **[2008.08124](http://arxiv.org/abs/2008.08124)** : WloopPHI: A tool for ab initio characterization of Weyl semimetals (Weyl, arXiv)

1. **[2105.02194](http://arxiv.org/abs/2105.02194)** : Zero-field 29Si nuclear magnetic resonance signature of helimagnons in MnSi (MnSi, arXiv)

1. **[2105.01872](http://arxiv.org/abs/2105.01872)** : $d$- and $p$-wave quantum liquid crystal orders in cuprate superconductors, $\kappa$-(BEDT-TTF)$_2$X, and coupled chain Hubbard models: functional-renormalization-group analysis (Kontani, arXiv)

1. **[2105.01813](http://arxiv.org/abs/2105.01813)** : Phenomenological model for the third-harmonic magnetic response of superconductors: application to Sr$_{2}$RuO$_{4}$ (ruthenate, arXiv)

1. **[2105.01689](http://arxiv.org/abs/2105.01689)** : Twofold van Hove singularity and origin of charge order in topological kagome superconductor CsV3Sb5 (CsV3Sb5, arXiv)

1. **[PhysRevB.103.195108](https://link.aps.org/doi/10.1103/PhysRevB.103.195108)** : Phase diagram of the spin-$\frac{1}{2}$ Yukawa--Sachdev-Ye-Kitaev model: Non-Fermi liquid, insulator, and superconductor (ZYMeng, PRB)

1. **[PhysRevLett.126.185301](https://link.aps.org/doi/10.1103/PhysRevLett.126.185301)** : Three-Dimensional Dirac Phonons with Inversion Symmetry (Dirac Phonons, PRL)

1. **[2105.01626](http://arxiv.org/abs/2105.01626)** : **Microscopic formulas for thermoelectric transport coefficients in lattice systems (thermoelectric, arXiv)**

1. **[2105.01624](http://arxiv.org/abs/2105.01624)** : A general model of MnSi-like spiral magnets (MnSi, arXiv)

1. **[2105.01544](http://arxiv.org/abs/2105.01544)** : Magnetostriction of {\alpha}-RuCl3 flakes in the zigzag phase (RuCl3 flakes, arXiv)

1. **[2105.01122](http://arxiv.org/abs/2105.01122)** : Complex pressure-temperature structural phase diagram of honeycomb iridate Cu$_2$IrO$_3$ (iridates, arXiv)

1. **[2105.01075](http://arxiv.org/abs/2105.01075)** : Fingerprints of quantum criticality in locally resolved transport (Qauntum criticality, arXiv)

1. **[2105.01397](http://arxiv.org/abs/2105.01397)** : Anisotropic compression and role of Sb in the superconducting kagome metal CsV$_3$Sb$_5$ (CsV3Sb5, arXiv)

1. **[2105.01243](http://arxiv.org/abs/2105.01243)** : Reentrant Superconductivity from Moir{\'e} Landau Levels (AHMacDonald, arXiv)

1. **[2105.01214](http://arxiv.org/abs/2105.01214)** : Study of charge density waves in suspended 2H-TaS2 and 2H-TaSe2 by nanomechanical resonance (TaS2, arXiv)

1. **[PhysRevB.103.L201101](https://link.aps.org/doi/10.1103/PhysRevB.103.L201101)** : Topological Nernst effect, anomalous Nernst effect, and anomalous thermal Hall effect in the Dirac semimetal ${\mathrm{Fe}}_{3}{\mathrm{Sn}}_{2}$ (Fe3Sn2, PRB)

1. **[PhysRevB.103.205403](https://link.aps.org/doi/10.1103/PhysRevB.103.205403)** : Tunable large Berry dipole in strained twisted bilayer graphene (FGuinea, PRB)

1. **[PhysRevB.103.205302](https://link.aps.org/doi/10.1103/PhysRevB.103.205302)** : Itinerant versus localized plasmons in an assembly of metal-dielectric parallel flat slabs in the presence of a perpendicular magnetic field: Faraday and magneto-optical Kerr effects (Bergman, PRB)

1. **[PhysRevB.103.195103](https://link.aps.org/doi/10.1103/PhysRevB.103.195103)** : Mirror Chern numbers in the hybrid Wannier representation (mirror chern number, PRB)

1. **[PhysRevB.103.195101](https://link.aps.org/doi/10.1103/PhysRevB.103.195101)** : Dependence of $\mathrm{DFT}+\mathrm{DMFT}$ results on the construction of the correlated orbitals (AJMillis, PRB)

1. **[PhysRevB.103.184502](https://link.aps.org/doi/10.1103/PhysRevB.103.184502)** : Unconventional Majorana fermions on the surface of topological superconductors protected by rotational symmetry (majorana, PRB)

1. **[PhysRevB.103.205104](https://link.aps.org/doi/10.1103/PhysRevB.103.205104)** : Large anomalous Hall effect induced by gapped nodal lines in GdZn and GdCd (nodal line, PRB)

1. **[PhysRevB.103.184301](https://link.aps.org/doi/10.1103/PhysRevB.103.184301)** : Observation of a chiral wave function in the twofold-degenerate quadruple Weyl system BaPtGe (Weyl system, PRB)

1. **[PhysRevB.103.174502](https://link.aps.org/doi/10.1103/PhysRevB.103.174502)** : Time-reversal symmetry breaking and multigap superconductivity in the noncentrosymmetric superconductor ${\mathrm{La}}_{7}{\mathrm{Ni}}_{3}$ (La7Ni3, PRB)

1. **[PhysRevLett.126.187601](https://link.aps.org/doi/10.1103/PhysRevLett.126.187601)** : Cooperative Cluster Jahn-Teller Effect as a Possible Route to Antiferroelectricity (antiferro, PRL)

1. **[2105.00902](http://arxiv.org/abs/2105.00902)** : Frozen deconfined quantum criticality (QCP, arXiv)

1. **[s43580-021-00051-y](https://doi.org/10.1557/s43580-021-00051-y)** : A snapshot review—Fluctuations in quantum materials: from skyrmions to superconductivity (skyrmion-SC, arXiv)

1. **[2105.00550](http://arxiv.org/abs/2105.00550)** : Tunable chiral charge order in kagome superconductor RbV3Sb5 (kagome SC, arXiv)

1. **[2105.00464](http://arxiv.org/abs/2105.00464)** : Phase diagram of the three-band d-p model (three band model, arXiv)

1. **[2105.00688](http://arxiv.org/abs/2105.00688)** : A toy model for localized to itinerant electron transitions (localized itinerant, arXiv)

1. **[2105.00387](http://arxiv.org/abs/2105.00387)** : High-energy magnetic excitations from heavy quasiparticles in CeCu$_2$Si$_2$ (CeCu2Si2, arXiv)

1. **[PhysRevB.103.L201401](https://link.aps.org/doi/10.1103/PhysRevB.103.L201401)** : Femtosecond photoluminescence from monolayer ${\mathrm{MoS}}_{2}$: Time-domain study on exciton diffusion (MoS2, PRB)

1. **[PhysRevB.103.L201102](https://link.aps.org/doi/10.1103/PhysRevB.103.L201102)** : Koopmans' theorem as the mechanism of nearly gapless surface states in self-doped magnetic topological insulators (magnetic TI, PRB)

1. **[PhysRevB.103.195401](https://link.aps.org/doi/10.1103/PhysRevB.103.195401)** : Readout of Majorana bound states via Landau-Zener transition (majorana, PRB)

1. **[PhysRevB.103.195105](https://link.aps.org/doi/10.1103/PhysRevB.103.195105)** : Spin-orbit coupling in the kagome lattice with flux and time-reversal symmetry (kagome, PRB)

1. **[PhysRevB.103.195104](https://link.aps.org/doi/10.1103/PhysRevB.103.195104)** : Orbital susceptibility of T-graphene: Interplay of high-order van Hove singularities and Dirac cones (T-graphene, PRB)

1. **[PhysRevB.103.174403](https://link.aps.org/doi/10.1103/PhysRevB.103.174403)** : Infrared phonon spectroscopy on the Cairo pentagonal antiferromagnet ${\mathrm{Bi}}_{2}{\mathrm{Fe}}_{4}{\mathrm{O}}_{9}$: A study through the pressure-induced structural transition (Cairo pentagonal, PRB)

1. **[PhysRevB.103.174402](https://link.aps.org/doi/10.1103/PhysRevB.103.174402)** : Topological magnons for thermal Hall transport in frustrated magnets with bond-dependent interactions (YBKim, PRB)

1. **[PhysRevB.103.174401](https://link.aps.org/doi/10.1103/PhysRevB.103.174401)** : Magnetic anisotropy in the van der Waals ferromagnet $\mathrm{V}{\mathrm{I}}_{3}$ (VI3, PRB)

1. **[2104.15125](http://arxiv.org/abs/2104.15125)** : Triangular pair-density wave in confined superfluid $^3$He (PDW, arXiv)

1. **[2104.15012](http://arxiv.org/abs/2104.15012)** : Optical vortex manipulation for topological quantum computation (vortex, arXiv)

1. **[2104.15026](http://arxiv.org/abs/2104.15026)** : Magnetic impurities at quantum critical points: large-$N$ expansion and SPT connections (Vishwanath, arXiv)

1. **[2104.14869](http://arxiv.org/abs/2104.14869)** : Many-Body Quantum States with Exact Conservation of Non-Abelian and Lattice Symmetries through Variational Monte Carlo (VMC, arXiv)

1. **[2104.14857](http://arxiv.org/abs/2104.14857)** : Surface plasmonics of Weyl semimetals (Weyl, arXiv)

1. **[2104.14853](http://arxiv.org/abs/2104.14853)** : **Development of spin fluctuations under the presence of $d$-wave bond order in cuprate superconductors (Kontani, arXiv)**

1. **[2104.14634](http://arxiv.org/abs/2104.14634)** : Topological charge density wave in monolayer NbSe2 (Topological CDW, arXiv)

1. **[2104.14606](http://arxiv.org/abs/2104.14606)** : Pseudogap phase and fractionalization : an experimental test (Pepin, arXiv)

1. **[2104.14588](http://arxiv.org/abs/2104.14588)** : Universal magnetic oscillations of conductivity in the incoherent regime of correlated systems (Zitko, arXiv)

1. **[2104.14578](http://arxiv.org/abs/2104.14578)** : Conductivity in the Hubbard model: orbital effects of magnetic field (Hubbard, arXiv)

extension: markdown


text:
The default nginx conf has a high file limit it is suggested to increase the file limit to that value

to do so edit ` /etc/security/limits.conf`, this is the per user value
append the lines
```
* hard nofile <limit>`
* soft nofile <limit>
```

Check that there are no conflicting declarations under /etc/security/limits.d/*.conf, as those files take precedence.

then edit `/etc/sysctl.conf`, this is the system wide value
add or change
`fs.file-max = <value>`
this should be at least 1.5 times the limit used before, 200342 is a default value.

finally edit both `/etc/systemd/system.conf` and `/etc/systemd/user.conf`
under the `[Manager]` section see [systemd-system.conf(5)](https://www.freedesktop.org/software/systemd/man/systemd-system.conf.html) for more
add or uncomment or modify the line
`DefaultLimitNOFILE=<value>` This value is per process and should be as the one used per user, generally speaking

repository: a-h-i/evaluator

repo_name: a-h-i/evaluator


text:
# Nsrlsvr Analysis Plugin

Notes on how to use the nsrlsvr analysis plugin.

## Setting up nsrlsvr

The source of nsrlsvr can be found [here](https://github.com/rjhansen/nsrlsvr)

Follow the [installation instructions](https://github.com/rjhansen/nsrlsvr/blob/master/INSTALL).

## Running nsrlsvr

To run nsrlsvr:

```bash
nsrlsvr -f /fullpath/NSRLFile.txt
```

To test if nsrlsvr is working you'll need [nsrllookup](https://github.com/rjhansen/nsrllookup)

To run nsrllookup against your instance of nsrlsvr:

```bash
echo $MD5 | nsrllookup -s localhost -p 9120 -k
```

Which will return $MD5 if present in NSRLFile.txt and nothing when $MD5 does not present.

## Running the analysis plugin

First run log2timeline to calculate the hashes:

```bash
log2timeline.py --hashers md5 --storage-file timeline.plaso image.raw
```

**Make sure to enable hashers supported by nsrlsvr, which is md5 in this example.**

Next run psort to tag events:

```bash
psort.py --analysis nsrlsvr --nsrlsvr-hash md5 --nsrlsvr-host localhost --nsrlsvr-port 9120 -o null timeline.plaso
```

The last step would be to export a timeline with the tags:

```bash
psort.py -o dynamic --fields datetime,timestamp_desc,source,source_long,message,parser,tag -w timeline.csv timeline.plaso
```

gha_language: Python


text:
# Infor Design System

The Infor Design System is a set of use-case driven design practices, development tools, and support documentation to create a cohesive user experience across all Infor CloudSuite applications.

This repository contains the fundamentals of the Infor Design System, including design tokens, which are design metadata, and basic tools like icons. For more information, see [design.infor.com](https://design.infor.com).

## Getting Started for Designers

To get started, :arrow_down:[download the latest release](https://github.com/infor-design/design-system/releases/latest) :arrow_down: of our IDS Design Kit. In that package, you'll find icons, font files for Source Sans Pro, and our design tokens.

See our [getting started page](https://design.infor.com/guidelines/getting-started-designers) for more information.

## Installing IDS Identity in your project

Part of the Infor Design System is a package of different assets that create the Infor identity. This includes the design tokens, font files, and icons.

Install this into your project with:

```shell
npm install --save-dev ids-identity
```

Then look in `node_modules/ids-identity` for the assets.

## Building Assets Locally

For designers and developers wanting to build these assets locally, see our [developer guide](docs/DEVELOP.md).

## Using Jenkins

- To release the next version, specify major, minor, or patch for RELEASE_INCREMENT, and clear RELEASEIT_FLAGS.
- To update an existing git release/tag, clear RELEASE_INCREMENT, and use these flags for RELEASEIT_FLAGS `--dry-run=false --no-increment --no-npm`. Before doing this, remove the tag/version from github so it gets re-created.

## Local Docker

Create a .env file and populate it. AWS keys are required only for local docker runs.

```bash
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=

NPM_TOKEN=""
GITHUB_ACCESS_TOKEN=
DOCS_API_KEY=

# specify the semantic version target X.X.X
RELEASE_INCREMENT=minor

RELEASEIT_FLAGS="--dry-run=true"
```

Then `make build`.

## Help

For questions and support, please [open an new Issue](https://github.com/infor-design/design-system/issues/new?template=support.md&title=[Support]).

repository: infor-design/design-system

repo_name: infor-design/design-system


text:
# [Fridge Friend](https://codechung.github.io/fridgefriend/)

Find recipes based on ingredients you have in your refrigerator. Learn more about the recipe's ingredients and nutrition facts. Watch how to make the recipe on youtube.

## Step 1: Add ingredients to the page

## Step 2: Find the recipe you're interested in

## Step 3: Watch videos on how to make the recipe

## Technologies used:

HTML

CSS

JavaScript

Jquery

repository: CodeChung/fridgefriend

repo_name: CodeChung/fridgefriend


text:
# Twitter API v2

Strongly typed, full-featured, light, versatile yet powerful Twitter API v1.1 and v2 client for Node.js.

## Highlights

✅ **Ready for v2 and good ol' v1.1 Twitter API**

✅ **Light: No dependencies, 11.7kb minified+gzipped**

✅ **Bundled types for request parameters and responses**

✅ **Streaming support**

✅ **Pagination utils**

✅ **Media upload helpers**

## Why?

Sometimes, you just want to quickly bootstrap an application using the Twitter API.
Even if they're a lot a available librairies on the JavaScript ecosystem, they usually just
provide wrappers around HTTP methods, and some of them are bloated with many dependencies.

`twitter-api-v2` meant to provide full endpoint wrapping, from method name to response data,
using descriptive typings for read/write/DMs rights, request parameters and response payload.

A small feature comparaison with other libs:

| Package        | API version(s) | Response typings | Media helpers | Pagination | Subdependencies |  Size (gzip)  |
| -------------- | -------------- | ---------------- | ------------- | ---------- | --------------- | -------------:|
| twitter-api-v2 | v1.1, v2, labs | ✅               | ✅             | ✅         | 0               | ~11.7 kB      |
| twit           | v1.1           | ❌               | ✅             | ❌         | 51              | ~214.5 kB     |
| twitter        | v1.1           | ❌               | ❌             | ❌         | 50              | ~182.1 kB     |
| twitter-lite   | v1.1, v2       | ❌               | ❌*            | ❌         | 4               | ~5.3 kB       |
| twitter-v2     | v2             | ❌               | ❌             | ❌         | 7               | ~4.5 kB       |

\**No support for `media/upload`, cannot send a `multipart/form-data` encoded-body without tricks*

## Features

Here's the detailed feature list of `twitter-api-v2`:

### Basics:
- Support for v1.1 and **v2 of Twitter API**
- Make signed HTTP requests to Twitter with every Twitter required auth type:
  - classic **OAuth 1.0a** authentification for user-context endpoints
  - **OAuth2 Bearer token** for app-only endpoints
  - **Basic** HTTP Authorization, required for some auth endpoints or Entreprise API
- Helpers for numerous HTTP request methods (`GET`, `POST`, `PUT`, `DELETE` and `PATCH`),
  that handle query string parse & format, automatic body formatting and more
- High-class support for stream endpoints, with easy data consumption and auto-reconnect on stream errors

### Request helpers:
- Automatic paginator for endpoints like user and tweet timelines,
  allowing payload consumption with modern asynchronous iterators until your rate-limit is hit
- Convenient methods for authentication - generate auth links and ask for tokens to your users will be a breeze
- Media upload with API v1.1, including **long video & subtitles support**,  automatic media type detection,
  **chunked upload** and support for **concurrent uploads**
- Dedicated methods that wraps API v1.1 & v2 endpoints, with **typed arguments** and fully **typed responses**
  *(WIP - not all public endpoints are available)*
- Bundled parsing of rate limit headers
- Typed errors, meaningful error messages, error enumerations for both v1.1 and v2

### Type-safe first:
- **Typings for tweet, user, media entities (and more) are bundled in this package!**
- Type-safe wrapping of dedicated methods in 3 right level: *DM*/*Read-write*/*Read-only* (just like Twitter API do!) -
  you can declare a read-only client - you will only see the methods associated with read-only endpoints

And last but not least, fully powered by native `Promise`s.

## How to use

Install it through your favorite package manager:
```bash
yarn add twitter-api-v2
# or
npm i twitter-api-v2
```

Here's is a quick example of usage:

```ts
import TwitterApi from 'twitter-api-v2';

// Instanciate with desired auth type (here's Bearer v2 auth)
const twitterClient = new TwitterApi('<YOUR_APP_USER_TOKEN>');

// Tell typescript it's a readonly app
const roClient = twitterClient.readOnly;

// Play with the built in methods
const user = await roClient.v2.userByUsername('plhery');
await twitterClient.v1.tweet('Hello, this is a test.');
// You can upload media easily!
await twitterClient.v1.uploadMedia('./big-buck-bunny.mp4');

// Or manually call the API
await twitterClient.v2.get('tweets/search/recent', { query: 'nodeJS', max_results: 100 });
const tweets = await twitterClient.get('https://api.twitter.com/2/tweets/search/recent?query=nodeJS&max_results=100');
```

### Basics

You want **to know more about client usage? See [the Basics](./doc/basics.md)**!

### Examples

Wanna see that in action? Jump to [Examples part](./doc/examples.md).

## Authentification

Lost between the different ways to auth inside Twitter API?
Don't know how to implement 3-legged OAuth flow?

See [Authentification part](./doc/auth.md) to know more and have a comprehensive guide a every Twitter authentification process.

## Streaming

APIs dedicated to streaming are available in [Streaming part](./doc/streaming.md).

## Full package API

Each Twitter endpoint > method association is described in details inside [the v1.1 comprehensive documentation](./doc/v1.md)
and [the v2 comprehensive documentation](./doc/v2.md).

gha_language: TypeScript


text:
# ActiveDebianRepository

ActiveDebianRepository Gem is used in [Cpkg-on-rails](https://github.com/virtlab-unibo/cpkg-on-rails)
to handle Debian repositories. Its main purpose is to create debian metapackages
(packages with documents and dependencies but not installable software) and
place it in the right folder under a debian repository.

## Requirements

* ruby 2.0 or greater
* dpkg installed on the system
* debhelper installed on the system

## Installation

Add this line to your application's Gemfile:

    gem 'active_debian_repository'

And then execute:

    $ bundle

## Migration

    rails generate active_debian_repository:migration
    rake db:migrate

## Components

ActiveDebianRepository has the following components:

### ActiveDebianRepository::AptSource

It handles the debian source (Repository, as in
/etc/apt/sources.list) and can be used with
acts_as_apt_source. For example

```ruby
class Archive < ActiveRecord::Base
  has_many :packages
  acts_as_apt_source
end
```

and then, in order to register a Repository that corresponds
to the line `deb http://mi.mirror.garr.it/mirrors/debian/ stable main`
in `/etc/apt/sources.list`, just do

```ruby
# deb http://mi.mirror.garr.it/mirrors/debian/ stable main
source = AptSource.new(uri:          'http://mi.mirror.garr.it/mirrors/debian',
                       distribution: 'stable',
                       component:    'main',
                       arch:         'binary-amd64')
```

where `arch` can be one of `['binary-amd64', 'binary-i386', 'source']`.

Each Source has_many Packages (from ActiveDebianRepository::Package). The database
can be updated with each package in the archive. With the method
self.db_attrbutes you get the correct attributes for database.

```ruby
source = AptSource.new(...)
source.update_db_from_net
```

all `archive.packages` are inserted in database with their
metadata (name, description, version...). The information
is taken from
`source.url`

### ActiveDebianRepository::Package

in your project you use this component adding
`acts_as_debian_package` in your model (< ActiveRecord::Base).

```ruby
class Package < ActiveRecord::Base
  belongs_to :archive
  acts_as_debian_package section:    'vlab',
                         homepage:   'https://www.virtlab.unibo.it/cpkg/',
                         maintainer: 'Unibo Virtlab',
                         email<EMAIL_ADDRESS>end
```

### ActiveDebianRepository::Parser

```ruby
parser = ActiveDebianRepository::Parser.new('/home/tmp/Packages')
parser.each do |package|
  p package
end
```

Takes a file name with the archive index and provides iteration (with each)
for every package in the filename

### ActiveDebianRepository::Equivs

Given a `ActiveDebianRepository::Package` it provides a methods to create the debian
`.deb` file (internally it uses `/usr/bin/dpkg-buildpackage` from `dpkg-dev`).

```ruby
package = ActiveDebianRepository::Package.first
equivs = ActiveDebianRepository::Equivs.new(package, dest_dir)
equivs.create
```

The file is created in `dest_dir` dir and
is named `equivs.package_filename`.

For example, given

```ruby
dest_dir = '/var/www/repo/dists/packages'
package = ActiveDebianRepository::Package.new(name: 'test123', version: '12.8')

```

the file is created as `/var/www/repo/dists/packages/test123_12.8.deb`

### Examples

You can find examples on how to use this gem in the *spec/spec_helper.rb* file.

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

gha_language: Ruby


text:
# PDK

This is a prototype PDK implementation using the Puppet Content Template system

## Features

- Compiled/No Runtime needed
- Configuration instead of Interview/Prompting
- Building block for upstream projects
- Continuous Integration top-level support
- 'No special language knowledge' needed to create a template

The command calls the template engine to create the artifacts on disk based on the specified template and options.

repository: da-ar/pdkgo

repo_name: da-ar/pdkgo


text:
# Spring Boot Thymeleaf

Spring Boot version of [php-samples/todo-list](https://github.com/JahnelGroup/php-samples/tree/master/todo-list).

## Todo List Sample Circut

This application is part of the Todo List sample circut. References to other implementations of a Todo List can be found in [JahnelGroup/challenges/todo-list](https://github.com/JahnelGroup/challenges/tree/master/todo-list).

## Structure

### File Structure

The overall file structure is as follows:

```text
/spring-boot-thymeleaf/
├── src/main
│   └── kotlin/com/jahnelgroup/
│       └── App.kt
│   └── resources
│       └── templates
│           └── *.html
│       └── application.properties
├── Dockerfile
├── build.gradle
└── docker-compose.yml
```

### Database: MySQL

The root password is defined in [.env](./.env) and loaded as an environment variable in the [docker-compose.yml](./docker-compose.yml) file.

```
envrionment:
      MYSQL_ROOT_PASSWORD: "${DB_ROOT_PASSWORD}"
```

The default schema is generated by Hibernate based on the domain modeling.

## Prerequisites

You will need to install [docker](https://docs.docker.com/install/) and [docker-compose](https://docs.docker.com/compose/install).

## Run

Bring up the entire stack with:

```bash
$ docker-compose up -d
```

The application can then be located at [http://localhost:8080](http://localhost:8080).

### Adminer
Validate that the database is up and schema was created with Adminer (previously known as phpMyAdmin). Navigate to [http://localhost:8081](http://localhost:8081) and login:

* System: MySQL
* Server: db
* Username: root
* Password: rootpassword
* Database: todolist

repository: olegxtend/spring-boot-samples

gha_language: Kotlin

repo_name: olegxtend/spring-boot-samples


text:
<!---
  Copyright 2012 Open Planets Foundation

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

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

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

# Facebook Import extension for MediaWiki

A MediaWiki extension to facilitate the transfer of information and resources from Facebook into a wiki. It does this in two ways.
- When users log in using Facebook (via the [Facebook Open Graph Extension](http://www.mediawiki.org/wiki/Extension:Facebook)) they are presented with a form populated with information from their Facebook profile, submission of which populates their User Page with that information.
- A Special Page is created at http://[hostname]/[path]/index.php/Special:FacebookImport to which can be submitted the URL of a photograph on Facebook. Upon submission, the photo is imported into the wiki.

## Dependencies
- Developed using MediaWiki 1.19, untested on other versions.
- Requires the [Facebook Open Graph Extension](http://www.mediawiki.org/wiki/Extension:Facebook).
- The MediaWiki API needs to be enabled.
- Uploads and Copy Uploads need to be enabled in the wiki, and users need to have the upload and upload_by_url permissions, in order to import photos.
- Your Facebook app needs the appropriate permissions to import photos - typically user_photos, and possibly friends_photos.

## Installation
Standard MediaWiki extension installation - place in extensions folder and include in your wiki's LocalSettings.php e.g. <tt>require_once("$IP/extensions/FacebookImport/FacebookImport.php");</tt>.

## Configuration
Firstly, make sure you've got the Facebook Open Graph Extension configured correctly to work with your Facebook application. In order to enable photo imports, you'll need to add a hook to your LocalSettings.php file as shown on the [Facebook Open Graph Extension wiki page](http://www.mediawiki.org/wiki/Extension:Facebook#Facebook_permissions). To allow users to import their own photos (or photos they're tagged in) you'll need to add the 'user_photos' permission. The 'friends_photos' permission is need to allow users to import their friends' photos. These permissions also need to be enabled in your Facebook Application. If only confirmed users can edit your wiki, make sure that email_address permissions is not deselected in the hook.

Configuration options for this extension take the form of two arrays in FacebookImport.php, $wgFbImportOptions and $wgFbConnectionImportOptions. The elements of those arrays are themselves arrays, each with three elements - a boolean value to indicate whether that item should be included in the User Page import form, a string for the label for that input, and a string for the type of input (textfield or textarea).

repository: vicgc/SPRUCE

repo_name: vicgc/SPRUCE


text:
# Perenniporia oviformis var. borneensis Corner, 1989 VARIETY

#### Status
SYNONYM

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

#### Published in
Beih. Nova Hedwigia 96: 108 (1989)

#### Original name
Perenniporia oviformis var. borneensis Corner, 1989

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Polyporales/Polyporaceae/Perenniporia/Perenniporia oviformis/ Syn. Perenniporia oviformis borneensis/README.md

repo_name: mdoering/backbone


text:
# Pilot

> Play the intro music

## Introduction
Welcome to the '' Podcast. The is episode three. And I am your host Paras Nath Chaudhary. In today's episode we are going to talk about ''. To follow up for our upcoming episodes please follow us on Twitter and Facebook @opnchaudhary.

> segue *(if any)*

## Content
* Topic 1
> vocal segue "We are going to talk about ..."
* Topic 2
> Sponsored message *(if any)*

> musical segue *(if any)*
* Topic 3

## Takeaway ( *Call to Action* )

### Closing Remarks:
Well, That's all for today's episode.

### Thanks audience
Thank you for listening.

### What's next
Join us again in our next episode where we will talk about ...

## Outro
You can find us on Twitter and Facebook @opnchaudhary. Please leave us your reviews so that we can improve the show.

> Play the outro music


text:
# trim-fq-nf

[TOC]

The [trim-fq-nf](https://github.com/AndersenLab/trim-fq-nf) workflow performs FASTQ trimming to remove poor quality sequences and technical sequences such as adapters. It should be used with high-coverage genomic DNA. You should not use the trim-fq-nf workflow on low-coverage NIL or RIL data. Recent updates in 2021 also include running a species check on the FASTQ and generating a sample sheet of high-quality, species-confirmed samples for [alignment](https://github.com/AndersenLab/alignment-nf).

# Pipeline overview

```

____           .__                     _____                            _____
_/  |_ _______ |__|  _____           _/ ____\\  ______           ____  _/ ____\\
\\   __\\\\_  __ \\|  | /     \\   ______ \\   __\\  / ____/  ______  /    \\ \\   __\\
 |  |   |  | \\/|  ||  Y Y  \\ /_____/  |  |   < <_|  | /_____/ |   |  \\ |  |
 |__|   |__|   |__||__|_|  /          |__|    \\__   |         |___|  / |__|
                         \\/                      |__|              \\/

    parameters              description                                   Set/Default
    ==========              ===========                                   ========================
    --debug                 Use --debug to indicate debug mode            ${params.debug}
    --fastq_folder          Name of the raw fastq folder                  ${params.fastq_folder}
    --raw_path              Path to raw fastq folder                      ${params.raw_path}
    --processed_path        Path to processed fastq folder (output)       ${params.processed_path}
    --genome_sheet          File with fasta locations for species check   ${params.genome_sheet}
    --out                   Folder name to write results                  ${params.out}
    --subsample_read_count  How many reads to use for species check       ${params.subsample_read_count}

```

![Pipeline-overview](img/trim-fq-nf.drawio.svg)

* You have downloaded FASTQ Data to a subdirectory within a raw directory. For wild isolates this will be `/projects/b1059/data/transfer/raw/<folder_name>`
* FASTQs __must__ end in a `.fq.gz` extension for the pipeline to work.
* You have modified FASTQ names if necessary to add strain names or other identifying information.
* You have installed software-requirements (see below for more info)

## Software requirements

* Nextflow v20.01+ (see the dry guide on Nextflow [here](quest-nextflow.md) or the Nextflow documentation [here](https://www.nextflow.io/docs/latest/getstarted.html)). On QUEST, you can access this version by loading the `nf20` conda environment prior to running the pipeline command:

```
module load python/anaconda3.6
source activate /projects/b1059/software/conda_envs/nf20_env
```

* Currently only runs on Quest with conda environments installed at `/projects/b1059/software/conda_envs/`

!!! Note
    All FASTQs should end with a `_R1_001.fastq.gz` or a `_R2_001.fastq.gz`. You can rename FASTQs using the rename command:

    ```
    rename --dry-run --subst .fq.gz .fastq.gz --subst _1 _R1_001 --subst _2 _R2_001 *.fq.gz
    ```

    The `--dry-run` flag will output how files will be renamed. Review the output and remove
    the flag when you are ready.

### Relevant Docker Images

*Note: Before 20220301, this pipeline was run using existing conda environments on QUEST. However, these have since been migrated to docker imgaes to allow for better control and reproducibility across platforms. If you need to access the conda version, you can always run an old commit with `nextflow run andersenlab/alignment-nf -r 20220216-Release`*

* `andersenlab/trim-fq` ([link](https://hub.docker.com/r/andersenlab/trim-fq)): Docker image is created within this pipeline using GitHub actions. Whenever a change is made to `env/trim-fq.Dockerfile` or `.github/workflows/build_trimfq_docker.yml` GitHub actions will create a new docker image and push if successful
* `andersenlab/multiqc` ([link](https://hub.docker.com/r/andersenlab/multiqc)): Docker image is created within this pipeline using GitHub actions. Whenever a change is made to `env/multiqc.Dockerfile` or `.github/workflows/build_multiqc_docker.yml` GitHub actions will create a new docker image and push if successful

To access these docker images, first load the `singularity` module on QUEST.

```
module load singularity
```

Also, make sure that you add the following code to your `~/.bash_profile`. This line makes sure that any singularity images you download will go to a shared location on `b1059` for other users to take advantage of (without them also having to download the same image).

```
# add singularity cache
export SINGULARITY_CACHEDIR='/projects/b1059/singularity/'
```

# Usage

## Testing the pipeline on QUEST

*This command uses a test dataset*

```
nextflow run andersenlab/trim-fq-nf --debug
```

## Running the pipeline on QUEST

*Note: if you are having issues running Nextflow or need reminders, check out the [Nextflow](quest-nextflow.md) page.*

```
nextflow run andersenlab/trim-fq-nf --fastq_folder <name_of_folder>
```

!!! Important
    The pipeline expects the folder containing raw fastq files to be located at `/projects/b1059/data/transfer/raw/`. And all processed fastq files will be output to `/projects/b1059/data/transfer/processed/`

# Profiles

## -profile standard (Default)

If no profile is designated, the default profile will run both fastq trimming AND species check

## -profile trim_only

Use this profile to only trim fastq files and not perform species check.

## -profile sp_check_only

Use this profile to only run species check and not fastq trimming. This is useful for running species checks on previously trimmed fastqs.

# Parameters

## --debug

You should use `--debug true` for testing/debugging purposes. This will run the debug test set (located in the `test_data/raw` folder).

For example:

```
nextflow run andersenlab/trim-fq-nf --debug -resume
```

Using `--debug` will automatically set the fastq_folder to `test_data/raw/20210406_test1`

## --fastq_folder

This should be the name of the folder containing all fastq files located at `/projects/b1059/data/transfer/raw/`. As long as there are no overlapping file names (be sure to check this first), you can combine multiple pools sequenced at the same time into one larger folder at this step.

### --raw_path (optional)

The path to the `fastq_folder` if not default (`/projects/b1059/data/transfer/raw/`)

### --processed_path (optional)

The path to output folder if not default (`/projects/b1059/data/transfer/processed/`)

### --genome_sheet (optional)

Path to a tsv file listing project IDs for species. Default is located in `bin/genome_sheet.tsv`

### --out (optional)

Name of output folder with results. Default is "processFQ-{fastq_folder}"

### --subsample_read_count (optional)

How many reads to use for species check.  The rest of the output files and reports will be generated in a new folder in the directory in which you ran the nextflow pipeline, labeled by `processFQ-{fastq_folder}`.

__MultiQC__

* `multi_QC/{strain}_{library}_fastp.html` - fastp html report detailing trimming and quality

* `multi_QC/multiqc_report.html` - aggregate multi QC report for all strains pre and post trimming

* `multi_QC/multiqc_data/*.txt or .json` - files used to make previous reports

__Species check__

If a species check is run, the `multiqc_data/multiqc_samtools_stats.txt` will contain the results of reads mapped to each species. Furthermore, several reports and sample sheets will be generated:

* `species_check/species_check_{date}_{library}.html` is an HTML report showing how many strains have issues (not in master sheet, possibly different species, etc.)

* `species_check/{library}_multiple_libraries.tsv` - strains sequenced in multiple libraries

* `species_check/{library}_strains_most_likely_species.tsv` - list of all strains in library labeled by (1) the species in record and (2) most likely species by sequencing

* `species_check/{library}_strains_not_in_master.tsv` - list of strains not found in Robyn's wild isolate master sheets for CE, CB, or CT

* `species_check/{library}_strains_possibly_diff_species.tsv` - list of strains whose species in record does not match the likely species by sequencing

* `species_check/WI_all_{date}.tsv` - copy of all strains (CE, CB, and CT) and species designation in record

* `sample_sheet_{date}_{library}_all_temp.tsv` - temporary sample sheet with all strains for all species combined. DO NOT USE THIS FOR ALIGNMENT.

__Sample sheets__

If a species check is run, the `species_check/sample_sheet` folder will also contain 6 sample sheets to be used for alignment:

* `sample_sheet/sample_sheet_{species}_{date}_ALL.tsv` - sample sheet for `alignment-nf` using ALL strains of a particular species (i.e. c_elegans). This is useful for species we have not performed any alignments for or when we update the reference genome and need to re-align all strains.

* `sample_sheet/sample_sheet_{species}_{date}_NEW.tsv` - sample sheet for `alignment-nf` using all fastq from any library for ONLY strains sequenced in this particular library of a particular species (i.e. c_elegans, RET63). This is useful when the reference genome does not change and there is no need to re-align thousands of strains to save on computational power.

!!! Note
    The "new" sample sheet will still contain old fastq sequenced in a previous pool (i.e. RET55) if that strain was re-sequenced in the current pool (i.e. RET63). After running `alignment-nf`, this will create a new BAM file incorporating all fastq for that strain.

# Data storage

## Backup

Once you have completed the trim-fq-nf pipeline you should backup the **raw** FASTQs. More information on this is available in the [backup](backup.md)

## Poor quality data

If you observe poor quality sequence data you should notify Robyn through the appropriate channels and then remove the data from further analysis.

## Cleanup

If you have triple-checked everything and are satisfied with the results, the original **raw** sequence data can be deleted. The **processed** sequence data (FASTQ files) should be moved to their appropriate location, split by species (`/projects/b1059/data/{species}/WI/fastq/dna/`). The following line can be used to move processed fastq prior to running `alignment-nf`:

```

# change directories into the folder containing the processed fastq files
cd /projects/b1059/data/transfer/processed/20210510_RET63/

# move files one species at a time (might be a more efficient line of code for this, but it works...)
# !!!! make sure to change the file name !!!!!

# file name ~ - ~ CHANGE THIS ~ - ~
file='/projects/b1059/Katie/trim-fq-nf/20210510_RET63/species_check/sample_sheet/sample_sheet_c_tropicalis_20201222a_NEW.tsv'

# species
sp="c_`echo $file | xargs -n1 basename | awk -F[__] '{print $4}'`"

# get list of files to move from file
awk NR\>1 $file > temp.tsv
cat temp.tsv | awk '{print $4}' > files_to_move.txt
cat temp.tsv | awk '{print $5}' >> files_to_move.txt

# move files
cat files_to_move.txt | while read line
do
   mv $line /projects/b1059/data/$sp/WI/fastq/dna/
done

# remove temp file
rm files_to_move.txt
rm temp.tsv

```

!!! Note
    The sample sheets ONLY contain strains that species in record matches most likely species by sequencing. If, after moving all the FASTQ for each species to their proper folder, you have FASTQ remaining, these are likely to be found in `strains_possibly_diff_species.tsv`. You should notify Robyn and Erik about these strains through the appropriate channels and delete the FASTQ or move to another temporary location until it can be re-sequenced.

repository: AndersenLab/dry-guide

repo_name: AndersenLab/dry-guide


text:
# OPC-UA and Calvin

This (small) example demonstrates how to get Calvin to collect data from an
OPC-UA server by subscribing to a collection of parameters.

The parameters are defined for the `data.source` capability in `calvin.conf`
(see also `paramconfig` in the example.)

Format of paramconfig:

```json
{
    "endpoint": "opc.tcp://address:port",
    "namespace": "namespace (name, not id)",
    "paramconfig": {
        "tag": {
            "address": "node_id (without namespace)",
            "info": "N/A"
        }
    },
    "timeout": 10,
    "monitoring_interval": 1000
}
```

Format of data item:

```json
{
    "status": 0,
    "calvints":<PHONE_NUMBER>.580605,
    "sourcets":<PHONE_NUMBER>.950132,
    "value": true,
    "tag": "tag",
    "serverts":<PHONE_NUMBER>.353072,
    "type": "Boolean",
    "id": "node_id (without namespace)"
}
```

Note: This format will likely change.

When data is coming in at a higher speed than it can be processed (e.g. when
there are connection issues) it may be necessary to persist the data to disk
in order to ensure it is not (completely) lost in case of power failure or
spurious crashes/reboots. For this, there is a persistent buffer actor which
will use the `buffer.persistent` capability to store data - see `buffer.calvin`.

Note that there are no guarantees on the ordering of the data.

## Setup

### Installation

Install dependencies using:

    $ pip install -r requirements.txt

## Running

Run the script with the following command:

    $ csruntime --host localhost opcua-subscribe.calvin

repository: olaan/calvin-base

repo_name: olaan/calvin-base


text:
# Updating a Sample Submission Programmatically

The main difference between programmatically creating new samples and updating existing ones
is that the `MODIFY` action should be used instead of the `ADD` action:

```
<SUBMISSION>
     <ACTIONS>
         <ACTION>
             <MODIFY/>
         </ACTION>
    </ACTIONS>
</SUBMISSION>
```

Please note that the new sample XML must either contain the original alias or the
assigned accession number for the correct sample to be updated.

Detailed advice on how to programmatically update samples using XML
including instructions for retrieving previously submitted Sample XMLs can be
found in [Programmatic Submission Options](../../submit/general-guide/programmatic.html).
Sample XMLs can also be manually edited using the
[Webin Portal](../../submit/general-guide/submissions-portal.html).


text:
---
layout: post
title:  "Yocto Build : Useful Commands"
date:   2018-04-22 03:52:38
categories: Tech
hidden: true
tags: [DIY, Coding]
image:
  background: witewall_3.png
---

This month, I was working on Yocto build system to create my own custom linux distribution. Online we can find many tutorials to build an image. but the tutorial on how to create/build/debug custom layer is hard to find. This is sort of help cheatsheet to look uptu for commands.

Clean and Build new Yocto Meta layer :-

>bitbake tool_name  -c do_compile

---------------------------------------------------------------------

You can use a devshell to efficiently debug commands or simply edit packages.

>python3 /home/ubuntu/temp/yocto_build/bitbake/bin/bitbake tool_name -c devshell

---------------------------------------------------------------------
Root FS is present here :-
>./build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs
>./build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs

---------------------------------------------------------------------
[Very imp] For any recipe, you can find the values of any variable by getting an environment file as:-

> bitbake -e netperf > env

In the env file, you can search value of WORKDIR as:

>grep -rin "workdir=" env

---------------------------------------------------------------------
Find the file/modules:-

>find . -name "*tool_name*"

---------------------------------------------------------------------
If the Size is less in df -h :-

>rm -rf /tmp

>bitbake core-image-sato

Note: The output is at

>build/tmp/deploy/images/intel-corei7-64/

---------------------------------------------------------------------
Location of the kernel source:-

>/home/ubuntu/temp/yocto_build/build/tmp/work-shared/intel-corei7-64/kernel-source/

This is the Staging Area:-

>/corei7-64-intel-common-poky-linux/linux-intel-rt/4.9.27+gitAUTOINC+8b40e0ad3a_20d97c347a-r0/linux-corei7-64-intel-common-preempt-rt-build/.

Do this from the Staging Area.

>make mrproper

>make clean

---------------------------------------------------------------------

Add this in local.conf to put the binaries in the rootfs

>IMAGE_INSTALL_append = " tool_name"

---------------------------------------------------------------------

Create the new iso,HDD image for your distro including your layers:-

>bitbake -c cleanall tool_name

>bitbake core-image-sato -c cleanall

>bitbake core-image-sato

---------------------------------------------------------------------

license: ISC


text:
---
# Course title, summary, and position.
linktitle: EECS 281
summary: Notes for EECS 281 at the University of Michigan Winter 2020
weight: 1

# Page metadata.
title: Final Topics
date: "2018-09-09T00:00:00Z"
lastmod: "2018-09-09T00:00:00Z"
draft: false  # Is this a draft? true/false
toc: true  # Show table of contents? true/false
type: docs  # Do not modify.

# Add menu entry to sidebar.
# - name: Declare this menu item as a parent with ID `name`.
# - weight: Position of link in menu.
menu:
  example:
    name: Final Topics
    weight: 1
---

repository: NickHolden/academic-kickstart

repo_name: NickHolden/academic-kickstart


text:
# lightline-hunks
## :warning: this repository was transferred to another owner: [sineto/lightline-hunks](https://github.com/sineto/lightline-hunks).
This plugin provides git hunks and git branch for [lightline](https://github.com/itchyny/lightline.vim).

## Configurations
### Set to lightline status
1. Register the components:
```viml
let g:lightline.component_function = {
  \  'lightline_hunks': 'lightline#hunks#composer',
  \ }
```
2. Add the component to the lightline:
```viml
let g:lightline.active = { 'left': [['lightline_hunks']] }
```

### Global Variables
#### g:lightline#hunks#branch_symbol
Symbol visible to the left of the branch. Default is ` `.

#### g:lightline#hunks#hunk_symbols
Hunk count symbols. Default is `['+', '~', '-']` to `added, changed and deleted` respectivelly.
##### Example:
```viml
let g:lightline#hunks#hunk_symbols = [ 'A:', 'M:', 'R:' ]
```

#### g:lightline#hunks#exclude_filetypes
Prevent certain filetypes from showing Git information. Default is `[]`.
##### Example:
```viml
let g:lightline#hunks#exclude_filetypes = [ 'startify', 'nerdtree', 'vista_kind', 'tagbar' ]
```

#### g:lightline#hunks#only_branch
When set with `1` will shows only branch name and symbol. Default is `0`.
##### Example:
```viml
let g:lightline#hunks#only_branch = 1
```

## License
[MIT License](LICENSE)

repository: sinetoami/lightline-hunks

gha_language: Vim script

repo_name: sinetoami/lightline-hunks


text:
# Changelog

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

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

## [v3.2.0] - 2023-08-14
### Added
- Support for PHP 8.1 and up

### Removed
- Support for PHP below 7.4

## [Earlier Releases]

Releases up to and including v3.1.2 predate this changelog.

repository: dxw/cidr

gha_language: PHP

repo_name: dxw/cidr


text:
## Schwurbler Extension
### A word frequency util in a chrome extension that marks the conspiracy words in red (5 words so far)

Wordy lists all words on the current web page by usage frequency.

###Installation

Drag [wordy-extension.crx](https://github.com/angus-c/wordy-extension/blob/master/wordy-extension.crx) to your chrome extensions page.
I'll probably add it to the store at some point.

###Usage

By default wordy lists every 5+ letter word on the page in frequency order

![alt tag](https://raw.github.com/angus-c/wordy-extension/master/demo1.png)

####Adjusting the minimum word size

Move the slidy bar to set the minimum word size for the search

####Filtering by regular expression

You can also filter the results with a regular expression...

![alt tag](https://raw.github.com/angus-c/wordy-extension/master/demo2.png)

###Testing

##Liste an möglichen Frameworks und HOWTOS für den Topic Modelling Ansatz:
http://mallet.cs.umass.edu/topics.php
https://www.analyticsvidhya.com/blog/2016/08/beginners-guide-to-topic-modeling-in-python/
https://nlp.stanford.edu/software/tmt/tmt-0.4/
http://academicearth.org/?s=machine%20learning

repository: braindef/wordy-extension

repo_name: braindef/wordy-extension


text:
# ExcelCOM
COM wrapper to make Excel Interop more usable

# Requires
* MS Office 2016
* https://github.com/pythonnet/pythonnet

repository: Lord-Evil/ExcelCOM

repo_name: Lord-Evil/ExcelCOM