Skip to Main Content

11/07/2023 |

The All-New GPT Conditions: Powered by OpenAI® and ChatGPT

Hello, traders, and welcome to another exciting software update from your friends here at TrendSpider! In this update, we’re pleased to bring the power of OpenAI® and ChatGPT to our scripting functionality across the platform with the release of GPT Conditions. Details after the jump!

Visual Scripting With ChatGPT

TrendSpider now leverages OpenAI’s ChatGPT technology via the all-new ‘GPT Condition’ functionality, which allows traders to create Visual Script conditions by typing simple sentences in plain English instead of building them by clicking through menus. This new functionality can help you put your ideas together without having any prior knowledge of how our Visual Scripting works, and can save you tons of time by not having to click through various drop-down menus to build your conditions! Here are the most important items you need to know to start employing this resourceful functionality today!

Where Are GPT Conditions Used?

GPT Conditions can be utilized in any place where there’s a Visual Script editor. This includes tools like the Strategy Tester, Market Scanner, Multi-Factor Alerts, and more. You can add a GPT Condition by clicking on the ‘add a GPT condition’ link.

Each GPT Condition converts one line of text into one line of a Visual Script. You can verify whether your input has been interpreted correctly by checking the resulting structured condition.

GPT Conditions are powered by a language model, which means that it can do a good job tolerating typos, unclear instructions, or ambiguous input. The best way for you to figure out how to talk to it is to play with it and experiment.

Example Prompts

When it comes to acceptable inputs for GPT Conditions, the range is wide and can not be defined strictly. Experimenting is the best way to get to know the correct ways to prompt. Here’s a list of examples that you can use as a means of getting to know this new functionality.

  • Price touched SMA 50
  • RSI above 70
  • SMA 20 > SMA 50
  • EMA death cross
  • TheStrat is 2u
  • Seq Count is 9
  • High > Previous candle high
  • Price above SMA 200
  • RSI crossed up 70
  • Candle low below Bollinger high
  • Relative Volume above 3.5
  • Rel Vol above 3.5
  • RVOL > 3.5
  • 5 min SMA cross up 10 min BBands Top

Getting Specific with GPT Conditions

You can be as specific as ‘SMA(20) greater than Bollinger Bands(20) Top’ or as brief as ‘SMA(20) > BBands Top’, or even ‘Price cross up SMA’. GPT Condition will do its best to determine your intention and then fill the missing data with reasonable defaults. Pending the result you get back is not exactly what your query intended, you can always manually edit the script to your needs.

Format For Indicator Inputs

Indicator inputs can be recognized in a broad range of formats, but normally INDICATOR ARG1 ARG2 (i.e, sma 20 or bbands 20 4) or INDICATOR(ARG1, ARG2, …) (i.e. ,bbands(20, 3.5)) are safe bets.

Format For Time Frames

It is imperative to be verbose when specifying time frames. This means the GPT Condition prefers inputs like ‘5 min’ to ‘5’, or ‘Daily’ to ‘D’. For example, 5 min SMA 20 cross up daily SMA 200.

What If It Doesn’t Understand You?

If you’re having difficulty getting the desired results from your GPT Condition, consider making your requests more specific and provide more context. Adding additional detail will often help return the desired output.

In essence, the only thing GPT Condition has to work with is what you type in it. For example, ‘High > Previous High’ might not work the way you wanted, but ‘High > Previous Candle High’ will.

Current Limitations

There are currently a few key limitations that you must be aware of. They are as follows:

  • GPT Conditions currently only support using price action and/or the top 150 most popular indicators. Candle patterns, chart patterns, and other types of data supported by Visual Scripts currently can not be interpreted by GPT Conditions.
  • The “Within x% from” operator is not supported
  • The “By at least x%” operator is not supported

As always, we hope you find this new update helpful! Feel free to reach out to us via the ‘Contact Us’ button if you have any questions!