You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was using the pwmscan scan-sequence.py for my regions of interest. I have a question about the scores generated in the output files. Are the scores the number of weight or are they the relative scores described in JASPAR website?
are the the scores normalized as described as following?:
"Normalize the weight scores. For example, a threshold of W=5 could be good for SOX2 but will be far from optimal for REST, so, to avoid this problem the weights (or scores) are normalized where the highest weight (score) corresponds to a Relative score of 100 or 1000 (depending the granularity). A Relative score of 800 will consider all the binding sites above that number independently of the matrix width and the weight, maybe a Score of 800 in Sox2 corresponds to a weight of 5, whilst in REST corresponds to a weight of 12."
The text was updated successfully, but these errors were encountered:
Hello, I was using the pwmscan scan-sequence.py for my regions of interest. I have a question about the scores generated in the output files. Are the scores the number of weight or are they the relative scores described in JASPAR website?
are the the scores normalized as described as following?:
"Normalize the weight scores. For example, a threshold of W=5 could be good for SOX2 but will be far from optimal for REST, so, to avoid this problem the weights (or scores) are normalized where the highest weight (score) corresponds to a Relative score of 100 or 1000 (depending the granularity). A Relative score of 800 will consider all the binding sites above that number independently of the matrix width and the weight, maybe a Score of 800 in Sox2 corresponds to a weight of 5, whilst in REST corresponds to a weight of 12."
The text was updated successfully, but these errors were encountered: