> 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-5-update.md).

# Week 5 Update

What was accomplished: 

1. Finished designing the peristatic pump, and got the 27:1 gear motor attached to the mechanism
2. Researched syringe pump method as an alternative option in case the peristatic pump wouldn't work. Designed several diagrams, but before reaching CAD phase, found a lot of critical drawbacks that convinced me to use the peristatic pump instead(including linear actuators that require built in encoders)
3. Start working on PPT for the presentation on tuesday

Roadblocks:

1. 3d printed parts for the pump(may be accurate, but should have initially been designed to account for clearance holes for drilling through)
2. Finding the right material for syringe pump(a glass syringe would be optimal to handle all the liquids required, but the larger models do not have built in syringe needles, so a glass syringe + recyclable needle with luer locks was thought out)

TO DOs:

1. Finalize PPT for tuesday
2. Help Advaith move the pump mechanisms into the overall assembly, as well as implementing other components(Im not sure how the spin coater is going to look like)


---

# 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-5-update.md?ask=<question>&goal=<user_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.