 Research
 Open Access
 Published:
xHMMER3x2: Utilizing HMMER3’s speed and HMMER2’s sensitivity and specificity in the glocal alignment mode for improved largescale protein domain annotation
Biology Direct volume 11, Article number: 63 (2016)
Abstract
Background
While the localmode HMMER3 is notable for its massive speed improvement, the slower glocalmode HMMER2 is more exact for domain annotation by enforcing full domaintosequence alignments. Since a unit of domain necessarily implies a unit of function, localmode HMMER3 alone remains insufficient for precise function annotation tasks. In addition, the incomparable Evalues for the same domain model by different HMMER builds create difficulty when checking for domain annotation consistency on a largescale basis.
Results
In this work, both the speed of HMMER3 and glocalmode alignment of HMMER2 are combined within the xHMMER3x2 framework for tackling the largescale domain annotation task. Briefly, HMMER3 is utilized for initial domain detection so that HMMER2 can subsequently perform the glocalmode, sequencetofulldomain alignments for the detected HMMER3 hits. An Evalue calibration procedure is required to ensure that the search space by HMMER2 is sufficiently replicated by HMMER3. We find that the latter is straightforwardly possible for ~80% of the models in the Pfam domain library (release 29). However in the case of the remaining ~20% of HMMER3 domain models, the respective HMMER2 counterparts are more sensitive. Thus, HMMER3 searches alone are insufficient to ensure sensitivity and a HMMER2based search needs to be initiated. When tested on the set of UniProt human sequences, xHMMER3x2 can be configured to be between 7× and 201× faster than HMMER2, but with descending domain detection sensitivity from 99.8 to 95.7% with respect to HMMER2 alone; HMMER3’s sensitivity was 95.7%. At extremes, xHMMER3x2 is either the slow glocalmode HMMER2 or the fast HMMER3 with glocalmode. Finally, the Evalues to falsepositive rates (FPR) mapping by xHMMER3x2 allows Evalues of different model builds to be compared, so that any annotation discrepancies in a largescale annotation exercise can be flagged for further examination by dissectHMMER.
Conclusion
The xHMMER3x2 workflow allows largescale domain annotation speed to be drastically improved over HMMER2 without compromising for domaindetection with regard to sensitivity and sequencetodomain alignment incompleteness. The xHMMER3x2 code and its webserver (for Pfam release 27, 28 and 29) are freely available at http://xhmmer3x2.bii.astar.edu.sg/.
Reviewers
Reviewed by Thomas Dandekar, L. Aravind, Oliviero Carugo and Shamil Sunyaev. For the full reviews, please go to the Reviewers’ comments section.
Author summary
Over the past decade, the OMICs frenzy from arrays to sequencing has swarmed genomic research with voluminous amount of data and elucidated lists of candidate genes/proteins. Yet, many of these genes/proteins remained not wellunderstood in relation to the observed phenotype. The major gap to our full understanding stems from our lack in complete gene/protein functions which, in turn, impedes researchers from assembling the sets of biomolecular mechanisms that can sufficiently explain the observed phenotype in these OMICs experiments; the knowledge of gene/protein functions is a premise necessary for delivering the big promises in personalized medicine.
Despite so, experimental characterization of gene/protein function still receives insufficient attention nowadays. This can be attested by the dwindling number of characterized genes/proteins reported over the past decade. Sadly, one can expect this number to continue to grow at a slow rate.
On this basis, the only viable approach is to computationally transfer function annotation of the wellstudied gene/protein sequences to the lessstudied or novel ones for functional hints. Implicitly, this entails that these insilico function annotations must always be kept consistent regardless of the revisions made to function annotation databases or associated software tools used during the computations.
Background
The value of biomedical and biotechnological applications from biomolecular sequence information is generally limited by the degree of functional annotation of noncoding genomic regions, proteincoding genes and the proteins themselves [1, 2]. Whereas experimental characterization of all genes in all organisms is out of question by their sheer number, computational annotation transfer from a smaller number of wellstudied proteins greatly expands the space of functionally characterized protein sequences [3–5].
While lexical analysis and certain simple sequence motiffunction correlations are helpful for understanding functions for nonglobular protein segments, the homology concept based on significant levels of sequence similarity (mostly with regard to the hydrophobic pattern and functional residues indicative for conservation of fold, structure and function) is the foundation for understanding functions of globular protein regions [3–5]. A pair of sequences is considered homologous as a result of a statistical assessment of their alignment with a statistical mutation model quantified with an Evalue criterion.
Since an element of chance implies a chance for error, unjustified annotations can arise and percolate into databases [6–9]. Thus, functional annotation is a challenging and nontrivial task [9–15].
Traditionally, largescale domain function annotation is achieved through the HMMER [16–18] algorithm with companion domain libraries like Pfam [19, 20] and SMART [21, 22]. This involves searching against a library of functional domains for each query protein sequence, a process that needs to be repeated for all protein isoforms (many thousands even for bacterial genomes and typically dozens of thousands for a eukaryote genome) and for all genomes under study. The HMMER2 version with its glocal mode is highly valued by the genomics community for its exact domain placement over query sequences; i.e., it enforces full alignments to domain models (each domain being a unit of function); the latter being the modus operandi of the sequence homology concept. Additionally, HMMER2 is known for its reliability of Evalue guided domain assignments despite slow computation. Fortunately, the recent HMMER3 is marked by its quantum leap in computation speed that makes any largescale domain annotation task practical on standard computers. However, HMMER3 cannot reproduce HMMER2’s glocal mode alignments, it works just in the fragmented domain alignment mode. Hence, neither HMMER variants alone is a complete solution for practical largescale annotation of known globular domain given the large stream of new genomic data from the current era.
Taken together, the preceding conditions give rise to the utility and design rationale behind xHMMER3x2. First, the basic idea is to utilize HMMER3’s improved speed to first scan for statistically significant sequencetodomain hits. Then, the sequencetofulldomain alignments of these hits are reproduced through the glocalmode of HMMER2. Overall, this approach will greatly reduce the search space for HMMER2 so that xHMMER3x2’s overall speed will be most similar to HMMER3 while retaining the more desirable glocalmode alignments. The major aspect is then to ensure that the search space of glocalmode HMMER2 is sufficiently replicated by HMMER3 localmode for any given Evalue cutoff as faithfully as possible. We achieve this goal through the receiver operating characteristic (ROC) calibration of the domain library to be used by xHMMER3x2 so that the Evalues for every domain model from different builds are made comparable through the falsepositive rate measure.
In hindsight, the application of the calibration procedure on the Pfam domain library reveals three postcalibration findings that underline some of the fundamental differences between HMMER3’s search style and HMMER2’s glocal mode that justify for the necessity of xHMMER3x2 to unify both HMMER variants into a common framework. Another important outcome is that the falsepositive quantification by xHMMER3x2 results in a key step for flagging discrepancies in largescale domain annotation for manual scrutiny.
Results and discussion
Postcalibration finding 1: On average, HMMER3 Evalues need to be more stringent than HMMER2 glocalmode Evalues to exhibit the same FPR
The function annotation task via the HMMER algorithm is innately coupled to the domain libraries. In this work, the Pfam library (release 29) with a total of 16295 domain models was examined. Furthermore, to capture the same search space of glocalmode HMMER2 via the localmode HMMER3, a calibration (or normalization) procedure is needed to relate the different Evalues generated by either tool for the same sequences and domain models (See Methods on “Calibration procedure ..”).
Briefly, this entails the objective comparison of the receiver operating characteristic (ROC) curves generated by the two HMMER builds (i.e., HMMER2 and HMMER3) for each domain model. The query sequence set is specific to every domain model and it is composed of a positive set of α protein sequences (from the seed sequences of the Pfam domain model of interest, actually the potentially “true hits”) and the consensus sequences of the remaining 16294 domain models (if these sequences are hit, they are regarded as “false hits”).
Figure 1 depicts the falsepositive rate (FPR) value against the median Evalue of negative domain hits in Pfam library (release 29) for the two HMMER builds in a doubly logarithmic plot. The HMMER2 (in solid red) and HMMER3 (in solid blue) plots are shown with their interquartile ranges (IQRs) in dotted red and blue lines respectively. In a nutshell, the FPRs for each domain model are computed over 16294 negative domain consensus sequences of the Pfam library. For each domain, a list of i negative Evalues are sorted in ascending order and labelled with its order from 1 to i. The order is in fact the FP value and the FPR range for this domain is, hence, between 1/16294 and i/16294.
Over the full body of the Pfam library, we found in our test calculations that the falsepositive (FP) values span between 1 and 626 for HMMER2 and between 1 and 2143 for HMMER3. In turn, this translates to the sampled FPR ranges of between 6.14e5 (1 out of 16294) and 3.842 (626 out of 16294) for HMMER2 and between 6.14e5 and 1.32e1 (2143 out of 16294) for HMMER3. Then, at each sample FPR or FP points, the median Evalues of the negative domain hits of the Pfam library were taken to give the median Evalue ranges of between 2.13e9 to 2.40e + 1 for HMMER2 and between 1.35e20 and 7.1e2 for HMMER3. A reproducible feature to note for HMMER2 software suite is the occurrence of a breakpoint due to the switch in statistical model from the extreme value distribution (EVD) to the logistic model when the similarity score grows larger. In our previous work, the median Evalue of Pfam domain (release 23) for this switch occurs at 1.0e7 [10] which falls within the current (release 29) Evalue breakpoint range of between 10^{−3} and 10^{−8}.
Separately, the upper FPR limit of HMMER2 is lower than that of HMMER3 since it detects much less falsepositive hits than HMMER3. This is unsurprising since HMMER2 enforces complete sequencetodomain alignment when operating in glocalmode, while HMMER3 does not (and the occurrence of a sequence similar to a fraction of the domain suffices). And for the intended purpose of capturing the search space by HMMER2, the common upper limit of FPR at 5.60e3 (see label corresponding to 91 falsepositives in Fig. 1) is theoretically sufficient for both HMMER variants, albeit at different Evalue of 0.1 for HMMER2 and at 4.15e7 for HMMER3.
In any case, an overall comparison of the two negative domain hits plots reveals that the median Evalue needs to be more stringent in HMMER3 than in HMMER2 given a fixed FPR. The magnitude difference is about (10^{6} ~ 10^{11}) across the sampled range. This is consistent with the HMMER manual’s recommended Evalue cutoff of < <1 for HMMER3 and <0.1 (between 0.1 and 1 requires manual checking) for HMMER2 to gather trusted hits. As an example, when one imposes the recommended trusted domain Evalue cutoff of 0.1 for HMMER2, the corresponding FPR will be at 5.60e3 (see dotted vertical line). The latter translates into 91 falsepositive hits. Meanwhile, the equivalent HMMER3 Evalue will be 4.15e7 at this FPR setting. If extreme stringency is applied to achieve zero FP (i.e., FPR <6.14e5 or FP <1 given our search database size), then the required HMMER2 and HMMER3 Evalues will be at 2.13e9 and at 1.35e20 respectively (see leftmost dotted vertical line in Fig. 1).
However, complicated situations can arise as the HMMER2 and HMMER3 Evalues enter the lower FPR of below 5.6e3 (FP = 91) where the IQR of the two plots start to overlap. Essentially, this implies that there can be cases where the HMMER2 Evalues can exhibit higher stringency than its HMMER3 equivalent, therefore bucking the general trend of HMMER3’s stringency over HMMER2. As such, a direct comparison of Evalues from different HMMER builds even for comparable sequencetodomain alignments is not always a straightforward exercise.
Postcalibration finding 2: About 20% of HMMER2 domain models have better sensitivity than the HMMER3 counterpart over all the FPR range
After the domain library calibration procedure, the HMMER builds with the better sensitivity can be evaluated for the domain library. Briefly, the area under curve (AUC; see Eq. 1) of the HMMER2 and HMMER3 models are first computed for a fixed FP value, x. These evaluated FP values, which correspond to respective FPRs (in parentheses), are x _{1} = 1 (6.14e5), x _{2} = 5 (3.07e4), x _{3} = 10 (6.14e4), x _{4} = 20 (1.20e3), x _{5} = 30 (1.80e3), x _{6} = 40 (2.50e3), x _{7} = 50 (3.10e3), x _{8} = 60 (3.70e3), x _{9} = 70 (4.30e3), x _{10} = 80 (4.90e3), x _{11} = 90 (5.50e3) and x _{12} = 100 (6.14e3). Furthermore, to enhance the stability of the model selection, a predefined set of FP values A (see Eq. 2) and its associated model counts (Eqs. 3 and 4) are evaluated and taken as the overall criteria for model selection (See Methods on “ Criteria for domain model build…” for details).
Figure 2a depicts the total number (see Eqs. 5–7) of HMMER2 (in red), HMMER3 (in blue) and undetermined (in green) model builds selected by the various sets of FP. The FP set starts with all the evaluated FP values of 1 to 100. As the plot moves along the horizontal axis from left to right, the smaller FP values are dropped progressively. Based on the HMMER2 plot (in red), a stringent set of 3066 HMMER2 models were found to be more sensitive than their HMMER3 counterparts for all evaluated FP sets. As the smaller FP values are dropped, more HMMER2 domains were added until a maximum of 3502 models have been reached. This is about 21.5% of the evaluated Pfam domain library (release 29). Meanwhile, a large proportion of HMMER3 domain models remain more sensitive than their HMMER2 counterparts. Quantitatively speaking, this is between 68.5% (11158/16295) and 78.3% (12757/16295) of the domain library (blue plot). A sizeable percentage of domain models (up to 12.7% of the Pfam library) has shown to be fluctuating between HMMER2 and HMMER3 depending on the evaluated FP value set (green plot) and hence, not deterministic for selection.
Figure 2b shows the normalized AUC difference (see Eq. 1) being expressed as percentage and averaged over the sets of selected HMMER2/HMMER3/undetermined domain models corresponding to Fig. 2a. Basically, a large difference implies higher sensitivity of either the HMMER2 or HMMER3 models. Specifically for the HMMER2 sets (red plot), the average AUC difference ranges between 1.61 and 3.59% while this is held steadily at about 0.3% (blue plot) for the HMMER3 sets. For the sets of undetermined models, the average AUC difference stabilizes to 0% as more low FP values were excluded (green plot) and are hence deemed to perform closer to the HMMER3 models.
Overall, the domain sensitivity evaluation revealed that about 20% (between 3066 and 3502; see Additional file 1 from xHMMER3x2 website) of the HMMER3 models were found unsuitable for the initial domain scanning in the xHMMER3x2 workflow. Interestingly, these 3502 models were biased towards shorter domain models with a median of 171 alignment positions (IQR = 170). The latter is suggestive of alignment quality issues when coupled to the localmode HMMER3. In any case, these HMMER3 models cannot capture the HMMER2 search space sufficiently and hence, their HMMER2 model counterparts need to be used despite a longer computational speed. Fortunately, the slowdown caused by this 20% of the Pfam library is not detrimental; the slowest xHMMER3x2 will still outperform the standalone glocalmode HMMER2 at least by an order of magnitude (see below, Results section 5).
In hindsight, larger numbers of domain hits (which can include falsepositives at the same time) can generally be expected from localstyle search mode (as in HMMER3) compared with the glocal mode regime (as in HMMER2) since alignments over the full domain model are not enforced in the first case. Fortunately, HMMER3 provides larger number of hits and, as a trend, better sensitivity than HMMER2. However, on the flip side, HMMER3’s tendency towards partial domain coverage is insufficient to justify for function annotation transfer since a full domain necessarily implies a unit of function. The extent of HMMER3’s partial coverage over various FPR values is quantified in the next section.
Postcalibration finding 3: Average domain coverage by HMMER3 positive hits is about 88% of the domain model length
In a strict sense, partial sequencetodomain alignments generally do not justify for a sequence segment having the function of the domain hit since the completeness of a 3D structural unit (as implied by the domain unit) is a precondition for functional annotation transfer. The latter is especially relevant to HMMER3 since it can only operate in localmode.
To study the completeness of domain coverage by HMMER3, we first computed the average “coverage per domain model” by taking the total coverage of detected positive hits divided by the total detected positive hits at a FPR for a given domain model. Finally, an overall average is taken over all 16295 HMMER3build Pfam models. Figure 3a depicts across the sampled FPR range of between 6.14e5 and 6.14e3 (in logarithmic scale) together with the standard error bars at each evaluated FPR value. Briefly, the “coverage per domain model” gives an idea of how much the sequencetodomain alignment hits cover the domain model on average. If the domain coverage of a model is complete in all cases, then the average is expected to be one. Across the FPR range, the average domain coverage of the Pfam domain models with HMMER3 straddles at about 0.88 (see horizontal dotted line) with the lower limit (median1.5IQR) of the average domain coverage at about 0.85.
Although the average “coverage per domain model” remains relatively stable across all FPR values, incomplete domain coverage is expected to have different impact especially in cases of relatively long and of the shorter domain models. Figure 3b gives the distribution of domain length of the Pfam release 29 library. There are a total of 1801 domains with length of 485 alignment positions or more (i.e., >median + 1.5IQR; see vertical line in Fig. 3b). Therefore, the lack of coverage constitutes at least 58 ((1–0.88) × 484.5) missing alignment positions. The latter is about the size of the smallest known domain (e.g., zinc finger models); thus, completeness of the respective domain range in the query sequence is at least doubtful. On the other hand, there are 1429 with domains length of 58 alignment positions and less, where annotation transfers are even more unjustified under incomplete coverage. Taken together, these 3230 (1801 + 1429) implicated models make up almost 20% of the Pfam library. Therefore, despite HMMER3’s generally superior sensitivity, it suffices only for initial fast domain detection. Ultimately, HMMER2 will still be required for realignment over the full domain model, especially for the shorter ones.
The xHMMER3x2 workflow and webserver implementation
Figure 4 gives an overview of the threestaged xHMMER3x2 workflow. Briefly, xHMMER3x2 first invokes HMMER3 to scan for initial domain hits over a set of query sequences that matches the search space of HMMER2. The hits are then carried over to HMMER2 for refinement into full sequencetodomain alignments.
In the first stage of xHMMER3x2, N (3066 ~ 3502) HMMER2 and M (13229 ~ 12793) HMMER3 models can be utilized for the search (where N < <M) based on the sensitivity evaluation between HMMER2 and HMMER3 models in Fig. 2a. The upper Evalue limit is set to 0.1 for HMMER3 and 24 for HMMER2 which corresponds to the maximum sampled FP values of 2143 and 626 respectively according to Fig. 1. Essentially, the smaller search space of HMMER2 should be sufficiently captured.
Generally speaking, since the total number of utilized HMMER3 models far exceeds that of HMMER2 (80% versus 20%), the speed of xHMMER3x2 is expected to be closer to the faster HMMER3 than the slower glocalmode HMMER2. As such, reasonable computational speed can be achieved without sacrificing for detection sensitivity but with the caveat that the HMMER3 hits might be fragmented to various extents. Upon the selection of the appropriate model builds, the respective hmmpfam (HMMER2) and hmmscan (HMMER3) runs are executed with the respective sublibraries of HMMER2 and HMMER3 domain models.
In the second stage, the two runs from the dominant HMMER3 and the minority HMMER2 will result in K localmode and L glocalmode sequencetodomain alignments respectively for a given query sequence. The resulting K localmode alignments will be searched against the same K domain models but in glocalmode HMMER2. The latter is considered as the full domain realignment step as intended by glocalmode HMMER2 originally. Since the number of models used in the realignment step is expected to be much less than the total number of HMMER3 models used (i.e., K < <N < <M), this is an area of major speed gain by xHMMER3x2 over pure HMMER2. At the end of stage two, xHMMER3x2 would have produced K pairs of HMMER2/HMMER3 and L HMMER2 sequencetodomain hits over K + L domain models for every query sequence.
The third stage of xHMMER3x2 estimates the FPR (and FPs out of 16294) values of the domain hits based on their Evalues. For each domain model, the previously calibrated HMMER2/HMMER3 ROCs are purposed to assign the particular domain hits to the appropriate FPR interval based on their Evalues. The intervals are bounded by the evaluated FPR (FP) points: 6.14e5 (1), 3.07e4 (5), 6.14e4 (10), 9.21e4 (15), 1.20e3 (20), 1.50e3 (25), 1.80e3 (30), 2.50e3 (40), 3.10e3 (50), 3.70e3 (60), 4.30e3 (70), 4.90e3 (80), 5.50e3 (90) and 6.14e3 (100) as depicted in Fig. 4. The estimated FPR (FP) values of the domain hits are simply the nearest margin of their assigned FPR interval.
The overall xHMMER3x2 workflow is implemented as a software suite in PERL language. It is freely available for download at http://xhmmer3x2.bii.astar.edu.sg for local installation. Since xHMMER3x2 requires the carefullyselected domain models for its proper performance, the list of calibrated models for the recent Pfam domain libraries (release 27, 28 and 29) are also provided at the same site. Alternatively, an online webserver (for up to 1000 FASTAformatted sequences) exists at the download site as well. When multiple sequences are inputted, the result is returned via email in tabulated form as electronically readable file containing query sequences, Pfam model hits together with their alignments Evalues and standardized FPRs. Upon input of a single sequence, the HMMER2 and HMMER3 results are presented graphicallyenhanced for easy comparison.
xHMMER3x2 improves on computational speed over HMMER2 and domaindetection sensitivity over HMMER3
To evaluate the realworld performance of xHMMER3x2, the sequences and Pfam domain annotations of the human UniProt/SwissProt sequences were evaluated. The source file was extracted from the public resource at ftp://ftp.uniprot.org/pub/databases/uniprot/current_release/knowledgebase/complete/uniprot_sprot.dat.gz.
To create a reference set for evaluation purpose, the sequences were reannotated via the glocalmode HMMER2 against the Pfam domain library (release 29). Only the reannotated domains that overlap with the existing UniProt/SwissProt Pfam annotations were retained. The latter aims to exclude UniProt annotations that cannot be reproduced by this computation as a result of direct inheritance from previous releases, percolation errors, etc. Overall, our reannotation resulted in 27878 (out of 27988 reported annotations) Pfam domain hits which span across 17517 sequences over 5719 unique domain models. Since the complete human proteome is a moving scientific target [23], the reannotated set used here is only for benchmarking purpose only. The list of originallyreported and recomputed domain annotations for the human UniProt/SwissProt sequences is available at the xHMMER3x2 website (see Additional file 2). Furthermore, a cutoff Evalue of 1e9 (corresponds to the negative domain Evalue for FP < 1 in Fig. 1) was applied to derive a stringent set of 24696 positives domains which now covers 16175 sequences over 5509 unique domain models.
To examine the tradeoffs between computational speed and domaindetection sensitivity, these 16175 sequences were subjected to hmmscan/hmmpfam searches via HMMER3 (as reference), glocalmode HMMER2 and 5 configurations of xHMMER3x2 (where N = 3502, N = top 1500/1000/500 and N = 0) against the Pfam library (release 29). The top most sensitive HMMER2 domain models were ranked according to the AUC evaluation via Eq. 1.
Figure 5 illustrates the domaindetection sensitivity and speed differences against HMMER3 (in log scale) for both HMMER2 and xHMMER3x2. The horizontal dotted line across the xaxis sets the reference where there is no speed difference from HMMER3. The leftmost boxplot depicts the most timeconsuming HMMER2 at about 221 times (i.e., M _{ h2}/M _{ h3} = 10^{2.34}; see lefthand side of Eq. 12) slower than HMMER3, but with the improved sensitivity of 4.3% (100% versus 95.7%) over HMMER3. This translates to capturing 1074 more hits than HMMER3. In hindsight, this finding corroborates with our earlier postcalibration finding that some HMMER3 domain models have lower sensitivity than HMMER2.
For the various setting of xHMMER3x2, the fastest is achieved by running all HMMER3 models (i.e., N = 0; see rightmost boxplot) which is only 1.1 times (i.e., 10^{0.04}) slower than HMMER3 (due to the necessary full domain realignment of glocalmode HMMER2 in xHMMER3x2; see Fig. 4 Stage 2) but about 201 times (221÷1.1) faster than HMMER2. In hindsight, the realignment step of xHMMER3x2 does not impede its overall speed and the condition where K < <N < <M is generally true. However this is not without a caveat that its sensitivity has been compromised to 95.7% (same as HMMER3).
Meanwhile, the tradeoffs between speed and sensitivity can be observed when the various sets of selected HMMER2 models were invoked by xHMMER3x2. Based on Fig. 5, as N (i.e., the number of default HMMER2 models) decreases from 3502,1500,1000 to 500 (see second to fifth boxplots from left), xHMMER3x2’s sensitivity decreases from 99.8, 99.3, 99.1 to 98.6% respectively. In contrast, its speed increases accordingly from 32× (M _{ h2}/(M _{ h3} + K _{ h3}) = 10^{1.50}; see righthand side of Eq. 12), 17× (M _{ h2}/(M _{ h3} + K _{ h3}) = 10^{1.23}), 12× (M _{ h2}/(M _{ h3} + K _{ h3}) = 10^{1.07}) to 6× (M _{ h2}/(M _{ h3} + K _{ h3}) = 10^{0.80}) slower than HMMER3. Alternatively, this translates to 7 × (222÷32), 13 × (221÷17), 18.5 × (221÷12) and 37 × (221÷6.2) faster than HMMER2 respectively. Overall, the best compromise is achieved with the top 1000 most sensitive HMMER2 domains while the remaining as HMMER3 models. For most occasions, this configuration is the recommended and default mode in the xHMMER3x2 webserver since it achieves the best balance between domainsensitivity (at 99.1%) and speed (12× slower than HMMER3 but 18.5× faster than HMMER2). However, when fast annotation is the main consideration, xHMMER3x2 offers the “glocalmode HMMER3” as its fastest mode that is almost as fast as the native localmode HMMER3.
In summary, the xHMMER3x2 framework will always produce the glocalmode alignments and it can be configured to achieve a balance between speed and domaindetection sensitivity. On one extreme, it can be configured for full speed when all HMMER3 models are selected, thus mimicking a ‘glocalmode’ HMMER3. On the other end, when all HMMER2 models are deployed, xHMMER3x2 reverts back to HMMER2 with the highest level of domaindetection sensitivity.
Falsepositive quantification of calibrated domain hits allows for direct comparison between HMMER variants to evaluate for annotation consistency
At the end stage of xHMMER3x2, the FPR (FP) values for all the sequencetodomain hits would have been estimated accordingly. To evaluate the consistency of domain annotation, the 23622 common domain hits to both HMMER2 and HMMER3 from the preceding analyzed set of 16175 human UniProt/SwissProt sequences were further examined.
We define annotation consistency as the concordance in statistical assessment of same domain hits between HMMER2 and HMMER3 for a particular sequence segment. Figure 6a depicts the 23622 pairs of HMMER2/HMMER3 Evalues (as loglog plot) that now covers 5492 unique domain models. The set of blue points denotes the case where the estimated FP values of the paired HMMER2/HMMER3 hits matched exactly, while the red points denote the unmatched cases.
Based on the linear regression analysis, the mathematical relationship of HMMER2 against HMMER3 Evalues was found to be y = 0.72x, R ^{2} = 0.91 (matched cases) and y = 0.77x, R ^{2} = 0.22 (unmatched cases). In other words, the paired HMMER2/HMMER3 Evalues are not equivalent, and nonlinear to each other particularly for the unmatched cases given the bad R ^{2} (coefficient of determination) values. Additionally, about 86.5% of the pairs show higher stringency of HMMER2 Evalues over HMMER3, and vice versa for the remaining pairs. To reiterate, direct comparison using Evalues to determine concordance proves to be difficult. It is also important to remember that the evaluated Pfam annotations in UniProt are generally constrained to one domain hit per sequence segment. In more realistic settings, the same sequence segment can have multiple significant domain hits. In the absence of FPR estimation, the actual error rates associated to the overlapping domain hits will simply be masked behind a set of inseparable Evalues.
Utilizing the estimated FP values of the paired HMMER2/HMMER3 hits, the difference (i.e., FP_{H2}FP_{H3}) values were taken. The histogram of the 23622 pairs of FP difference values were shown in Fig. 6b. In contrast to the Evalue plot, 95% (22428) of the data points converges to the singular point at FP_{H2} = FP_{H3} or 0 (see blue dot). When the small difference of FP_{H2}FP_{H3} = ±4 (see vertical dotted lines) are also considered since FP values are approximated to their nearest values, the overall statistical concordance of the HMMER pairs makes up about 98% (addition of another 766) of the data points. As such, FP quantification by xHMMER3x2 offers an easy and quick way to check for general concordance of the paired HMMER2/HMMER3 hits.
Unique to xHMMER3x2, its FPR quantification helps to highlight an annotation inconsistency based on an observed leftskewness in the histogram. More specifically, a handful ([FP_{H2}FP_{H3} < −4] = 389) data pairs exhibited higher HMMER3 FPR than that of HMMER2 despite similar sequencetodomain alignments. These 389 outliers, which span across 140 unique Pfam domain models (see Additional file 3 from xHMMER3x2 website). Once again, the problematic domain models belong to the shorter ones; this set of 140 domains has a median length of 166.5 alignment positions (IQR = 204).
To resolve the annotation discrepancies, the sequences containing the 389 domain hits were subjected to a dissectHMMER [13–15, 24] analysis where pairs of HMMER Evalues are dissected into their foldcritical and remnant contributions. Briefly, it is the foldcritical parts (the supposedly 3D structural part) of a sequencetodomain alignment that argues for a similar overall fold, hence similar function whereas the remnant part represents disordered, fibrillary or other nonglobular regions that might be not obligatory for the domain fold [13, 14, 24]. As such, the Evalues of the foldcritical contributions has to be more significant than the remnant parts to justify for annotation transfer.
Figure 7 shows the boxplots of the total, foldcritical and remnant HMMER2 and HMMER3 Evalues of the 389 dissected domain hits. As a baseline for significance, the dotted horizontal line (at 1) denotes the HMMER2’s recommended Evalue of 0.1. The first two boxplots on the left shows that the total HMMER2 Evalues of the 389 unmatched cases displays higher significance than that of HMMER3. Meanwhile, the foldcritical Evalue boxplots display higher significance than the remnant boxplots whether for the case of HMMER2 or HMMER3. Additionally, both the foldcritical boxplots were considered significant when compared to their corresponding remnant counterparts. Taken together, the dissectHMMER analysis is strongly suggestive that these 389 HMMER2/HMMER3based Pfam annotations were justifiable by their foldcritical plots; the annotation discrepancy is resolved.
Scrutiny of the remnant boxplots further revealed that the remnant Evalues of the HMMER3 were so heavily penalized that they exceeded the recommended cutoff of 0.1 (−1 in log10 scale). Therefore, when the scores were added up as part of the total HMMER3 Evalues, the latter becomes much less significant than that of HMMER2 and hence their larger FPRs. It is likely that HMMER3 cannot justify any independent nonglobular alignment segments of the domain model without significant score compensation from other alignment pieces. Unfortunately, it is beyond the scope of this work to examine why the remnant segments of these particular HMMER3 models appeared to be so heavily penalized though this sheds some light on why certain HMMER3 models were less sensitive than their HMMER2 counterparts.
Conclusion
Protein domain function annotation for the experimentallyunverified ones is at best a computational prediction that is based on the statistical evaluation of the sequence homology concept. With every new revision of any domain model library or the associated software tool, the corresponding annotation update becomes a frequent and routine task; the task of ensuring annotation consistency with every software or library migration is rarely cared for. Simultaneously, as more new genomes are being churned out, the need for a reliable and fast protein annotation workflow, that takes into account of annotation consistency, cannot be ignored.
In this work, the proposed xHMMER3x2 annotation framework is squarely aimed at alleviating both annotation discrepancies and speed issues that can arise from practical largescale protein annotations. Notably, its scalability will allow for the future inclusion of newer HMMER variant. It simply requires the calibration of this new variant over a common domain library to allow its Evalues to be compared against the others for selecting the most sensitive variantdependent domain model amongst all. The remaining task is then to carefully balanced for the annotation speed.
Methods
Calibration procedure for HMMER2 and HMMER3 domain models towards comparable falsepositive rates
The function annotation task via the HMMER algorithm is innately coupled to the domain libraries. The calibration procedure used here is generally applicable to any domain libraries to normalize between the two different model builds. It aims to capture the search space of glocalmode HMMER2 via the localmode HMMER3, therefore relating the different Evalues generated by the two HMMER variants. In a nutshell, we determined the truepositive rate (i.e., sensitivity) and falsepositive rate (i.e., 1specificity) for the two HMMER builds (i.e., HMMER2 and HMMER3) of any domain model.
The calibration workflow is schematically shown in Fig. 8. In stage 1 of Fig. 8, the “hmmsearch” sequencetodomain alignments and corresponding Evalues of the two HMMER variants are first produced over a query set of α + 16294 sequences for every domain model. The query sequence set is specific to every domain model and it is composed of a positive set of α protein sequences (from the seed sequences of the Pfam domain model of interest, actually the potentially “true hits”) and the consensus sequences of the remaining 16294 domain models (if these sequences are hit, they are regarded as “false hits”). The query sequences are extracted from the Pfam domain library alignments and are downloaded from ftp://ftp.ebi.ac.uk/pub/databases/Pfam/releases/Pfam29.0/PfamA.full.gz.
Aside applying the Evalues cutoff of 1000 to capture as many hits as possible, the Evalues were also calculated for the database size of 16295 (via the z option) instead of α + 16294, so that the Evalues will corroborate with hmmpfam(HMMER2)/hmmscan(HMMER3) search results in the subsequent xHMMER3x2 workflow. At the end of stage 1, two separate computations would have been executed and produced β HMMER2 and γ HMMER3 sequencetodomain alignments over the space of α + 16294 query sequences.
In stage 2 of Fig. 8, the β glocal HMMER2 and γ local HMMER3 sequencetodomain hits can be stratified into paired HMMER2/HMMER3 hits, HMMER2only hits and HMMER3only hits. More specifically, the paired hits are HMMER2 and HMMER3 hits where the domain model sequences overlap (see dissectHMMER for details [13, 14]). The orphaned HMMER2 and HMMER3 hits are those that are found only by the HMMER variant itself. For the paired HMMER2/HMMER3 hits, each glocalmode HMMER2 hit is reconstructed to reproduce the local alignment made by its HMMER3 counterpart. As a result, a new Evalue for this reconstructed localmode HMMER2 alignment is also derived following published procedures [9, 13, 14].
In stage 3 of Fig. 8, the orphaned glocalmode and reconstructed localmode Evalues of HMMER2 are partitioned into their positive and negative sets (see red histograms). The same is done for the paired and orphaned HMMER3 Evalues (see blue histograms). For each designated Evalue cutoff, the respective falsepositive rates (FPR) and truepositive rates (TPR) can be quantified from the two sets of histograms. Consequently, the ROC (receiver operator curves) of HMMER2 (in red) and HMMER3 (in blue) can be overlaid on each other and made comparable at any FPR value. As an example, HMMER2 and HMMER3 require Evalue cutoffs of 0.1 and 0.01 respectively to achieve a falsepositive rate of 0.2 for the particular domain model used for this diagram. Also, the resulting AUC (area under curve) for HMMER3 is larger than that for HMMER2 at FPR = 0.2 based on the criteria (see blue box) and, hence, indicates better sensitivity.
It is important to note that marginally large FPRs or certain higher Evalues can nevertheless suggest correct yet distant hits rather than totally wrong ones. Thus, our computed FPRs reflect the worst case thresholds. For a domain library like Pfam with clan classification of families of related domains, this is especially true.
Criteria for domain model build selection
The base criteria for isolating a higher HMMER2 sensitivity at a particular FPR can be written into the conditional statement:
where AUC _{ diff } is the difference between the area under curves (AUC) of HMMER2 and HMMER3, x is a fixed false positive rate. Here, the AUC value is normalized to total area under evaluation where 16294 is the total number of negative domains for any Pfam domain (release 29) model. Furthermore, to ensure that the sensitivity of an evaluated domain model does not fluctuate at different absolute numbers of falsepositives (FPs), a counting mechanism is enforced to ensure that Eq. (1) holds over a set A which comprises of numbers of FPs or corresponding FPRs given as :
while, the equation for the count based on (1) for domain model y, can be written as follows:
where A is the cardinality of the set A of selected FPs of Eq. (2). As an example, a HMMER2 domain model is considered better than its HMMER3 alternate counterpart only when the following condition is satisfied :
Conversely, a zero count or count = 0 describes the opposite case where the sensitivity of the HMMER3 model is better than that of HMMER2 at all FP sets.
In our study, the set of selected cases of falsepositive hits (FP) corresponding to respective FPRs (in parentheses) are: x _{1} = 1 (6.14e5), x _{2} = 5 (3.07e4), x _{3} = 10 (6.14e4), x _{4} = 20 (1.20e3), x _{5} = 30 (1.80e3), x _{6} = 40 (2.50e3), x _{7} = 50 (3.10e3), x _{8} = 60 (3.70e3), x _{9} = 70 (4.30e3), x _{10} = 80 (4.90e3), x _{11} = 90 (5.50e3) and x _{12} = 100 (6.14e3).
Finally, the total number of selected HMMER2/HMMER3 and undetermined domain models for the set A of selected FP value, are as follows :
Theoretical speed improvement of xHMMER3x2 over glocalmode HMMER2
Theoretically, the speed improvement of xHMMER3x2 over the glocalmode HMMER2 algorithm can be quantified in the following manner. First, let the total run time of xHMMER3x2 for one sequence be defined as:
Also, let the run time of HMMER2 be defined as:
where M, N is the number of HMMER3 and HMMER2 models being used for a given FPR setting, K is the number of HMMER2 models used to realign the HMMER3derived sequencetodomain alignments (i.e., K ⊂ M), t _{ h3,i } and t _{ h2,i } refer to the HMMER3 and HMMER2 computational time required for domain model i.
Against HMMER2, the speed improvement (expressed by a factor f) is attributed to the set of M models. Therefore, let the relevant terms in xHMMER3x2 (see Eq. 8) and HMMER2 (see Eq. 9) be related by the factor f via the following:
Furthermore, let \( {\displaystyle \sum_{i=1}^M{t}_{h3,i}}={M}_{h3} \), \( {\displaystyle \sum_{k=1}^{K\subset M}{t}_{h2,k}}={K}_{h2} \) and \( {\displaystyle \sum_{i=1}^M{t}_{h2,i}}={M}_{h2} \) where t _{ h3,i } and t _{ h2,i } are a unit of time in HMMER2 and HMMER3 respectively, then Eq. (10) can be simplified as f[M _{ h3} + K _{ h2}] = M _{ h2} and rearranged as follows :
where random variables M _{ h3 } and M _{ h2 } describe the total time taken for a sequence to perform hmmscan (HMMER3) and hmmpfam (HMMER2) searches respectively, against a database of M domain models (Stage 1 of Fig. 4). Similarly, random variable K _{ h2 } is the total time taken for a sequence to complete hmmpfam search against a set of K domain models (Stage 2 of Fig. 4).
Finally, the theoretical upper limit of xHMMER3x2’s speed improvement over HMMER2 is bounded by \( \frac{M_{h2}}{M_{h3}} \) (i.e., HMMER2 versus HMMER3) as follows:
Reviewers’ comments
Reviewer’s report 1: Thomas Dandekar, Department of Bioinformatics, University of Wuerzburg, Germany
ChoonKong Yap et al. make a good case that HMMER3 speed and HMMER2’s sensitivity and specificity can be well combined for improved largescale protein annotation. All is made available for the interested reader, xHMMER3x2 is ready for use by the community.
There is not much to correct: the method is well explained and detailed, and, most of all, made fully available. Already the abstract explains that now the user has the choice from the script to go for faster annotation or higher accuracy (highest was 99.8%), fastest is HMMER3 glocal mode, but only 95.7% detection sensitivity. And again, all is well explained and as far as I can judge technically sound and well prepared I think what would now help to add, is a bit more practical experience (so simply explain in the discussion, what you already did do, did you for instance always take the “fast but sloppy” mode, so in essence HMMER3, or is there maybe a magical mix (such as BLOSUM62 with 62%) of HMMER2 optimal in your hands and in your experience? Finally, also comment how maybe future advances or other methods would influence this annotation procedure.
Authors’ response: We thank the reviewer for his comments. We have added in the discussion to advise users to run xHMMER3x2 configured with the top 1000 HMMER2 domains as the recommended mode since this has the best balance in terms of sensitivity and speed. Also, the webserver now flags this configuration as the recommended mode under the mode selection list. The discussion on how xHMMER3x2 will be influenced by future advances or other methods is included in the conclusion.
Reviewer’s report 2: L Aravind, Protein and Genome Evolution Research Group, Computational Biology Branch, NCBI/NLM/NIH
HMMER3 has revolutionized HMM based search approaches by speeding up the searches greatly. However, this has come at the cost of preciseness of domain annotation that HMMER2’s glocal mode allowed. The authors attempt to remedy this compromise by combining the initial search with HMMER3 for detecting the domain followed by a HMMER2like alignment procedure for the detected hits. Overall the glocal search procedure of HMMER2 does seem to provide more complete alignments which are often useful to ascertain domain boundaries. I have not compiled the program to run locally but testing on the server shows that it runs at comparable speed to a Pfam scan of single sequence with HMMER3.
I have no particular issues with the overall methodology. But I have some practical comments as a user who pays close attention to the quality of alignments: 1) Even though the technically the alignments produced by the webserver should be similar to a local HMMER2 Pfam scan, the examples I used produced “aesthetically” poorer alignments in that they were more gapridden. Is this arising from the attempt to cover the entire length of the Pfam model? 2) On trying a sequence where the match genuinely should not cover the entire Pfam model the alignments appear to be artificially stretched out to cover the entire length. While these issues might not greatly negatively affect an annotation pipeline for domains on a largescale they might still affect the use of this search for in depth domain analysis in particular cases.
Authors’ response: We thank the reviewer for his comments. For this work, all positions in the domain models’ seed multiple sequence alignments were considered during HMMER model building. On a largescale basis, it helps to simplify the HMMER2 versus HMMER3 sequencetodomain hit comparisons, especially for cases where missing domain model positions can vary between HMMER2 and HMMER3 due to their parameterization differences.
At the same time, the quality of the sequencetodomain alignment is also highly dependent on the curated seed alignments of the domain libraries. The visually poorer alignments as observed by the reviewer for the sequence example XP_002989768.1 was generated with Pfam release 29 for a pair of SBDS (PF01172) HMMER2/HMMER3 hits and a single SBDS_C (PF09377) HMMER2 hit. When the same example was tested on Pfam release 27, a stark improvement in alignment quality was made. Also, an additional SBDS_C (PF09377.5) HMMER3 domain hit, which covers about 2/3 of the model’s length, was also recovered. On closer examination of these alignments, we noted that the full model lengths of the SBDS and SBDS_C domains in Pfam releases 27 and 29 vary by 38 (132 versus 170) and 365 (234 versus 599) positions respectively. Mainly, the artificially stretched sequencetodomain HMMER2 SBDS_C hit as observed with Pfam release 29, was due to a much longer domain model which includes more nonglobular regions.
On a separate note, we wish to highlight that the seed alignments from Pfam release 28 and upwards were constructed from the reference proteome instead of the UniProt sequences. Given the same Pfam model, any differences in the seed sequences between releases will have a major impact on the final sequencetodomain alignment quality. The implication of this sequence database change, in terms of search sensitivity/specificity, alignment quality, etc. will require a separate scrutiny.
The search server could simplify the delivery of results by having the results directly presented rather than needing an additional click on the xHMMER3x2 query status page that is presented first.
Authors’ response: The search server has now simplified the delivery of results by having the results directly presented rather than needing an additional click on the xHMMER3x2 query status page.
Reviewer’s report 3: Oliviero Carugo, Chemistry Department, University of Pavia
The manuscript submitted by Eisenhaber and Wong describes a novel computational approach for protein function annotation on the basis of sequence similarity. A webserver is also presented, to allow biologists to use this computational methodology. The basic idea is to couple two methods. One, HMMER2, is slow and the other, HMMER3, is fast. However, HMMER2’s glocal more alignments cannot be performed by HMMER3. Moreover, HMMER2 is probably more reliable than HMMER3, especially in the Evaluebased domain assignments. The scientists lead by Eisenhaber and Wong designed an empirical interface, xHMMER3x2, which seems to be reliable and fast. Empirical parameters have been adapted based on PFAM29.
The manuscript is very technical and sometime not easy to read. Most of the users of the server will probably never read the manuscript, which is too complex for the average biologist. However, it is important to publish a detailed description of this computational method, to allow bioinformaticians to understand it and, possibly, to improve it. On the contrary I warmly suggest the Authors to prepare a more colloquial description of this methods and to make it available in the web pages at http://xhmmer3x2.bii.astar.edu.sg. This would greatly help biologists to try to understand the basics features of this method. About the computational procedure. Large use is made of the ROC curves. I have nothing again it. However, it is a better idea, in my opinion, to couple the ROC with the precisionrecall curves (see for example a simple description published by [25]). Eventually, the Authors are required to read carefully the manuscript, which contains some minor mistakes. For example, in the Introduction (lines 13 and 14) one can read “A pair of sequences is considered homologues …” while it should be “homologous” (adjective). Another example, in reference 4 is written “Edited by Edited by”. In fine, the resolution of the figures seem insufficient to me.
Authors’ response: We thank the reviewer for his comments. As suggested by the reviewer, a simplified description of our method is now available online and accessible via the “introduction” link right after the main title of the xHMMER3x2 webserver page. Alternatively, the link is given as http://xhmmer3x2.bii.astar.edu.sg/introduction.html .
With regard to the use of ROC in our work, it is squarely aimed at calibrating between two different builds of the same domain mode to select for the more sensitivity one to be executed in xHMMER3x2. In fact, ROC was not used for performance measure. Rather, xHMMER3x2 was evaluated simultaneously for both speed and sensitivity. Nevertheless, the precisionrecall (PR) curve helps to reveal any large class imbalance problem after the domain model calibration step. As such, the xHMMER3x2 webserver now presents a link to both the ROC and precisionrecall (PR) curves of every domain model in the returned results.
In hindsight, we are mindful of the limitations of any ratio measures (truepositive rates/recall rates, falsepositive rates, precision rates) that may mask the true characteristics of the underlying data. Therefore, xHMMER3x2 reports the absolute number of falsepositives (in discrete steps of FP = 1,5,10,15, …) that is associated to every sequencetodomain alignment hit, much like how the Evalues were intended for. Generally speaking, the FP range of 1 to 5 is relatively reliable for annotation purpose while any value beyond is considered for discovery purpose. As an example, Fig. 9 depicts the ROC and PR curves (HMMER3 in blue; HMMER2 in red) for the domain model PF03915 AIP3. From the figure, trusted AIP3 domain hits have the precision value of about 1.0 (see PR curve) with the truepositive/recall rate of about 0.4 (see ROC) as marked by FP = 1 and 5. Beyond that, the precision rate deteriorates with a synchronized increase in falsepositive rate.
Reviewer’s report 4: Shamil Sunyaev, Division of Genetics, Dept. of Medicine, Brigham & Women’s Hospital and Harvard Medical School
The authors try to find a balance between two versions of HMMER (the more recent version offering a much greater speed at the price of slightly reduced sensitivity). They offer an umbrella approach combining both versions and adding estimation of falsepositive rate. Although addressing a technical point, this work provides a potentially useful protein domain annotation software.
I find that the analysis of FPR should be clarified. The analysis suggests that Evalues for both versions of HMMER are not perfectly tuned. Is this due to specific assumptions in the statistical model of HMMER, or this is a result of the choice of the negative dataset?
Authors’ response: We thank the reviewer for his comments. Indeed, the reviewer’s first intuition is correct. The fundamental difference stems from the statistical models which gives rise to the different sets of HMMER2 and HMMER3 scoring parameters (i.e., the emission and transition probabilities). As such, even comparable sequencetodomain alignments can give quite different Evalues. In addition, when comparing alignments between partial HMMER3 and full HMMER2 hits, only the overlapping segments were considered for rederiving the HMMER2 scores. Despite so, these Evalues are still not comparable.
Abbreviations
 FPR:

