Open robmarkcole opened 1 week ago
Another option would be to remove any figure logging from TorchGeo entirely. If users want it, they can subclass the trainer and add it. This feature has historically been a nightmare to maintain/test and has been riddled with bugs. The proposal here is to make it even more complicated.
More positively, can you start a discussion with the Lightning folks to see if there is an easier way to do this automatically? Or a way that can unify the interface somehow? This just seems like too much work to support out of the box.
RE lightning I see a lot of work was done in https://github.com/Lightning-AI/pytorch-lightning/pull/6227 but ultimately they decided this was too complex to maintain, and closed the PR.
Perhaps as you say, logging figures should be left to users to subclass the trainers. I think basic logging of samples on the dataset is a necessity however
Summary
Currently logging of figures (e.g. in Classification and Segmentation trainers) assumes Tensorboard logger which has the method
add_figure
. However other loggers have similar methods but with different names and are currently not supported. e.g. MLflow uses log_figure. This FR is to support these loggers and document which are supportedRationale
Many orgs use a service for logging such as mlflow or wandb etc, and it would be nice for these to just work.
Implementation
We would probably want to abstract this for use by all trainers, but adding this method is one soluton
Alternatives
None
Additional information
No response