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

Eigen Decompsition #1

Open
Sen0108 opened this issue Jul 12, 2022 · 16 comments
Open

Eigen Decompsition #1

Sen0108 opened this issue Jul 12, 2022 · 16 comments

Comments

@Sen0108
Copy link

Sen0108 commented Jul 12, 2022

I was trying the pipeline with HT1080 HI-C data (.mcool generated from distiller.nf). Unfortunately, eigdecomp rule never worked. I think it is the problem with partition. I am sending you my SRA code (SRR7586416, SRR7586418). Please tell me what to do.

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

Hello. Can you post the traceback of the error you see?

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

Yeah sure... first one when I have to tried to run it in vscode individually each rule. Second one, is within the conda environment.

Screen Shot 2022-07-12 at 11 03 13 AM

Screen Shot 2022-07-12 at 11 06 42 AM

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

the assembly was hg38

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

The chromosome order in your coolers might be different than what is expected.

What is the output of cooler dump -t chroms {your_data}.mcool::resolutions/50000 ?

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

Ok. What is the solution? I am sending you the cooler dump output
HT1080.txt

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

Need to go for sorting?

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

Easiest thing is to rebuild your coolers from pairs using a properly sorted chromsizes file:

https://github.com/open2c/distiller-nf/blob/master/sorted_chromsizes/hg38.reduced.chrom.sizes

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

Ok. let me try that. Thanks.

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

I got a new error

Screen Shot 2022-07-12 at 1 12 07 PM

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

Did you "look above for the error message" as it says?

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

Yeah but it's just the log like the previous image

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

The log should contain somewhere the actual error that caused the workflow to terminate. You can browse the complete log file printed on the last line of what you posted.

There's no way I can solve your issue without that information.

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

This is the complete log
Screen Shot 2022-07-12 at 2 19 15 PM

@nvictus
Copy link
Member

nvictus commented Jul 12, 2022

Hmm. That's strange. Looks like it might be a resource problem. What are the specs on your machine, cores & memory?

@Sen0108
Copy link
Author

Sen0108 commented Jul 12, 2022

I am working in cluster under conda environment. We can go as much as 40 vCPUs core and maximum RAM = 372 GB

@Sen0108
Copy link
Author

Sen0108 commented Jul 14, 2022

I tried with another machine having specification 7 (11th Gen), GPU (RPX3060), RAM =16 GB. But the same problem occurred

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

2 participants