Sweep: Write me a python program that plays the output of a .wav file on a Raspberry Pi Pico and add it to the /sweepai directory

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement

Description

This pull request adds a new Python script, play_wav_pico.py, to the /sweepai directory. The script allows for playing the output of a .wav file on a Raspberry Pi Pico.

Summary

• Added play_wav_pico.py to the /sweepai directory
• The script uses the wave and machine modules
• Defines a function play_wav(filename) that plays the .wav file specified by filename
• The play_wav function reads the frames of the .wav file and sets the duty cycle of the PWM pin on the Raspberry Pi Pico accordingly
• Added a main function that calls play_wav with a sample .wav file, audio.wav
• The script is executed when the file is run directly

Fixes #50.

---

🎉 Latest improvements to Sweep:

• We just released a dashboard to track Sweep's progress on your issue in real-time, showing every stage of the process – from search to planning and coding.
• Sweep uses OpenAI's latest Assistant API to plan code changes and modify code! This is 3x faster and significantly more reliable as it allows Sweep to edit code and validate the changes in tight iterations, the same way as a human would.
• Try using the GitHub issues extension to create Sweep issues directly from your editor! GitHub Issues and Pull Requests.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-ai]

Rollback Files For Sweep

• Rollback changes to sweepai/play_wav_pico.py

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: We should use loguru for error logging. If the log is inside an exception, use logger.exception to add tracebacks, where logger is imported from loguru. Use f-strings for string formatting in logger calls.
• Apply: There should be no debug log or print statements in production code.
• Apply: All functions should have parameters and output annotated with type hints. Use list, tuple and dict instead of typing.List, typing.Tuple and typing.dict.
• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the same directory. For example, sweepai/api_test.py tests sweepai/api.py. Use unittest and unittest.mock as required.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.
• Apply: Remove any comments before code that are obvious. For example # this prints hello world; print('hello world').