"Regular Stored Values vs History Lists"

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

I understand that the ability to store values into History Lists, expands the uses of the Stored Values options, and also opens up more possibilities.

Putting all this aside, when it comes to speed/reaction time, and the option to let's say:
1. Setting/Modify a stored value when LTP is greater than another stored value.
2. Setting a signal when LTP of a selection is less than it was X-seconds ago.


Are there situations where using History Lists would/could enable BA to react even faster to such price movements, or even spot otherwise "undetectable" changes?
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

Testing a Stored Value and value held in a History List are as quick as each other.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dallas wrote:
Mon Feb 08, 2021 11:39 am
Testing a Stored Value and value held in a History List are as quick as each other.
Thank you!
Can anyone give me an example where storing the Last Traded Price in a History List might be more beneficial than only as a Stored Value?
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

lotora wrote:
Thu Mar 04, 2021 9:55 am
Dallas wrote:
Mon Feb 08, 2021 11:39 am
Testing a Stored Value and value held in a History List are as quick as each other.
Thank you!
Can anyone give me an example where storing the Last Traded Price in a History List might be more beneficial than only as a Stored Value?
If you want to look up the most recent LTP stored value you'd use a regular Stored Value
If you wanted to look up an historic LTP stored value you'd use a History List
Post Reply

Return to “Bet Angel - Automation”