| Back to Multiple platform build/check report for BioC 3.19: simplified long |
|
This page was generated on 2024-10-18 20:39 -0400 (Fri, 18 Oct 2024).
| Hostname | OS | Arch (*) | R version | Installed pkgs |
|---|---|---|---|---|
| nebbiolo1 | Linux (Ubuntu 22.04.3 LTS) | x86_64 | 4.4.1 (2024-06-14) -- "Race for Your Life" | 4763 |
| palomino7 | Windows Server 2022 Datacenter | x64 | 4.4.1 (2024-06-14 ucrt) -- "Race for Your Life" | 4500 |
| merida1 | macOS 12.7.5 Monterey | x86_64 | 4.4.1 (2024-06-14) -- "Race for Your Life" | 4530 |
| kjohnson1 | macOS 13.6.6 Ventura | arm64 | 4.4.1 (2024-06-14) -- "Race for Your Life" | 4480 |
| 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 | ||||
| Package 723/2300 | Hostname | OS / Arch | INSTALL | BUILD | CHECK | BUILD BIN | ||||||||
| FindIT2 1.10.0 (landing page) Guandong Shang
| nebbiolo1 | Linux (Ubuntu 22.04.3 LTS) / x86_64 | OK | OK | OK | |||||||||
| palomino7 | Windows Server 2022 Datacenter / x64 | OK | OK | OK | OK | |||||||||
| merida1 | macOS 12.7.5 Monterey / x86_64 | OK | OK | OK | OK | |||||||||
| kjohnson1 | macOS 13.6.6 Ventura / arm64 | OK | OK | OK | OK | |||||||||
|
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. - If 'R CMD check' started to fail recently on the Linux builder(s) over a missing dependency, add the missing dependency to 'Suggests:' in your DESCRIPTION file. See Renviron.bioc for more information. |
| Package: FindIT2 |
| Version: 1.10.0 |
| Command: E:\biocbuild\bbs-3.19-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=E:\biocbuild\bbs-3.19-bioc\R\library --no-vignettes --timings FindIT2_1.10.0.tar.gz |
| StartedAt: 2024-10-17 01:29:16 -0400 (Thu, 17 Oct 2024) |
| EndedAt: 2024-10-17 01:35:35 -0400 (Thu, 17 Oct 2024) |
| EllapsedTime: 379.2 seconds |
| RetCode: 0 |
| Status: OK |
| CheckDir: FindIT2.Rcheck |
| Warnings: 0 |
##############################################################################
##############################################################################
###
### Running command:
###
### E:\biocbuild\bbs-3.19-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=E:\biocbuild\bbs-3.19-bioc\R\library --no-vignettes --timings FindIT2_1.10.0.tar.gz
###
##############################################################################
##############################################################################
* using log directory 'E:/biocbuild/bbs-3.19-bioc/meat/FindIT2.Rcheck'
* using R version 4.4.1 (2024-06-14 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
gcc.exe (GCC) 13.2.0
GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* using option '--no-vignettes'
* checking for file 'FindIT2/DESCRIPTION' ... OK
* this is package 'FindIT2' version '1.10.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 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 code 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 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
calcRP_region 7.40 0.18 7.58
findIT_regionRP 7.21 0.16 7.35
* checking for unstated dependencies in 'tests' ... OK
* checking tests ...
Running 'testthat.R'
OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE
Status: OK
FindIT2.Rcheck/00install.out
############################################################################## ############################################################################## ### ### Running command: ### ### E:\biocbuild\bbs-3.19-bioc\R\bin\R.exe CMD INSTALL FindIT2 ### ############################################################################## ############################################################################## * installing to library 'E:/biocbuild/bbs-3.19-bioc/R/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.4.1 (2024-06-14 ucrt) -- "Race for Your Life"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64
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, table, tapply,
union, unique, unsplit, which.max, which.min
Loading required package: S4Vectors
Attaching package: 'S4Vectors'
The following object is masked from 'package:utils':
findMatches
The following objects are masked from 'package:base':
I, expand.grid, unname
Loading required package: IRanges
Attaching package: 'IRanges'
The following object is masked from 'package:grDevices':
windows
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")
>> checking seqlevels match... 2024-10-17 1:34:24 AM
>> 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... 2024-10-17 1:34:24 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:34:25 AM
>> finding overlap peak in gene scan region... 2024-10-17 1:34:25 AM
>> dealing with left peak not your gene scan region... 2024-10-17 1:34:25 AM
>> merging two set peaks... 2024-10-17 1:34:25 AM
>> calculating distance and dealing with gene strand... 2024-10-17 1:34:25 AM
>> merging all info together ... 2024-10-17 1:34:25 AM
>> done 2024-10-17 1:34:26 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:26 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-10-17 1:34:27 AM
>> calculating RP using centerToTSS and peak score2024-10-17 1:34:27 AM
>> merging all info together 2024-10-17 1:34:29 AM
>> done 2024-10-17 1:34:31 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:31 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-10-17 1:34:32 AM
>> calculating RP using centerToTSS and peak score2024-10-17 1:34:32 AM
>> merging all info together 2024-10-17 1:34:35 AM
>> done 2024-10-17 1:34:35 AM
>> checking seqlevels match... 2024-10-17 1:34:35 AM
>> 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... 2024-10-17 1:34:35 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:34:36 AM
>> finding overlap peak in gene scan region... 2024-10-17 1:34:36 AM
>> dealing with left peak not your gene scan region... 2024-10-17 1:34:36 AM
>> merging two set peaks... 2024-10-17 1:34:37 AM
>> calculating distance and dealing with gene strand... 2024-10-17 1:34:37 AM
>> merging all info together ... 2024-10-17 1:34:37 AM
>> done 2024-10-17 1:34:37 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:37 AM
>> calculating RP using centerToTSS and TF hit 2024-10-17 1:34:38 AM
>> merging all info together 2024-10-17 1:34:38 AM
>> done 2024-10-17 1:34:38 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:38 AM
>> calculating RP using centerToTSS and TF hit 2024-10-17 1:34:39 AM
>> merging all info together 2024-10-17 1:34:39 AM
>> done 2024-10-17 1:34:39 AM
>> checking seqlevels match... 2024-10-17 1:34:40 AM
>> 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... 2024-10-17 1:34:40 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:34:41 AM
>> finding overlap peak in gene scan region... 2024-10-17 1:34:41 AM
>> dealing with left peak not your gene scan region... 2024-10-17 1:34:41 AM
>> merging two set peaks... 2024-10-17 1:34:41 AM
>> calculating distance and dealing with gene strand... 2024-10-17 1:34:41 AM
>> merging all info together ... 2024-10-17 1:34:41 AM
>> done 2024-10-17 1:34:41 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:41 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-10-17 1:34:42 AM
>> calculating RP using centerToTSS and peak score2024-10-17 1:34:42 AM
>> merging all info together 2024-10-17 1:34:44 AM
>> done 2024-10-17 1:34:45 AM
>> extracting RP info from regionRP... 2024-10-17 1:34:46 AM
>> dealing with TF_GR_databse... 2024-10-17 1:34:46 AM
>> calculating percent and p-value... 2024-10-17 1:34:46 AM
>> dealing withE5_0h_R1... 2024-10-17 1:34:46 AM
>> dealing withE5_0h_R2... 2024-10-17 1:34:46 AM
>> dealing withE5_4h_R1... 2024-10-17 1:34:46 AM
>> dealing withE5_4h_R2... 2024-10-17 1:34:46 AM
>> dealing withE5_8h_R1... 2024-10-17 1:34:47 AM
>> dealing withE5_8h_R2... 2024-10-17 1:34:47 AM
>> dealing withE5_16h_R1... 2024-10-17 1:34:47 AM
>> dealing withE5_16h_R2... 2024-10-17 1:34:47 AM
>> dealing withE5_24h_R1... 2024-10-17 1:34:47 AM
>> dealing withE5_24h_R2... 2024-10-17 1:34:47 AM
>> dealing withE5_48h_R1... 2024-10-17 1:34:47 AM
>> dealing withE5_48h_R2... 2024-10-17 1:34:47 AM
>> dealing withE5_48h_R3... 2024-10-17 1:34:47 AM
>> dealing withE5_72h_R1... 2024-10-17 1:34:47 AM
>> dealing withE5_72h_R2... 2024-10-17 1:34:47 AM
>> dealing withE5_72h_R3... 2024-10-17 1:34:47 AM
>> merging all info together... 2024-10-17 1:34:47 AM
>> done 2024-10-17 1:34:47 AM
>> preparing gene features information... 2024-10-17 1:34:47 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:34:48 AM
>> calculating p-value for each TF, which may be time consuming... 2024-10-17 1:34:48 AM
>> merging all info together... 2024-10-17 1:34:48 AM
>> done 2024-10-17 1:34:48 AM
>> dealing with TF_GR_database... 2024-10-17 1:34:49 AM
>> calculating coef and converting into z-score using INT... 2024-10-17 1:34:49 AM
>> dealing with E5_0h_R1... 2024-10-17 1:34:49 AM
>> dealing with E5_0h_R2... 2024-10-17 1:34:49 AM
>> dealing with E5_4h_R1... 2024-10-17 1:34:49 AM
>> dealing with E5_4h_R2... 2024-10-17 1:34:49 AM
>> dealing with E5_8h_R1... 2024-10-17 1:34:49 AM
>> dealing with E5_8h_R2... 2024-10-17 1:34:49 AM
>> dealing with E5_16h_R1... 2024-10-17 1:34:50 AM
>> dealing with E5_16h_R2... 2024-10-17 1:34:50 AM
>> dealing with E5_24h_R1... 2024-10-17 1:34:50 AM
>> dealing with E5_24h_R2... 2024-10-17 1:34:50 AM
>> dealing with E5_48h_R1... 2024-10-17 1:34:50 AM
>> dealing with E5_48h_R2... 2024-10-17 1:34:50 AM
>> dealing with E5_48h_R3... 2024-10-17 1:34:50 AM
>> dealing with E5_72h_R1... 2024-10-17 1:34:50 AM
>> dealing with E5_72h_R2... 2024-10-17 1:34:50 AM
>> dealing with E5_72h_R3... 2024-10-17 1:34:50 AM
>> merging all info together... 2024-10-17 1:34:50 AM
>> done 2024-10-17 1:34:51 AM
>> checking seqlevels match... 2024-10-17 1:34:51 AM
>> 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... 2024-10-17 1:34:51 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:34:52 AM
>> finding overlap peak in gene scan region... 2024-10-17 1:34:52 AM
>> dealing with left peak not your gene scan region... 2024-10-17 1:34:52 AM
>> merging two set peaks... 2024-10-17 1:34:52 AM
>> calculating distance and dealing with gene strand... 2024-10-17 1:34:52 AM
>> merging all info together ... 2024-10-17 1:34:52 AM
>> done 2024-10-17 1:34:52 AM
>> calculating peakCenter to TSS using peak-gene pair... 2024-10-17 1:34:52 AM
>> calculating RP using centerToTSS and TF hit 2024-10-17 1:34:53 AM
>> merging all info together 2024-10-17 1:34:53 AM
>> done 2024-10-17 1:34:53 AM
>> checking seqlevels match... 2024-10-17 1:34:54 AM
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match... 2024-10-17 1:34:54 AM
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match... 2024-10-17 1:34:57 AM
>> 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... 2024-10-17 1:34:57 AM
>> 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... 2024-10-17 1:34:57 AM
>> finding nearest gene and calculating distance... 2024-10-17 1:34:58 AM
>> dealing with gene strand ... 2024-10-17 1:34:58 AM
>> merging all info together ... 2024-10-17 1:34:58 AM
>> done 2024-10-17 1:34:58 AM
>> checking seqlevels match... 2024-10-17 1:34:58 AM
>> 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... 2024-10-17 1:34:59 AM
>> 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... 2024-10-17 1:34:59 AM
>> finding nearest gene and calculating distance... 2024-10-17 1:34:59 AM
>> dealing with gene strand ... 2024-10-17 1:34:59 AM
>> merging all info together ... 2024-10-17 1:35:00 AM
>> done 2024-10-17 1:35:00 AM
>> checking seqlevels match... 2024-10-17 1:35:00 AM
>> 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... 2024-10-17 1:35:01 AM
>> 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... 2024-10-17 1:35:01 AM
>> finding nearest gene and calculating distance... 2024-10-17 1:35:01 AM
>> dealing with gene strand ... 2024-10-17 1:35:01 AM
>> merging all info together ... 2024-10-17 1:35:01 AM
>> done 2024-10-17 1:35:01 AM
>> checking seqlevels match... 2024-10-17 1:35:02 AM
>> 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... 2024-10-17 1:35:03 AM
>> 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... 2024-10-17 1:35:03 AM
>> finding nearest gene and calculating distance... 2024-10-17 1:35:04 AM
>> dealing with gene strand ... 2024-10-17 1:35:04 AM
>> merging all info together ... 2024-10-17 1:35:04 AM
>> done 2024-10-17 1:35:04 AM
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match... 2024-10-17 1:35:05 AM
>> 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... 2024-10-17 1:35:05 AM
>> 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... 2024-10-17 1:35:05 AM
>> finding nearest gene and calculating distance... 2024-10-17 1:35:06 AM
>> dealing with gene strand ... 2024-10-17 1:35:06 AM
>> merging all info together ... 2024-10-17 1:35:06 AM
>> done 2024-10-17 1:35:06 AM
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match... 2024-10-17 1:35:07 AM
>> 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... 2024-10-17 1:35:09 AM
>> 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... 2024-10-17 1:35:10 AM
>> checking seqlevels match... 2024-10-17 1:35:11 AM
>> 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... 2024-10-17 1:35:11 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2024-10-17 1:35:13 AM
>> merging all info together... 2024-10-17 1:35:13 AM
>> done 2024-10-17 1:35:13 AM
>> checking seqlevels match... 2024-10-17 1:35:13 AM
>> 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... 2024-10-17 1:35:13 AM
>> checking seqlevels match... 2024-10-17 1:35:14 AM
>> 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... 2024-10-17 1:35:15 AM
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene... 2024-10-17 1:35:15 AM
>> checking seqlevels match... 2024-10-17 1:35:15 AM
>> 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... 2024-10-17 1:35:16 AM
>> calculating cor and pvalue, which may be time consuming... 2024-10-17 1:35:16 AM
>> merging all info together... 2024-10-17 1:35:16 AM
>> done 2024-10-17 1:35:16 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2024-10-17 1:35:16 AM
>> merging all info together... 2024-10-17 1:35:16 AM
>> done 2024-10-17 1:35:17 AM
>> checking seqlevels match... 2024-10-17 1:35:17 AM
>> 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... 2024-10-17 1:35:17 AM
>> some scan range may cross Chr bound, trimming... 2024-10-17 1:35:18 AM
>> finding overlap peak in gene scan region... 2024-10-17 1:35:18 AM
>> dealing with left peak not your gene scan region... 2024-10-17 1:35:18 AM
>> merging two set peaks... 2024-10-17 1:35:18 AM
>> calculating distance and dealing with gene strand... 2024-10-17 1:35:18 AM
>> merging all info together ... 2024-10-17 1:35:18 AM
>> done 2024-10-17 1:35:18 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2024-10-17 1:35:20 AM
>> merging all info together... 2024-10-17 1:35:20 AM
>> done 2024-10-17 1:35:20 AM
>> checking seqlevels match... 2024-10-17 1:35:20 AM
>> 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... 2024-10-17 1:35:20 AM
>> checking seqlevels match... 2024-10-17 1:35:20 AM
>> 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... 2024-10-17 1:35:21 AM
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene... 2024-10-17 1:35:22 AM
>> checking seqlevels match... 2024-10-17 1:35:22 AM
>> 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... 2024-10-17 1:35:24 AM
>> calculating cor and pvalue, which may be time consuming... 2024-10-17 1:35:24 AM
>> merging all info together... 2024-10-17 1:35:24 AM
>> done 2024-10-17 1:35:24 AM
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 63 ]
>
> proc.time()
user system elapsed
73.04 2.53 75.62
FindIT2.Rcheck/FindIT2-Ex.timings
| name | user | system | elapsed | |
| TF_target_database | 0.00 | 0.01 | 0.02 | |
| calcRP_TFHit | 3.36 | 0.09 | 3.67 | |
| calcRP_coverage | 0.08 | 0.00 | 0.07 | |
| calcRP_region | 7.40 | 0.18 | 7.58 | |
| enhancerPromoterCor | 3.16 | 0.12 | 3.28 | |
| findIT_MARA | 0.50 | 0.03 | 0.53 | |
| findIT_TFHit | 1.25 | 0.03 | 1.28 | |
| findIT_TTPair | 0.09 | 0.08 | 0.17 | |
| findIT_enrichFisher | 0.17 | 0.01 | 0.19 | |
| findIT_enrichWilcox | 0.22 | 0.02 | 0.23 | |
| findIT_regionRP | 7.21 | 0.16 | 7.35 | |
| getAssocPairNumber | 1.53 | 0.03 | 1.57 | |
| integrate_ChIP_RNA | 2.53 | 0.09 | 2.62 | |
| integrate_replicates | 0 | 0 | 0 | |
| jaccard_findIT_TTpair | 0.14 | 0.06 | 0.20 | |
| jaccard_findIT_enrichFisher | 0.24 | 0.02 | 0.25 | |
| loadPeakFile | 0.06 | 0.00 | 0.07 | |
| mm_geneBound | 1.59 | 0.06 | 1.65 | |
| mm_geneScan | 1.38 | 0.05 | 1.43 | |
| mm_nearestGene | 1.26 | 0.01 | 1.28 | |
| peakGeneCor | 2.88 | 0.18 | 3.05 | |
| plot_annoDistance | 1.50 | 0.04 | 1.55 | |
| plot_peakGeneAlias_summary | 1.64 | 0.05 | 1.68 | |
| plot_peakGeneCor | 3.87 | 0.25 | 4.14 | |
| test_geneSet | 0 | 0 | 0 | |