similar to: text search in r

Hiya, I am trying to look at the similarities between a number of sequences, for example i am trying to see how similar "ababbbassdaa" is to "addffggssbbsbbs" I was wondering is the some way for me to see how similar they are in terms of, for example, number of a's, number of b's, how often a and ab are consecutive, how often abab is together etc. Any advice

On 03/02/2015 02:38 AM, Oliver Welter wrote: > Guys, dovecot is open source - if you desire a feature that the upstream > programmer did not include, pay him a bounty to do so or send him a > patch to be included. Period. We can discuss and mightbe somebody will > fork if he is not willing to accept such a solutuion for any political > reason. > > I am really tired of reading

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Steffen Kaiser wrote: > passdb { driver = ipdeny args = <host>/matchpattern/action .... > *** } > With next passdb{} as 1st in chain: passdb { driver = checkpassword args = "/tmp/chktst ip=%r service=%s" result_success = continue result_failure = return-fail } and this script BEGIN /tmp/chktst #!/bin/bash echo

Is there a function to efficiently search for a subsequence within a vector? For example, with x <- 1:100 I'd like to search for the sequence c(49,50,51), and be told that it occurs exactly once, starting at location 49. (The items in the vectors might be numeric or character, and there might be repetitions within the search pattern or within the vector I'm searching.) Duncan

Hi, I was wondering I'm going about this in the correct way. I need to test if there are coding sequences or exons in hg19 which match a string of 100bp "D" i.e. [A,G or T]. However I'm getting a strange result. I get a hit on chr7, using the 100bp search however when I search with 60bp sequence of "D" I don't get any hits. library("BSgenome")

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 2 Mar 2015, Dave McGuire wrote: > On 03/02/2015 02:38 AM, Oliver Welter wrote: >> Guys, dovecot is open source - if you desire a feature that the upstream >> programmer did not include, pay him a bounty to do so or send him a >> patch to be included. Period. We can discuss and mightbe somebody will >> fork if he is