jimster
01-31-2013, 10:07 PM
Hello Support,
I know pretty much everything for HM1 is currently on the low burner, but what you pulled out to fix Hand Histories (HHs) on Stars that where using "Run it Twice" is just bad from a developer standpoint.
Instead of writing a small function that clones the HHs to the point that the split began, and inserting the cards till showdown from the two rundowns seperately and make them unique from each other in naming, everything from the start of the dual run is just snipped out. So every aspect in terms of Session Review regarding this hands is lost. You cannot review them correctly in regards to board runout and equity. They are just mutilated HHs.
This functionality could even be used afterwards and you could just implement an embargo oppertunity for the hands during import progress to not fuck up the performance and leave them out.
If you are not able to code this due to company HM2 restriction bullshit, I have a tool that is achieving the correct HH reformatting myself. So you would just have to provide an embargo for "Run it twice"-Hands into a different folder and I do it myself instead of having to request all HHs from stars again and filter them for Run it Twice and manually purging the mutilated HHs from my DBs. Is that too much asked even for the halfass job you are pulling on HM1 currently?
Thanks in advance!
P.S.: Run it Twice was introduced before the holidays, that is over a month ago. Still no valid solution, with that turnaround time I would get my ass fired. But I guess you just dont care, or are no longer allowed to care. What a shame! HM1 is a magnificent work of art and technology in my book and how it is currently handled is not acceptable.
Please think about a maintenance model to support the program the way it should be supported!
I know pretty much everything for HM1 is currently on the low burner, but what you pulled out to fix Hand Histories (HHs) on Stars that where using "Run it Twice" is just bad from a developer standpoint.
Instead of writing a small function that clones the HHs to the point that the split began, and inserting the cards till showdown from the two rundowns seperately and make them unique from each other in naming, everything from the start of the dual run is just snipped out. So every aspect in terms of Session Review regarding this hands is lost. You cannot review them correctly in regards to board runout and equity. They are just mutilated HHs.
This functionality could even be used afterwards and you could just implement an embargo oppertunity for the hands during import progress to not fuck up the performance and leave them out.
If you are not able to code this due to company HM2 restriction bullshit, I have a tool that is achieving the correct HH reformatting myself. So you would just have to provide an embargo for "Run it twice"-Hands into a different folder and I do it myself instead of having to request all HHs from stars again and filter them for Run it Twice and manually purging the mutilated HHs from my DBs. Is that too much asked even for the halfass job you are pulling on HM1 currently?
Thanks in advance!
P.S.: Run it Twice was introduced before the holidays, that is over a month ago. Still no valid solution, with that turnaround time I would get my ass fired. But I guess you just dont care, or are no longer allowed to care. What a shame! HM1 is a magnificent work of art and technology in my book and how it is currently handled is not acceptable.
Please think about a maintenance model to support the program the way it should be supported!