This project has been archived by its maintainers, and is no longer receiving any updates.
A Domain Specific Language for Timeseries Analysis.
–
- Documentation:
- Dowloads:
- Source:
- Keywords:
timeserie, quantitative, finance, statistics, web
–
Timeseries analysis and a timeseries domain specific language written in Python.
Timeserie Object
To create a timeseries object directly:
>>> from dynts import timeseries
>>> ts = timeseries('test')
>>> ts.type
'zoo'
>>> ts.name
'test'
>>> ts
TimeSeries:zoo:test
>>> str(ts)
'test'
DSL
At the core of the library there is a Domain-Specific-Language (DSL) dedicated to timeserie analysis and manipulation. DynTS makes timeserie manipulation easy and fun. This is a simple multiplication:
>>> import dynts
>>> e = dynts.parse('2*GOOG')
>>> e
2.0 * goog
>>> len(e)
2
>>> list(e)
[2.0, goog]
>>> ts = dynts.evaluate(e).unwind()
>>> ts
TimeSeries:zoo:2.0 * goog
>>> len(ts)
251
Requirements
There are several requirements that must be met:
python 2.5 or later. Note that Python 3 series are not supported yet.
numpy for arrays and matrices.
ccy for date and currency manipulation.
Depending on the back-end used, additional dependencies need to be met. For example, there are back-ends depending on the following R packages:
zoo and PerformanceAnlytics for the zoo back-end (currently the default one)
timeSeries for the rmetrics back-end
Installing rpy2 on Linux is straightforward, on windows it requires the python for windows extension library.
Optional Requirements
xlwt to create spreadsheet from timeseries.
simplejson if python version is less then 2.6
matplotlib for plotting.
djpcms for the web.views module.
Running Tests
Form the package directory:
python runtests.py
or, once installed:
from dynts import runtests runtests()
If you are behind a proxy, some tests will fail unless you write a little script which looks like this:
from dynts.conf import settings
from dynts import runtests
settings.proxies['http'] = 'http://your.proxy.com:80'
if __name__ == '__main__':
runtests()
Community
Trying to use an IRC channel #dynts on irc.freenode.net (you can use the webchat at http://webchat.freenode.net/).
If you find a bug or would like to request a feature, please submit an issue.
Metadata
Release files for dynts 0.3.1
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 | |
|---|---|---|---|---|
| dynts-0.3.1.tar.gz | 122.6 kB | Without provenance | Details |
Release files / dynts-0.3.1.tar.gz
| Download URL | dynts-0.3.1.tar.gz |
|---|---|
| Size | 122.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46f8392d8f22d9f1b323e0270518307dfb490f0dd2bc0373a24a291ef7c1dc6d
|
|
BLAKE2b-256 checksum How to use checksums |
76cd35490d58e14dddcd03de4c579c1df1b146a00e3f989d58a921f33774598a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dynts 0.3.1
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.