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

Not able to run GENIE3 and GRNBOOST2 #92

Open
Aishwarya-Girish opened this issue Apr 6, 2023 · 8 comments
Open

Not able to run GENIE3 and GRNBOOST2 #92

Aishwarya-Girish opened this issue Apr 6, 2023 · 8 comments
Assignees

Comments

@Aishwarya-Girish
Copy link

Hi,

I am not able to run GENIE3 and GRNBOOST2, perhaps due to some Arboreto error. The error message I get is :

OSError: Timed out trying to connect to 'inproc://172.17.0.5/9/1' after 10 s: Timed out trying to connect to 'inproc://172.17.0.5/9/1' after 10 s: connect() didn't finish in time

Attached below is an image of the same. Would be grateful if you could help me resolve the issue.

image
image

@ktakers
Copy link
Collaborator

ktakers commented Apr 6, 2023

The tornado timeout appears to be the same issue reported in #66, #48, and #42. According to the Arboreto issue aertslab/arboreto#10 , GENIE3 can run successfully despite those timeout errors.

Can you please check under the directory outputs/example/GSD/GENIE3 to see if there's a rankedEdges.csv or an outFile.txt, which would indicate that GENIE3 did actually complete successfully?

@ktakers ktakers self-assigned this Apr 6, 2023
@Aishwarya-Girish
Copy link
Author

Aishwarya-Girish commented Apr 7, 2023 via email

@Aishwarya-Girish
Copy link
Author

Aishwarya-Girish commented Apr 7, 2023 via email

@elhaam
Copy link

elhaam commented Apr 13, 2023

I faced the same issue. The way I solved this was by stopping and removing all docker images to solve this error:
Please be cautious running the below command since it stops and removes all docker images, maybe you can select a specific docker image of your choice, instead.

docker stop $(docker ps -aq) && docker rm $(docker ps-aq)

@tmmurali
Copy link
Member

tmmurali commented Jun 3, 2023

@Aishwarya-Girish does the idea proposed by @elhaam work for you? If it does, we can close this issue.

@Aishwarya-Girish
Copy link
Author

I am sorry sir, the idea doesn't work. GENIE3 and GRNBOOST2 still dont function due to the same issue

@elhaam
Copy link

elhaam commented Dec 4, 2023

@tmmurali @Aishwarya-Girish Another solution that has helped me in some cases is going to your Beeline/input/example/your_example/GENIE3 directory and removing subdirectories made for GENIE3. Also, remove subdirectories from Beeline/output/example/your_example/GENIE3 as well. Then run BoolODE.py again. This helped me run GENIE3 in some cases when I got the above error.

For a couple of experiments, I still couldn't run GENIE3 due to the above error, which was not resolved by the solutions I shared here.

@kevchen03
Copy link
Collaborator

Hello @Aishwarya-Girish @tmmurali ,
Assuming that the run phase inside BLRunner is completed, a temporary solution that has worked for me is to comment out the for-loops for generateInputs and run. The rankedEdges.csv file is generated solely within the parseOutput function using the files generated by the run phase, so you should be able to comment out the generateInputs and run loops to skip straight to generating the rankedEdges.csv file.

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

6 participants