fix class design inconsistency for `HistoryMonitor`
As a developper I want class design inconsistency for HistoryMonitor
to be fixed.
The issue:
-
HistoryMonitor
is defined as part of node (fedbiomed.node.history_monitor.HistoryMonitor
) - but it is also used by some modules in common (
fedbiomed.common.training_plans
)
A possible solution:
- a stub (null payload)
common.HistoryMonitor
- a subclass
node.NodeHistoryMonitor(HistoryMonitor)
with the payload of actual history monitor - use
common.HistoryMonitor
incommon
- if needed, add additional checks in
common
? (should not be necessary)
Dear user, please keep the lign below when submitting an issue: