Back to Multiple platform build/check report for BioC 3.21:   simplified   long
ABCDE[F]GHIJKLMNOPQRSTUVWXYZ

This page was generated on 2025-09-01 11:42 -0400 (Mon, 01 Sep 2025).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo1Linux (Ubuntu 24.04.3 LTS)x86_644.5.1 (2025-06-13) -- "Great Square Root" 4824
merida1macOS 12.7.5 Montereyx86_644.5.1 RC (2025-06-05 r88288) -- "Great Square Root" 4606
kjohnson1macOS 13.6.6 Venturaarm644.5.1 Patched (2025-06-14 r88325) -- "Great Square Root" 4547
kunpeng2Linux (openEuler 24.03 LTS)aarch64R Under development (unstable) (2025-02-19 r87757) -- "Unsuffered Consequences" 4579
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 730/2341HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.14.0  (landing page)
Guandong Shang
Snapshot Date: 2025-08-28 13:40 -0400 (Thu, 28 Aug 2025)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: RELEASE_3_21
git_last_commit: b0f7ffc
git_last_commit_date: 2025-04-15 12:34:18 -0400 (Tue, 15 Apr 2025)
nebbiolo1Linux (Ubuntu 24.04.3 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
merida1macOS 12.7.5 Monterey / x86_64  OK    OK    OK    OK  UNNEEDED, same version is already published
kjohnson1macOS 13.6.6 Ventura / arm64  OK    OK    OK    OK  UNNEEDED, same version is already published
kunpeng2Linux (openEuler 24.03 LTS) / aarch64  OK    OK    OK  


CHECK results for FindIT2 on kunpeng2

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.
- See Martin Grigorov's blog post for how to debug Linux ARM64 related issues on a x86_64 host.

raw results


Summary

Package: FindIT2
Version: 1.14.0
Command: /home/biocbuild/R/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/R/R/site-library --no-vignettes --timings FindIT2_1.14.0.tar.gz
StartedAt: 2025-08-29 09:28:56 -0000 (Fri, 29 Aug 2025)
EndedAt: 2025-08-29 09:36:46 -0000 (Fri, 29 Aug 2025)
EllapsedTime: 470.2 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/R/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/R/R/site-library --no-vignettes --timings FindIT2_1.14.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.21-bioc/meat/FindIT2.Rcheck’
* using R Under development (unstable) (2025-02-19 r87757)
* using platform: aarch64-unknown-linux-gnu
* R was compiled by
    aarch64-unknown-linux-gnu-gcc (GCC) 14.2.0
    GNU Fortran (GCC) 14.2.0
* running under: openEuler 24.03 (LTS-SP1)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.14.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
calcRP_coverage  8.179  0.212   8.408
findIT_regionRP  8.220  0.012   8.251
calcRP_region    6.460  0.048   6.524
plot_peakGeneCor 4.991  0.072   5.075
* 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


Installation output

FindIT2.Rcheck/00install.out

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/R/R/bin/R CMD INSTALL FindIT2
###
##############################################################################
##############################################################################


* installing to library ‘/home/biocbuild/R/R-devel_2025-02-19/site-library’
* installing *source* package ‘FindIT2’ ...
** this is package ‘FindIT2’ version ‘1.14.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)

Tests output

FindIT2.Rcheck/tests/testthat.Rout


