semvec/pypi-packages huggingface dataset:
ephysiopy 2.0.66
Add your description here
Requires Python: >=3.13

[![Python package](https://github.com/rhayman/ephysiopy/actions/workflows/python-package.yml/badge.svg)](https://github.com/rhayman/ephysiopy/actions/workflows/python-package.yml)

Synopsis
========

Tools for the analysis of electrophysiological data collected with the Axona or openephys recording systems.

Installation
============

ephysiopy requires python3.7 or greater. The easiest way to install is using pip:

``python3 -m pip install ephysiopy``

or,

``pip3 install ephysiopy``

Or similar.

Documentation
=============

An ongoing lack of effort. There is more or less up-to-date documentation here:

https://rhayman.github.io/ephysiopy/

Code Example
============

Neuropixels / openephys tetrode recordings
------------------------------------------

For openephys-type analysis there are two main entry classes depending on whether you are doing
OpenEphys- or Axona-based analysis. Both classes inherit from the same abstract base
class (TrialInterface) and so share a high degree of overlap in what they can do. Because
of the inheritance structure, the methods you call on each concrete class are the same

```python
from ephysiopy.io.recording import OpenEphysBase
trial = OpenEphysBase("/path/to/top_level")
```

The "/path/to/top_level" bit here means that if your directory hierarchy looks like this:

::

    ├── 2020-03-20_12-40-15
    ├── Record Node 101
    |    └── settings.xml
             experiment1
    |        └── recording1
    |            ├── structure.oebin
    |            ├── sync_messages.txt
    |            ├── continuous
    |            |   └── Neuropix-PXI-107.0
    |            |       └── continuous.dat
    |            └── events
    ├── Record Node 102


Then the "/path/to/top_level" is the folder "2020-03-20_12-40-15"

On insantiation of an OpenEphysBase object the directory structure containing the recording
is traversed and various file locations are noted for later processing of the data in them.

The pos data is loaded by calling the load_pos_data() method:

```python
npx.load_pos_data(ppm=300, jumpmax=100, cm=True)
```

Note
ppm = pixels per metre, used to convert pixel coords to cms.
jumpmax = maximum "jump" in cms for point to be considered "bad" and smoothed over

The same principles apply to the other classes that inherit from TrialInterface (AxonaTrial and OpenEphysNWB)


Plotting data
=============

A mixin class called FigureMaker allows consistent plots, regardless of recording technique. All plotting functions
there begin with "plot" e.g "_rate_map" and return an instance of a matplotlib axis. The plotting functions in turn
call a corresponding "get" function e.g. "get_rate_map" that will return an instance of the BinnedData class 
containing the binned data, the histogram edges, the variable being binned (XY, SPEED etc) and the map type 
(RATE, SPK, POS).
recurring-ical-events 3.8.1
Calculate recurrence times of events, todos, alarms and journals based on icalendar RFC5545.
Requires Python: >=3.8
Keywords: alarm, calendar, events, icalendar, ics, journal, rfc5545, scheduling, todo

Recurring ICal events for Python
================================

.. image:: https://github.com/niccokunzmann/python-recurring-ical-events/actions/workflows/tests.yml/badge.svg
   :target: https://github.com/niccokunzmann/python-recurring-ical-events/actions/workflows/tests.yml
   :alt: GitHub CI build and test status
.. image:: https://badge.fury.io/py/recurring-ical-events.svg
   :target: https://pypi.python.org/pypi/recurring-ical-events
   :alt: Python Package Version on Pypi
.. image:: https://img.shields.io/pypi/dm/recurring-ical-events.svg
   :target: https://pypi.org/project/recurring-ical-events/#files
   :alt: Downloads from Pypi
.. image:: https://img.shields.io/opencollective/all/open-web-calendar?label=support%20on%20open%20collective
   :target: https://opencollective.com/open-web-calendar/
   :alt: Support on Open Collective
.. image:: https://img.shields.io/github/issues/niccokunzmann/python-recurring-ical-events?logo=github&label=issues%20seek%20funding&color=%230062ff
   :target: https://polar.sh/niccokunzmann/python-recurring-ical-events
   :alt: issues seek funding

ICal has some complexity to it:
Events, TODOs, Journal entries and Alarms can be repeated, removed from the feed and edited later on.
This tool takes care of these complexities.

Please have a look here:

- `Documentation`_
- `Changelog`_
- `PyPI package`_
- `GitHub repository`_

.. _Documentation: https://recurring-ical-events.readthedocs.io/
.. _Changelog: https://recurring-ical-events.readthedocs.io/en/latest/changelog.html
.. _PyPI package: https://pypi.org/project/recurring-ical-events/
.. _GitHub repository: https://github.com/niccokunzmann/python-recurring-ical-events