Resources
Use these guides to set up your tools, keep your research records, and prepare your work for review. Start with Git and GitHub, then set up your editor and student site.
Start here
- Learn Git and GitHub basics. Clone a project, save commits, upload changes, and open a pull request.
- Set up VS Code. Install the editor, open a folder, and use the terminal and Git.
- Build your student or internship site. Use
2026studentor2026intern. Clone your repository, change your details, write meeting notes, and publish your updates. - Set up Python. Create a project environment. Learn when to use venv, Conda, or Docker.
Choose a guide
| Guide | What you will do | Check your result |
|---|---|---|
| Git and GitHub basics | Clone, commit, push, and review work with branches and pull requests | Find your commit on GitHub and complete one practice PR |
| Student and internship websites | Clone, edit, preview, and publish your own research site | Open your site and its meeting page |
| VS Code essentials | Open projects, run Python, use Git, and connect to a lab computer | Run a small script with the correct interpreter |
| Python, venv, Conda, and Docker | Set up one environment for each project | Rebuild the environment from a saved file |
| Write with Overleaf | Start a paper, add references, and work with your supervisor | Compile a PDF with working citations |
| Trossen WidowX AI arm | Check the hardware, install the driver, connect, and run a reviewed first move | Complete one clear, controlled movement |
| Find papers and check research venues | Check JCR Q1/Q2 journals and strong conference venues, then record what you read | Bring a short reading list to your meeting |
Use a simple work cycle
- Open the correct project folder.
- Get the latest changes before editing.
- Use a separate Python environment for each project.
- Save your code, settings, and reading notes in clear files.
- Check your changes before you upload them.
- Before a meeting, write your progress, results, questions, and next steps.
Read each guide in order. Stop at a failed check and use its problem-solving section before you continue.
