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

Question: Why is this score 35, and not 36 #117

Open
movermeyer opened this issue Apr 18, 2018 · 8 comments
Open

Question: Why is this score 35, and not 36 #117

movermeyer opened this issue Apr 18, 2018 · 8 comments

Comments

@movermeyer
Copy link

This was the starting position of a puzzle:
odd_score

Why is the displayed score of this is 35, and not 36?:

1 gap         = -4
0 gap extends =  0
40 matches    = 40
0 mismatches  =  0
              -----
                36

Tested on PHYLO Web v2.0.1

@movermeyer movermeyer changed the title Question: Why is the score 35, and not 36 Question: Why is this score 35, and not 36 Apr 18, 2018
@waldispuhl
Copy link

Sorry for the delay, I havent noticed your comment earlier.
We actually modified the scoring scheme and counting gap extends at extremities (no gap open though).
We will post more info on the website ASAP.

@movermeyer
Copy link
Author

Thanks.

I've been trying to reverse engineer the scoring algorithm to get a better understanding of what makes a good alignment. But I keep getting tripped up by cases that don't seem to match the counts displayed at the top.

I'm looking forward to seeing the new code and better docs/info on the site.

@waldispuhl
Copy link

We have developed a customized version of the Fitch algorithm. Are you familiar with it. I'll try to retrieve a PDF explaining the exact scheme and post it. We are planning to release more material about it in upcoming the month.

@movermeyer
Copy link
Author

I can't say I'm familiar with it (or genomics in general. I'm just learning now).
I'll take a look. I found this nice looking PDF for Fitch's Algorithm. But It'll be nice to see how yours differs.

@akashzcoder
Copy link

akashzcoder commented Apr 25, 2018

There is an additional attribute in the scoring type2: trail score penalty. This has been recently added to phylo which is why game GUI is not reflecting the trail score.
New score works like this: subScore = ((match * 1) + (mismatch * (-1)) + open*(-4)+ extend*(-1) + trail*(-1));
38951307-bba9efc8-4337-11e8-8e36-d6b61f82f172-2
Since, this puzzle was occupying a length of 20(max number of nucleotides in each sequence) in the original gene sequences, hence an increase in length gives a trail penalty to the other sequence. This is because when the solution will be aggregated in the original MSA then this trail will also behave like a gap.

@akashzcoder
Copy link

The following concern has been addressed. Please find the update below:
image_new

@chrisdrogaris
Copy link

Hi movermeyer

An updated build with the trail parameter added can be found on this link :
https://phylo.cs.mcgill.ca/play.html

@movermeyer
Copy link
Author

@chrisdrogaris Thanks. While I now understand why it exists, it doesn't have an explanation yet in the info dialog:

explanation

Two other questions:

  1. When does the version number change? It still says v2.0.1. Or is that link considered "beta" and the version hasn't been bumped yet?
  2. When will the code be made available on GitHub?

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

4 participants