R Under development (unstable) (2025-02-19 r87757) -- "Unsuffered Consequences"
Copyright (C) 2025 The R Foundation for Statistical Computing
Platform: aarch64-unknown-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: 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...		2025-08-29 09:35:28
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:35:30
>> preparing weight info...		2025-08-29 09:35:30
>> loading E50h_sampleChr5.bw info...		2025-08-29 09:35:30
------------
>> extracting and calcluating Chr5 signal...		2025-08-29 09:35:30
>> dealing with Chr5 left gene signal...		2025-08-29 09:35:38
>> norming Chr5RP accoring to the whole Chr RP...		2025-08-29 09:35:38
>> merging all Chr RP together...		2025-08-29 09:35:38
>> done		2025-08-29 09:35:38
>> checking seqlevels match...		2025-08-29 09:35:38
>> 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-08-29 09:35:38
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:35:39
>> finding overlap peak in gene scan region...		2025-08-29 09:35:39
>> dealing with left peak not your gene scan region...		2025-08-29 09:35:39
>> merging two set peaks...		2025-08-29 09:35:39
>> calculating distance and dealing with gene strand...		2025-08-29 09:35:40
>> merging all info together ...		2025-08-29 09:35:40
>> done		2025-08-29 09:35:40
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:35:40
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-29 09:35:41
>> calculating RP using centerToTSS and peak score2025-08-29 09:35:41
>> merging all info together		2025-08-29 09:35:43
>> done		2025-08-29 09:35:45
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:35:45
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-29 09:35:46
>> calculating RP using centerToTSS and peak score2025-08-29 09:35:46
>> merging all info together		2025-08-29 09:35:50
>> done		2025-08-29 09:35:50
>> checking seqlevels match...		2025-08-29 09:35:50
>> 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-08-29 09:35:50
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:35:52
>> finding overlap peak in gene scan region...		2025-08-29 09:35:52
>> dealing with left peak not your gene scan region...		2025-08-29 09:35:52
>> merging two set peaks...		2025-08-29 09:35:52
>> calculating distance and dealing with gene strand...		2025-08-29 09:35:52
>> merging all info together ...		2025-08-29 09:35:52
>> done		2025-08-29 09:35:52
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:35:52
>> calculating RP using centerToTSS and TF hit		2025-08-29 09:35:53
>> merging all info together		2025-08-29 09:35:53
>> done		2025-08-29 09:35:53
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:35:53
>> calculating RP using centerToTSS and TF hit		2025-08-29 09:35:54
>> merging all info together		2025-08-29 09:35:54
>> done		2025-08-29 09:35:54
>> checking seqlevels match...		2025-08-29 09:35: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-08-29 09:35:55
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:35:56
>> finding overlap peak in gene scan region...		2025-08-29 09:35:56
>> dealing with left peak not your gene scan region...		2025-08-29 09:35:56
>> merging two set peaks...		2025-08-29 09:35:57
>> calculating distance and dealing with gene strand...		2025-08-29 09:35:57
>> merging all info together ...		2025-08-29 09:35:57
>> done		2025-08-29 09:35:57
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:35:57
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-29 09:35:59
>> calculating RP using centerToTSS and peak score2025-08-29 09:35:59
>> merging all info together		2025-08-29 09:36:02
>> done		2025-08-29 09:36:02
>> extracting RP info from regionRP...		2025-08-29 09:36:03
>> dealing with TF_GR_databse...		2025-08-29 09:36:03
>> calculating percent and p-value...		2025-08-29 09:36:03
>> dealing withE5_0h_R1...		2025-08-29 09:36:03
>> dealing withE5_0h_R2...		2025-08-29 09:36:03
>> dealing withE5_4h_R1...		2025-08-29 09:36:03
>> dealing withE5_4h_R2...		2025-08-29 09:36:03
>> dealing withE5_8h_R1...		2025-08-29 09:36:03
>> dealing withE5_8h_R2...		2025-08-29 09:36:03
>> dealing withE5_16h_R1...		2025-08-29 09:36:03
>> dealing withE5_16h_R2...		2025-08-29 09:36:03
>> dealing withE5_24h_R1...		2025-08-29 09:36:04
>> dealing withE5_24h_R2...		2025-08-29 09:36:04
>> dealing withE5_48h_R1...		2025-08-29 09:36:04
>> dealing withE5_48h_R2...		2025-08-29 09:36:04
>> dealing withE5_48h_R3...		2025-08-29 09:36:04
>> dealing withE5_72h_R1...		2025-08-29 09:36:04
>> dealing withE5_72h_R2...		2025-08-29 09:36:04
>> dealing withE5_72h_R3...		2025-08-29 09:36:04
>> merging all info together...		2025-08-29 09:36:04
>> done		2025-08-29 09:36:04
>> preparing gene features information...		2025-08-29 09:36:04
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:36:05
>> calculating p-value for each TF, which may be time consuming...		2025-08-29 09:36:05
>> merging all info together...		2025-08-29 09:36:05
>> done		2025-08-29 09:36:05
>> dealing with TF_GR_database...		2025-08-29 09:36:06
>> calculating coef and converting into z-score using INT...		2025-08-29 09:36:06
>> dealing with E5_0h_R1...		2025-08-29 09:36:06
>> dealing with E5_0h_R2...		2025-08-29 09:36:06
>> dealing with E5_4h_R1...		2025-08-29 09:36:06
>> dealing with E5_4h_R2...		2025-08-29 09:36:06
>> dealing with E5_8h_R1...		2025-08-29 09:36:06
>> dealing with E5_8h_R2...		2025-08-29 09:36:06
>> dealing with E5_16h_R1...		2025-08-29 09:36:06
>> dealing with E5_16h_R2...		2025-08-29 09:36:06
>> dealing with E5_24h_R1...		2025-08-29 09:36:07
>> dealing with E5_24h_R2...		2025-08-29 09:36:07
>> dealing with E5_48h_R1...		2025-08-29 09:36:07
>> dealing with E5_48h_R2...		2025-08-29 09:36:07
>> dealing with E5_48h_R3...		2025-08-29 09:36:07
>> dealing with E5_72h_R1...		2025-08-29 09:36:07
>> dealing with E5_72h_R2...		2025-08-29 09:36:07
>> dealing with E5_72h_R3...		2025-08-29 09:36:07
>> merging all info together...		2025-08-29 09:36:07
>> done		2025-08-29 09:36:08
>> checking seqlevels match...		2025-08-29 09:36: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-08-29 09:36:08
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:36:09
>> finding overlap peak in gene scan region...		2025-08-29 09:36:09
>> dealing with left peak not your gene scan region...		2025-08-29 09:36:09
>> merging two set peaks...		2025-08-29 09:36:09
>> calculating distance and dealing with gene strand...		2025-08-29 09:36:09
>> merging all info together ...		2025-08-29 09:36:09
>> done		2025-08-29 09:36:09
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-29 09:36:09
>> calculating RP using centerToTSS and TF hit		2025-08-29 09:36:10
>> merging all info together		2025-08-29 09:36:10
>> done		2025-08-29 09:36:10
>> checking seqlevels match...		2025-08-29 09:36:11
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-08-29 09:36:11
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-08-29 09:36: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
>> checking seqlevels match...		2025-08-29 09:36: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-08-29 09:36:15
>> finding nearest gene and calculating distance...		2025-08-29 09:36:16
>> dealing with gene strand ...		2025-08-29 09:36:16
>> merging all info together ...		2025-08-29 09:36:16
>> done		2025-08-29 09:36:16
>> checking seqlevels match...		2025-08-29 09:36: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
>> checking seqlevels match...		2025-08-29 09:36: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-08-29 09:36:16
>> finding nearest gene and calculating distance...		2025-08-29 09:36:17
>> dealing with gene strand ...		2025-08-29 09:36:17
>> merging all info together ...		2025-08-29 09:36:17
>> done		2025-08-29 09:36:17
>> checking seqlevels match...		2025-08-29 09:36:18
>> 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-08-29 09:36:18
>> 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-08-29 09:36:18
>> finding nearest gene and calculating distance...		2025-08-29 09:36:19
>> dealing with gene strand ...		2025-08-29 09:36:19
>> merging all info together ...		2025-08-29 09:36:19
>> done		2025-08-29 09:36:19
>> checking seqlevels match...		2025-08-29 09:36:20
>> 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-08-29 09:36:21
>> 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-08-29 09:36:21
>> finding nearest gene and calculating distance...		2025-08-29 09:36:22
>> dealing with gene strand ...		2025-08-29 09:36:22
>> merging all info together ...		2025-08-29 09:36:22
>> done		2025-08-29 09:36:22
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-08-29 09:36: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
>> checking seqlevels match...		2025-08-29 09:36: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-08-29 09:36:23
>> finding nearest gene and calculating distance...		2025-08-29 09:36:24
>> dealing with gene strand ...		2025-08-29 09:36:24
>> merging all info together ...		2025-08-29 09:36:24
>> done		2025-08-29 09:36:24
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-08-29 09:36:25
>> 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-08-29 09:36: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
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:36:27
>> checking seqlevels match...		2025-08-29 09:36:28
>> 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-08-29 09:36:29
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-29 09:36:31
>> merging all info together...		2025-08-29 09:36:31
>> done		2025-08-29 09:36:31
>> checking seqlevels match...		2025-08-29 09:36: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
>> using scanPromoter parameter to scan promoter for each gene...		2025-08-29 09:36:31
>> checking seqlevels match...		2025-08-29 09:36: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
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:36:32
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-08-29 09:36:33
>> checking seqlevels match...		2025-08-29 09:36:33
>> 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-08-29 09:36:34
>> calculating cor and pvalue, which may be time consuming...		2025-08-29 09:36:34
>> merging all info together...		2025-08-29 09:36:34
>> done		2025-08-29 09:36:34
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-29 09:36:34
>> merging all info together...		2025-08-29 09:36:35
>> done		2025-08-29 09:36:35
>> checking seqlevels match...		2025-08-29 09:36: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-08-29 09:36:35
>> some scan range may cross Chr bound, trimming...		2025-08-29 09:36:36
>> finding overlap peak in gene scan region...		2025-08-29 09:36:36
>> dealing with left peak not your gene scan region...		2025-08-29 09:36:36
>> merging two set peaks...		2025-08-29 09:36:36
>> calculating distance and dealing with gene strand...		2025-08-29 09:36:36
>> merging all info together ...		2025-08-29 09:36:36
>> done		2025-08-29 09:36:36
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-29 09:36:38
>> merging all info together...		2025-08-29 09:36:38
>> done		2025-08-29 09:36:38
>> checking seqlevels match...		2025-08-29 09:36:38
>> 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-08-29 09:36:38
>> checking seqlevels match...		2025-08-29 09:36:38
>> 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-08-29 09:36:39
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-08-29 09:36:39
>> checking seqlevels match...		2025-08-29 09:36:39
>> 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-08-29 09:36:40
>> calculating cor and pvalue, which may be time consuming...		2025-08-29 09:36:41
>> merging all info together...		2025-08-29 09:36:41
>> done		2025-08-29 09:36:41
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 
 88.371   2.592  91.140 

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database000
calcRP_TFHit4.6470.1474.966
calcRP_coverage8.1790.2128.408
calcRP_region6.4600.0486.524
enhancerPromoterCor3.3850.0203.412
findIT_MARA0.5970.0040.602
findIT_TFHit1.3270.0081.337
findIT_TTPair0.0950.0000.096
findIT_enrichFisher0.2050.0040.209
findIT_enrichWilcox0.230.000.23
findIT_regionRP8.2200.0128.251
getAssocPairNumber1.5530.0081.564
integrate_ChIP_RNA2.6790.0042.688
integrate_replicates0.0020.0000.002
jaccard_findIT_TTpair0.1220.0040.126
jaccard_findIT_enrichFisher0.2550.0040.260
loadPeakFile0.1090.0000.109
mm_geneBound1.6050.0041.613
mm_geneScan1.6140.0031.625
mm_nearestGene1.4560.0071.467
peakGeneCor3.2160.0003.222
plot_annoDistance1.9810.0081.993
plot_peakGeneAlias_summary1.7410.0041.749
plot_peakGeneCor4.9910.0725.075
test_geneSet000