> For the complete documentation index, see [llms.txt](https://docs.hackerfabiitb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackerfabiitb.org/processes/liftoff.md).

# Liftoff

1. 1. Solvent Clean and N2 Dry
      2\. Dehydration Bake
      3\. Cool(room temp)
      4\. Spin Coat 70uL of LOR
      5\. Final Speed - 3000 rpm
      6\. Accel/Decel - 300 rpm/s
      7\. Total Time - 50s(i.e. Time at final speed = 30s)
      8\. Bake 190C for 5 mins
      9\. Cool(room temp)
      10\. Spin Coat 70uL of S1813 PPR
      11\. Final Speed - 4000 rpm
      12\. Accel/Decel - 400 rpm/s
      13\. Total Time - 50s(i.e. Time at final speed = 30s)
      14\. Expose - big checkerboard pattern - 65s
      15\. Develop in MF319 - 60s
      16\. Sputter - 115W for 30 mins
      17\. Remove resist - Acetone/PG remover at 100C for \~5 mins

i think this misses a pre exposure bake we generally do with PPR


---

# 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.hackerfabiitb.org/processes/liftoff.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.