False positive rate
 HMM:

Hidden Markov Model
 IQR:

Interquartile range
 ROC:

Receiver Operating Characteristics
 TPR:

True positive rate
References
 1.
Eisenhaber F. A decade after the first full human genome sequencing: when will we understand our own genome? J Bioinform Comput Biol. 2012;10:1271001.
 2.
Kuznetsov V, Lee HK, MaurerStroh S, Molnar MJ, Pongor S, Eisenhaber B, Eisenhaber F. How bioinformatics influences health informatics: usage of biomolecular sequences, expression profiles and automated microscopic image analyses for clinical needs and public health. Health Inf Sci Syst. 2013;1:2.
 3.
Bork P, Dandekar T, DiazLazcoz Y, Eisenhaber F, Huynen M, Yuan Y. Predicting function: from genes to genomes and back. J Mol Biol. 1998;283:707–25.
 4.
Eisenhaber F. Bioinformatics: mystery, astrology or service technology. In: Eisenhaber F, editor. Discovering biomolecular mechanisms with computational biology. 1st ed. Georgetown and New York: Landes Biosciences and Springer; 2006. p. 1–10.
 5.
Eisenhaber F. Prediction of protein function: two basic concepts and one practical recipe. Chapter 3. In: Eisenhaber F, editor. Discovering biomolecular mechanisms with computational biology. 1st ed. Georgetown: Landes Biosciences and Eurekah.com; 2006. p. 39–54.
 6.
