-
Notifications
You must be signed in to change notification settings - Fork 23
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
gather - show all failed edges in error message #1095
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1095 +/- ##
==========================================
- Coverage 94.62% 92.90% -1.73%
==========================================
Files 136 137 +1
Lines 10087 10103 +16
==========================================
- Hits 9545 9386 -159
- Misses 542 717 +175
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
74e558b
to
bfe911e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fine to me, but the error message seems like it might be a bit too unweildy.
Ideally we want something that's easy to parse for edges rather than a lot of text around each printed line.
openfecli/commands/gather.py
Outdated
if maybe_rhfe and not maybe_rbfe: | ||
msg += ( | ||
f"{ligpair}:\n" | ||
"\tAssuming this is an RHFE calculation, " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like it might get really noisy, with lots of Assuming X this is missing
. Could we just set that as a single header and then just +=
on a list of edge information?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jthorton @IAlibay how do you feel about this solution?
Here's what the output looks like:
My thinking is that we pass through as much info to the user as we can without trying to be overly clever and auto-detecting rbfe vs rhfe, since it sounds like verbosity hurts more than helps.
Happy to change it again in the future depending on user needs.
fec49d6
to
cae75d1
Compare
cae75d1
to
f6c9ef8
Compare
No API break detected ✅ |
Closes #1101
Checklist
news
entryDevelopers certificate of origin