We have quite a few parameters in the static solver and the rollout algorithm. Right now these are managed fairly ad-hoc:
We pass in the defaults for the static solver, but have no good way to change its operators or parameters without changing the code.
Similarly, rollout has various configuration settings that are also stored in or near the code. Some parameters are passed into the rollout function as arguments, others are read directly from another Python file.
We should streamline this a bit more. I'm thinking of a general Config class on the Python side, that stores the relevant static operators, and the static and dynamic parameters. It should support being constructed from code (for tuning), or by reading from a file (e.g., with a classmethod from_file).
We have quite a few parameters in the static solver and the rollout algorithm. Right now these are managed fairly ad-hoc:
We should streamline this a bit more. I'm thinking of a general
Configclass on the Python side, that stores the relevant static operators, and the static and dynamic parameters. It should support being constructed from code (for tuning), or by reading from a file (e.g., with a classmethodfrom_file).