Back to Multiple platform build/check report for BioC 3.17 |
|
This page was generated on 2023-04-12 10:55:24 -0400 (Wed, 12 Apr 2023).
Hostname | OS | Arch (*) | R version | Installed pkgs |
---|---|---|---|---|
nebbiolo1 | Linux (Ubuntu 22.04.1 LTS) | x86_64 | 4.3.0 alpha (2023-04-03 r84154) | 4547 |
nebbiolo2 | Linux (Ubuntu 20.04.5 LTS) | x86_64 | R Under development (unstable) (2023-02-14 r83833) -- "Unsuffered Consequences" | 4333 |
Click on any hostname to see more info about the system (e.g. compilers) (*) as reported by 'uname -p', except on Windows and Mac OS X |
To the developers/maintainers of the FindIT2 package: - Allow up to 24 hours (and sometimes 48 hours) for your latest push to git@git.bioconductor.org:packages/FindIT2.git to reflect on this report. See Troubleshooting Build Report for more information. - Use the following Renviron settings to reproduce errors and warnings. Note: If "R CMD check" recently failed on the Linux builder over a missing dependency, add the missing dependency to "Suggests" in your DESCRIPTION file. See the Renviron.bioc for details. |
Package 692/2207 | Hostname | OS / Arch | INSTALL | BUILD | CHECK | BUILD BIN | ||||||||
FindIT2 1.5.0 (landing page) Guandong Shang
| nebbiolo1 | Linux (Ubuntu 22.04.1 LTS) / x86_64 | OK | OK | OK | |||||||||
nebbiolo2 | Linux (Ubuntu 20.04.5 LTS) / x86_64 | OK | OK | OK | ||||||||||
Package: FindIT2 |
Version: 1.5.0 |
Command: /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.17-bioc/R/site-library --timings FindIT2_1.5.0.tar.gz |
StartedAt: 2023-04-11 20:18:15 -0400 (Tue, 11 Apr 2023) |
EndedAt: 2023-04-11 20:25:25 -0400 (Tue, 11 Apr 2023) |
EllapsedTime: 430.7 seconds |
RetCode: 0 |
Status: OK |
CheckDir: FindIT2.Rcheck |
Warnings: 0 |
############################################################################## ############################################################################## ### ### Running command: ### ### /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.17-bioc/R/site-library --timings FindIT2_1.5.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/home/biocbuild/bbs-3.17-bioc/meat/FindIT2.Rcheck’ * using R version 4.3.0 alpha (2023-04-03 r84154) * using platform: x86_64-pc-linux-gnu (64-bit) * R was compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 GNU Fortran (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 * running under: Ubuntu 22.04.2 LTS * using session charset: UTF-8 * checking for file ‘FindIT2/DESCRIPTION’ ... OK * this is package ‘FindIT2’ version ‘1.5.0’ * package encoding: UTF-8 * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘FindIT2’ can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking ‘build’ directory ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking R files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking whether the namespace can be loaded with stated dependencies ... OK * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... OK * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking contents of ‘data’ directory ... OK * checking data for non-ASCII characters ... OK * checking data for ASCII and uncompressed saves ... OK * checking files in ‘vignettes’ ... OK * checking examples ... OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed findIT_regionRP 5.498 0.088 5.586 * checking for unstated dependencies in ‘tests’ ... OK * checking tests ... Running ‘testthat.R’ OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes in ‘inst/doc’ ... OK * checking running R code from vignettes ... ‘FindIT2.Rmd’ using ‘UTF-8’... OK NONE * checking re-building of vignette outputs ... OK * checking PDF version of manual ... OK * DONE Status: OK
FindIT2.Rcheck/00install.out
############################################################################## ############################################################################## ### ### Running command: ### ### /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD INSTALL FindIT2 ### ############################################################################## ############################################################################## * installing to library ‘/home/biocbuild/bbs-3.17-bioc/R/site-library’ * installing *source* package ‘FindIT2’ ... ** using staged installation ** R ** data ** inst ** byte-compile and prepare package for lazy loading ** help *** installing help indices ** building package indices ** installing vignettes ** testing if installed package can be loaded from temporary location ** testing if installed package can be loaded from final location ** testing if installed package keeps a record of temporary installation path * DONE (FindIT2)
FindIT2.Rcheck/tests/testthat.Rout
R version 4.3.0 alpha (2023-04-03 r84154) Copyright (C) 2023 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > library(testthat) > library(FindIT2) Loading required package: GenomicRanges Loading required package: stats4 Loading required package: BiocGenerics Attaching package: 'BiocGenerics' The following objects are masked from 'package:stats': IQR, mad, sd, var, xtabs The following objects are masked from 'package:base': Filter, Find, Map, Position, Reduce, anyDuplicated, aperm, append, as.data.frame, basename, cbind, colnames, dirname, do.call, duplicated, eval, evalq, get, grep, grepl, intersect, is.unsorted, lapply, mapply, match, mget, order, paste, pmax, pmax.int, pmin, pmin.int, rank, rbind, rownames, sapply, setdiff, sort, table, tapply, union, unique, unsplit, which.max, which.min Loading required package: S4Vectors Attaching package: 'S4Vectors' The following objects are masked from 'package:base': I, expand.grid, unname Loading required package: IRanges Loading required package: GenomeInfoDb > if (!requireNamespace("TxDb.Athaliana.BioMart.plantsmart28")) { + stop("unable to load TxDb.Athaliana.BioMart.plantsmart28") + } Loading required namespace: TxDb.Athaliana.BioMart.plantsmart28 > > test_check("FindIT2") >> preparing gene features information... 2023-04-11 20:23:25 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:27 >> preparing weight info... 2023-04-11 20:23:27 >> loading E50h_sampleChr5.bw info... 2023-04-11 20:23:27 ------------ >> extracting and calcluating Chr5 signal... 2023-04-11 20:23:28 >> dealing with Chr5 left gene signal... 2023-04-11 20:23:31 >> norming Chr5RP accoring to the whole Chr RP... 2023-04-11 20:23:31 >> merging all Chr RP together... 2023-04-11 20:23:31 >> done 2023-04-11 20:23:31 >> checking seqlevels match... 2023-04-11 20:23:31 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2023-04-11 20:23:31 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:32 >> finding overlap peak in gene scan region... 2023-04-11 20:23:32 >> dealing with left peak not your gene scan region... 2023-04-11 20:23:32 >> merging two set peaks... 2023-04-11 20:23:32 >> calculating distance and dealing with gene strand... 2023-04-11 20:23:32 >> merging all info together ... 2023-04-11 20:23:32 >> done 2023-04-11 20:23:32 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:32 >> pre-filling 1356 noAssoc peak gene's RP with 0... 2023-04-11 20:23:33 >> calculating RP using centerToTSS and peak score2023-04-11 20:23:33 >> merging all info together 2023-04-11 20:23:35 >> done 2023-04-11 20:23:36 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:36 >> pre-filling 1356 noAssoc peak gene's RP with 0... 2023-04-11 20:23:37 >> calculating RP using centerToTSS and peak score2023-04-11 20:23:37 >> merging all info together 2023-04-11 20:23:39 >> done 2023-04-11 20:23:40 >> checking seqlevels match... 2023-04-11 20:23:40 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2023-04-11 20:23:40 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:41 >> finding overlap peak in gene scan region... 2023-04-11 20:23:41 >> dealing with left peak not your gene scan region... 2023-04-11 20:23:41 >> merging two set peaks... 2023-04-11 20:23:41 >> calculating distance and dealing with gene strand... 2023-04-11 20:23:41 >> merging all info together ... 2023-04-11 20:23:41 >> done 2023-04-11 20:23:41 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:41 >> calculating RP using centerToTSS and TF hit 2023-04-11 20:23:42 >> merging all info together 2023-04-11 20:23:42 >> done 2023-04-11 20:23:42 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:42 >> calculating RP using centerToTSS and TF hit 2023-04-11 20:23:43 >> merging all info together 2023-04-11 20:23:43 >> done 2023-04-11 20:23:43 >> checking seqlevels match... 2023-04-11 20:23:44 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2023-04-11 20:23:44 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:45 >> finding overlap peak in gene scan region... 2023-04-11 20:23:45 >> dealing with left peak not your gene scan region... 2023-04-11 20:23:45 >> merging two set peaks... 2023-04-11 20:23:45 >> calculating distance and dealing with gene strand... 2023-04-11 20:23:45 >> merging all info together ... 2023-04-11 20:23:45 >> done 2023-04-11 20:23:45 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:45 >> pre-filling 1356 noAssoc peak gene's RP with 0... 2023-04-11 20:23:47 >> calculating RP using centerToTSS and peak score2023-04-11 20:23:47 >> merging all info together 2023-04-11 20:23:49 >> done 2023-04-11 20:23:49 >> extracting RP info from regionRP... 2023-04-11 20:23:50 >> dealing with TF_GR_databse... 2023-04-11 20:23:50 >> calculating percent and p-value... 2023-04-11 20:23:50 >> dealing withE5_0h_R1... 2023-04-11 20:23:50 >> dealing withE5_0h_R2... 2023-04-11 20:23:50 >> dealing withE5_4h_R1... 2023-04-11 20:23:50 >> dealing withE5_4h_R2... 2023-04-11 20:23:50 >> dealing withE5_8h_R1... 2023-04-11 20:23:50 >> dealing withE5_8h_R2... 2023-04-11 20:23:50 >> dealing withE5_16h_R1... 2023-04-11 20:23:50 >> dealing withE5_16h_R2... 2023-04-11 20:23:50 >> dealing withE5_24h_R1... 2023-04-11 20:23:50 >> dealing withE5_24h_R2... 2023-04-11 20:23:50 >> dealing withE5_48h_R1... 2023-04-11 20:23:51 >> dealing withE5_48h_R2... 2023-04-11 20:23:51 >> dealing withE5_48h_R3... 2023-04-11 20:23:51 >> dealing withE5_72h_R1... 2023-04-11 20:23:51 >> dealing withE5_72h_R2... 2023-04-11 20:23:51 >> dealing withE5_72h_R3... 2023-04-11 20:23:51 >> merging all info together... 2023-04-11 20:23:51 >> done 2023-04-11 20:23:51 >> preparing gene features information... 2023-04-11 20:23:51 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:52 >> calculating p-value for each TF, which may be time consuming... 2023-04-11 20:23:52 >> merging all info together... 2023-04-11 20:23:52 >> done 2023-04-11 20:23:52 >> dealing with TF_GR_database... 2023-04-11 20:23:52 >> calculating coef and converting into z-score using INT... 2023-04-11 20:23:52 >> dealing with E5_0h_R1... 2023-04-11 20:23:52 >> dealing with E5_0h_R2... 2023-04-11 20:23:52 >> dealing with E5_4h_R1... 2023-04-11 20:23:52 >> dealing with E5_4h_R2... 2023-04-11 20:23:52 >> dealing with E5_8h_R1... 2023-04-11 20:23:52 >> dealing with E5_8h_R2... 2023-04-11 20:23:53 >> dealing with E5_16h_R1... 2023-04-11 20:23:53 >> dealing with E5_16h_R2... 2023-04-11 20:23:53 >> dealing with E5_24h_R1... 2023-04-11 20:23:53 >> dealing with E5_24h_R2... 2023-04-11 20:23:53 >> dealing with E5_48h_R1... 2023-04-11 20:23:53 >> dealing with E5_48h_R2... 2023-04-11 20:23:53 >> dealing with E5_48h_R3... 2023-04-11 20:23:53 >> dealing with E5_72h_R1... 2023-04-11 20:23:53 >> dealing with E5_72h_R2... 2023-04-11 20:23:53 >> dealing with E5_72h_R3... 2023-04-11 20:23:53 >> merging all info together... 2023-04-11 20:23:53 >> done 2023-04-11 20:23:54 >> checking seqlevels match... 2023-04-11 20:23:54 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2023-04-11 20:23:54 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:23:54 >> finding overlap peak in gene scan region... 2023-04-11 20:23:54 >> dealing with left peak not your gene scan region... 2023-04-11 20:23:54 >> merging two set peaks... 2023-04-11 20:23:55 >> calculating distance and dealing with gene strand... 2023-04-11 20:23:55 >> merging all info together ... 2023-04-11 20:23:55 >> done 2023-04-11 20:23:55 >> calculating peakCenter to TSS using peak-gene pair... 2023-04-11 20:23:55 >> calculating RP using centerToTSS and TF hit 2023-04-11 20:23:55 >> merging all info together 2023-04-11 20:23:55 >> done 2023-04-11 20:23:55 >> checking seqlevels match... 2023-04-11 20:23:56 >> your peak_GR seqlevel:5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... >> checking seqlevels match... 2023-04-11 20:23:56 >> your peak_GR seqlevel:Chr5 Chr6... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... >> checking seqlevels match... 2023-04-11 20:23:59 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:23:59 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotating Peak using nearest gene mode begins >> preparing gene features information... 2023-04-11 20:23:59 >> finding nearest gene and calculating distance... 2023-04-11 20:24:00 >> dealing with gene strand ... 2023-04-11 20:24:00 >> merging all info together ... 2023-04-11 20:24:00 >> done 2023-04-11 20:24:00 >> checking seqlevels match... 2023-04-11 20:24:00 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:24:00 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotating Peak using nearest gene mode begins >> preparing gene features information... 2023-04-11 20:24:00 >> finding nearest gene and calculating distance... 2023-04-11 20:24:01 >> dealing with gene strand ... 2023-04-11 20:24:01 >> merging all info together ... 2023-04-11 20:24:01 >> done 2023-04-11 20:24:01 >> checking seqlevels match... 2023-04-11 20:24:01 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:24:02 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotating Peak using nearest gene mode begins >> preparing gene features information... 2023-04-11 20:24:02 >> finding nearest gene and calculating distance... 2023-04-11 20:24:02 >> dealing with gene strand ... 2023-04-11 20:24:02 >> merging all info together ... 2023-04-11 20:24:02 >> done 2023-04-11 20:24:02 >> checking seqlevels match... 2023-04-11 20:24:03 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:24:03 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotating Peak using nearest gene mode begins >> preparing gene features information... 2023-04-11 20:24:03 >> finding nearest gene and calculating distance... 2023-04-11 20:24:04 >> dealing with gene strand ... 2023-04-11 20:24:04 >> merging all info together ... 2023-04-11 20:24:04 >> done 2023-04-11 20:24:04 It seems that there 1 genes have not been annotated by nearestGene mode >> checking seqlevels match... 2023-04-11 20:24:05 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:24:05 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotating Peak using nearest gene mode begins >> preparing gene features information... 2023-04-11 20:24:05 >> finding nearest gene and calculating distance... 2023-04-11 20:24:06 >> dealing with gene strand ... 2023-04-11 20:24:06 >> merging all info together ... 2023-04-11 20:24:06 >> done 2023-04-11 20:24:06 It seems that there 1 genes have not been annotated by nearestGene mode >> checking seqlevels match... 2023-04-11 20:24:07 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> checking seqlevels match... 2023-04-11 20:24:08 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:09 >> checking seqlevels match... 2023-04-11 20:24:09 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:10 Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2023-04-11 20:24:11 >> merging all info together... 2023-04-11 20:24:11 >> done 2023-04-11 20:24:11 >> checking seqlevels match... 2023-04-11 20:24:11 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> using scanPromoter parameter to scan promoter for each gene... 2023-04-11 20:24:11 >> checking seqlevels match... 2023-04-11 20:24:11 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:12 >> there are 85 gene have scaned promoter >> using scanEnhancer parameter to scan Enhancer for each gene... 2023-04-11 20:24:12 >> checking seqlevels match... 2023-04-11 20:24:12 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:13 >> calculating cor and pvalue, which may be time consuming... 2023-04-11 20:24:13 >> merging all info together... 2023-04-11 20:24:13 >> done 2023-04-11 20:24:14 Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2023-04-11 20:24:14 >> merging all info together... 2023-04-11 20:24:14 >> done 2023-04-11 20:24:14 >> checking seqlevels match... 2023-04-11 20:24:14 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2023-04-11 20:24:14 >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:15 >> finding overlap peak in gene scan region... 2023-04-11 20:24:15 >> dealing with left peak not your gene scan region... 2023-04-11 20:24:15 >> merging two set peaks... 2023-04-11 20:24:15 >> calculating distance and dealing with gene strand... 2023-04-11 20:24:15 >> merging all info together ... 2023-04-11 20:24:15 >> done 2023-04-11 20:24:15 Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2023-04-11 20:24:16 >> merging all info together... 2023-04-11 20:24:16 >> done 2023-04-11 20:24:16 >> checking seqlevels match... 2023-04-11 20:24:16 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> using scanPromoter parameter to scan promoter for each gene... 2023-04-11 20:24:16 >> checking seqlevels match... 2023-04-11 20:24:16 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:17 >> there are 85 gene have scaned promoter >> using scanEnhancer parameter to scan Enhancer for each gene... 2023-04-11 20:24:17 >> checking seqlevels match... 2023-04-11 20:24:17 >> your peak_GR seqlevel:Chr5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... Good, your Chrs in peak_GR is all in Txdb >> some scan range may cross Chr bound, trimming... 2023-04-11 20:24:18 >> calculating cor and pvalue, which may be time consuming... 2023-04-11 20:24:18 >> merging all info together... 2023-04-11 20:24:18 >> done 2023-04-11 20:24:18 Joining with `by = join_by(feature_id)` Joining with `by = join_by(feature_id)` `geom_smooth()` using formula = 'y ~ x' Joining with `by = join_by(feature_id)` Joining with `by = join_by(feature_id)` `geom_smooth()` using formula = 'y ~ x' [ FAIL 0 | WARN 0 | SKIP 0 | PASS 65 ] > > proc.time() user system elapsed 63.172 1.893 65.055
FindIT2.Rcheck/FindIT2-Ex.timings
name | user | system | elapsed | |
TF_target_database | 0.001 | 0.000 | 0.000 | |
calcRP_TFHit | 3.642 | 0.219 | 3.876 | |
calcRP_coverage | 3.923 | 0.776 | 4.699 | |
calcRP_region | 4.574 | 0.136 | 4.711 | |
enhancerPromoterCor | 2.611 | 0.032 | 2.642 | |
findIT_MARA | 0.428 | 0.020 | 0.447 | |
findIT_TFHit | 1.775 | 0.160 | 1.935 | |
findIT_TTPair | 0.075 | 0.002 | 0.077 | |
findIT_enrichFisher | 0.156 | 0.012 | 0.168 | |
findIT_enrichWilcox | 0.165 | 0.004 | 0.169 | |
findIT_regionRP | 5.498 | 0.088 | 5.586 | |
getAssocPairNumber | 1.161 | 0.016 | 1.177 | |
integrate_ChIP_RNA | 2.010 | 0.028 | 2.038 | |
integrate_replicates | 0.002 | 0.000 | 0.002 | |
jaccard_findIT_TTpair | 0.102 | 0.004 | 0.106 | |
jaccard_findIT_enrichFisher | 0.203 | 0.000 | 0.203 | |
loadPeakFile | 0.057 | 0.000 | 0.057 | |
mm_geneBound | 1.132 | 0.012 | 1.144 | |
mm_geneScan | 1.137 | 0.020 | 1.158 | |
mm_nearestGene | 1.049 | 0.016 | 1.065 | |
peakGeneCor | 2.147 | 0.044 | 2.191 | |
plot_annoDistance | 2.222 | 0.104 | 2.325 | |
plot_peakGeneAlias_summary | 1.195 | 0.000 | 1.194 | |
plot_peakGeneCor | 2.580 | 0.016 | 2.595 | |
test_geneSet | 0.001 | 0.000 | 0.001 | |