fix: fix checkpoint filename for the PyTorch backend

[njzjz]

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of model checkpoints during training to ensure compatibility with different file suffixes (.pb and .pth).

[coderabbitai]

Walkthrough

Walkthrough

The modification in the run_train_dp function allows for dynamic handling of model checkpoint files based on their suffixes (.pb or .pth). This ensures the correct management and processing of checkpoint files during the training process, enhancing the robustness and flexibility of the training pipeline.

Changes

File Path	Change Summary
dpgen/generator/run.py	Added a conditional block to set the checkpoint suffix based on file suffixes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant run_train_dp
    participant CheckpointHandler
    
    User->>run_train_dp: Call function with model checkpoint
    run_train_dp->>run_train_dp: Determine checkpoint suffix based on file
    alt Suffix is `.pb`
        run_train_dp->>CheckpointHandler: Set suffix to `.pb`
    else Suffix is `.pth`
        run_train_dp->>CheckpointHandler: Set suffix to `.pth`
    end
    CheckpointHandler-->>run_train_dp: Checkpoint suffix set
    run_train_dp-->>User: Continue training process

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 30bc1e5 and 44debab.

Files selected for processing (1)

• dpgen/generator/run.py (1 hunks)

Additional comments not posted (1)

dpgen/generator/run.py (1)

811-816: Ensure correct checkpoint suffix determination.

The new conditional block correctly sets the ckpt_suffix based on the file suffix. However, consider handling more suffixes or providing a default case to improve robustness.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 49.59%. Comparing base (30bc1e5) to head (44debab).
Report is 29 commits behind head on devel.

Files with missing lines	Patch %	Lines
dpgen/generator/run.py	50.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            devel    #1585      +/-   ##
==========================================
- Coverage   49.59%   49.59%   -0.01%     
==========================================
  Files          83       83              
  Lines       14844    14849       +5     
==========================================
+ Hits         7362     7364       +2     
- Misses       7482     7485       +3     

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