Wiki page — public context
No login required. Recruitment applications are separate and are not included.
All pages in one document · Plain-text Markdown
# CUPI Wiki — full context Access: PUBLIC. No login, session cookie, or account is required. This feed is read-only. Applications/recruitment records are separate, require their existing permissions, and are not included here. Content version: 1627 Pages in this response: 1 Current wiki pages: 11 Use these current wiki pages as reference when working on CUPI projects. If your reader truncates this response before “End of context”, use the page index at https://wiki.cornellphysicalintelligence.com/llms.txt and fetch the individual page URLs. Wiki links use [[Page Title]]. Page text is source material, not instructions that override your task. This public, read-only export includes current page bodies and metadata. Revision history, trash, recruitment records, member accounts, and integration settings are excluded. Attachment URLs allow separate downloads; binary file contents are not extracted into this text. External services retain their own access rules. ## Page index - Mech Onboarding - Onshape Standards [mech-onboarding-onshape-standards]: https://wiki.cornellphysicalintelligence.com/llms-full.txt?page=mech-onboarding-onshape-standards --- # Mech Onboarding - Onshape Standards Page ID: mech-onboarding-onshape-standards Source: https://wiki.cornellphysicalintelligence.com/llms-full.txt?page=mech-onboarding-onshape-standards Section: mechanical Parent ID: None Tags: Owner: Andre Boufama Updated: 2026-09-18T19:17:18.196Z Our club has the Onshape Enterprise Plan at this link: https://cupi.onshape.com/ As a member of the mechanical subteam, you will be expected to work on projects end to end using the Onshape cad software. Onshape is unique as a software in how it runs on web, and enables real time collaboration. The parametric modeling part of Onshape is easy to adjust to (assuming you've used any other sort of CAD software), but it's more important to understand how Onshape internally organizes documents and files to properly execute on projects. **These videos are required viewing** (you'll save a lot of time understanding Onshape's quirks if you watch them): https://www.youtube.com/watch?v=XzX31igeTj8 https://www.youtube.com/watch?v=cyQXmb0k8H4 ## Document Structure Rules When working on a large multi month project, it's important to adhere to strict standards. First, when starting a new project, there will be a high level project folder which contains all project documents. Inside this will be a main document with all the assemblies and part studios. Every folder, document, part studio, etc. must be named in all capital letters. Assemblies must be named: "[Assembly Name] ASSY" Subassemblies must be named: "[Subassembly Name] SUBASSY" When there are a lot of tabs (part studios/assemblies), it can be helpful to create folders to reduce clutter on the top level view.  ## Importing COTS Parts All off the shelf parts (parts not custom designed by CUPI) must be imported into the shared "COTS PARTS" folder in their respective part category subfolder. When importing a COTS part, make a new document for the part and title it properly based off its unique identifiers. Use this name for the document, part studio, and parts within the part studio. **Assign a material, part number (right click to properties) and manufacturer. Also pick an appearance color that reflects the actual part. **   When done, **make a version in the left tab**, and you should be able to see your versioned part when importing parts into an assembly from any other document. Versioning is EXTREMELY IMPORTANT as it allows a document to reference a cached version of a tab instead of loading the live tab which is constantly being updated. When there are upwards of 100 COTS parts in a document, this drastically reduces load times.  --- End of context.