Cosmos in the Stacks engines

| Type | |
|---|---|
| Authors | Sol McJimsey Opi Gonzales Matthew Simpson |
| Location | Arcata, California, United States |
| Status | Deployed |
| Years | |
| Made | Yes |
| Replicated | No |
| Uses | Education, Inspiration, Aesthetics |
| Map | |
|---|---|
| Location | Arcata, United States |
| Coordinates |
The Gas and Electric engine models were designed for the engines and technology section of the third floor of the Cal Poly Humboldt library. The project acts as an interactive display model of both gas and electric engines using color coordinated parts and lights to lead the user. The project is intended to be an inspirational, engaging, and fun activity for anyone that come across it within the library. It was designed and constructed during the Spring 2025 semester for the Engineering 205: Introduction to Design class.
Background
[edit | edit source]Who what when where why
The basis of this project stems from the Engineering 205: Introduction to Design class. Within Engineering 205 students learn about the design process as well as put it into action with a large scale project. The large scale projects are funded usually form an outside source and act as some sort of instalment or product for the given client. For the 2025 Spring Semester the Engineering 205 class worked with both the Cal Poly Humboldt makerspace as well as the Cal Poly Humboldt Library. The Engines project was in collaboration with the Cal Poly Humboldt Library and their Cosmos in the Stacks Program. The Cosmos in the Stacks is a program ran by the library with the goal to, "explore self-guided interactive exhibits in the library stacks and curate an adventure through all the disciplines in the Library of Congress Classification system" (Cosmos in the Stacks Library Cite). As part of this program the Engine project will be placed on the third floor of the library within the engines section as pictured. The area designated to it includes two cleared out bookshelves as well as the space in between the wall and bookshelf.
***Picture***
The Engines project was selected by Gear No.3, a group of 3 engineering students consisting of Sol McJimsey, Opi Gonzales Padilla, and Matthew Simpson.
Problem statement
[edit | edit source]The objective of this project create a self-guided interactive experience that showcases the gas and electric engines section of the library all while being engaging, interactive, and inspiring to future engineers.
Criteria
[edit | edit source]Include a brief intro to the criteria and then include a table with constraints and weights (0-10 highest).
| Criteria | Description | Weight (1-10) |
|---|---|---|
| Durability | The greater resistance to wear and tear, less intense maintenance, and less risk of breakage are all preferred. | 10 |
| Aesthetics | The visual/spatial design of the project must be simple/approachable, accessible, appealing, and facilitate learning to a broad range of users. | 9 |
| Interactivity | The user(s) must be able to manually engage with the display, in a way that is tactile and/or results in a change that facilitates their learning. | 8 |
| Accuracy of Information | The display must be simplified for understanding of the user, but not at the expense of losing critical details of engines; users who seek to learn more in-depth information should not be misled by the models. | 7 |
| Noise Level | A display with less sound and/or fewer sudden spikes in sound is preferred. | 5 |
| Cost | Cheaper materials/pieces for the display building as well as less labor time required to assemble, are preferred. | 4 |
Prototyping
[edit | edit source]Show examples of the prototyping process including what you learned. A great way to communicate your design your process (and to earn extra points!) is to show your early drawings (by hand and digital), failed attempts and photos of tools, materials and your team (or your hands) as you build this prototype.
- Sample gallery
-
Sample caption text.
-
More sample caption text. This would look better with different images.:)
-
Even more sample caption text.
Final product
[edit | edit source]Describe your final product here with image and labels. Start with the biggest overview first.
Construction
[edit | edit source]A very complete description of how the final project is built. This large section should have lots of pictures. Use the Help:Images#Galleries and probably Template:Steps (e.g. Barrel O' Fun Worm Bin Instructions).
- Sample gallery
-
Sample caption text.
-
More sample caption text. This would look better with different images.:)
-
Even more sample caption text.
Video instructions
[edit | edit source]A good way to display a process is by making a video explaining your process. See Template:Video for information on how to add and annotate videos.
Bill of materials
[edit | edit source]Description of costs, donations, the fact that this is just proposed, etc. For a simple cost table, see Help:Table examples#Cost Table and Template:Bill of materials for two nice formats.
| Item | Amount | Cost per unit | Total |
|---|---|---|---|
| Things — Get at the thing store | 3 | USD 5.75 | USD 17.25 |
| Another thing — 3' x 2', yellow | 1 | USD 150.00 | USD 150.00 |
| Grand total | USD 167.25EUR 143.84 <br />GBP 122.09 <br />CAD 207.39 <br />MXN 3,487.16 <br />INR 12,518.66 <br /> | ||
Operation
[edit | edit source]This is how to operate. It should have a brief introduction. You might want to show images or videos with step-by-step instructions when needed.
Maintenance
[edit | edit source]Introduce this maintenance section. Help ask the questions:
- Are there any needed actions for maintenance?
- How often?
- Who should perform maintenance?
Maintenance schedule
[edit | edit source]This is when to maintain what. Please keep the format the same as it populates the kiosk in CCAT.
- 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
Conclusion
[edit | edit source]Testing results
[edit | edit source]Describe the testing results.
Discussion
[edit | edit source]Discuss the testing results.
Lessons learned
[edit | edit source]Discuss lessons were learned during this project and what you would do different next time.
Next steps
[edit | edit source]Discuss any next steps for the project as it goes on into the future.
Troubleshooting
[edit | edit source]This is only how to troubleshoot basic operation. For complex issues, the solution might just say something like 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 | Etc. |
Team
[edit | edit source]Introduce team and semester in the following format:
- Lonny Grafman
- Emilio Velis
- One bullet for each team member.
References
[edit | edit source]
| Authors | |
|---|---|
| License | CC-BY-SA-4.0 |
| Organizations | Cal Poly Humboldt |
| Cite as | Lonny (2025–2026). "Cosmos in the Stacks engines". Appropedia. Retrieved June 3, 2026. |

