Author Topic: Nightmare with CSV logging  (Read 69 times)

  • All members
  • Posts: 197
  • Karma: +1/-0
Nightmare with CSV logging
« on: Tue, 05 December, 2017, 15:14 »
Hi,

I am here to have another rant about MFP! - I am truly hoping that one of you experienced guys tells me how stupid I am, by doing something that is totally wrong, at which point I will hang my head in shame, and apologise, but, so far, what I have done in my trigger seems to be right....

I am not really sure what the point is in being able to separate out 'selections' and get particular data respective to a selection, and yet, it is not possible to separate out individual conditions for each strategy using that selection.

I have a number of strategies, their names are not important, and for the purposes of the text, I will refer to them as <stratName>, but, today, if you observe the image, I had one of the strategies place a lay bet, and another strategy place 2 lay bets, all on the same selection.

I added to my trigger the following to write to a CSV file...

<stratName>,["sel_name"],[bm_layp],[bm_laya]

which as you know, will produce an entry in the csv file I assign to, as for example

T2RM3_A1A2D1D2WL,"Streaming",5.10,0.53

OK, so, given the above, you can see that the strategy,T2RM3_A1A2D1D2WL, triggers the selection, "Streaming", and places a bet at price 5.10 for £0.53. All good so far....

What is alarming, is that each of my strategies, uses a different sized bank, and consequent different sized stakes are placed on the selection.

MFP is doing its job by getting that right (thankfully!), but, for some reason, the SAME stake is being shown for the selection.

If you look at the images attached, from the actual results statement, you can see that Streaming, has 0.53, 0.30 and  0.30 respectively, yet, when you look at the image of the CSV log, they ALL show 0.53 for the stake...

The logging is really important to me because I also have another CSV file that get produced on the settled market, to indicate the Win/Loss ([sel_place]), and once I get these 2, then I have an application I made, which will then query these csv files and log the results into excel. BUT, I cant do that if the logs are incorrect.

  • Administrator
  • Posts: 5517
  • Karma: +198/-1
  • Gender: Female
*
Re: Nightmare with CSV logging
« Reply #1 on: Tue, 05 December, 2017, 20:18 »
Hello!

Bets are updated every X seconds (either together with the market or once in 3 seconds by default). Therefore, the variable bm_laya does not acquire its value immediately after you have placed a bet: you need to wait for a while before writing that value to the log file, otherwise, naturally, the same (currently matched) value will be recorded to the log file.
Always try your triggers in Test Mode before switching to real money!

You can get a faster response from us if you contact us via FaceBook Messenger.

Присоединяйтесь к нашей официальной группе ВКонтакте!

  • All members
  • Posts: 197
  • Karma: +1/-0
Re: Nightmare with CSV logging
« Reply #2 on: Tue, 05 December, 2017, 20:54 »
OK, thanks for the response Oxa,

I have a refresh of 0.2 in play...

I am not sure how I am going to implement a delay, but I will try and figure out the logic of that.

BUT, just so I am clear, if I have a horse named HorseA, and I have 3 separate triggers that have this as a selection, and if we use tr1, tr2 and tr3...

can I be assured that..
 HorseA triggered by tr1 will have a specific bm_laya
HorseA triggered by tr2 will have a specific bm_laya
HorseA triggered by tr3 will have a specific bm_laya

and at some point LATER, I can reference each of these separate bm_laya's ?

and as per my last post, I should get 3 values, where bm_laya(tr1) = 0.53, bm_laya(tr2) = 0.30 and bm_laya(tr3) = 0.3

is the bm_laya specific to a betID?

I am struggling to believe that is the case, because if it was linked to a specific betID, then I should be able to get it at any point?

Thanks.

  • Administrator
  • Posts: 5517
  • Karma: +198/-1
  • Gender: Female
*
Re: Nightmare with CSV logging
« Reply #3 on: Tue, 05 December, 2017, 21:11 »
Sorry, but bm_laya always returns the amount of the latest matched lay amount. So if you have three triggers that place different bets on the same selection, then at some point later you will still have bm_laya point to the latest value only, not all three of them.

The way out here is to place one bet, wait 0.3 sec (just longer than the refresh interval), then write to the log file. Then place the next bet, wait, write to the log file and so on.
Always try your triggers in Test Mode before switching to real money!

You can get a faster response from us if you contact us via FaceBook Messenger.

Присоединяйтесь к нашей официальной группе ВКонтакте!

  • All members
  • Posts: 197
  • Karma: +1/-0
Re: Nightmare with CSV logging
« Reply #4 on: Wed, 06 December, 2017, 08:42 »
Hi Oxa,

Thanks for the response.

Well, I really don't wish to be rude, but that is pretty poor...

So, my rant is justified. MFP can't give me my basic requirement. I don't understand why a product that can do so much, fails in this basic requirement

I know that a CSV file is produced in the statement folder, after every event is settled, BUT, those logs are not strategy specific, and so, if I have 10 different selections on 10 different strategies, some producing 2 or more bets on the same selection, then I have to manually go through everything in order to be able to log it properly - this is painful and very time consuming. I was hoping that MFP would have been able to handle a little more complexity, but, unfortunately, this means I will just have to stick to basic triggers.

I may have to look at reverse engineering the bets into the specific levels, using the statement CSV file, but this is clumsy, and would have been easier to do if my trigger was able to log a stake amount, accurately against the selection inside my own CSV file.

Disappointing.

Many more complaints, but I am not going to air them here.

Mark.

  • Administrator
  • Posts: 5517
  • Karma: +198/-1
  • Gender: Female
*
Re: Nightmare with CSV logging
« Reply #5 on: Wed, 06 December, 2017, 09:37 »
Fair enough, sorry to hear that, it might be worth to look for alternatives that allow doing what you are looking for.
Always try your triggers in Test Mode before switching to real money!

You can get a faster response from us if you contact us via FaceBook Messenger.

Присоединяйтесь к нашей официальной группе ВКонтакте!

  • All members
  • Posts: 746
  • Karma: +36/-1
Re: Nightmare with CSV logging
« Reply #6 on: Thu, 07 December, 2017, 20:46 »
A lot of users wouldn't consider the subject of your complaint as a basic requirement.  This software is so comprehensive it is difficult to appreciate at times.   Good luck in trying to find an alternative that even approaches what MFP can do.