Weight of money

[Archery1969]

Hi,

Is there any reason why there is no option to store a selections WOM to a stored value ?

Cheers,

[BettingAndBotting]

I was looking for that too. Seems you can only store 'the Money available to Back and/or Lay at a price for each selection'.

[Archery1969]

I was looking for that too. Seems you can only store 'the Money available to Back and/or Lay at a price for each selection'.

Yeah, that means you would have to-do the calculations yourself which will slow it down allot. I have a pretty fast machine but whenever i try to-do any calculations with stored values then my machine basically dies a slow death, all very odd.

[Dallas]

I was looking for that too. Seems you can only store 'the Money available to Back and/or Lay at a price for each selection'.

Yeah, that means you would have to-do the calculations yourself which will slow it down allot. I have a pretty fast machine but whenever i try to-do any calculations with stored values then my machine basically dies a slow death, all very odd.

If you wanted to do the calculation its as follows
Take the total of the money available on the back side divided by the total of the money available on both sides.

e.g. If the back money available is £100 at 2.02, £150 at 2.04 and £175 at 2.06
and the lay money available is £75 at 2.08, £100 at 2.10 and £125 at 2.12.

Then WOM = (£100 + £150 + £175) / (£100 + £150 + £175 + £75 + £100 + £125) = £425 / £725 = 58.6%

You could do this with SV with no delay (once set up disable writing each calculation to the log or it will soon slow down over time)

[Atho55]

If you are just looking to be above or below a threshold value then a SV that returns a 1 when above or 0 when below works. You can then use either the 1 or 0 as the trigger.

When applied to the 1 Click screen it gives an overview of many at the same time.

WOM.jpg

[sniffer66]

I was looking for that too. Seems you can only store 'the Money available to Back and/or Lay at a price for each selection'.

Yeah, that means you would have to-do the calculations yourself which will slow it down allot. I have a pretty fast machine but whenever i try to-do any calculations with stored values then my machine basically dies a slow death, all very odd.

If you wanted to do the calculation its as follows
Take the total of the money available on the back side divided by the total of the money available on both sides.

e.g. If the back money available is £100 at 2.02, £150 at 2.04 and £175 at 2.06
and the lay money available is £75 at 2.08, £100 at 2.10 and £125 at 2.12.

Then WOM = (£100 + £150 + £175) / (£100 + £150 + £175 + £75 + £100 + £125) = £425 / £725 = 58.6%

You could do this with SV with no delay (once set up disable writing each calculation to the log or it will soon slow down over time)

I did just this a few weeks ago as an experiment to see if I could ignore spoofers. I extended the WOM out past 3 places and set it to ignore single values over x%. Need to revisit that again

Writing those to the log really does kill your machine though

[Archery1969]

My reason for the original post was probably not very scientific but:

1. Adding up all the individual WOM's and dividing by the number to get an average Market WOM.
2. If a selections WOM < 33% and the Market WOM > 50% then BTL that selection. Reason being the market is supporting the selection.
3. If a selections WOM > 66% and the Market WOM < 50% then LTB that selection. Reason being the market is opposing the selection.

Not sure but might work ok on say the favourite for nicking a tick or two.

Anyway, will give it a go.

[ShaunWhite]

If you wanted to do the calculation its as follows

That's one way

Market WOM > 50%

I like it but 'Market WoM' has a balance point some way off 50%. Largely due to the fact that the betting world is traditionally full of savvy layers and mug punters.

[Archery1969]

If you wanted to do the calculation its as follows

That's one way

Market WOM > 50%

I like it but 'Market WoM' has a balance point some way off 50%. Largely due to the fact that the betting world is traditionally full of savvy layers and mug punters.

Yeah I realise that Shaun. Just gave it as an example. I would use something allot greater than 50%.

[Stubbo]

How using stored values do you do the division aspect of this calculation....which function of a stored value supports dividing one number by another?