[Fix] The keyword mode appears nested multiple times in the log

[huaibovip]

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.

Motivation

When log_with_hierarchy is set to True, the keyword mode appears nested multiple times in the log. For example, val/val/data_time: 0.0332 val/val/time: 0.4490.

Modification

mmengine/mmengine/runner/log_processor.py

Line 379 in a483dba

for log_cfg in custom_cfg:

        for log_cfg in custom_cfg:
            if not reserve_prefix:
                data_src = log_cfg.pop('data_src')
                log_name = f"{log_cfg.pop('log_name', data_src)}"
            else:
                data_src = f"{mode}/{log_cfg.pop('data_src')}"
                log_name = f"{mode}/{log_cfg.pop('log_name', data_src)}"

to

        for log_cfg in custom_cfg:
            data_src = log_cfg.pop('data_src')
            log_name = f"{log_cfg.pop('log_name', data_src)}"
            if reserve_prefix:
                data_src = f"{mode}/{data_src}"
                log_name = f"{mode}/{log_name}"

BC-breaking (Optional)

Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.

Use cases (Optional)

If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.

Checklist

1. Pre-commit or other linting tools are used to fix the potential lint issues.
2. The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
3. If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
4. The documentation has been modified accordingly, like docstring or example tutorials.

[HAOCHENYE]

Hi, do you mean that you configure custom_cfg and set log_with_hierarchy to true simultaneously? The code snippet you modified only works when custom_cfg is configured.

[huaibovip]

@HAOCHENYE

Hi, I only set log_with_hierarchy=True, while keeping custom_cfg default, besides I use EpochBased mode.

The variable custom_cfg gets assigned here, so the code I changed takes effect.

mmengine/mmengine/runner/log_processor.py

Line 296 in a483dba

if 'time' not in custom_keys:

[HAOCHENYE]

Suggested change

	data_src = f"{mode}/{data_src}"
	log_name = f"{mode}/{log_name}"
	data_src = f'{mode}/{data_src}'
	log_name = f'{mode}/{log_name}'

[HAOCHENYE]

Ah-ha! Indeed, that's the case. Thank you for your contribution. We'll merge ASAP after lint is fixed.