Skip to content

Latest commit

 

History

History
132 lines (95 loc) · 6.23 KB

README.md

File metadata and controls

132 lines (95 loc) · 6.23 KB
Raw

About scikit-mobility

Home: https://github.com/scikit-mobility/scikit-mobility

Package license: BSD-3-Clause

Feedstock license: BSD-3-Clause

Summary: A toolbox for analyzing and processing mobility data.

Documentation: https://github.com/scikit-mobility/scikit-mobility

scikit-mobility is a library for human mobility analysis in Python. The library allows to: (i) represent trajectories and mobility flows with proper data structures, TrajDataFrame and FlowDataFrame; (ii) manage and manipulate mobility data of various formats (call detail records, GPS data, data from social media, survey data, etc.); (ii) extract mobility metrics and patterns from data, both at individual and collective level (e.g., length of displacements, characteristic distance, origin-destination matrix, etc.); (iii) generate synthetic individual trajectories using standard mathematical models (random walk models, exploration and preferential return model, etc.); (iv) generate synthetic mobility flows using standard migration models (gravity model, radiation model, etc.); (v) assess the privacy risk associated with a mobility data set.

Current build status

All platforms:

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing scikit-mobility

Installing scikit-mobility from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, scikit-mobility can be installed with:

conda install scikit-mobility

It is possible to list all of the versions of scikit-mobility available on your platform with:

conda search scikit-mobility --channel conda-forge

About conda-forge

Powered by NumFOCUS

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating scikit-mobility-feedstock

If you would like to improve the scikit-mobility recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/scikit-mobility-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers