Screenshot_20230628_121117_BT Email.jpg
Australian racing
- ShaunWhite
- Posts: 9731
- Joined: Sat Sep 03, 2016 3:42 am
You do not have the required permissions to view the files attached to this post.
-
- Posts: 1081
- Joined: Fri Nov 20, 2015 9:38 am
Still seem to be charged 6.5% atm (although rounding can take it higher). Anyone else noticed a difference?
edit - scrub that, maybe rounding is taking it down (as well as up), seem to be paying between 6.7% and 10.2%....
edit - scrub that, maybe rounding is taking it down (as well as up), seem to be paying between 6.7% and 10.2%....
I think SA recently went from 5 to 7%, so it seems you are just seeing rounding errors, I thinksionascaig wrote: ↑Sat Jul 01, 2023 9:01 amStill seem to be charged 6.5% atm (although rounding can take it higher). Anyone else noticed a difference?
edit - scrub that, maybe rounding is taking it down (as well as up), seem to be paying between 6.7% and 10.2%....
-
- Posts: 1081
- Joined: Fri Nov 20, 2015 9:38 am
- ShaunWhite
- Posts: 9731
- Joined: Sat Sep 03, 2016 3:42 am
Was there anything unusual about the racing in Aus (3rd july)? Checking my auto it's only traded Pakenham, and absolutely smashed it. Nothing else, I don't do any NSW anyway but other meetings seemed to happen. Logs seem normal so I'm foxed.
Often on a Monday you will see just NSW * 2, sometimes with a Vic as well. Yesterday was supposed to be Pak+NSW+NSW+QLD but QLD was cancelled.ShaunWhite wrote: ↑Mon Jul 03, 2023 2:32 pmWas there anything unusual about the racing in Aus (3rd july)? Checking my auto it's only traded Pakenham, and absolutely smashed it. Nothing else, I don't do any NSW anyway but other meetings seemed to happen. Logs seem normal so I'm foxed.
- ShaunWhite
- Posts: 9731
- Joined: Sat Sep 03, 2016 3:42 am
That's a good clue. I didn't think to check the results and (i hope) only Corowa(NSW), Muswellbrook(NSW) and Pakenham(VC) ran. and Globe Derby(SA), Charlton(VIC) and Pinjarra(WA) were cancelled?
Sorry, I was only referring to Gallops. The other three meetings you mentioned were harness. They all ran according to plan.ShaunWhite wrote: ↑Tue Jul 04, 2023 1:02 amThat's a good clue. I didn't think to check the results and (i hope) only Corowa(NSW), Muswellbrook(NSW) and Pakenham(VC) ran. and Globe Derby(SA), Charlton(VIC) and Pinjarra(WA) were cancelled?
These might helpShaunWhite wrote: ↑Tue Jul 04, 2023 1:02 amThat's a good clue. I didn't think to check the results and (i hope) only Corowa(NSW), Muswellbrook(NSW) and Pakenham(VC) ran. and Globe Derby(SA), Charlton(VIC) and Pinjarra(WA) were cancelled?
https://www.tab.com.au/racing/meetings/today/R
https://www.tab.com.au/racing/meetings/tomorrow
https://www.tab.com.au/racing/meetings/ ... esterday/H
Add this to the list https://www.wizardofodds.com.au/Anbell wrote: ↑Tue Jul 04, 2023 4:12 amThese might helpShaunWhite wrote: ↑Tue Jul 04, 2023 1:02 amThat's a good clue. I didn't think to check the results and (i hope) only Corowa(NSW), Muswellbrook(NSW) and Pakenham(VC) ran. and Globe Derby(SA), Charlton(VIC) and Pinjarra(WA) were cancelled?
https://www.tab.com.au/racing/meetings/today/R
https://www.tab.com.au/racing/meetings/tomorrow
https://www.tab.com.au/racing/meetings/ ... esterday/H
Pakenham (AUS) 24th Aug - 04:30 R2 1400m Mdn
I had bets matched at 04:34:39 at 1.01 / 1000 (indicating the end of race)
My BA instance thought it was still pre-race market
My log shows the race suspending / turning in-play at 04:35:01
My BA supposedly fetched sensible prices on all runners at 04:34:37 (typical pre-race prices e.g. 6/1 etc., not 1.01/1000)
Does anyone else have a different time for race turning in-play, or experienced similar issues?
...PS I received an error in the log of a different market, around the same time:
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
I had bets matched at 04:34:39 at 1.01 / 1000 (indicating the end of race)
My BA instance thought it was still pre-race market
My log shows the race suspending / turning in-play at 04:35:01
My BA supposedly fetched sensible prices on all runners at 04:34:37 (typical pre-race prices e.g. 6/1 etc., not 1.01/1000)
Does anyone else have a different time for race turning in-play, or experienced similar issues?
...PS I received an error in the log of a different market, around the same time:
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
My bots logs show that that race turned inplay at 04:33:19. No errors.eightbo wrote: ↑Thu Aug 24, 2023 7:35 amPakenham (AUS) 24th Aug - 04:30 R2 1400m Mdn
I had bets matched at 04:34:39 at 1.01 / 1000 (indicating the end of race)
My BA instance thought it was still pre-race market
My log shows the race suspending / turning in-play at 04:35:01
My BA supposedly fetched sensible prices on all runners at 04:34:37 (typical pre-race prices e.g. 6/1 etc., not 1.01/1000)
Does anyone else have a different time for race turning in-play, or experienced similar issues?
...PS I received an error in the log of a different market, around the same time:
24/08/2023 04:34:41: [G_Auto 1] : APING Exception: APING,market id passed is invalid . - 32099|ANGX-0002|BetAngelHelper.APINGErrorData
Last edited by napshnap on Thu Aug 24, 2023 7:52 am, edited 1 time in total.
-
- Posts: 1081
- Joined: Fri Nov 20, 2015 9:38 am
24/08/2023 04:25:00: Market changed to Pakenham (AUS) 24th Aug - 04:30 R2 1400m Mdneightbo wrote: ↑Thu Aug 24, 2023 7:35 amPakenham (AUS) 24th Aug - 04:30 R2 1400m Mdn
I had bets matched at 04:34:39 at 1.01 / 1000 (indicating the end of race)
My BA instance thought it was still pre-race market
My log shows the race suspending / turning in-play at 04:35:01
My BA supposedly fetched sensible prices on all runners at 04:34:37 (typical pre-race prices e.g. 6/1 etc., not 1.01/1000)
Does anyone else have a different time for race turning in-play, or experienced similar issues?
24/08/2023 04:33:18: Market has been suspended
24/08/2023 04:33:19: Market is in-play
24/08/2023 04:33:20: Market has been unsuspended
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 1. Disselation: SP = 2.97
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 2. Kilwinning: SP = 90.681
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 3. Master Of Mischief: SP = 42.35
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 4. Mizen: SP = 23
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 5. Night Ruler: SP = 300
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 8. Gangitano: SP = 1.968
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 9. True Prophet: SP = 110
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 11. Relentless Ruby: SP = 24.794
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 12. Suprendre: SP = 68.782
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 13. Demanding Voyage: SP = 235.596
24/08/2023 04:33:40: [G_Auto 1] : Store Value for 14. Artelimar: SP = 344.86
24/08/2023 04:34:43: Market has been suspended
Thank you, friends!
I assumed that was the case.
It's almost as if my BA instance is freezing for some reason, and upon unfreezing it immediately runs the code using old data (accurate at the initial freeze time).
And my bet(s) fire into an in-play market, BEFORE the guardian realises the market suspended / turned in-play.
My original failsafe condition on bet execute rules of 'Market not in-play' is not working for this situation (can recall similar situation in recent months, too)
Perhaps I'll try adding a condition to check market volume has updated (now) vs. 5s ago and 10s ago as an extra failsafe.
I have a recording of the previous similar situation somewhere but can't track it down right now annoyingly. I have a feeling that volume may have been actively updating and it was just the suspend/in-play that was delayed. Maybe I'm using up too much memory on the windows machine or something... No that's probably not it as the market only had 10 runners which is hardly a lot, and not much else was running at that time vs. what I run in the day time.
Bit of a headscratcher for me this one
I assumed that was the case.
It's almost as if my BA instance is freezing for some reason, and upon unfreezing it immediately runs the code using old data (accurate at the initial freeze time).
And my bet(s) fire into an in-play market, BEFORE the guardian realises the market suspended / turned in-play.
My original failsafe condition on bet execute rules of 'Market not in-play' is not working for this situation (can recall similar situation in recent months, too)
Perhaps I'll try adding a condition to check market volume has updated (now) vs. 5s ago and 10s ago as an extra failsafe.
I have a recording of the previous similar situation somewhere but can't track it down right now annoyingly. I have a feeling that volume may have been actively updating and it was just the suspend/in-play that was delayed. Maybe I'm using up too much memory on the windows machine or something... No that's probably not it as the market only had 10 runners which is hardly a lot, and not much else was running at that time vs. what I run in the day time.
Bit of a headscratcher for me this one
That''s a good move. When I code I always consider the worst scenario and never rely on someone else (like: "Oh this field I get form api will be always correct (like, venue or type/distance) - NOPE!"). Also, double check everything with 1-2 day lag with a fresh mind.
Last edited by napshnap on Thu Aug 24, 2023 9:13 am, edited 1 time in total.