Sentence examples for database estimation from inspiring English sources

By removing the length bias from the EST database estimation, we achieve agreement between the two sets of data, thus explaining the apparent contradiction.

The bias in the abundance within the EST database estimation of the expression level is approximately proportional to the gene length, as shown by the linear regression in Figure 4. Also shown in Figure 4 is the same length bias when the abundance is calculated from the full WormBase EST database [ 30, 31], rather than by the method that separates the data into two developmental stages [ 22].

For this reason, sequences were aligned both to a reference transcript database (for estimation of expression of well-annotated transcripts) and to the human genome (for estimation of total expression of all exons, whether annotated or not).

Section 2 describes the database, the estimation of the public pay gaps with micro data, and the linkages between different (micro and macro) measures of the gap.

Medical databases allow estimation of prevalences of birth defects with enhanced precision, but systematic error remains a potentially serious problem.

Since the civil registration number is recorded in all Danish databases, the estimation of completeness is possible on an individual level.

Some databases support estimation of between-occasion variability (BOV), where a drug is administered on two or more occasions in each subject that might be separated by a sufficient interval for the underlying kinetics to vary between occasions.

However, for most model parameters, whose values cannot be measured in laboratories or be accessed from literature or databases, parameter estimation is a necessary process to characterize their values.

These transcriptome annotations were loaded into an SQLite database, and abundance estimation was performed using the RSEM method87.

In our study, we analysed the efficiency of the regional-level CORINE Land Cover CLCC) database for the estimation of the naturalness of the vegetation.

Our motivation is to leverage the already existing cost model from a production database for cost estimation of local operator processing, while still covering the space of all query plans.