Help with 'Additional Information' display problems

[JasBarrow]

Looks like i missed a condition out of each of the 'display' rules

If you add the same stored value condition as the 'New Low' rule uses that should resolve it.

Without that it was testing to see if a new low was hit during the last 60 secs and if so triggering and displaying the current vwap (even if its now gone higher).
With that condition it will test its still lower at the time the rule triggers

Sorry Dallas I meant to include a copy of the log. Let me know if it would be of any use.

Thanks again

[Dallas]

Hey Dallas

I've tried it on the last few races and adding the extra condition like you said has fixed that problem but I'm still left with the other issue. I've attached a screengrab from the 18:45 at Leicester. The two numbers on top are the 4 minute and 2 minute VWAP, number on the bottom is the current VWAP. This grab was timed at 00:59 seconds to post and as you can see the 1 minute VWAP was 4.1 but didnt populate. Also the 3 minute VWAP was 4.26 and didnt populate. And on other occasions I still see that some dont populate at any intervals even though the VWAP is falling at each interval.

Each time you answer me I feel I owe you an extra beer!

If you could post up the log i'll see if i can spot anything, it could now just be down to the arm times of the rules need a little tweeaking

If you've got the live VWAP showing in te bottom window that is helpful, if you also have the log open in Guardian then you see that live VWAP drop to a new low during the previous minute you should see it written to the log as a new low (if it doesn't theres an problem them), if it does but the next next 'minute' rule doesn't display it the problem lies in why that rule didn't trigger

[JasBarrow]

Hey Dallas

I've tried it on the last few races and adding the extra condition like you said has fixed that problem but I'm still left with the other issue. I've attached a screengrab from the 18:45 at Leicester. The two numbers on top are the 4 minute and 2 minute VWAP, number on the bottom is the current VWAP. This grab was timed at 00:59 seconds to post and as you can see the 1 minute VWAP was 4.1 but didnt populate. Also the 3 minute VWAP was 4.26 and didnt populate. And on other occasions I still see that some dont populate at any intervals even though the VWAP is falling at each interval.

Each time you answer me I feel I owe you an extra beer!

If you could post up the log i'll see if i can spot anything, it could now just be down to the arm times of the rules need a little tweeaking

If you've got the live VWAP showing in te bottom window that is helpful, if you also have the log open in Guardian then you see that live VWAP drop to a new low during the previous minute you should see it written to the log as a new low (if it doesn't theres an problem them), if it does but the next next 'minute' rule doesn't display it the problem lies in why that rule didn't trigger

Hi Dallas,

Looking at some logs from today I can see why some of the some of the rules aren't triggering. A new low is being set if the value is the same as the last second, as you can see from one of the attached images. Giga White has the same value for 3 seconds straight but it gets counted as a new low. This is having a knock on effect with the rule maxing out at 100 sooner than it should and some of the later rules not triggering for that reason. That's easy to fix by increasing the number of times we allow the rule to trigger but it doesn't explain why an identical value is triggering a new signal.

Also in some cases the 4 minute rule isn't triggering even if the value is less than the initial VWAP stored at 5 minutes. The attached images show Jamacho's VWAP at 5mins, 4mins and 3 mins. Even though its less at 4 and 3 mins you can see on the additional info image it only appears at 3 minutes and not 4.

I'm having trouble attaching the entire log from the race that corresponds to the image I posted yesterday, forum wont let me attach a word or notepad document. You might not need it now but if you do let me know the best way to attach it.

[Dallas]

The 100 triggers was just a random number I put in to begin the test and never changed it, once you revert back to you own timing that would be more than enough, so if that needs increasing for now just do it.

Just as a test try setting the rearm for every 2 seconds and see if that makes any difference

[JasBarrow]

The 100 triggers was just a random number I put in to begin the test and never changed it, once you revert back to you own timing that would be more than enough, so if that needs increasing for now just do it.

Just as a test try setting the rearm for every 2 seconds and see if that makes any difference

Hi Dallas,

Like you say the 100 triggers isn't a big deal as that's easy to change.

I've been playing around with it today but its still very random. The new signal seems to be firing ok (except when it fires for a value the same as the previous) when a new low happens but like the Jamacho images I posted in the last message its very random whether or not that shows in the additional info section on the ladder. I can't make much sense of it!

[Dallas]

The 100 triggers was just a random number I put in to begin the test and never changed it, once you revert back to you own timing that would be more than enough, so if that needs increasing for now just do it.

Just as a test try setting the rearm for every 2 seconds and see if that makes any difference

Hi Dallas,

Like you say the 100 triggers isn't a big deal as that's easy to change.

