Morning
is there an easy (and efficient) way to calculate the number of ticks between the back and lay prices for every selection in-play (horse racing), rearm every refresh, using guardian automation...
I guess i could create a formula for each odds step change (ie 1.01 to 2, 2 to 3) etc and assign a value, then subtract one from the other (something similar to how i do it in C# for the increments etc shown below)
Or whether it would be more efficient to assign a store value depending on the odds..ie SV = 1 for odds 1.01...SV = 350 for 1000, then subtract one from another, But I would need a lot of SV's (350) and that doesn't sound efficient?
Any thoughts please for the simplest solution?
Thanks
Peter
EG:
namespace HorseRacing
{
public class BetfairPriceIncrements
{
//Double
public double TicksDown(double odds)
{
double increment = 0;
if (odds < 1.01)
{
return 1.01;
}
else if (odds <= 2.0)
{
increment = 0.01;
}
else if (odds <= 3.0)
{
increment = 0.02;
}
else if (odds <= 4.0)
.
.
.
etc....
Guardian Auto - Ticks
Unfortunately, theirs no easy way to count the number of ticks in guardian.
So it’s going depend on how many ticks your looking to count and your automation skills.
If you can, create a file the same as your code, I think that would be the more professional way to do it. The tricky bit is counting the ticks on crossovers, 2.82 to 3.4 for example.
Im 100% sure it can be done, im just not sure how. That’s why I went for the easier option and choses to use the condition (historic relative odds condition).
You can use this to count the ticks between the prices. The downside is you need a rule for every tick that you want to count.
Here’s a file I created a while back, It counts up to 5 ticks, everything over is 6 Too view the count on the ladder or use the SV, you need to use
SV = TICKS _COUNT for the SELECTION
If you wish to add more ticks, you would just need to follow the sequence down file from rule (TICKS 5).
You may end up with a lot of rules, but the file is optimised, so you won’t have rules needlessly firing.
So it’s going depend on how many ticks your looking to count and your automation skills.
If you can, create a file the same as your code, I think that would be the more professional way to do it. The tricky bit is counting the ticks on crossovers, 2.82 to 3.4 for example.
Im 100% sure it can be done, im just not sure how. That’s why I went for the easier option and choses to use the condition (historic relative odds condition).
You can use this to count the ticks between the prices. The downside is you need a rule for every tick that you want to count.
Here’s a file I created a while back, It counts up to 5 ticks, everything over is 6 Too view the count on the ladder or use the SV, you need to use
SV = TICKS _COUNT for the SELECTION
If you wish to add more ticks, you would just need to follow the sequence down file from rule (TICKS 5).
You may end up with a lot of rules, but the file is optimised, so you won’t have rules needlessly firing.
You do not have the required permissions to view the files attached to this post.