semvec/pypi-packages huggingface dataset:
Optical-Flow-Gunnar-Farneback 3.0
Calculates the optical flow according to Gunnar-Farneback

# Optical Flow

Allows, based on the calculation of the Gunnar-Farneback optical flow, to observe the movement of objects within the spot. The result is divided into the total moving pixels, the movement of the pixels up, right, down and left and the speed with which the pixels move between two frames.   

## Installation

Run

```shell
pip install Optical-Flow-Gunnar-Farneback==3.0
```

## Usage

Import and run optical_flow

```python
from optical_flow import optical_flow

of = optical_flow.get_OF(scaling, inputPath, outputPath, information_saved))
of = optical_flow.get_OF(0.3, "W1_01_eon.mp4", '/Results/', 1) #An example of how function is called 
#Scaling float between 0.0 and 1.0; inputPath = str; outputPath = str; information_saved between 0.1 and max FPS)
of
# [(VideoDuration = 1.04, movedPixel = 0.662733593216252, upMovement = 0.24390145882731182, rightMovement = 0.4105051641683077, 
# downMovement = 0.16341277177189245, leftMovement = 0.17587911425471206, medianVelocity = 3.0)...]

# The length of the result list depends on the parameter information_saved.  
```

## Ideas

The **Scaling** value is a factor that determines what percentage of the spot is viewed. With a value of 0.3, starting from the center of the video, 30 percent of the video is used to calculate the optical flow.  
The **Input Path** describes the video to be used for the Optical Flow calculation.  
The calculated video of the optical flow is stored under the **Output Path**.   
The **Information Saved** value specifies how often information is saved. This function has been integrated due to the time-consuming time required. With a value of 1, the data is calculated 1x per second. If the FPS value of the video is used (e.g. FPS = 25), the data is saved every frame. 

## Maintainer

* [Andreas Bloch](mailto:andreas.bloch@mediengruppe-rtl.de)
plover-minimal-english-stenotype 1.1.0
Plover English stenotype system plug-in with no automatic unfolding of orthography rules
Keywords: plover plover_plugin

# Minimal English Stenotype

> Plover English stenotype system plug-in with no automatic unfolding of orthography rules

One normally helpful feature of plover is it's ability to automatically unfold certain suffixes from a stroke. 
This allows plover to recognise more condensed strokes for words that don't exist in the dictionary.

For example, if plover had a dictionary containing only the following entries:
``` json
"CAT" : "cat",
"-G" : "{^ing}",
```

One could stoke the following:
- `KAT` -> "cat"
- `KAT/G` -> "catting" using normal plover orthography rules for suffixes
- `KAGT` -> "catting" using plover automatic unfolding orthography rules

This final method may not be wanted, especially when using plover with other theories such as Magnum or Phoenix, as it can lead to output that is unrelated to what is expected and does not have an entry.
This can make finding unassigned brief strokes more difficult, as you would have to search specifically through the dictionary rather than seeing untranslated raw steno output.
Additionally, this can trip up the creation of briefs, especially in briefs heavy theories as they may not follow the same ideas that plover does.

This plug-in removes this automatic unfolding orthography from plover, allowing it to exactly follow entries specified in dictionary. 

## Installation

Install through the Plover Plugins Manager.