semvec/pypi-packages huggingface dataset:
squash_matrix_api 1.0.0
Squash Matrix API
Keywords: Swagger

    # Endeavor The squash matrix API enables clubs, players, and regions to own their information, with results being updated weekly. The API information sits ontop of squash matrix australia website [https://squashmatrix.com](https://squashmatrix.com) # API Aside from the documentation provided below, there is also a &#x60;{json:api}&#x60; available and can be accessed in the same manner, with the addition of the accept header &#x60;{accept: application/vnd.api+json}&#x60;. More information about json api can be viewed on their website at [http://jsonapi.org/](http://jsonapi.org/) # Squash Matrix Scrapper There is a ruby SDK for retrieving information from [https://squashmatrix.com](https://squashmatrix.com) which can be found at https://rubygems.org/gems/squash_matrix # SDK&#39;s Please stay posted! Client sdk&#39;s for the following will be provided shortly:    - Javascript   - Java   - Ruby  # Blog Find relevent and interesting media on [wilkosz.com.au](http://wilkosz.com.au) # Contact Join this endeavor and be appart of the community [https://www.facebook.com/squashmatrixapi](https://www.facebook.com/squashmatrixapi) &lt;hr /&gt;  # noqa: E501
greensim 2.3.1
Discrete event simulation toolkit based on greenlets

# greensim: discrete event simulation toolkit

[![CircleCI](https://circleci.com/gh/ElementAI/greensim.svg?style=svg&circle-token=31275ead18a30a28dae9e44069f26a4ea58046f0)](https://circleci.com/gh/ElementAI/greensim)

This is a set of simple tools for modeling and running simulations of discrete
event systems. It is based on the implementation of each independant part of
the system that generates events into a function: these are the simulation's
*processes*. They are then `add()`ed to a `Simulator` object, which
coordinates the timeline over which processes execute. Such functions indicate
what happens at various moments within this process, and using functions
`advance()` and `pause()` (valid only in context of process routines) to
forward the simulation to the next moment.

With processes duly added to the `Simulator` object, the simulation is
launched by calling its method `run()`. The simulation stops, thereby
returning from `run()`, when the simulator runs out of events, or if one of
the processes invokes function `stop()`. The simulation can be resumed by
calling method `run()` over again, and so on.

Take a look at the files in [examples]() subdirectory to get a concrete
understanding.

Reference documentation for classes and tools is available as docstrings.