Skip to main content

MISSO

Installation

  • Using pip
pip install misso

Note: In our benchmarks, multi-core version was always faster than the GPU accelerated version. So, we highly recommend installing just the CPU version and using multi-core computation.

  • Installing from source

Usage

from misso import MISSO


For a more detailed usage, check out the Tutorials folder.

Benchmarks

** Benchmarks were run on a machine with the following configuration

CPU:       6 core Intel Core i7-8750H (-MT-MCP-) [12 core with Hyperthreading]
           arch: Skylake rev.10 cache: 9216 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26399
           clock speeds: max: 4100 MHz 1: 2479 MHz 2: 3013 MHz 3: 3211 MHz
           4: 3098 MHz 5: 3362 MHz 6: 3769 MHz 7: 3082 MHz 8: 3290 MHz
           9: 3090 MHz 10: 3141 MHz 11: 3055 MHz 12: 3650 MHz
Graphics:  Card-1: Intel Device 3e9b bus-ID: 00:02.0
           Card-2: NVIDIA Device 1f10 bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 3840x1600@59.99hz
           OpenGL: renderer: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2
           version: 4.6.0 NVIDIA 440.100 Direct Render: Yes

License

TODO

  • Try gradient-based solvers
    • Conjugate-gradient descent
  • Multi-processing for lsmi computation
    • Reduce interprocess overhead
    • Try other methods to parallelize the code
  • Benchmarks
    • Multiprocessing
    • GPU benchmarks
    • Solver Benchmarks
    • Run benchmarks on multiple machines and put in benchmark reports
  • Detailed comparison with graphical Lasso (Tutorials)
    • Toy Example
    • Time Series: Stationary & Dynamic link
    • Comparison of MISSO and GLASSO on indirect coupling link
  • GPU Acceleration
    • Use Cupy for solving
    • Reduce GPU overhead
    • Verify correctness (Still an issue)
    • Try torch for GPU acceleration
  • tqdm for Notebook and Script
  • Pandas DataFrame support
  • Packaging
    • pip package
    • Travis CI
  • Readme

Metadata

Release files for misso 0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for misso 0.1
File Size Uploaded Provenance Actions
misso-0.1.tar.gz 5.9 kB Without provenance Details for misso-0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for misso 0.1
File Interpreter ABI Platform Actions
misso-0.1-py3-none-any.whl Python 3 none any Details for misso-0.1-py3-none-any.whl

Total release size: 13.1 kB

Release files / misso-0.1.tar.gz

Download URL misso-0.1.tar.gz
Size 5.9 kB
Tags Source
SHA-256 checksum
How to use checksums
74bdac98fbd103d1cfaf8b00425d8861295803db9b994fb586d6651288803982
BLAKE2b-256 checksum
How to use checksums
f1fc4c0a18029bf99582b30a849b8f8ca10e8c90328741c6cbbc34ca3cab65ae
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.7.3

Release files / misso-0.1-py3-none-any.whl

Download URL misso-0.1-py3-none-any.whl
Size 7.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
06a16d5d88093b3629206864d2d7941f890e70d8037f02dd2bed5e10d564eb57
BLAKE2b-256 checksum
How to use checksums
38b65deaa20cf806454b77af573983a5ed302b47665cba5b6ca5b2640ec319f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.7.3

Security for misso 0.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.

Release history Release notifications | RSS feed

This release

0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page