(Created page with "{{Template:ENGR215inprogress|CHANGE THIS TO THE DATE OF FINALS WEEk}} ==Abstract== File:Sound Garden Appropedia.png ''The purpose of the Sound Garden is to demonstrate t...") |
|||
| Line 7: | Line 7: | ||
== Background == | == Background == | ||
Ken Pinkerton from the Redwood Discovery Museum in Eureka, CA asked for an exhibit that will educate kids about the physical nature of sound. | |||
== Problem statement and criteria == | == Problem statement and criteria == | ||
Revision as of 07:30, 4 December 2017
Abstract
The purpose of the Sound Garden is to demonstrate to the user the physical relationships between wavelength and sound in a safe, interactive, and understandable way. The Sound Garden satisfies the weighted criteria specified by the client for building a PVC xylophone-like musical exhibit. Designed by The Engineers That Could, The Sound Garden is a musical addition to the Redwood Discovery Museum's collection of wave-related exhibits. The design is a fun, appealing way for museum-goers of all ages learn about the physics of the sound. The Engineers designed the project for their Engineering 215 class at Humboldt State University.
Background
Ken Pinkerton from the Redwood Discovery Museum in Eureka, CA asked for an exhibit that will educate kids about the physical nature of sound.
Problem statement and criteria
Use sortable table.
Description of final project
Photos and descriptions. Use gallery.
Include a how to use and maintain section. See the how to template below.
Costs
Use Help:Table_examples#Cost_Table.
Testing Results
How to build
Use Template:How_to
Maintenance
Introduce this maintenance section.
Schedule
This is when to maintain what.
- Daily
- A daily task
- A daily task
- Weekly
- a weekly task
- a weekly task
- Monthly
- a monthly task
- a monthly task
- Yearly
- a yearly task
- a yearly task
- Every __ years
- task
- task
Instructions
This is how to maintain. The step by step how to template {{How to}} is most likely best for this part.
Troubleshooting
This is only how to troubleshoot basic operation. For complex issues, the solution might just say contact ________. It should be a table in this format:
| Problem | Suggestion |
|---|---|
| Example issue | Example solution or suggestion |
| Does not turn on | Make sure it is plugged in |
| Another issue | Et cetera |
Discussion and next steps
Suggestions for future changes
This is where to lay out suggestions for how to make the project function better in the future.
References
See Help:Footnotes for more. Template:Reflist