Guandong Shang
| Snapshot Date: 2025-11-04 13:40 -0500 (Tue, 04 Nov 2025) |
| git_url: https://git.bioconductor.org/packages/FindIT2 |
| git_branch: devel |
| git_last_commit: 6e3f32a |
| git_last_commit_date: 2025-10-29 11:10:30 -0500 (Wed, 29 Oct 2025) |
| Back to Build/check report for BioC 3.23: simplified long |
|
This page was generated on 2025-11-05 11:32 -0500 (Wed, 05 Nov 2025).
| Hostname | OS | Arch (*) | R version | Installed pkgs |
|---|---|---|---|---|
| nebbiolo1 | Linux (Ubuntu 24.04.3 LTS) | x86_64 | R Under development (unstable) (2025-10-20 r88955) -- "Unsuffered Consequences" | 4818 |
| 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 728/2323 | Hostname | OS / Arch | INSTALL | BUILD | CHECK | BUILD BIN | ||||||||
| FindIT2 1.17.0 (landing page) Guandong Shang
| nebbiolo1 | Linux (Ubuntu 24.04.3 LTS) / x86_64 | 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.17.0 |
| Command: /home/biocbuild/bbs-3.23-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.23-bioc/R/site-library --timings FindIT2_1.17.0.tar.gz |
| StartedAt: 2025-11-04 23:23:22 -0500 (Tue, 04 Nov 2025) |
| EndedAt: 2025-11-04 23:29:58 -0500 (Tue, 04 Nov 2025) |
| EllapsedTime: 395.7 seconds |
| RetCode: 0 |
| Status: OK |
| CheckDir: FindIT2.Rcheck |
| Warnings: 0 |
##############################################################################
##############################################################################
###
### Running command:
###
### /home/biocbuild/bbs-3.23-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.23-bioc/R/site-library --timings FindIT2_1.17.0.tar.gz
###
##############################################################################
##############################################################################
* using log directory ‘/home/biocbuild/bbs-3.23-bioc/meat/FindIT2.Rcheck’
* using R Under development (unstable) (2025-10-20 r88955)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
GNU Fortran (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
* running under: Ubuntu 24.04.3 LTS
* using session charset: UTF-8
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.17.0’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... INFO
Imports includes 22 non-default packages.
Importing from so many packages makes the package vulnerable to any of
them becoming unavailable. Move as many as possible to Suggests and
use conditionally.
* 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 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 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 6.073 0.142 6.216
calcRP_region 5.068 0.067 5.136
* 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 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.23-bioc/R/bin/R CMD INSTALL FindIT2 ### ############################################################################## ############################################################################## * installing to library ‘/home/biocbuild/bbs-3.23-bioc/R/site-library’ * installing *source* package ‘FindIT2’ ... ** this is package ‘FindIT2’ version ‘1.17.0’ ** 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 Under development (unstable) (2025-10-20 r88955) -- "Unsuffered Consequences"
Copyright (C) 2025 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu
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
Loading required package: generics
Attaching package: 'generics'
The following objects are masked from 'package:base':
as.difftime, as.factor, as.ordered, intersect, is.element, setdiff,
setequal, union
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, is.unsorted, lapply,
mapply, match, mget, order, paste, pmax, pmax.int, pmin, pmin.int,
rank, rbind, rownames, sapply, saveRDS, table, tapply, 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
Loading required package: Seqinfo
> 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... 2025-11-04 23:28:10
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:12
>> preparing weight info... 2025-11-04 23:28:12
>> loading E50h_sampleChr5.bw info... 2025-11-04 23:28:12
------------
>> extracting and calcluating Chr5 signal... 2025-11-04 23:28:12
>> dealing with Chr5 left gene signal... 2025-11-04 23:28:15
>> norming Chr5RP accoring to the whole Chr RP... 2025-11-04 23:28:15
>> merging all Chr RP together... 2025-11-04 23:28:15
>> done 2025-11-04 23:28:15
>> checking seqlevels match... 2025-11-04 23:28:15
>> 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... 2025-11-04 23:28:15
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:16
>> finding overlap peak in gene scan region... 2025-11-04 23:28:16
>> dealing with left peak not your gene scan region... 2025-11-04 23:28:16
>> merging two set peaks... 2025-11-04 23:28:16
>> calculating distance and dealing with gene strand... 2025-11-04 23:28:16
>> merging all info together ... 2025-11-04 23:28:16
>> done 2025-11-04 23:28:16
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:16
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2025-11-04 23:28:17
>> calculating RP using centerToTSS and peak score2025-11-04 23:28:17
>> merging all info together 2025-11-04 23:28:19
>> done 2025-11-04 23:28:19
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:20
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2025-11-04 23:28:20
>> calculating RP using centerToTSS and peak score2025-11-04 23:28:20
>> merging all info together 2025-11-04 23:28:23
>> done 2025-11-04 23:28:23
>> checking seqlevels match... 2025-11-04 23:28:23
>> 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... 2025-11-04 23:28:23
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:24
>> finding overlap peak in gene scan region... 2025-11-04 23:28:24
>> dealing with left peak not your gene scan region... 2025-11-04 23:28:24
>> merging two set peaks... 2025-11-04 23:28:24
>> calculating distance and dealing with gene strand... 2025-11-04 23:28:24
>> merging all info together ... 2025-11-04 23:28:24
>> done 2025-11-04 23:28:24
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:24
>> calculating RP using centerToTSS and TF hit 2025-11-04 23:28:25
>> merging all info together 2025-11-04 23:28:25
>> done 2025-11-04 23:28:25
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:25
>> calculating RP using centerToTSS and TF hit 2025-11-04 23:28:26
>> merging all info together 2025-11-04 23:28:26
>> done 2025-11-04 23:28:26
>> checking seqlevels match... 2025-11-04 23:28:26
>> 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... 2025-11-04 23:28:26
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:28
>> finding overlap peak in gene scan region... 2025-11-04 23:28:28
>> dealing with left peak not your gene scan region... 2025-11-04 23:28:28
>> merging two set peaks... 2025-11-04 23:28:28
>> calculating distance and dealing with gene strand... 2025-11-04 23:28:28
>> merging all info together ... 2025-11-04 23:28:28
>> done 2025-11-04 23:28:28
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:28
>> pre-filling 1356 noAssoc peak gene's RP with 0... 2025-11-04 23:28:29
>> calculating RP using centerToTSS and peak score2025-11-04 23:28:29
>> merging all info together 2025-11-04 23:28:31
>> done 2025-11-04 23:28:31
>> extracting RP info from regionRP... 2025-11-04 23:28:32
>> dealing with TF_GR_databse... 2025-11-04 23:28:32
>> calculating percent and p-value... 2025-11-04 23:28:32
>> dealing withE5_0h_R1... 2025-11-04 23:28:32
>> dealing withE5_0h_R2... 2025-11-04 23:28:32
>> dealing withE5_4h_R1... 2025-11-04 23:28:32
>> dealing withE5_4h_R2... 2025-11-04 23:28:32
>> dealing withE5_8h_R1... 2025-11-04 23:28:32
>> dealing withE5_8h_R2... 2025-11-04 23:28:33
>> dealing withE5_16h_R1... 2025-11-04 23:28:33
>> dealing withE5_16h_R2... 2025-11-04 23:28:33
>> dealing withE5_24h_R1... 2025-11-04 23:28:33
>> dealing withE5_24h_R2... 2025-11-04 23:28:33
>> dealing withE5_48h_R1... 2025-11-04 23:28:33
>> dealing withE5_48h_R2... 2025-11-04 23:28:33
>> dealing withE5_48h_R3... 2025-11-04 23:28:33
>> dealing withE5_72h_R1... 2025-11-04 23:28:33
>> dealing withE5_72h_R2... 2025-11-04 23:28:33
>> dealing withE5_72h_R3... 2025-11-04 23:28:33
>> merging all info together... 2025-11-04 23:28:33
>> done 2025-11-04 23:28:33
>> preparing gene features information... 2025-11-04 23:28:33
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:34
>> calculating p-value for each TF, which may be time consuming... 2025-11-04 23:28:34
>> merging all info together... 2025-11-04 23:28:34
>> done 2025-11-04 23:28:34
>> dealing with TF_GR_database... 2025-11-04 23:28:34
>> calculating coef and converting into z-score using INT... 2025-11-04 23:28:34
>> dealing with E5_0h_R1... 2025-11-04 23:28:34
>> dealing with E5_0h_R2... 2025-11-04 23:28:34
>> dealing with E5_4h_R1... 2025-11-04 23:28:34
>> dealing with E5_4h_R2... 2025-11-04 23:28:34
>> dealing with E5_8h_R1... 2025-11-04 23:28:34
>> dealing with E5_8h_R2... 2025-11-04 23:28:34
>> dealing with E5_16h_R1... 2025-11-04 23:28:35
>> dealing with E5_16h_R2... 2025-11-04 23:28:35
>> dealing with E5_24h_R1... 2025-11-04 23:28:35
>> dealing with E5_24h_R2... 2025-11-04 23:28:35
>> dealing with E5_48h_R1... 2025-11-04 23:28:35
>> dealing with E5_48h_R2... 2025-11-04 23:28:35
>> dealing with E5_48h_R3... 2025-11-04 23:28:35
>> dealing with E5_72h_R1... 2025-11-04 23:28:35
>> dealing with E5_72h_R2... 2025-11-04 23:28:35
>> dealing with E5_72h_R3... 2025-11-04 23:28:35
>> merging all info together... 2025-11-04 23:28:35
>> done 2025-11-04 23:28:35
>> checking seqlevels match... 2025-11-04 23:28:35
>> 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... 2025-11-04 23:28:35
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:36
>> finding overlap peak in gene scan region... 2025-11-04 23:28:36
>> dealing with left peak not your gene scan region... 2025-11-04 23:28:36
>> merging two set peaks... 2025-11-04 23:28:36
>> calculating distance and dealing with gene strand... 2025-11-04 23:28:36
>> merging all info together ... 2025-11-04 23:28:36
>> done 2025-11-04 23:28:36
>> calculating peakCenter to TSS using peak-gene pair... 2025-11-04 23:28:36
>> calculating RP using centerToTSS and TF hit 2025-11-04 23:28:37
>> merging all info together 2025-11-04 23:28:37
>> done 2025-11-04 23:28:37
>> checking seqlevels match... 2025-11-04 23:28:37
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match... 2025-11-04 23:28:37
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match... 2025-11-04 23:28: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
>> checking seqlevels match... 2025-11-04 23:28: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information... 2025-11-04 23:28:40
>> finding nearest gene and calculating distance... 2025-11-04 23:28:41
>> dealing with gene strand ... 2025-11-04 23:28:41
>> merging all info together ... 2025-11-04 23:28:41
>> done 2025-11-04 23:28:41
>> checking seqlevels match... 2025-11-04 23:28:41
>> 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... 2025-11-04 23:28:41
>> 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... 2025-11-04 23:28:41
>> finding nearest gene and calculating distance... 2025-11-04 23:28:42
>> dealing with gene strand ... 2025-11-04 23:28:42
>> merging all info together ... 2025-11-04 23:28:42
>> done 2025-11-04 23:28:42
>> checking seqlevels match... 2025-11-04 23:28:42
>> 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... 2025-11-04 23:28:42
>> 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... 2025-11-04 23:28:42
>> finding nearest gene and calculating distance... 2025-11-04 23:28:43
>> dealing with gene strand ... 2025-11-04 23:28:43
>> merging all info together ... 2025-11-04 23:28:43
>> done 2025-11-04 23:28:43
>> checking seqlevels match... 2025-11-04 23:28: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
>> checking seqlevels match... 2025-11-04 23:28: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information... 2025-11-04 23:28:44
>> finding nearest gene and calculating distance... 2025-11-04 23:28:45
>> dealing with gene strand ... 2025-11-04 23:28:45
>> merging all info together ... 2025-11-04 23:28:45
>> done 2025-11-04 23:28:45
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match... 2025-11-04 23:28:45
>> 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... 2025-11-04 23:28:45
>> 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... 2025-11-04 23:28:45
>> finding nearest gene and calculating distance... 2025-11-04 23:28:46
>> dealing with gene strand ... 2025-11-04 23:28:46
>> merging all info together ... 2025-11-04 23:28:46
>> done 2025-11-04 23:28:46
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match... 2025-11-04 23:28:47
>> 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... 2025-11-04 23:28:48
>> 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... 2025-11-04 23:28:48
>> checking seqlevels match... 2025-11-04 23:28:49
>> 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... 2025-11-04 23:28:50
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2025-11-04 23:28:51
>> merging all info together... 2025-11-04 23:28:51
>> done 2025-11-04 23:28:51
>> checking seqlevels match... 2025-11-04 23:28:51
>> 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... 2025-11-04 23:28:51
>> checking seqlevels match... 2025-11-04 23:28:51
>> 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... 2025-11-04 23:28:52
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene... 2025-11-04 23:28:52
>> checking seqlevels match... 2025-11-04 23:28:52
>> 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... 2025-11-04 23:28:53
>> calculating cor and pvalue, which may be time consuming... 2025-11-04 23:28:53
>> merging all info together... 2025-11-04 23:28:53
>> done 2025-11-04 23:28:53
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2025-11-04 23:28:53
>> merging all info together... 2025-11-04 23:28:53
>> done 2025-11-04 23:28:53
>> checking seqlevels match... 2025-11-04 23:28:53
>> 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... 2025-11-04 23:28:53
>> some scan range may cross Chr bound, trimming... 2025-11-04 23:28:54
>> finding overlap peak in gene scan region... 2025-11-04 23:28:54
>> dealing with left peak not your gene scan region... 2025-11-04 23:28:54
>> merging two set peaks... 2025-11-04 23:28:54
>> calculating distance and dealing with gene strand... 2025-11-04 23:28:54
>> merging all info together ... 2025-11-04 23:28:54
>> done 2025-11-04 23:28:54
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming... 2025-11-04 23:28:55
>> merging all info together... 2025-11-04 23:28:55
>> done 2025-11-04 23:28:55
>> checking seqlevels match... 2025-11-04 23:28:55
>> 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... 2025-11-04 23:28:55
>> checking seqlevels match... 2025-11-04 23:28:55
>> 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... 2025-11-04 23:28:56
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene... 2025-11-04 23:28:56
>> checking seqlevels match... 2025-11-04 23:28:56
>> 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... 2025-11-04 23:28:57
>> calculating cor and pvalue, which may be time consuming... 2025-11-04 23:28:57
>> merging all info together... 2025-11-04 23:28:57
>> done 2025-11-04 23:28:57
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
57.400 1.752 59.154
FindIT2.Rcheck/FindIT2-Ex.timings
| name | user | system | elapsed | |
| TF_target_database | 0 | 0 | 0 | |
| calcRP_TFHit | 3.214 | 0.118 | 3.350 | |
| calcRP_coverage | 2.645 | 0.203 | 2.849 | |
| calcRP_region | 5.068 | 0.067 | 5.136 | |
| enhancerPromoterCor | 2.234 | 0.048 | 2.283 | |
| findIT_MARA | 0.414 | 0.007 | 0.421 | |
| findIT_TFHit | 0.774 | 0.024 | 0.798 | |
| findIT_TTPair | 0.067 | 0.000 | 0.068 | |
| findIT_enrichFisher | 0.142 | 0.002 | 0.144 | |
| findIT_enrichWilcox | 0.157 | 0.002 | 0.160 | |
| findIT_regionRP | 6.073 | 0.142 | 6.216 | |
| getAssocPairNumber | 0.989 | 0.008 | 0.997 | |
| integrate_ChIP_RNA | 1.856 | 0.064 | 1.920 | |
| integrate_replicates | 0.002 | 0.001 | 0.002 | |
| jaccard_findIT_TTpair | 0.091 | 0.001 | 0.092 | |
| jaccard_findIT_enrichFisher | 0.186 | 0.003 | 0.188 | |
| loadPeakFile | 0.055 | 0.000 | 0.056 | |
| mm_geneBound | 1.045 | 0.007 | 1.052 | |
| mm_geneScan | 1.071 | 0.005 | 1.076 | |
| mm_nearestGene | 0.971 | 0.004 | 0.974 | |
| peakGeneCor | 2.017 | 0.007 | 2.025 | |
| plot_annoDistance | 1.509 | 0.007 | 1.516 | |
| plot_peakGeneAlias_summary | 1.237 | 0.005 | 1.242 | |
| plot_peakGeneCor | 2.819 | 0.012 | 2.832 | |
| test_geneSet | 0.001 | 0.000 | 0.000 | |