labtrade
A visual tool to support the development of strategies in Quantitative Finance.
Getting Started
Requirements
PyQt5==5.15.6
PyQt5-sip==12.9.0
PyQt5-Qt5==5.15.2
pyqtgraph==0.11.0
pandas==1.1.5
numpy==1.19.5
sklearn==1.0.1
Installation
https://github.com/fab2112/labtrade.git
Features
- Support for develop strategies in Tecnhical analisys / Machine learning / Reinforcement learning
- Future / Spot markets strategies
- Strategy backtest
- Analyse of performance / risk (Equity-curve / Drawndowns / Sharpe-Ratio / Sortino / Calmar)
- Market emulation (stop-loss, stop-gain, maker-fee's)
- Analyse of continue rates in real data
- User-friendly visual for quantitative analysis
Metadata
Release files for labtrade 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| labtrade-1.0.0.tar.gz | 9.3 kB | Without provenance | Details for labtrade-1.0.0.tar.gz |
Release files / labtrade-1.0.0.tar.gz
| Download URL | labtrade-1.0.0.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c95676dcc51ad279a9019458b3540f5bb6abef934bf1957455db839197fbbaff
|
|
BLAKE2b-256 checksum How to use checksums |
8a68182342eae7e44c23113d6eb62d8ca6f93553a2e1d4aececbe190a4d340b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.6.4 pkginfo/1.8.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.8
|
Security for labtrade 1.0.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.