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

This page was generated on 2025-08-16 12:03 -0400 (Sat, 16 Aug 2025).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo2Linux (Ubuntu 24.04.3 LTS)x86_644.5.1 (2025-06-13) -- "Great Square Root" 4818
lconwaymacOS 12.7.1 Montereyx86_644.5.1 (2025-06-13) -- "Great Square Root" 4596
kjohnson3macOS 13.7.7 Venturaarm644.5.1 Patched (2025-06-14 r88325) -- "Great Square Root" 4538
taishanLinux (openEuler 24.03 LTS)aarch644.5.0 (2025-04-11) -- "How About a Twenty-Six" 4535
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/2317HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.15.1  (landing page)
Guandong Shang
Snapshot Date: 2025-08-15 13:45 -0400 (Fri, 15 Aug 2025)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: devel
git_last_commit: 82d0b10
git_last_commit_date: 2025-07-22 19:49:08 -0400 (Tue, 22 Jul 2025)
nebbiolo2Linux (Ubuntu 24.04.3 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
lconwaymacOS 12.7.1 Monterey / x86_64  OK    OK    OK    OK  UNNEEDED, same version is already published
kjohnson3macOS 13.7.7 Ventura / arm64  OK    OK    OK    OK  UNNEEDED, same version is already published
taishanLinux (openEuler 24.03 LTS) / aarch64  OK    OK    OK  


CHECK results for FindIT2 on nebbiolo2

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.

raw results


Summary

Package: FindIT2
Version: 1.15.1
Command: /home/biocbuild/bbs-3.22-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.22-bioc/R/site-library --timings FindIT2_1.15.1.tar.gz
StartedAt: 2025-08-15 22:25:22 -0400 (Fri, 15 Aug 2025)
EndedAt: 2025-08-15 22:31:54 -0400 (Fri, 15 Aug 2025)
EllapsedTime: 391.7 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.22-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.22-bioc/R/site-library --timings FindIT2_1.15.1.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.22-bioc/meat/FindIT2.Rcheck’
* using R version 4.5.1 (2025-06-13)
* 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.15.1’
* 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 5.318  0.028   5.346
* 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


Installation output

FindIT2.Rcheck/00install.out

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.22-bioc/R/bin/R CMD INSTALL FindIT2
###
##############################################################################
##############################################################################


* installing to library ‘/home/biocbuild/bbs-3.22-bioc/R/site-library’
* installing *source* package ‘FindIT2’ ...
** this is package ‘FindIT2’ version ‘1.15.1’
** 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 version 4.5.1 (2025-06-13) -- "Great Square Root"
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-08-15 22:30:06
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:08
>> preparing weight info...		2025-08-15 22:30:08
>> loading E50h_sampleChr5.bw info...		2025-08-15 22:30:08
------------
>> extracting and calcluating Chr5 signal...		2025-08-15 22:30:08
>> dealing with Chr5 left gene signal...		2025-08-15 22:30:11
>> norming Chr5RP accoring to the whole Chr RP...		2025-08-15 22:30:11
>> merging all Chr RP together...		2025-08-15 22:30:11
>> done		2025-08-15 22:30:11
>> checking seqlevels match...		2025-08-15 22:30: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-08-15 22:30:11
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:12
>> finding overlap peak in gene scan region...		2025-08-15 22:30:12
>> dealing with left peak not your gene scan region...		2025-08-15 22:30:12
>> merging two set peaks...		2025-08-15 22:30:12
>> calculating distance and dealing with gene strand...		2025-08-15 22:30:13
>> merging all info together ...		2025-08-15 22:30:13
>> done		2025-08-15 22:30:13
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:13
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-15 22:30:13
>> calculating RP using centerToTSS and peak score2025-08-15 22:30:13
>> merging all info together		2025-08-15 22:30:15
>> done		2025-08-15 22:30:16
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:16
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-15 22:30:17
>> calculating RP using centerToTSS and peak score2025-08-15 22:30:17
>> merging all info together		2025-08-15 22:30:19
>> done		2025-08-15 22:30:20
>> checking seqlevels match...		2025-08-15 22:30: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-08-15 22:30:20
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:20
>> finding overlap peak in gene scan region...		2025-08-15 22:30:20
>> dealing with left peak not your gene scan region...		2025-08-15 22:30:20
>> merging two set peaks...		2025-08-15 22:30:21
>> calculating distance and dealing with gene strand...		2025-08-15 22:30:21
>> merging all info together ...		2025-08-15 22:30:21
>> done		2025-08-15 22:30:21
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:21
>> calculating RP using centerToTSS and TF hit		2025-08-15 22:30:21
>> merging all info together		2025-08-15 22:30:21
>> done		2025-08-15 22:30:21
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:21
>> calculating RP using centerToTSS and TF hit		2025-08-15 22:30:22
>> merging all info together		2025-08-15 22:30:22
>> done		2025-08-15 22:30:22
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30:23
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:25
>> finding overlap peak in gene scan region...		2025-08-15 22:30:25
>> dealing with left peak not your gene scan region...		2025-08-15 22:30:25
>> merging two set peaks...		2025-08-15 22:30:25
>> calculating distance and dealing with gene strand...		2025-08-15 22:30:25
>> merging all info together ...		2025-08-15 22:30:25
>> done		2025-08-15 22:30:25
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:25
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-08-15 22:30:25
>> calculating RP using centerToTSS and peak score2025-08-15 22:30:25
>> merging all info together		2025-08-15 22:30:27
>> done		2025-08-15 22:30:28
>> extracting RP info from regionRP...		2025-08-15 22:30:28
>> dealing with TF_GR_databse...		2025-08-15 22:30:28
>> calculating percent and p-value...		2025-08-15 22:30:28
>> dealing withE5_0h_R1...		2025-08-15 22:30:28
>> dealing withE5_0h_R2...		2025-08-15 22:30:28
>> dealing withE5_4h_R1...		2025-08-15 22:30:28
>> dealing withE5_4h_R2...		2025-08-15 22:30:28
>> dealing withE5_8h_R1...		2025-08-15 22:30:28
>> dealing withE5_8h_R2...		2025-08-15 22:30:28
>> dealing withE5_16h_R1...		2025-08-15 22:30:28
>> dealing withE5_16h_R2...		2025-08-15 22:30:29
>> dealing withE5_24h_R1...		2025-08-15 22:30:29
>> dealing withE5_24h_R2...		2025-08-15 22:30:29
>> dealing withE5_48h_R1...		2025-08-15 22:30:29
>> dealing withE5_48h_R2...		2025-08-15 22:30:29
>> dealing withE5_48h_R3...		2025-08-15 22:30:29
>> dealing withE5_72h_R1...		2025-08-15 22:30:29
>> dealing withE5_72h_R2...		2025-08-15 22:30:29
>> dealing withE5_72h_R3...		2025-08-15 22:30:29
>> merging all info together...		2025-08-15 22:30:29
>> done		2025-08-15 22:30:29
>> preparing gene features information...		2025-08-15 22:30:29
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:30
>> calculating p-value for each TF, which may be time consuming...		2025-08-15 22:30:30
>> merging all info together...		2025-08-15 22:30:30
>> done		2025-08-15 22:30:30
>> dealing with TF_GR_database...		2025-08-15 22:30:30
>> calculating coef and converting into z-score using INT...		2025-08-15 22:30:30
>> dealing with E5_0h_R1...		2025-08-15 22:30:30
>> dealing with E5_0h_R2...		2025-08-15 22:30:30
>> dealing with E5_4h_R1...		2025-08-15 22:30:30
>> dealing with E5_4h_R2...		2025-08-15 22:30:30
>> dealing with E5_8h_R1...		2025-08-15 22:30:30
>> dealing with E5_8h_R2...		2025-08-15 22:30:30
>> dealing with E5_16h_R1...		2025-08-15 22:30:31
>> dealing with E5_16h_R2...		2025-08-15 22:30:31
>> dealing with E5_24h_R1...		2025-08-15 22:30:31
>> dealing with E5_24h_R2...		2025-08-15 22:30:31
>> dealing with E5_48h_R1...		2025-08-15 22:30:31
>> dealing with E5_48h_R2...		2025-08-15 22:30:31
>> dealing with E5_48h_R3...		2025-08-15 22:30:31
>> dealing with E5_72h_R1...		2025-08-15 22:30:31
>> dealing with E5_72h_R2...		2025-08-15 22:30:31
>> dealing with E5_72h_R3...		2025-08-15 22:30:31
>> merging all info together...		2025-08-15 22:30:31
>> done		2025-08-15 22:30:31
>> checking seqlevels match...		2025-08-15 22:30:32
>> 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-15 22:30:32
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:32
>> finding overlap peak in gene scan region...		2025-08-15 22:30:32
>> dealing with left peak not your gene scan region...		2025-08-15 22:30:32
>> merging two set peaks...		2025-08-15 22:30:32
>> calculating distance and dealing with gene strand...		2025-08-15 22:30:32
>> merging all info together ...		2025-08-15 22:30:32
>> done		2025-08-15 22:30:32
>> calculating peakCenter to TSS using peak-gene pair...		2025-08-15 22:30:32
>> calculating RP using centerToTSS and TF hit		2025-08-15 22:30:33
>> merging all info together		2025-08-15 22:30:33
>> done		2025-08-15 22:30:33
>> checking seqlevels match...		2025-08-15 22:30:33
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-08-15 22:30:34
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-08-15 22:30:36
>> 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-15 22:30:36
>> 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-15 22:30:36
>> finding nearest gene and calculating distance...		2025-08-15 22:30:37
>> dealing with gene strand ...		2025-08-15 22:30:37
>> merging all info together ...		2025-08-15 22:30:37
>> done		2025-08-15 22:30:37
>> checking seqlevels match...		2025-08-15 22:30:37
>> 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-15 22:30:37
>> 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-15 22:30:37
>> finding nearest gene and calculating distance...		2025-08-15 22:30:38
>> dealing with gene strand ...		2025-08-15 22:30:38
>> merging all info together ...		2025-08-15 22:30:38
>> done		2025-08-15 22:30:38
>> checking seqlevels match...		2025-08-15 22:30: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
>> checking seqlevels match...		2025-08-15 22:30: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-08-15 22:30:39
>> finding nearest gene and calculating distance...		2025-08-15 22:30:39
>> dealing with gene strand ...		2025-08-15 22:30:39
>> merging all info together ...		2025-08-15 22:30:39
>> done		2025-08-15 22:30:39
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30: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-08-15 22:30:41
>> finding nearest gene and calculating distance...		2025-08-15 22:30:42
>> dealing with gene strand ...		2025-08-15 22:30:42
>> merging all info together ...		2025-08-15 22:30:42
>> done		2025-08-15 22:30:42
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30: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-08-15 22:30:43
>> finding nearest gene and calculating distance...		2025-08-15 22:30:43
>> dealing with gene strand ...		2025-08-15 22:30:43
>> merging all info together ...		2025-08-15 22:30:43
>> done		2025-08-15 22:30:43
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30: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
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:45
>> checking seqlevels match...		2025-08-15 22:30:46
>> 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-15 22:30:47
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-15 22:30:48
>> merging all info together...		2025-08-15 22:30:48
>> done		2025-08-15 22:30:48
>> checking seqlevels match...		2025-08-15 22:30: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
>> using scanPromoter parameter to scan promoter for each gene...		2025-08-15 22:30:48
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30:49
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-08-15 22:30:49
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30:50
>> calculating cor and pvalue, which may be time consuming...		2025-08-15 22:30:50
>> merging all info together...		2025-08-15 22:30:50
>> done		2025-08-15 22:30:50
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-15 22:30:50
>> merging all info together...		2025-08-15 22:30:50
>> done		2025-08-15 22:30:50
>> checking seqlevels match...		2025-08-15 22:30: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-15 22:30:50
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:51
>> finding overlap peak in gene scan region...		2025-08-15 22:30:51
>> dealing with left peak not your gene scan region...		2025-08-15 22:30:51
>> merging two set peaks...		2025-08-15 22:30:51
>> calculating distance and dealing with gene strand...		2025-08-15 22:30:51
>> merging all info together ...		2025-08-15 22:30:51
>> done		2025-08-15 22:30:51
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-08-15 22:30:52
>> merging all info together...		2025-08-15 22:30:52
>> done		2025-08-15 22:30:52
>> checking seqlevels match...		2025-08-15 22:30: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
>> using scanPromoter parameter to scan promoter for each gene...		2025-08-15 22:30:52
>> checking seqlevels match...		2025-08-15 22:30: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-08-15 22:30:53
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-08-15 22:30:53
>> checking seqlevels match...		2025-08-15 22:30: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
>> some scan range may cross Chr bound, trimming...		2025-08-15 22:30:54
>> calculating cor and pvalue, which may be time consuming...		2025-08-15 22:30:54
>> merging all info together...		2025-08-15 22:30:54
>> done		2025-08-15 22:30:54
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 
 58.854   1.629  60.477 

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database000
calcRP_TFHit2.5990.0892.748
calcRP_coverage4.1360.7934.930
calcRP_region4.3060.0694.374
enhancerPromoterCor3.2640.0333.297
findIT_MARA0.4030.0000.403
findIT_TFHit0.8490.0030.853
findIT_TTPair0.0680.0010.069
findIT_enrichFisher0.1470.0010.149
findIT_enrichWilcox0.1610.0020.163
findIT_regionRP5.3180.0285.346
getAssocPairNumber1.0870.0021.089
integrate_ChIP_RNA1.8170.0011.818
integrate_replicates0.0020.0000.002
jaccard_findIT_TTpair0.0890.0020.091
jaccard_findIT_enrichFisher0.1890.0000.189
loadPeakFile0.0550.0000.055
mm_geneBound1.0960.0031.099
mm_geneScan1.1090.0041.113
mm_nearestGene0.9910.0020.993
peakGeneCor2.0870.0072.094
plot_annoDistance1.3830.0011.384
plot_peakGeneAlias_summary1.2270.0051.233
plot_peakGeneCor2.6220.0152.637
test_geneSet000