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.

Sign up for GitHub

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

Jump to bottom

Logging #230

Closed
ryanccarelli opened this issue Nov 11, 2021 · 4 comments
Closed

Logging #230

ryanccarelli opened this issue Nov 11, 2021 · 4 comments
Assignees
@BeeGass
Labels
enhancement New feature or request

Comments

@ryanccarelli
Copy link
Contributor

Currently we have print statements that should be handled by logging.
@ryanccarelli ryanccarelli added the enhancement New feature or request label Nov 11, 2021
@BeeGass
Copy link
Contributor

BeeGass commented Feb 24, 2022

To create a list to reference in the future:

  • development mode that can be enabled to see pathml specific logs
  • be able to switch from terminal outputted logs and log file
    • logging of user hardware
  • logging distributed computing through DASK's API

Please let me know what other things I missed. I know there are class specific things that should take precedent.

@jacob-rosenthal
Copy link
Collaborator

Looks good. Lets also add:

  • logging configuration details of dask cluster when running pipelines with distributed=True (number of workers, resources per worker, worker configurations, etc. etc.)

@BeeGass
Copy link
Contributor

BeeGass commented Feb 25, 2022

  • log and better error handle when environment variables are not found or have not been imported.

@jacob-rosenthal
Copy link
Collaborator

Added in #304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BeeGass BeeGass

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BeeGass @jacob-rosenthal @ryanccarelli