# Fluid.ampslice~ documentation

**URL:** <https://discourse.flucoma.org/t/fluid-ampslice-documentation/201>\
**Category:** New Ideas\
**Created:** [May 22, 2019, 9:43pm UTC](https://discourse.flucoma.org/t/fluid-ampslice-documentation/201 "2019-05-22T21:43:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [May 23, 2019, 1:00pm UTC](https://discourse.flucoma.org/t/fluid-ampslice-documentation/201/3 "2019-05-23T13:00:00Z")

</div>

Yeah, they make sense (to you in particular) but in looking at a long list of attributes, lots of names like `minslicelength`, `maxslicelength`, etc… it’s difficult to picture what that means.

Even when you demoed the stuff in SC you used a visual example for what each parameter was doing since it’s kind of an abstract concept much of the time.

What I mean with “symbolic meaning” is “what it actually does”, not so much the [naming convention stuff](https://discourse.flucoma.org/t/naming-numing-conventions/202/2). I don’t mind the names here.

---

_[View the full topic](https://discourse.flucoma.org/t/fluid-ampslice-documentation/201)._
