Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Customize CLI reporter #19

Closed
3 tasks
jieonh opened this issue Dec 13, 2022 · 1 comment
Closed
3 tasks

Feature: Customize CLI reporter #19

jieonh opened this issue Dec 13, 2022 · 1 comment
Assignees
Labels
Features New feature or request

Comments

@jieonh
Copy link
Collaborator

jieonh commented Dec 13, 2022

What

Customize CLI reporter to print output at appropriate intervals. (per epoch, etc.)

Why

  • The default CLI reporter prints outputs too frequently, making it difficult to check the results.
  • Previously, I made the custom reporter (reports at end of each trial) to solved that problem, but there was an inconvenience that the reporting cycle was too long.

It is not a priority, and when I analyzed it last time, it was not as easy as I thought to change it to print in cycles rather than ray Trial units. But I still think it's worth looking into, since the need has come up several times.

How

  • Choose appropriate reporting intervals
  • Analysis CLI reporter Class
  • Customize reporter
@jieonh jieonh added the Features New feature or request label Dec 13, 2022
@jieonh jieonh self-assigned this Dec 13, 2022
@jieonh jieonh changed the title Feature: Customize ray reporter to have a proper reporting intervals Feature: Customize CLI reporter to have a proper reporting intervals Dec 13, 2022
@jieonh jieonh changed the title Feature: Customize CLI reporter to have a proper reporting intervals Feature: Customize CLI reporter Dec 13, 2022
@seoulsky-field seoulsky-field added this to the Dataset: CheXpert milestone Dec 30, 2022
@jieonh
Copy link
Collaborator Author

jieonh commented Jan 17, 2023

I'm closing this issue because Custom Ray CLI logger is no longer necessary as we have implemented better CLI logger (rich).

@jieonh jieonh closed this as completed Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Features New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants