Skip to content

[NeMo-UX] Update default PTL logging save_dir#9985

Merged
ashors1 merged 1 commit intomainfrom
cherry-pick-main-a78cc36eab5806a0e53828c438d27f4f95373379
Aug 6, 2024
Merged

[NeMo-UX] Update default PTL logging save_dir#9985
ashors1 merged 1 commit intomainfrom
cherry-pick-main-a78cc36eab5806a0e53828c438d27f4f95373379

Conversation

@github-actions
Copy link
Contributor

What does this PR do ?

If a user passes a save_dir to a PTL logger, by default we write the logs to <log_dir> / save_dir, where <log_dir> is determined by NeMoLogger. Previously, save_dir was ignored, and the logs would be written to <log_dir>.

Collection: [Note which collection this PR will affect]

Changelog

  • Add specific line by line info of high level changes in this PR.

Usage

  • You can potentially add a usage example below
# Add a code snippet demonstrating how to use this 

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests?
  • Did you add or update any necessary documentation?
  • Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
    • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

  • Related to # (issue)

* updat default PTL logging directories

Signed-off-by: ashors1 <ashors@nvidia.com>

* fix logger versions

Signed-off-by: ashors1 <ashors@nvidia.com>

* fix failed test

Signed-off-by: ashors1 <ashors@nvidia.com>

* add better documentation for 'update_logger_directory'

Signed-off-by: ashors1 <ashors@nvidia.com>

---------

Signed-off-by: ashors1 <ashors@nvidia.com>
@ashors1 ashors1 merged commit cb72f02 into main Aug 6, 2024
@ashors1 ashors1 deleted the cherry-pick-main-a78cc36eab5806a0e53828c438d27f4f95373379 branch August 6, 2024 22:08
adityavavre pushed a commit to adityavavre/NeMo that referenced this pull request Sep 15, 2024
…VIDIA-NeMo#9985)

* updat default PTL logging directories

* fix logger versions

* fix failed test

* add better documentation for 'update_logger_directory'

---------

Signed-off-by: ashors1 <ashors@nvidia.com>
Co-authored-by: Anna Shors <71393111+ashors1@users.noreply.github.com>
Signed-off-by: adityavavre <aditya.vavre@gmail.com>
monica-sekoyan pushed a commit that referenced this pull request Oct 14, 2024
* updat default PTL logging directories



* fix logger versions



* fix failed test



* add better documentation for 'update_logger_directory'



---------

Signed-off-by: ashors1 <ashors@nvidia.com>
Co-authored-by: Anna Shors <71393111+ashors1@users.noreply.github.com>
hainan-xv pushed a commit to hainan-xv/NeMo that referenced this pull request Nov 5, 2024
…VIDIA-NeMo#9985)

* updat default PTL logging directories



* fix logger versions



* fix failed test



* add better documentation for 'update_logger_directory'



---------

Signed-off-by: ashors1 <ashors@nvidia.com>
Co-authored-by: Anna Shors <71393111+ashors1@users.noreply.github.com>
Signed-off-by: Hainan Xu <hainanx@nvidia.com>
XuesongYang pushed a commit to paarthneekhara/NeMo that referenced this pull request Jan 18, 2025
…VIDIA-NeMo#9985)

* updat default PTL logging directories



* fix logger versions



* fix failed test



* add better documentation for 'update_logger_directory'



---------

Signed-off-by: ashors1 <ashors@nvidia.com>
Co-authored-by: Anna Shors <71393111+ashors1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants