You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the excellent RL library. PFRL makes my life so much easy.
As the management of the experiment becomes complicated, I have tried PFRL with MLFlow. And I'm satisfied with the initial implementation (see code below). MLFlow helps to compare the performances of algorithms, to manage trained models and to monitor training results remotely.
On the other hand, if PFRL natively supports MLFlow, it would be even easier to use and I can expect the wisdom of various experiment management efforts from other users. At the moment, Tensorboard support was just added a few months ago, and I'm sure that each wants to use different tools, so I've listed this as an issue to discuss.
The motivations for native support:
to reduce overlapped logging functions
to give more detailed evaluation score access to MLFlow
An alternative instead of MLFlow native support:
to update record_tb_stats(self.tb_writer, agent_stats, eval_stats, t) to more general implementation (like eval_hooks)
More general question about the management..:
to log the history of reward shaping and observation feature engineering on custom environments (git diff is a bit hard to read through)
Thank you for the excellent RL library. PFRL makes my life so much easy.
As the management of the experiment becomes complicated, I have tried PFRL with MLFlow. And I'm satisfied with the initial implementation (see code below). MLFlow helps to compare the performances of algorithms, to manage trained models and to monitor training results remotely.
On the other hand, if PFRL natively supports MLFlow, it would be even easier to use and I can expect the wisdom of various experiment management efforts from other users. At the moment, Tensorboard support was just added a few months ago, and I'm sure that each wants to use different tools, so I've listed this as an issue to discuss.
The motivations for native support:
An alternative instead of MLFlow native support:
More general question about the management..:
How to use PFRL and MLFLOW together
The text was updated successfully, but these errors were encountered: