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

Complex Pipeline Failure - ValueError #229

Closed
cross12tamu opened this issue Mar 19, 2020 · 7 comments
Closed

Complex Pipeline Failure - ValueError #229

cross12tamu opened this issue Mar 19, 2020 · 7 comments

Comments

@cross12tamu
Copy link

This is somewhat related to Issue #215

I am running a complex pipeline and during the later steps, it hangs on the attached issue.
evcouplings_error

Let me know if there's anything else I need to provide for y'all.

Of note, I also did the (couple line) changes seen here

Thanks!

( For other jobs, I am also getting errors related to #213 , in which I will bump )

@thomashopf
Copy link
Contributor

@cross12tamu Could you please upload the entire pipeline output folder including config files somewhere? Then we can have a more detailed look at the issue

@thomashopf
Copy link
Contributor

Looks like this may be the same issue as #222

@aggreen
Copy link
Contributor

aggreen commented Mar 20, 2020

@thomashopf agree this is the same issue

@cross12tamu
Copy link
Author

Hey yall,

Is there a good way to send the entire output and config here on github? I can compress and email as well.

@thomashopf
Copy link
Contributor

Any link where we can download the files is fine (not aware of large uploads being possible at github)

@cross12tamu
Copy link
Author

cross12tamu commented Mar 27, 2020

Here a google drive link, let me know if it does not work.

@thomashopf
Copy link
Contributor

Thanks, this confirms we indeed have a duplicate of #222 here.

Until we have a fix implemented, in the "compare" section of you config, please change

plot_probability_cutoffs: [0.90, 0.99]

to

plot_probability_cutoffs: []

which will avoid running into the problematic code.

Please let us know in case this still doesn't fix it for you temporarily, closing this issue in favor of #222 for now.

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

No branches or pull requests

3 participants