Gilks WR, Audit B, De Angelis D, Tsoka S, Ouzounis CA. Modeling the percolation of annotation errors in a database of protein sequences. Bioinformatics. 2002;18:1641–9.
 7.
Gilks WR, Audit B, de Angelis D, Tsoka S, Ouzounis CA. Percolation of annotation errors through hierarchically structured protein sequence databases. Math Biosci. 2005;193:223–34.
 8.
Ouzounis CA, Karp PD. The past, present and future of genomewide reannotation. Genome Biol. 2002;3:COMMENT2001.
 9.
Wong WC, MaurerStroh S, Eisenhaber F. More than 1,001 problems with protein domain databases: transmembrane regions, signal peptides and the issue of sequence homology. PLoS Comput Biol. 2010;6:e1000867.
 10.
Wong WC, MaurerStroh S, Eisenhaber F. The Janusfaced Evalues of HMMER2: extreme value distribution or logistic function? J Bioinform Comput Biol. 2011;9:179–206.
 11.
Wong WC, MaurerStroh S, Eisenhaber F. Not all transmembrane helices are born equal: Towards the extension of the sequence homology concept to membrane proteins. Biol Direct. 2011;6:57.
 12.
Wong WC, MaurerStroh S, Schneider G, Eisenhaber F. Transmembrane helix: simple or complex. Nucleic Acids Res. 2012;40:W370–5.
 13.
