-
Notifications
You must be signed in to change notification settings - Fork 38
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
haddock3-analyse keyerror #977
Comments
|
in |
While capri_clt.csv has clusters |
nothing wrong in haddock3/src/haddock/modules/analysis/caprieval/capri.py Lines 945 to 947 in 7a9434e
The difference between less_io = false and less_io = true should not have two completely different execution schemes as that is quite prone to errors. Not to mention maintenance costs.
discusses already in #862 |
This here should not be two paths but rather only one using haddock3/src/haddock/modules/analysis/caprieval/__init__.py Lines 137 to 156 in 7a9434e
Working on it at 977-haddock3-analyse-keyerror |
Thanks for reporting it @sverhoeven, small oversight on my part since the
Confirmed fix with #978 $ ls -ltrh run1-full-like-webapp/analysis/11_caprieval_analysis/report.html
-rw-r--r-- 1 rodrigo users 335K Aug 23 13:59 run1-full-like-webapp/analysis/11_caprieval_analysis/report.html |
During haddock3-analyse of protein-protein example a caprieval analysis failed.
Module/Workflow/Library affected
haddock3-analyse command
Expected behavior
That
analysis/11_caprieval_analysis/report.html
exists.Actual behavior
The last caprieval analysis failed with
with
and
log.exception(e)
added I gotSteps to reproduce the behavior
I ran the docking-protein-protein-full.cfg workflow with following overwrites
See complete config and log at bottom of this issue.
Suggestions on how to fix it
Minor improvement would be to use
log.exception(e)
instead oflog.warning(f'{e}')
to get the full stack trace. Getting error1
is not very helpful.Version
7a9434e
Additional context
docking-protein-protein-full.like-webapp.cfg
log
The text was updated successfully, but these errors were encountered: