> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark/spikes/spike-input-fields.md).

# Spike Input Fields

## Spike Name

To change the name double click in the **Name** column give it a new name and then press `enter` or `tab` to save it.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-b2eca1622302550c5f3ab532142ae4c19fcdb92c%2FEdit%20Spike%20Name.gif?alt=media)

## Spike Type

To change the type double click in the **Type** column and select the desired type then press `enter` or `tab` to save it.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-2c4effd33b03f13d5f3f0437cc70530cabcc35f3%2FChange%20Spike%20To%20Incremental.gif?alt=media)

#### Useful for all types of movement (turntables, winches, lifts, etc.)

* [Simple](/docs/spikemark/spikes/simple.md) - The classic spike that you know and love. Give it a name. Give it a position. Give it a Go!
  * Uses only the [Spike Value](#spike-value).
* [Incremental](/docs/spikemark/spikes/incremental.md) - Increase or decrease the current position by a specific number.
  * Uses only the [Spike Factor](#spike-factor).

#### Useful for turntables

* [Nearest Multiple](/docs/spikemark/spikes/nearest-multiple.md) - Move forward (clockwise) or reverse (counterclockwise) to the nearest multiple of 0 to 359.
* [Nearest Forward Multiple](/docs/spikemark/spikes/nearest-forward-multiple.md) - Move only forward (clockwise) to the nearest multiple of your Spike Factor and Offset.
* [Nearest Reverse Multiple](/docs/spikemark/spikes/nearest-reverse-multiple.md) - Move only reverse (counterclockwise) to the nearest multiple of your Spike Factor and Offset.

## Spike Value

The Spike Value is used only for **Simple Cues** and can be any number [between the Minimum Reverse and Maximum Forward values.](/docs/spikemark/position-scale/limits/setting-soft-limits.md) If you know exactly where your unit wants to travel, put that location here.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-8253b8980d23ebf549fe46e422911a507f4a4278%2FEdit%20Spike%20Value.gif?alt=media)

## Spike Factor

The Spike Factor is essentially the number of different physical locations a unit can be moved to. It is really only relevant for turntables and treadmills, or other machines that can have continuous motion in a given direction.

For example, a turntable only has 360 degrees of travel before it is back to it's original position. A treadmill that has a matching paint pattern every 2' could use a 24" factor so that it would always match the paint.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-f352a9862ba96a0ee916e809fbb3656f1830260b%2FEdit%20NM%20Factor.gif?alt=media)

## Spike Offset

Spike Offset is the location away from the origin.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-9712677d9f2be3c560271a6aeb9ac4bfaabd242e%2FEdit%20NRM%20Spike%20Offset.gif?alt=media)


---

# 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.creativeconners.com/docs/spikemark/spikes/spike-input-fields.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.