parsing all possible inputs to assign values to the Event class
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 78
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
#31 implements the generation of soundscapes, but prioritizing the randomness of:
```
Event = namedtuple(
"Event",
[
"label",
"source_file",
"source_time",
"event_time",
"event_duration",
"snr",
"role",
"pitch_shift",
"time_stretch",
"event_position",
],
)
```
We need to better define the types of values and functions that we will support for the different values of this class.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #31 and the Event namedtuple definition shown here. Determine the supported types and functions for each Event field; the issue does not name a file or test. Done means the accepted inputs and value behavior are clearly defined for all listed fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100