-
Notifications
You must be signed in to change notification settings - Fork 36
Add icLarUrsu1 #320
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
base: main
Are you sure you want to change the base?
Add icLarUrsu1 #320
Conversation
|
Hi @jesgomez, thanks for sending the EAR of Larinus ursus. |
|
ok |
|
|
Hi @CaroB-M, do you agree to review this assembly? |
|
No |
|
@CaroB-M Ok thank you, I will look for the next reviewer on the list :) |
|
|
Hi @tommathers, do you agree to review this assembly? |
|
@tommathers Ok thank you, I will look for the next reviewer on the list :) |
|
|
Hi @SarahPelan, do you agree to review this assembly? |
|
yes |
|
Thanks for agreeing! |
SarahPelan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
I've checked this one and here's what I think:
SUPER_1:
~43,880 and ~73,846 both look like retained haplotype
SUPER_1_unloc_1:
I think this looks like a chromosome rather than being part of SUPER_1, scaffold_58 can join this new chromosome, probably as an unloc piece
SUPER_2:
~80,964-81,231 needs to move to ~71,652
SUPER_3:
I think you can join the unloc piece in at ~63,358 but the piece from 6,367-end of unloc_1 looks like duplication so needs removing.
SUPER_4:
~20,709-21,565 looks like duplication of SUPER_18 ~21,940
SUPER_6:
I think that ~80,964 to the end needs to flip
SUPER_10:
I don’t think the sequence at the start 0-2,889 belongs here. I think it would be better in the shrapnel as it doesn’t convincingly seem to fit anywhere
~20,334-25,846 looks like retained haplotype
I think super_10_unloc 1 is retained haplotype
super_10_unloc_2 matches to a few other places so put in the shapnel
SUPER_13:
~35,211 joined on telomeres, break here and rejoin ends together
SUPER_15:
39,652-46,074 looks like this should flip but there are no gaps here? Can you check?
SUPER_20:
Can you check the telomere tag at ~4,923?
It looks like 0-4,923 might go in at ~16,374, multi mapping reads may help to place the first part of this piece
scaffold_20 can join into SUPER_20 at ~32,374
scaffold_41 looks like it belongs somewhere in SUPER_10
scaffold_68 looks like duplication
scaffold_63 can join to start of SUPER_6
It might help to include multi-mapping reads when you make your updated pretext if you haven’t already.
Thanks,
Sarah
|
uoo, that was really useful, thanks a lot Sarah!! I indded had several doubts with this one and you gave suggestions for most of those doubtful locations. I implemented most of the changes you suggested,you can check by loading the new savestate I produced. You can find below some additional comments. BTW, this map is already including multimappings (it was obtained with mq0). SUPER_1: SUPER_1_unloc_1: SUPER_3: SUPER_4: SUPER_6: SUPER_10: SUPER_13: SUPER_15: SUPER_20: scaffold_20 can join into SUPER_20 at ~32,374 --> I agree, done |
|
Hi again, SUPER_1: 43,880-44,308Kbp and 73,044-73,846. Off diagonal signals and coverage drop here SUPER_13: I don’t think this flips, just break and join ends together in the same orientation. SUPER_15: I wouldn’t remove the piece you have tagged as haplotig in your savestate, looks like just repetitive region and should be included SUPER_20: I agree, add super_20 0-1,658kbp to shrapnel Thanks, |
|
ok, thank you Sarah. I applied the last changes you suggested, you can check them in savestate_3 if you wish. Now, if you all agree I'll produce an updated genome and submit the editted EAR soon. |
|
Can you send a link to your savestate_3 if you want me to look? |
|
That looks sensible thanks. |
|
Ping @tbrown91, |
|
Attention @tbrown91, the EAR PDF was updated. |
Assembly review request