Skip to content

trainer.validated/tested/predicted_ckpt_path: mark private or deprecate #10630

@jjenniferdai

Description

@jjenniferdai

Proposed refactor / Motivation

As detailed in this comment: #10573 (comment):

Pitch

To clarify/emphasize this, we can either:

  1. Set to private. Also just need one attribute (e.g. trainer._ckpt_path or trainer._last_restored_ckpt_path).

  2. Can we deprecate these attributes entirely? checkpoint_connector gives us info on the exact path here: https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/trainer/connectors/checkpoint_connector.py#L75

Additional context


If you enjoy Lightning, check out our other projects! ⚡

  • Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

  • Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

  • Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

  • Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

  • Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @justusschock @awaelchli @akihironitta @rohitgr7 @ananthsub @ninginthecloud @tchaton

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions