Fix network_type docstring formatting in PerceptualLoss

[aman0311x]

Fixes # .

Description

This pull request fixes incorrect formatting and clarifies the documentation
for the network_type argument in PerceptualLoss.

The docstring now correctly reflects the supported network options
and matches the actual implementation.

Types of changes

• Non-breaking change (fix or new feature that would not break existing functionality).
• Breaking change (fix or new feature that would cause existing functionality to change).
• New tests added to cover the changes.
• Integration tests passed locally by running ./runtests.sh -f -u --net --coverage.
• Quick tests passed locally by running ./runtests.sh --quick --unittests --disttests.
• In-line docstrings updated.
• Documentation updated, tested make html command in the docs/ folder.

No functional behavior is changed.

[coderabbitai]

Walkthrough

The enum class in monai/losses/perceptual.py was renamed from PercetualNetworkType to PerceptualNetworkType. All references in that file — including the PerceptualLoss constructor default, validation checks, error messages, and docstring examples — were updated to use PerceptualNetworkType. No runtime logic was changed aside from the identifier rename.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Confirm all references/imports in this file use PerceptualNetworkType.
• Search the repository for any remaining uses of PercetualNetworkType (public API, docs, type hints).
• Verify exported names/exports if the enum is part of the public API.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title directly matches the main change: fixing docstring formatting for the network_type parameter in PerceptualLoss.
Description check	✅ Passed	PR description follows the template structure with completed sections, though the issue number reference is incomplete.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

monai/losses/perceptual.py (1)

75-75: Update type annotation to match accepted types.

Type annotation specifies str but should be str | PercetualNetworkType to match the docstring and actual usage.

🔎 Proposed fix

-        network_type: str = PercetualNetworkType.alex,
+        network_type: str | PercetualNetworkType = PercetualNetworkType.alex,

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 15fd428 and 7ce29a1.

📒 Files selected for processing (1)

• monai/losses/perceptual.py

🧰 Additional context used

📓 Path-based instructions (1)

**/*.py

⚙️ CodeRabbit configuration file

Review the Python code for quality and correctness. Ensure variable names adhere to PEP8 style guides, are sensible and informative in regards to their function, though permitting simple names for loop and comprehension variables. Ensure routine names are meaningful in regards to their function and use verbs, adjectives, and nouns in a semantically appropriate way. Docstrings should be present for all definition which describe each variable, return value, and raised exception in the appropriate section of the Google-style of docstrings. Examine code for logical error or inconsistencies, and suggest what may be changed to addressed these. Suggest any enhancements for code improving efficiency, maintainability, comprehensibility, and correctness. Ensure new or modified definitions will be covered by existing or new unit tests.

Files:

• monai/losses/perceptual.py

🔇 Additional comments (2)

monai/losses/perceptual.py (2)

52-56: Docstring update is accurate but type annotation doesn't match.

The docstring correctly documents that network_type accepts both str and PercetualNetworkType, but the type annotation on line 75 only specifies str.

---

98-102: No issues found. StrEnum members inherit from str, so .lower() works on enum inputs and comparison against list(PercetualNetworkType) succeeds for both string and enum inputs. Logic is correct as written.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 7ce29a1 and e2d0a02.

📒 Files selected for processing (1)

• monai/losses/perceptual.py

🧰 Additional context used

📓 Path-based instructions (1)

**/*.py

⚙️ CodeRabbit configuration file

Review the Python code for quality and correctness. Ensure variable names adhere to PEP8 style guides, are sensible and informative in regards to their function, though permitting simple names for loop and comprehension variables. Ensure routine names are meaningful in regards to their function and use verbs, adjectives, and nouns in a semantically appropriate way. Docstrings should be present for all definition which describe each variable, return value, and raised exception in the appropriate section of the Google-style of docstrings. Examine code for logical error or inconsistencies, and suggest what may be changed to addressed these. Suggest any enhancements for code improving efficiency, maintainability, comprehensibility, and correctness. Ensure new or modified definitions will be covered by existing or new unit tests.

Files:

• monai/losses/perceptual.py

🧬 Code graph analysis (1)

monai/losses/perceptual.py (1)

monai/utils/enums.py (1)

• StrEnum (68-90)

🔇 Additional comments (1)

monai/losses/perceptual.py (1)

52-60: LGTM: Improved docstring clarity.

The reformatted list of valid network_type values is clearer than the previous inline notation.

[aman0311x]

Hi @virginiafdez,

The spelling/enum issue in PerceptualLoss has been fixed (PercetualNetworkType → PerceptualNetworkType), and all references/docstrings have been updated accordingly.

Additionally, all missing DCO sign-offs have been added via remediation commits. Everything should now be in order for review.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 3e92d74 and 8be3faa.

📒 Files selected for processing (1)

• e --abort

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Wrong file provided - cannot review git log output.

The file appears to be a git log dump rather than source code. The filename "e --abort" suggests a malformed command. The PR objectives indicate changes to monai/losses/perceptual.py (enum rename from PercetualNetworkType to PerceptualNetworkType), but that file was not provided for review.

Please provide the actual source file with code changes.

🤖 Prompt for AI Agents

In e --abort around lines 1-114 the uploaded file is a git log dump (wrong file)
instead of the intended source; replace this with the actual modified source
file monai/losses/perceptual.py containing the PR changes, rename the misspelled
enum PercetualNetworkType to PerceptualNetworkType (update the enum definition,
all references, imports, and type hints), fix related docstrings and any
occurrences of the old name, run unit tests and linters, and amend the commit/PR
to include the corrected file so reviewers can verify the change.