docs: fix DeepModeling brand name

[njzjz-bot]

Change "Deep Modeling" (with space) to "DeepModeling" (no space).
"Deep Modeling" is an incorrect brand name. The correct one is "DeepModeling".

Generated by the task: njzjz-bot/njzjz-bot#19.

Summary by CodeRabbit

• Chores
  • Updated organization name references in documentation and configuration files for consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.29%. Comparing base (348fe3a) to head (2b1f0ac).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #558      +/-   ##
==========================================
- Coverage   60.45%   57.29%   -3.16%     
==========================================
  Files          39       40       +1     
  Lines        3912     3925      +13     
==========================================
- Hits         2365     2249     -116     
- Misses       1547     1676     +129     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

📝 Walkthrough

Walkthrough

The organization name is being updated from "Deep Modeling" to "DeepModeling" across documentation files. This is a straightforward name consistency update in the README and Sphinx configuration copyright metadata.

Changes

Cohort / File(s)	Summary
Organization name update README.md, doc/conf.py	Updated all instances of "Deep Modeling" to "DeepModeling" in documentation and project metadata (Contributing section and copyright string)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: fix DeepModeling brand name' directly and clearly summarizes the main change in the pull request: correcting the brand name from 'Deep Modeling' to 'DeepModeling' in documentation files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 348fe3a and 2b1f0ac.

📒 Files selected for processing (2)

• README.md (1 hunks)
• doc/conf.py (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.py

📄 CodeRabbit inference engine (AGENTS.md)

**/*.py: Always add type hints in all Python code
Ensure code remains compatible with Python 3.7+ (avoid syntax/features newer than 3.7)
Use Ruff (via pre-commit) for linting and formatting

Files:

• doc/conf.py

🧠 Learnings (1)

📚 Learning: 2025-10-02T19:23:22.456Z

Learnt from: CR
Repo: deepmodeling/dpdispatcher PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-02T19:23:22.456Z
Learning: Applies to examples/dpdisp_run.py : Keep the example script examples/dpdisp_run.py as a runnable example using PEP 723 script metadata

Applied to files:

• doc/conf.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build (ssh_rsync)
• GitHub Check: build (slurm)
• GitHub Check: build (pbs)

🔇 Additional comments (2)

README.md (1)

42-42: Brand name consistency looks good.

The organization name has been correctly updated to match the official branding.

doc/conf.py (1)

23-23: Copyright metadata updated correctly.

The brand name in the Sphinx copyright string is now consistent with the author field (line 24) and the README documentation update.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}