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

DM-46351: Add debug log in _pipeline_graph to ID task label #447

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

leeskelvin
Copy link
Contributor

Checklist

  • ran Jenkins
  • added a release note for user-visible changes to doc/changes

@leeskelvin leeskelvin force-pushed the tickets/DM-46351 branch 2 times, most recently from 94f502d to 2fbfd18 Compare September 16, 2024 14:48
Copy link

codecov bot commented Sep 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.51%. Comparing base (dccb6f9) to head (3eead01).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #447   +/-   ##
=======================================
  Coverage   83.51%   83.51%           
=======================================
  Files          97       97           
  Lines       11426    11427    +1     
  Branches     2192     2192           
=======================================
+ Hits         9542     9543    +1     
  Misses       1529     1529           
  Partials      355      355           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -712,6 +712,7 @@ def add_task(
label = task_class._DefaultName
if config is None:
config = task_class.ConfigClass()
_LOG.debug("Task: %s %s", label, task_class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think something more verbose would be more helpful when disambiguating debug logs. Maybe something like Adding task with label: %s and class: %s to the pipeline graph

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current ticket produces output that looks like this:

lsst.pipe.base.pipeline_graph DEBUG: Task: photometricMatchVisit <class 'lsst.analysis.tools.tasks.photometricCatalogMatch.PhotometricCatalogMatchVisitTask'>

Your suggestion would produce output that looks like this:

lsst.pipe.base.pipeline_graph DEBUG: Adding task with label: photometricMatchVisit and class: <class 'lsst.analysis.tools.tasks.photometricCatalogMatch.PhotometricCatalogMatchVisitTask'> to the pipeline graph

Is the double "class" what you had in mind?

Copy link
Contributor Author

@leeskelvin leeskelvin Sep 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having discussed in-person, modifying to:

Adding task %s %s to the pipeline graph

@leeskelvin leeskelvin merged commit a82cb14 into main Sep 16, 2024
13 checks passed
@leeskelvin leeskelvin deleted the tickets/DM-46351 branch September 16, 2024 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants