Skip to content
This repository was archived by the owner on Jul 18, 2023. It is now read-only.

The parameters of Module 'draft-path' #129

Open
nottwy opened this issue Sep 12, 2017 · 25 comments
Open

The parameters of Module 'draft-path' #129

nottwy opened this issue Sep 12, 2017 · 25 comments

Comments

@nottwy
Copy link

nottwy commented Sep 12, 2017

Dear developer,

I want to make sure some parameters that module 'draft-path' uses.

hinge draft-path $PWD $db hsy50x.G2.graphml

  1. I use the name of daligner database here. Is it correct?
  2. should I use G2 or G3?

In your manual, you write G2. But in a issue,'#77', you write G3 there. Is there any difference?

thank you.

@nottwy nottwy changed the title draft-path parameters The parameters of Module 'draft-path' Sep 12, 2017
@govinda-kamath
Copy link
Collaborator

Yes. The name of the daligner database as $db. And you should use G2. G3 is still an experimental module for larger genomes.

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

@govinda-kamath ,
I'm assembling a large genome. And I don't see G3 file.
I run the pipeline provided in issue '#77', but I don't see the G3 file. Is it caused by a wrong operation?

@govinda-kamath
Copy link
Collaborator

Which commit of the software are you running?

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

I install it in Jun 28,2017 with git clone.
Which file should look to see the commit?

@govinda-kamath
Copy link
Collaborator

git log

should give you the commit that you installed.

But it's weird that there is no G3.

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

The first few rows look like this:
commit 459e309
Author: Govinda Kamath [email protected]
Date: Wed Jun 21 16:20:54 2017 +0530

@govinda-kamath
Copy link
Collaborator

This should actually still be producing a G3 file. Can you confirm the size of the G2 file?

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

464K Sep 12 14:29 hsy50x.G2c.graphml
418K Sep 12 14:29 hsy50x.G2s.graphml
457K Sep 12 14:29 hsy50x.Gc.graphml
411K Sep 12 14:29 hsy50x.Gs.graphml
756K Sep 12 14:29 hsy50x.G1.graphml
756K Sep 12 14:29 hsy50x.G2.graphml
4.5M Sep 12 14:29 hsy50x.G0.graphml
6.7M Sep 12 14:28 hsy50x.G00.graphml

@govinda-kamath
Copy link
Collaborator

govinda-kamath commented Sep 12, 2017

It looks like something went wrong in the clip run. G0, G1, G2, G3 are usually of similar sizes.

Can you return the STDOUT of the run of the draft-path?

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

command:
$hinge clip hsy.edges.hinges hsy.hinge.list 50x

output:
Tue Sep 12 16:49:22 CST 2017
0 bad coverage reads.
0 bad self aligned reads.
Tue Sep 12 16:50:43 CST 2017

Files generated:

756K Sep 12 16:50 hsy50x.G2.graphml
409K Sep 12 16:50 hsy50x.G2s.graphml
415K Sep 12 16:50 hsy50x.Gs.graphml
4.5M Sep 12 16:50 hsy50x.G0.graphml
756K Sep 12 16:50 hsy50x.G1.graphml
6.7M Sep 12 16:50 hsy50x.G00.graphml

@govinda-kamath
Copy link
Collaborator

Can you give us the hsy.edges.hinges and hsy.hinge.list files? These files contain no sequence information, in case you're worried about privacy.

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

I can provide it to you.
But when I prepare the data, I made a mistak and deleted 'hsy.hinge.list'.
I know you want to rerun in your local machine so it's useless if I only provide you 'hsy.edges.hinges'.

It must be a mistake of your program. And now I want to know, is it ok if I use G2 file?

@govinda-kamath
Copy link
Collaborator

Sure. You can. Though it looks like the code crashed somewhere there (so I'm not sure about if the results will be kosher).

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

it needs one or two day to get the file 'hsy.hinge.list'.
And I will mail it to you after I rerun the program. Can you provide me your email?

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

Another question, do you think HINGE is suited for a large genome with relative high repeat content? The size of our genome is ~1 Gb.

@govinda-kamath
Copy link
Collaborator

govinda-kamath commented Sep 12, 2017 via email

@govinda-kamath
Copy link
Collaborator

govinda-kamath commented Sep 12, 2017 via email

@nottwy
Copy link
Author

nottwy commented Sep 12, 2017

~1 Gb

@govinda-kamath
Copy link
Collaborator

govinda-kamath commented Sep 12, 2017 via email

@nottwy
Copy link
Author

nottwy commented Sep 15, 2017

Have you received my email?

@govinda-kamath
Copy link
Collaborator

Yes. We'll get back to you soon.

@ilanshom
Copy link
Collaborator

There were a few small issues with hinge clip that were preventing it from creating the G3 graph. We created a new branch called devG3, which should fix that.

In order to have the G3 graph produced, you should make sure that aggressive_pruning = true is in your nominal.ini file (we added it in devG3), and you should call hinge clip with the path to the ini file as the fourth argument. So your command should look like:

hinge clip hsy.edges.hinges hsy.hinge.list test path-to-ini/nominal.ini

Let us know if this works.

@nottwy
Copy link
Author

nottwy commented Sep 20, 2017

OK, I'll install devG3 branch and try as you suggested. I'll give you a reply as I get a result.

@nottwy
Copy link
Author

nottwy commented Oct 20, 2017

Before I report my result I want to say another thing: Your tool is really difficult to compile. I'm serious.
And now let's return to our topic. I haven't installed the devG3 branch successfully yet. I try to run the clip step with the old version of hinge. And it gives me an error message like this:
bad coverage reads.
0 bad self aligned reads.
couldn't finish sparsification10328
couldn't finish sparsification10382

I will try to install the devG3 branch and try again. And I hope this error message can help you solve other problems of hinge. I'll report the progess of devG3 in this issue later.

@govinda-kamath
Copy link
Collaborator

These are just reports on the graph about visualisation, not error messages. You should be able to continue on the pipeline.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants