> For the complete documentation index, see [llms.txt](https://docs.hackerfab.org/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackerfab.org/home/individual-fab-information/carnegie-mellon-university/cmu-updates/matthew-chois-updates/week-7-update.md).
# Week 7 Update
Spring break also added
What was accomplished:
* redesigned original spin coater design to suit Lab automation needs(by removing all mounting needed for LCD and buttons, and minimizing dimensions to fit the assembly)
* designed the syringe liquid handling design CAD on onshape, as well as ordering components for them
* Wrote down the hackerfab midsemester documentation
Roadblocks/issues:
* Finding the right syringe for liquid handling, since the main issue was finding a syringe with the right specifications. We needed our syringe to be made out of PTFE or glass, but a majority of the ones we found were made of polyethylene, which would eventually wear out due to acetone and IPA.
* The measurements for the nozzle of the syringe that we ordered was flawed(2mm is not equivalent to 0.4 inches), so we had to take into account the chance that the nozzle isn't the same measurement as advertised
* The nozzle of the syringe was also not meant for locking syringes(but were still ordered in case we would switch back to plastic syringes), so we would have to potentially find a way to attach a needle onto the tubing from the syringe
* 
TO DOs:
* Debug the lead screw stepper motor we have to calibrate the amount of liquid would needed to coat/clean a chip
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hackerfab.org/home/individual-fab-information/carnegie-mellon-university/cmu-updates/matthew-chois-updates/week-7-update.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
