# (Physical) Environment Requirements A hardware hackathon requires a specialized environment that supports assembly, testing, collaboration, and provides easy access to power and specialized tools. ## Workspace Needs * **Location and Layout:** Host the event in a large, open area, ideally adjacent to a functioning makerspace or fabrication lab. If this is not feasible, utilize engineering classrooms as they often have existing power and tables. * **Judging Accommodation:** If teams use the same tables for building and judging, ensure there are clear pathways and logical organization for judges. This setup also helps maintain general accessibility, and helps accommodate large or fragile projects that are difficult to move. * **Working space:** Provide ample tables and chairs. Ensure dedicated power access for soldering irons, 3D printers, and laptops. Utilize whiteboards, markers, and butcher paper for collaborative brainstorming and design. * **Common area:** Designate one common area (a classroom or lab) for all specialized tools and material checkout. This central hub is the ideal location for hardware checkout, kit pickup, and machined parts retrieval. * **Safety:** Clearly mark areas where hot tools or large machinery are in use. Have makerspace staff or trained volunteers supervise these zones. Display and share all safety protocols ahead of time. ### Specialized Tool Stations Set up dedicated workstations for specialized activities (fabrication, debugging) to improve event logistics and aid cleanup. Ensure these stations are staffed by experienced volunteers. | Station | Essential Tools/Equipment | Tips | | ----------------------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | | Fabrication | 3D printers, laser cutters, hand power tools | Some events delegate printing management to volunteers to allow participants to focus on their projects. | | Assembly/Wiring | Hot glue guns (with ample extra glue sticks), wire snippers, wire strippers, tweezers, electrical tape | Protect table surfaces with plywood or thick butcher paper. | | Testing/Debugging | Multimeters, USB programmers/cables | Offer video references ahead of time; ensure a mentor is stationed nearby. | | Specialized Electronics | Oscilloscopes, benchtop power supplies, soldering irons, logic analyzers | Consider hosting an asynchronous workshop for these tools before the event; ensure a mentor is stationed nearby. | ## Tech Needs Reliable power and connectivity are non-negotiable foundations for any hardware event. ### Power Ensure all venue outlets are functional. Provide sufficient surge-protected power strips at every station. Hardware projects often require separate power supplies for microcontrollers, laptops, chargers, and testing equipment. ### Networking Secure robust, high-speed Wi-Fi and plan for peak usage (uploads, documentation, data streaming). Work with venue infrastructure to ensure the network allows IoT and other devices, as these are often blocked by standard university networks. Encourage hackers to pre-download software drivers and IDEs ahead of time to reduce network load during the event. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.mlh.io/hardware-hackathon-guide/environment-requirements.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.