> For the complete documentation index, see [llms.txt](https://documentation.tjhsst.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.tjhsst.edu/machines/hpc-cluster/zoidberg.md).

# Zoidberg

**Zoidberg** is part of the [HPC Cluster](/machines/hpc-cluster.md) in name and location only. It's treated as mostly separate, and can be used outside of [Slurm](/services/cluster/slurm.md). Zoidberg is by far the most powerful HPC node as well. However, it's currently being used to power Ion instead of any cluster workloads.

## Technical Specifications

| **Specification** | Description                           |
| ----------------- | ------------------------------------- |
| **Server Type**   | SuperMicro 1U 4 GPU SuperServer       |
| **CPU**           | Intel(R) Xeon(R) E5-2630 v2 @ 2.60GHz |
| **GPU**           | 4x NVIDIA Tesla K80                   |
| **RAM**           | 64 GB                                 |
| **Hard Disks**    | 2x 250GB RAID 1                       |
| **OS**            | Ubuntu Server 24.04                   |
| **Purchase Date** | 2016                                  |

## Trivia

Zoidberg currently has a [workstation](/services/workstations.md) IP and is plugged into the workstation [VLAN](broken://pages/-LKcfr_D2r_IF1O5iJ30) by means of a long ethernet cable because the networking to the HPC cluster is broken ("it's fine if they can't DHCP" no it friggin isn't "well if they don't have static IPs then they're mis-managed" seriously?? also static IPs didn't seem to work anyway).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.tjhsst.edu/machines/hpc-cluster/zoidberg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.