# Naming tip racks

**URL:** <https://discuss.pylabrobot.org/t/naming-tip-racks/150>\
**Category:** resources\
**Created:** [February 6, 2025, 9:39pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150 "2025-02-06T21:39:28Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 6, 2025, 9:39pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/1 "2025-02-06T21:39:28Z")

</div>

in [Revising TipRacks](https://discuss.pylabrobot.org/t/revising-tipracks/71) we are discussing how to model tip racks correctly.

in this thread, let’s discuss naming of tip racks. Right now, we have inherited VENUS naming, roughly:

{L,S,H}{T}{F?}

- LSH: low (10), standard (300), high (1000) volume
- T: tip. (vs needle? i don’t think these are used)
- F?: filter or no filter

Let’s adopt a similar naming pattern as the plate naming standard that @CamilloMoschner introduced:

 ![](https://discuss.pylabrobot.org/uploads/default/original/1X/5d85d0194a079fc2b1582b9e7bbe15950b079393.png)

- manufacturer
- tip
- volume
- filter or ‘’
- suffix

example:

- HTF → HamiltonTip1000uLFilter
- HTF\_ULTRAWIDE → HamiltonTip1000uLFilterUltrawide

---

<div class="post-metadata">

**Author:** ![harley](https://discuss.pylabrobot.org/letter_avatar_proxy/v4/letter/h/a698b9/32.png) [@harley](https://discuss.pylabrobot.org/u/harley)\
**Post date:** [February 7, 2025, 11:55pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/2 "2025-02-07T23:55:21Z")

</div>

Agreed!

I had no idea what `HTF` stood for when I started but seeing `TIP_50ul_w_filter` for the 50uL tips made sense to me. I’m all for consistency here

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 8, 2025, 1:26am UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/3 "2025-02-08T01:26:55Z")

</div>

htf wtf

---

<div class="post-metadata">

**Author:** ![naikymen](https://discuss.pylabrobot.org/letter_avatar_proxy/v4/letter/n/51bf81/32.png) [@naikymen](https://discuss.pylabrobot.org/u/naikymen)\
**Post date:** [February 9, 2025, 3:05pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/4 "2025-02-09T15:05:32Z")

</div>

A few bits here:

- There will surely be more manufacturers than letters, and even less letters than would make sense to assign them. Perhaps no letters, or 3 or 4 if its important to people: EPP, HMTN, AXG, TRS, etc.
- What about positive displacement tips?
- Its a shame they used L for Low instead of Large, otherwise S/M/L would have been natural for encoding “size”. I don’t think that 300 uL should be called standard, “Medium” or any other word about intermediate size would be more descriptive.
- What about 5 mL tips? Would that be size X?
- What about larger “tips” like serological pipettes? I guess no one would call them tips although they _are_ just large tips.

I’d suggest something with parts, in this particular order:

- `TIP_[volume][feature flags]_[manufacturer]_[trademark stuff]`
- `feature flags` adds as many letters as features: L for low, F for filter, P for positive displacement, and so on.
  - Example: TIP\_1000F\_HMT → 1000 uL hamilton filter tip.
  - Example: TIP\_300\_EPP → 300 uL eppendorf tip, no extra features.
  - Example: TIP\_20F → any 20 uL tip with a filter.

- In this order the features and manufacturer can be omitted when irrelevant, and the name still make sense.
- I’d avoid poetic terms like “ULTRAWIDE” in a naming convention, unless a generic feature can be abstracted from them (e.g. a W feture flag).
  - Example: TIP\_5000F\_BB\_MEGAKILL → 5000 uL Best Buy MEGAKILL tips.

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 9, 2025, 6:11pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/5 "2025-02-09T18:11:33Z")

</div>

i should have clarified:

- right: we should be using the same 3 letter abbreviation format for manufacturers like we do for plates
- we haven’t used any positive displacement tips in plr yet, i like your suggestion for P
- these (lsh) letters are from venus. i propose moving away from them entirely:
  - large/low/standard is relative
  - it is imprecise
  - venus already uses them, redefining would be awkward
  - the box includes the volume as a number

- just call them 5000uL/5mL?
- have serological pipettes been used in automation 👀

> [@naikymen](#):
>
> L for low, F for filter, P for positive displacement, and so on.

I generally like to use as few acronyms/codes as possible. It is hard to decipher, and doesn’t really save time because everyone uses autocomplete anyway. [“Excessive use of made up acronyms is a significant impediment to communication”](https://www.goodreads.com/quotes/10659232-excessive-use-of-made-up-acronyms-is-a-significant-impediment)

> [@naikymen](#):
>
> - `TIP_[volume][feature flags]_[manufacturer]_[trademark stuff]`

I like this format, but I think keeping the format similar to plates makes more sense

> [@naikymen](#):
>
> I’d avoid poetic terms like “ULTRAWIDE” in a naming convention

That is what Hamilton calls this product. As far as I know, it’s a unique product and definitely a term that people will be searching for given that it’s printed on the box. (volume is printed as numbers, not the l/s/h terms)

---

<div class="post-metadata">

**Author:** ![ben](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/ben/32/41_2.png) [@ben](https://discuss.pylabrobot.org/u/ben)\
**Post date:** [February 9, 2025, 11:32pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/6 "2025-02-09T23:32:04Z")

</div>

> [@rickwierenga](#):
>
> definitely a term that people will be searching for given that it’s printed on the box

we should specify the orifice size of the wide bore (ie 1.2mm or 3.2mm?) to help users understand “ultra” - afaik hamilton sells both

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 10, 2025, 1:17am UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/7 "2025-02-10T01:17:48Z")

</div>

sure, we can include it if it helps people identify the tips

---

<div class="post-metadata">

**Author:** ![CamilloMoschner](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/camillomoschner/32/7_2.png) [@CamilloMoschner](https://discuss.pylabrobot.org/u/CamilloMoschner)\
**Post date:** [February 10, 2025, 8:42pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/8 "2025-02-10T20:42:06Z")

</div>

> [@ben](#):
>
> we should specify the orifice size of the wide bore (ie 1.2mm or 3.2mm?) to help users understand “ultra” - afaik hamilton sells both

Could be a metadata attribute or further documentation inside the docstring maybe?

> [@rickwierenga](#):
>
> I think keeping the format similar to plates makes more sense

I agree, PLR should have as consistent a naming-structure across all `resource`s as possible (I know `Tip` is currently not a subclass of `Resource` but that’s just a matter of time 🙂 )

> [@rickwierenga](#):
>
> [“Excessive use of made up acronyms is a significant impediment to communication”](https://www.goodreads.com/quotes/10659232-excessive-use-of-made-up-acronyms-is-a-significant-impediment)

A quote from a different time… but I completely agree with it: definition function names should not be a riddle to solve but completely self-explanatory (or as close to it as possible).  
The fact that we’re discussing what “S, M, L, F” means for different people is a testament to their ambiguous meaning.

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [September 19, 2025, 5:58pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/9 "2025-09-19T17:58:32Z")

</div>

thanks @CamilloMoschner for making a PR: [Update Hamilton TipRack Names by BioCam · Pull Request #674 · PyLabRobot/pylabrobot · GitHub](https://github.com/PyLabRobot/pylabrobot/pull/674)

---

<div class="post-metadata">

**Author:** ![cwehrhan](https://discuss.pylabrobot.org/letter_avatar_proxy/v4/letter/c/ecccb3/32.png) [@cwehrhan](https://discuss.pylabrobot.org/u/cwehrhan)\
**Post date:** [September 22, 2025, 5:25pm UTC](https://discuss.pylabrobot.org/t/naming-tip-racks/150/10 "2025-09-22T17:25:43Z")

</div>

Thank you for this, even after working with Hamiltons for 7 years I was going crazy trying to remember wtf they call a 300ul tip when writing my scripts hahah. This is sane