Wong WC, MaurerStroh S, Eisenhaber B, Eisenhaber F. On the necessity of dissecting sequence similarity scores into segmentspecific contributions for inferring protein homology, function prediction and annotation. BMC Bioinformatics. 2014;15:166.
 14.
Wong WC, Yap CK, Eisenhaber B, Eisenhaber F. dissectHMMER: a HMMERbased score dissection framework that statistically evaluates foldcritical sequence segments for domain fold similarity. Biol Direct. 2015;10:39.
 15.
Eisenhaber B, Kuchibhatla D, Sherman W, Sirota FL, Berezovsky IN, Wong WC, Eisenhaber F. The recipe for protein sequencebased function prediction and its implementation in the ANNOTATOR software environment. Methods Mol Biol. 2016;1415:477–506.
 16.
Durbin R, Eddy S, Krogh A, Mitchison G. Biological sequence analysis: Probabilistic models of proteins and nucleic acids. 1998.
 17.
Eddy SR. What is a hidden Markov model? Nat Biotechnol. 2004;22:1315–6.
 18.
Eddy SR. A probabilistic model of local sequence alignment that simplifies statistical significance estimation. PLoS Comput Biol. 2008;4:e1000069.
 19.
Finn RD, Mistry J, Tate J, Coggill P, Heger A, Pollington JE, Gavin OL, Gunasekaran P, Ceric G, Forslund K, et al. The Pfam protein families database. Nucleic Acids Res. 2010;38:D211–22.
 20.
