viziphant
viziphant copied to clipboard
INM-6
Visualization of electrophysiological data from Elephant
# Bug Documentation build with sphinx 5.3.0 (5.2.3 works) does not render math expressions properly, see: See: https://viziphant.readthedocs.io/en/latest/toctree/gpfa/viziphant.gpfa.plot_trajectories_spikeplay.html#viziphant.gpfa.plot_trajectories_spikeplay # Fix In previous Sphinx releases, mathjax was the default html math...
This PR removes the version cap on `sphinxcontrib-bibtex==1.0.0`. Newer versions of `sphinxcontrib-bibtex` require the path to the `.bib` file to be specified in the configuration file for the documentation (conf.py)....
This PR fixes #55 which occurred in relation with api changes in matplotlib 3.6.1. **Bug:** - `gca()` no longer accepts keyword arguments. **Fix:** - replace `gca()` with `add_subplot()`
- the `set-output` command will be disabled 31st May 2023, see: [changelog](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) This is similar to Neo PR [#1191](https://github.com/NeuralEnsemble/python-neo/pull/1191)
Tested with: - python: 3.8.10 - viziphant: 0.2.0 - matplotlib: 3.6.2 The following example: ```python import numpy as np import quantities as pq from elephant.gpfa import GPFA from elephant.spike_train_generation import...
- added two example visualizations to the `README.md`. - see: https://github.com/INM-6/viziphant/tree/feature/examples_readme - [ ] find and add a better example as the second figure
# Spack Package for Viziphant This PR contains a spack package for viziphant. This package is required to integrate viziphant as a component to EBRAINS Phase 3. With this, Viziphant...
This PR is a part of the integration of viziphant in ebrains phase 3. This step sets up a repository mirrored to gitlab.ebrains.eu. (https://gitlab.ebrains.eu/neural-ensemble/viziphant/) The added ebrains.yml will sync this...
Otherwise its easy to pass up this project because the results are unseen.
The plotting of array grids (currently: `array_data module`) should utilize information of the Neo object to plot itself, e.g., which electrode is which channel, etc. Currently this is not well...
