Bug?

Scenario is running MFpro 7 w Excel.
I connect and import 300 horses.
Then I decide I don't want to bet on half of them. So I paste in 150 horses over the top of the 300 cells and import cells with 'overwrite cells selected'. Msg reads 150 horses imported successfully.

Now I walk away and come back in the evening.

What happens next?
MFPro starts and remembers the first 300 horses and still backs them even though I ticked overwrite cells???

Why does this occur?


   

You have to delete all markets and then add them again.
When you import all of selections are switched off except the imported ones. So when you import less selections they are not reset.

I think that the wording should be changed or the architecture of the program.
The tick box says 'clear previously imported cells' this tells me my previously imported selections WILL be cleared.

As you state, this is not the case.

Although a rare event this can be very dangerous.

Example:
I imported many more selections than I should have, in error. I then replaced the selections with the correct ones and started wagering. After importing with the condition 'clear previously imported selections'.....??

I watched as many horses were matched that I had not imported but did import initially. This needs to be corrected or a new clear warning re written.
   

Sorry, missed the "Excel" and answered about "Import selections for auto-trading". Asking Oxa to answer.

Hi londolozi,

I have investigated into this issue and found that the way this setting - "Clear previously imported cells" - works is as follows.

When you specify the range of selections and their custom cells, the program looks for them in the markets added to "My Markets". If it find a selection with a specified name, it clears all cells that have been previously imported for that selection.

Which of course means that if you are trying to load a totally different set of selections, this will have no impact over the existing ones.

By the way, here is a quotation from the manual:

The box "Clear previously imported cells" will delete all cells that were previously assigned to the selections that you are trying to import.

So technically this is not a bug.

I now admit that the wording and the functionality of this setting is ambiguous and may mislead users. I do agree that a more straightforward behaviour would be just clearing all previously imported cells for all markets and selections whatsoever.

Thanks Oxa.
It is only a minor issue but I think a reasonable person would assume any previously assigned cells (horses) will be cleared.

I am aware of the functionality and hopefully know one else gets caught out.

I hope you follow up with an upgrade that "clears all previous cells"
It is costly

hi  londolozi
here is the alteration been tested ready for the next release.

5.   The setting “Clear previously imported cells” has changed its behaviour. It will now make the program delete all custom cells assigned to all selections in all markets before importing new ones from Excel. Moreover, the old imported cells will also be cleared from the corresponding market “queryxxxx” sheets.

mcbee

Sweet !

Here's another one.
Aust Cox Plate.

It's a Dundeel was a listed horses.
See the attached text files. How, Why did this happen?
At the time ID was $4.40...where did the $2.07 price come from???
 
16:38:11   Going to BACK $ 85.16 at 4.40 on selection '11. Its A Dundeel'. Bet is matched. If unmatched, bet will be matched at SP at In-Play. The bet was placed/cancelled by Trigger "Equipace 15".
16:38:11   Going to BACK $ 72.25 at 2.07 on selection '11. Its A Dundeel'. Bet is matched. If unmatched, bet will be matched at SP at In-Play. The bet was placed/cancelled by Trigger "Equipace 15".

Here's another one that costs me $100's

16:27:09   Going to LAY $ 47.07 at 5.50 on selection '4. Big Island'. Bet is unmatched. If unmatched, bet will be cancelled at In-Play. The bet was placed/cancelled by Trigger "PB_1 11". (condition - Time before off > zero)

16:27:08   Going to LAY to the liability of $ 211.83 at SP, price limit 15.00 on selection '4. Big Island'. The bet was placed/cancelled by Trigger "PB_1 11 inplay BSP". (condition = time before off < -0.1)

The both triggers have conditions including back matched & back unmatched= zero.

AUS / Darw (AUS) 26th Oct / 16:27 R2 1000m Hcap 4. Big Island    Lay    3152204086    26-Oct-13 16:27 C 5.5 47.07 5.5 (211.82)
    
AUS / Darw (AUS) 26th Oct / 16:27 R2 1000m Hcap 4. Big Island    Lay    3152204046    26-Oct-13 16:27 SP C  6.23 211.83 (211.83)

   
 
Refresh rate is 2secs.

The triggers are effectively 3 refreshes apart ( zero seconds an-0.1 or 6 seconds) 
How does this happen?

...of course the horse won and I lost x 2 +$200 !!!

Please explain. Triggers provides on request.

hi
what formula do you have in the price and amount fields.
also you say

The both triggers have conditions including back matched & back unmatched= zero

BUT, the bets are for LAY NOT BACK, so to have the condition back matched/unmatched will not work.


mcbee

Yes, you are right. I meant lay.
 
They have all four conditions lay & back, matched & unmatched= zero.

Triggers attached

hi

Here's another one that costs me $100's

Quote
16:27:09   Going to LAY $ 47.07 at 5.50 on selection '4. Big Island'. Bet is unmatched. If unmatched, bet will be cancelled at In-Play. The bet was placed/cancelled by Trigger "PB_1 11". (condition - Time before off > zero)

16:27:08   Going to LAY to the liability of $ 211.83 at SP, price limit 15.00 on selection '4. Big Island'. The bet was placed/cancelled by Trigger "PB_1 11 inplay BSP". (condition = time before off < -0.1)

the problem with this is at 16:27:08 pb_1_11 inplay BSP sent out to cancel the back bet and then placed the lay bet, at this time there were no unmatched or matched bets on the selection.
then at 16:27:09 (this is only .09 of a second, a blink of your eye lid) pb_1_11 placed the lay bet, again there were no umatched or matched bets on the selection(because pb_1_11 inplay BSP was cancelling the back bet and placing a lay bet) and got matched immediately.
BUT the pb_1_11 inplay BSP had already sent the requests out.
so both got matched.


mcbee

Hi
The first trigger does not make sense.
You cannot place a bet to be matched at SP after the off using lay at SP.
markets minutes before the off is less than -0.1 is after the off
If any operation is happening here it should only be the cancel operation.

If you want to do that after the off simply lay at actual_sp (any unmatched bets will have been cancelled at the off)