I've been playing around with it today but its still very random. The new signal seems to be firing ok (except when it fires for a value the same as the previous) when a new low happens but like the Jamacho images I posted in the last message its very random whether or not that shows in the additional info section on the ladder. I can't make much sense of it!

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

[JasBarrow]

The 100 triggers was just a random number I put in to begin the test and never changed it, once you revert back to you own timing that would be more than enough, so if that needs increasing for now just do it.

Just as a test try setting the rearm for every 2 seconds and see if that makes any difference

Hi Dallas,

Like you say the 100 triggers isn't a big deal as that's easy to change.

I've been playing around with it today but its still very random. The new signal seems to be firing ok (except when it fires for a value the same as the previous) when a new low happens but like the Jamacho images I posted in the last message its very random whether or not that shows in the additional info section on the ladder. I can't make much sense of it!

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

The 100 triggers was just a random number I put in to begin the test and never changed it, once you revert back to you own timing that would be more than enough, so if that needs increasing for now just do it.

Just as a test try setting the rearm for every 2 seconds and see if that makes any difference

Hi Dallas,

Like you say the 100 triggers isn't a big deal as that's easy to change.

I've been playing around with it today but its still very random. The new signal seems to be firing ok (except when it fires for a value the same as the previous) when a new low happens but like the Jamacho images I posted in the last message its very random whether or not that shows in the additional info section on the ladder. I can't make much sense of it!

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

HI Dallas that would be great I know you're busy.

Yeah I changed the re-arm on the New Low rule to 2 seconds. On the runner called Buffer Zone it worked perfectly, the VWAP dropped every minute and was triggered properly. On other runners it didnt always trigger though, in this race Urban Beat's VWAP was lower at 3 mins than at 4 but it didnt trigger as you can see from that part of the log but it did trigger at 1 min. 3 other runners had a lower VWAP at 2 mins but none triggered, and at 1 minute Woody Creek triggered and that was one that was lower at 2 mins but didnt trigger.

This was just one race, it repeated across several other races too. LIke I said it seems very random as to when it triggers and when it doesnt. Also the same problem of new lows being triggered when the values were the same were still happening.

[JasBarrow]

......

[JasBarrow]

.....

[JasBarrow]

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

Hi Dallas,

Did you get a chance to take a look a this?

I know you're a busy man so there's no sweat if you didn't

[Dallas]

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

Hi Dallas,

Did you get a chance to take a look a this?

I know you're a busy man so there's no sweat if you didn't

I had a look through the file earlier and couldn't see anything wrong with it or any obvious reason for it not working, but i'll test it fully by running it on some markets tomorrow and let you know

[JasBarrow]

Have you changed the re-arm time to 2secs?

I should have some spare time on Sunday so will take a closer look then but if you can confirm or post some screenshot when using a 2sec re-arm that would be useful

Hi Dallas,

Did you get a chance to take a look a this?

I know you're a busy man so there's no sweat if you didn't

I had a look through the file earlier and couldn't see anything wrong with it or any obvious reason for it not working, but i'll test it fully by running it on some markets tomorrow and let you know

Thanks Dallas, really appreciate it

[Dallas]

Hi Dallas,

Did you get a chance to take a look a this?

I know you're a busy man so there's no sweat if you didn't

I had a look through the file earlier and couldn't see anything wrong with it or any obvious reason for it not working, but i'll test it fully by running it on some markets tomorrow and let you know

Thanks Dallas, really appreciate it

OK, i've found were the problem is.

Once you have a VWAP at a minute the next will only store if its been lower during the last 60secs and still is lower at that next minute - this part works fine
But if its hit a new low from the previous minute then goes up slightly again (but not higher than the previous minute) its not triggering - because although its lower than the previous minute its now not the lowest its been during that last 60 secs.

It can of course be fixed but will require a bit of playing around to find the best way, i should have some more time later this week but thought i'd let you know where the problem is and what needs to be resolved in case you wanted to have a play yourself in the mean time

[JasBarrow]

I had a look through the file earlier and couldn't see anything wrong with it or any obvious reason for it not working, but i'll test it fully by running it on some markets tomorrow and let you know

Thanks Dallas, really appreciate it

OK, i've found were the problem is.

Once you have a VWAP at a minute the next will only store if its been lower during the last 60secs and still is lower at that next minute - this part works fine
But if its hit a new low from the previous minute then goes up slightly again (but not higher than the previous minute) its not triggering - because although its lower than the previous minute its now not the lowest its been during that last 60 secs.

It can of course be fixed but will require a bit of playing around to find the best way, i should have some more time later this week but thought i'd let you know where the problem is and what needs to be resolved in case you wanted to have a play yourself in the mean time

Deeper down the rabbit hole we go!

I'll have a peek at it this evening and spend some proper time looking at it tomorrow, I'm sure we'll get there between us (90% you and 10% me)