Redundancy in the log files about federatedscope

[yxdyc]

The output logging files are currently redundant, leading to disk space wastage and difficulties to find key results from the logging files. We may save the raw_metrics and training_metrics in other two log files with compact format.

[rayrayraykk]

The output logging files are currently redundant, leading to disk space wastage and difficulties to find key results from the logging files. We may save the raw_metrics and training_metrics in other two log files with compact format.

And we should delete the logs below, which have already been reported on the server-side.

FederatedScope/federatedscope/core/worker/client.py

Line 260 in 24deff5

for key in eval_metrics:

[rayrayraykk]

Another issue is the eval results of the global evaluation mode are empty, we should fix this.

[yxdyc]

The output logging files are currently redundant, leading to disk space wastage and difficulties to find key results from the logging files. We may save the raw_metrics and training_metrics in other two log files with compact format.

And we should delete the logs below, which have already been reported on the server-side.

FederatedScope/federatedscope/core/worker/client.py

Line 260 in 24deff5

for key in eval_metrics:

We still need this log when we are in distributed mode. Do you agree we mask these logs only in the ``simulation'' mode? @rayrayraykk

[rayrayraykk]

The output logging files are currently redundant, leading to disk space wastage and difficulties to find key results from the logging files. We may save the raw_metrics and training_metrics in other two log files with compact format.

And we should delete the logs below, which have already been reported on the server-side.

FederatedScope/federatedscope/core/worker/client.py

Line 260 in 24deff5

for key in eval_metrics:

We still need this log when we are in distributed mode. Do you agree we mask these logs only in the ``simulation'' mode? @rayrayraykk

Agree.

[yxdyc]

Solved in #29