I use a simple trigger that backs the selection at the off time for an amount modified by the bet_factor. ![]() The bet_factor value is picked up in imported_1 and used to modify bet size. The fourth entry is not a misprint: a selection may be bet several times with a different bet_factor. So in my case a selection file with headings would look like this: and, 1D-1 is a double precision value X 10-1. e.g., 1.0D0 is a double precision value X 100. ![]() The format for importing a selection file for Australian horse races used to be for each line in the text file: an entry number followed by a full stop then a space then the horse's name, all the previous enclosed in double quotation marks like this:Īdditional information useful for a trigger could be added separated by a tab, in my case I add a number that can be picked up as the imported_1 variable. the format of the FORTRAN input parameters, as you can see, carries the precision of the value with it. ![]() I have recently re-subscribed after an absence since 2016 and have been looking at any changes to MFP since then that may affect me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |