Scy how are you?
Could a nodelock be implemented to tell the solver that X action I do not want to be taken?
Here the example:
Of the 3 betting options, I want to abandon the medium sizing.
But I don't want to merge, let me explain?
Merge, for example with the big bet, will be a suboptimal strategy (mix frequency error)
compared to the solver deciding that % again between the 3 remaining options (bet big bet small check).
This can be done in edit tree or by exporting Turns by deleting the action.
The problem with this is that in database mode, deleting an action causes you to lose the reports.
This gives many benefits when studying and simplifying, because the data is "saved" in DB Mode and even by deleting the nodelock we could return to the base strategy.
Exporting turns is much more useful if we want to test different action nodelocks and/or add/remove sizings for something specific. and have the possibility of comparing with the base strategy on another window
But those changes in DB Mode make you lose all the other reports.
I think it shouldn't be that difficult to implement a nodelock to tell it what action NOT to take.
Thank you very much as always!
Last edited by Mates.; 03-27-2024 at 05:32 AM.