New beta links in the first post.
Fixes the betfair chart image download following their unannounced change yesterday.
Also should fix the editing of Value B settings of Historic Stored Values (found by Vovsen)
And adds milliseconds to time stamp on the Export of Stored Values (as requested by jimibt)
New beta version of Bet Angel v1.55.0 - now on general release
amazing -thank you so much.. will download and get started on it nowBet Angel wrote: ↑Fri Jul 24, 2020 12:06 pmNew beta links in the first post.
Fixes the betfair chart image download following their unannounced change yesterday.
Also should fix the editing of Value B settings of Historic Stored Values (found by Vovsen)
And adds milliseconds to time stamp on the Export of Stored Values (as requested by jimibt)
Here is the example on how to set up 'Reverse Greening Custom Columns' on one-click screen, I've also added a 2nd post with how to configure a custom column to 'Green Individual Selections' as you requestedTuco wrote: ↑Thu Jul 23, 2020 2:08 pm...yes, very versatile - look forward to the post tomorrow evening.You could add a 'Green Individual' column using the example i'll post up tomorrow evening.
With the new options in V1.55 you can effectively create a button to green up/close trade on individual selections, the market using the current or any reverse price/s of your choice
Thanks again Dallas.
[ I do think the current Trade Profit P & L closure should still get the 2 box greening option update for 'Green' (individual selection) or 'Green all' (all selections) in a future update ]
viewtopic.php?f=61&t=21159
I clearly need to look at these new History SVs in more detail but I'm not gonna sweat it either way. Personally I'm not interested in the charting applications available within BA so for me the History SVs are just another variant of SV.
I experimented a while ago with what was achievable with complex guardian scripts. Problem I hit was any serious complexity in BAF scripts (including rules that shuffle lots of SVs into other SVs for calculations or for historical comparison) is that it hits performance. So I basically switched completely the other way and decided to keep my Guardian BAF scripts as simple as possible and controlled by SVs which themselves are independently set either manually via a Servant or automatically via the Excel interface. Continuous complex SV calculations are theoretically possible in BAF scripts but in practice performance is affected.
My perception of BAF rules is that they a kind of pseudo-interpreted code. i.e. nowhere near as efficient as actual compiled code or normal runtime interpreted code. If there is an easy way of saving a snapshot of SVs for comparision with a earlier snapshots of SVs via a single fast and efficient BAF rule then that could be very useful and I felt these History SVs were the ideal medium to do that but dont bother on my account if its not easy.
Can I suggest adding an 'Explore Stored Values folder' option to the General section in Guardian's automation tab?
On a related note, I'm not sure how I'm going to extract the data at the end of the day. I tried using VLOOKUP, but to do that requires all the selection names to be in the same column, which isn't currently the case. Any alternative suggestions re data extraction gratefully received.
On a related note, I'm not sure how I'm going to extract the data at the end of the day. I tried using VLOOKUP, but to do that requires all the selection names to be in the same column, which isn't currently the case. Any alternative suggestions re data extraction gratefully received.
i did ask about this option yesterday for much the same reason. the BA dev team said that they'd look into if there was enough support. to me, it sounds like a good option to have both formats present and able to choose between them.weemac wrote: ↑Fri Jul 24, 2020 2:26 pmCan I suggest adding an 'Explore Stored Values folder' option to the General section in Guardian's automation tab?
On a related note, I'm not sure how I'm going to extract the data at the end of the day. I tried using VLOOKUP, but to do that requires all the selection names to be in the same column, which isn't currently the case. Any alternative suggestions re data extraction gratefully received.
see: viewtopic.php?f=46&t=21544#p228331
, meanwhile some other guy is championing some secret feature re: random staking on some other exchange software on YooToob 
You could add a 'Green Individual' column using the example i'll post up tomorrow evening.
With the new options in V1.55 you can effectively create a button to green up/close trade on individual selections, the market using the current or any reverse price/s of your choice
...yes, very versatile - look forward to the post tomorrow evening.
Thanks again Dallas.
[ I do think the current Trade Profit P & L closure should still get the 2 box greening option update for 'Green' (individual selection) or 'Green all' (all selections) in a future update ]
...thank you Dallas - I hadn't seen those two excellent tips and tricks topics which have been very well explained with superb screenshots providing excellent versatility for Trade Profit P & L closure.Here is the example on how to set up 'Reverse Greening Custom Columns' on one-click screen, I've also added a 2nd post with how to configure a custom column to 'Green Individual Selections' as you requested
viewtopic.php?f=61&t=21159
[ I do still think the Trade Profit P & L (current odds) closure column should still get the 2 box greening option update for 'Green' (individual selection) or 'Green all' (all selections) in the next/future update PLUS a Trade Profit P & L (reverse odds) closure column in the next/future update. I'll put it in the suggestions box to see if others would also like that easy peasy column option ]
-
paspuggie48
- Posts: 737
- Joined: Thu Jun 20, 2013 9:22 am
-
paspuggie48
- Posts: 737
- Joined: Thu Jun 20, 2013 9:22 am
Major thanks and great work from the DevOps team..yet againBet Angel wrote: ↑Fri Jul 24, 2020 12:06 pmNew beta links in the first post.
Fixes the betfair chart image download following their unannounced change yesterday.
Also should fix the editing of Value B settings of Historic Stored Values (found by Vovsen)
And adds milliseconds to time stamp on the Export of Stored Values (as requested by jimibt)