Sammut SJ, Finn RD, Bateman A. Pfam 10 years on: 10,000 families and still growing. Brief Bioinform. 2008;9:210–9.
 21.
Letunic I, Doerks T, Bork P. SMART 6: recent updates and new developments. Nucleic Acids Res. 2009;37:D229–32.
 22.
Schultz J, Milpetz F, Bork P, Ponting CP. SMART, a simple modular architecture research tool: identification of signaling domains. Proc Natl Acad Sci U S A. 1998;95:5857–64.
 23.
Sirota FL, Batagov A, Schneider G, Eisenhaber B, Eisenhaber F, MaurerStroh S. Beware of moving targets: reference proteome content fluctuates substantially over the years. J Bioinform Comput Biol. 2012;10:1250020.
 24.
Wong W. C, MaurerStroh, S, Eisenhaber B, Eisenhaber F. HMM score dissection website. 2014. [http://mendel.bii.astar.edu.sg/SEQUENCES/ProblemDomainsHMMscoredissection/]
 25.
Lever J, Krzywinski M, Altman N. Points of Significance: Classification evaluation. Nat Methods. 2016;13:603–4. A.D.
Acknowledgements
The authors acknowledge the help of Mr. Yong Taipang and his IT team support.
Funding
Supported by A*STAR Singapore, the grants “A*STARNKTH JGC 007”, “SERC IMaGIN”, and “IAF CAT3 Integrated Genomics Platform”.
Availability of data and materials
All supporting data is available at xhmmer3x2.bii.astar.edu.sg
Authors’ contributions
WCW, BE and FE conceived and designed the experiments: YCK implemented the software and performed the experiments. WCW, YCK, BE and FE analyzed the data. All authors wrote, read and approved the final manuscript.
Competing interests
The authors declare that they have no competing interests.
Consent for publication
Not applicable.
Ethics approval and consent to participate
Not applicable.
Author information
Affiliations
Corresponding authors
Additional files
Additional file 1:
List of top 1500/1000/500 better HMMER2 Pfam29 domain models. (TXT 76 kb)
Additional file 2:
List of original vs recomputed Pfam domain annotations for the human UniProt/SwissProt sequences. (TXT 12216 kb)
Additional file 3:
List of 140 Pfam domains with annotation inconsistencies. (TXT 10 kb)
Rights and permissions
Open Access This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The Creative Commons Public Domain Dedication waiver (http://creativecommons.org/publicdomain/zero/1.0/) applies to the data made available in this article, unless otherwise stated.
About this article
Cite this article
Yap, CK., Eisenhaber, B., Eisenhaber, F. et al. xHMMER3x2: Utilizing HMMER3’s speed and HMMER2’s sensitivity and specificity in the glocal alignment mode for improved largescale protein domain annotation. Biol Direct 11, 63 (2016). https://doi.org/10.1186/s1306201601630
Received:
Accepted:
Published:
Keywords
 Sequence homology
 Hidden Markov model
 Sequence similarity search
 Foldcritical sequence segment
 Nonglobular sequence segment
 Similarity score dissection