Welcome to EMGFlow

[srlivingstone]

Welcome to the EMGFlow community space. Use this General category for broad conversation: clarifications about workflows, tips, small how-tos, sharing context for planned studies, or anything that doesn’t fit a focused Q&A.

Quick links

• Repo: https://github.com/WiIIson/EMGFlow-Python-Package
• Docs: https://wiiison.github.io/EMGFlow-Python-Package

Where to post

• General (this thread): open topics, usage tips, brief how-tos, context sharing.
• Questions (Q&A): a specific “how do I…?” with code or error messages.
• Ideas/Feature requests: propose new functionality or improvements.
• Issues (GitHub Issues): confirmed bugs or reproducible failures in code.

How to ask for help effectively
Include a minimal, runnable context:

• EMGFlow version, Python version, OS.
• A short data snippet or synthetic example (CSV header + 5–10 rows).
• The exact call you ran and the observed vs. expected result.
• Any error trace in a fenced code block.

Example template:

**Goal:** e.g., notch + bandpass, then extract RMS

**Environment:**
- EMGFlow: 0.x.y
- Python: 3.10
- OS: Windows 11 / macOS 14 / Linux

**Snippet:**

import EMGFlow as emg
pn = emg.make_paths()
fs = 2000
emg.notch_filter_signals(pn["raw"], pn["notch"], ["EMG_zyg"], fs, [(60, 30)])

**Data sample (first lines):**
Time,EMG_zyg
0.0000,0.0023
0.0005,0.0041
...

Observed: …
Expected: …

Contributing
Contributions are welcome via issues or pull requests. Suggestions for features, usage tips, and questions can also be raised here in Discussions. If you plan a larger change, open a short proposal first to gather feedback.

Conduct
Keep discussions professional and specific. Share minimal data needed to reproduce issues. Remove sensitive information before posting.

Maintainer response times
Replies are best-effort. If your question blocks a deadline, state the date and what you have tried so far.

Introduce yourself below and tell us how you plan to use EMGFlow.