Skyline is a tool used with Atom to profile, visualize, and debug the training performance of PyTorch neural networks.
Note: Skyline is still under active development and should be considered a beta product. Its usage and system requirements are subject to change between versions. See Versioning for more details.
More information about Skyline, including its documentation, can be found on the Skyline website.
Installing Skyline
Skyline works with GPU-based neural networks that are implemented in PyTorch.
To run Skyline, you need:
- A system equipped with an NVIDIA GPU
- PyTorch 1.1.0+
- Python 3.6+
Skyline is installed using pip and the Atom Package Manager (apm).
pip install skyline-cli
apm install skyline
Generally you need both packages to use Skyline. However, depending on your
use case and development setup, you may only need the pip package or you may
need to install the packages on different machines. See the installation
page on the website for detailed
installation instructions tailored to different use cases.
After installing Skyline, you will be able to invoke the command line tool by
running skyline in your shell.
Getting Started
To get started quickly, check out the Getting Started page on the Skyline website.
For more information about using Skyline, including standalone profiling and setting up a remote project, please see the Skyline documentation.
Versioning
Skyline uses semantic versioning. Before the 1.0.0 release, backward compatibility between minor versions will not be guaranteed.
The Skyline command line tool and plugin use independent version numbers. However, it is very likely that minor and major versions of the command line tool and plugin will be released together (and hence share major/minor version numbers).
Generally speaking, the most recent version of the command line tool and plugin will be compatible with each other.
License
Skyline is open source software that is licensed under the Apache 2.0 License.
Please see the LICENSE and NOTICE files in this repository for more
information.
Inside the samples directory, we include code samples from third party
developers that carry their own open source licenses. Please see the
README.md and LICENSE files inside those directories for more information.
Authors
Skyline was written by and is primarily maintained by Geoffrey Yu (gxyu@cs.toronto.edu).
Skyline began as a research project at the University of Toronto in collaboration with Tovi Grossman and Gennady Pekhimenko.
Metadata
Release files for skyline-cli 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| skyline_cli-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for skyline_cli-0.5.0-py3-none-any.whl |
Release files / skyline_cli-0.5.0-py3-none-any.whl
| Download URL | skyline_cli-0.5.0-py3-none-any.whl |
|---|---|
| Size | 63.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39f5241eaa93718d387ab9a35ad38c4f1b9abd20605c5e8463e96d6333335869
|
|
BLAKE2b-256 checksum How to use checksums |
9e37bbc999522aa1023fe97ca074538bfdcb55ffdd34cfa5f277a5f877fa5513
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Security for skyline-cli 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.