Giter VIP home page Giter VIP logo

pycausality's People

Contributors

zackeskin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

pycausality's Issues

Separate production and testing versions

Currently PyCausality requires a number of dependencies (e.g. Nose, SciPy) which are in fact only used in testing. It is not uncommon to provide only the functional code when building for PyPi deployment, so consider removing testing-related code if this is not required for core functionality. The problem becomes clear when using PyCausality in non-local environments such as AWS Lambda or mobile, where environment management and storage issues become more difficult.

(Similarly, Matplotlib is required only for one method, so consider separating this out.)

An Error Reported

There was an error reported when I run "TE.nonlinear_TE(pdf_estimator = 'kernel', n_shuffles=100)".

self.add.results({'TE_XY': np.array(TEs)[:,0],

IndexError: too many indices for array

Reproducing Schreiber's article using PyCausality

I'm trying to reproduce Example 3 in Schreiber 2000's seminal article using PyCausality here.

image

I wonder if it is possible at all to reproduce such results with PyCausality and get the same TE numbers to reproduce the figure in question?

add_result() fails if already called

When running TE.nonlinearTE() or TE.linearTE(), if one of these has been called already in the TE object scope, then the add_result() method will fail.

This has been observed using windows but, from memory, is likely also to happen even without applying windowing.

For now, creating two objects (e.g. l_TE and nl_TE) is a simple workaround.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.