Difference between revisions of "BeagleBoard/GSoC/2021 Proposal/Bela Browser-based Workbench"

From eLinux.org
Jump to: navigation, search
(Bela Browser-based workbench)
Line 10: Line 10:
''Student'': [https://elinux.org/User:Laimonade Leo Aimone]<br>
''Student'': [https://elinux.org/User:Laimonade Leo Aimone]<br>
''Mentors'': (Possibly) Giulio Moro <br>
''Mentors'': (Possibly) Giulio Moro <br>

Revision as of 06:44, 11 April 2021

Bela Browser-based workbench

Student: Leo Aimone
Mentors: (Possibly) Giulio Moro
Wiki: https://elinux.org/BeagleBoard/GSoC/2021_Proposal/Bela_Browser-based_Workbench
Code: N/A


Status: proposal | Project type: cool stuff


Requirements have been completed listed on the ideas page and fill out this template.

About you

IRC: @laimonade:beagleboard.org
Github: N/A
School: Queen Mary University of London
Country: UK
Primary language: French, English, Spanish
Typical work hours: 8AM-11PM GMT
GSoC participation: Excited to participate to 2021 GSoC to have the opportunity to build a tool that can benefit to audio explorers like me.

About your project

Project name: A Bela Browser-based Workbench


The Bela audio cape adds the features of a powerful programmable audio system to the BeagleBoard Black. While the current integrated web-browser oscilloscope is ideal to quickly visualise signals, a few features could be added to make it a full fledge workbench.

This project aims at adding some of the capabilities of a professional oscilloscope to the current Bela web-browser oscilloscope. While the current visualisation of simultaneous signals is supported, the manipulating tools to obtain a desired view are still limited.

The following features will be added:

- More options for scaling the plot in each axis - Adjustable cursors for reading off measurements in time or amplitude - Automatic detection of amplitude or frequency from the plot - More options for triggering - XY mode - Updated visual appearance

In 10-20 sentences, what are you making, for whom, why and with what technologies (programming languages, etc.)? (We are looking for open source SOFTWARE submissions.)


Provide a development timeline with a milestone each of the 11 weeks and any pre-work. (A realistic timeline is critical to our selection process.)

May 17 Proposal accepted or rejected
Jun 07 Pre-work complete, Coding officially begins!
Jun 17 Milestone #1, Introductory YouTube video
June 24 Milestone #2
June 30 Milestone #3
July 12 18:00 UTC Milestone #4, Mentors and students can begin submitting Phase 1 evaluations
July 16 18:00 UTC Phase 1 Evaluation deadline
July 23 Milestone #5
July 30 Milestone #6
Aug 06 Milestone #7
August 10 Milestone #8, Completion YouTube video
August 16 - 26 18:00 UTC Final week: Students submit their final work product and their final mentor evaluation
August 23 - 30 18:00 UTC Mentors submit final student evaluations

Experience and approach

In 5-15 sentences, convince us you will be able to successfully complete your project in the timeline you have described.


What will you do if you get stuck on your project and your mentor isn’t around?


If successfully completed, what will its impact be on the BeagleBoard.org community? Include quotes from BeagleBoard.org community members who can be found on http://beagleboard.org/discuss and http://bbb.io/gsocchat.


Please complete the requirements listed on the ideas page. Provide link to pull request.


Is there anything else we should have asked you?