Conversation
Signed-off-by: ashors1 <ashors@nvidia.com>
ea8ca33 to
6b10bec
Compare
|
Does this close #34? |
Yes, there are a few loose ends that I'd like to tie up before officially closing, but this is the first step |
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
|
Does HF load from this format automagically if someone did |
Not right now. HF compatibility is one of the things I need to work on before closing #34 |
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
|
With the HF checkpoint support provided in this PR, we should also be able to close #110. Users can either save their checkpoints in HF format directly, or can convert the checkpoint from torch distributed format to HF format after training. Once the checkpoint is in the correct format, it can be loaded via cc @terrykong |
|
@ashors1 also could you add that ckpt converter script to our docs? |
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com> Signed-off-by: Anna Shors <ashors@nvidia.com> Signed-off-by: Parth Chadha <pchadha@nvidia.com>
Signed-off-by: ashors1 <ashors@nvidia.com> Signed-off-by: Anna Shors <ashors@nvidia.com>
What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Issues
List issues that this PR closes (syntax):
Closes #109
Closes #110
Usage
# Add a code snippet demonstrating how to use thisBefore your PR is "Ready for review"
Pre checks:
Additional Information