I'm having a little trouble understanding the difference between the e-value given when I use BLAST to align two sequences vs the e-value's given when I run BLAST for the same query sequence against a database.
For example, when I run BLAST between human myoglobin and human neuroglobin, the e-value given is 3e-4. But then, when I run BLAST for human myoglobin against a refseq protein database, human neuroglobin doesnt appear since it didn't reach the e-value cut threshhold (which is indeed bigger than 3e-4). So, I know the e-value is proportional to the query length(this doesnt change since i'm running human myoglobin in both cases), the database length, and that it decreases exponentially with the score. I'm assuming that the score shouldn't change in both cases (i'm using the same parameters), so the only thing that's left that can explain why human neuroglobin doesn't appear in the BLAST search is that the database length is different in the pairwise alignment, even though i'm selecting the same refseq protein database in both cases. This prompts me to think that when I run BLAST for a pairwise alignment, the database length used to calculate the e-value is just the length of the target sequence or the sum of both the query and target lengths. Is this so?