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

This page was generated on 2025-03-20 12:12 -0400 (Thu, 20 Mar 2025).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo2Linux (Ubuntu 24.04.1 LTS)x86_644.4.3 (2025-02-28) -- "Trophy Case" 4756
palomino8Windows Server 2022 Datacenterx644.4.3 (2025-02-28 ucrt) -- "Trophy Case" 4487
merida1macOS 12.7.5 Montereyx86_644.4.3 (2025-02-28) -- "Trophy Case" 4514
kjohnson1macOS 13.6.6 Venturaarm644.4.3 (2025-02-28) -- "Trophy Case" 4441
taishanLinux (openEuler 24.03 LTS)aarch644.4.3 (2025-02-28) -- "Trophy Case" 4406
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 716/2289HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.12.0  (landing page)
Guandong Shang
Snapshot Date: 2025-03-17 13:00 -0400 (Mon, 17 Mar 2025)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: RELEASE_3_20
git_last_commit: 1bcb4fc
git_last_commit_date: 2024-10-29 11:01:40 -0400 (Tue, 29 Oct 2024)
nebbiolo2Linux (Ubuntu 24.04.1 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
palomino8Windows Server 2022 Datacenter / x64  OK    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
taishanLinux (openEuler 24.03 LTS) / aarch64  OK    OK    OK  


CHECK results for FindIT2 on taishan

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.12.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.12.0.tar.gz
StartedAt: 2025-03-18 07:39:44 -0000 (Tue, 18 Mar 2025)
EndedAt: 2025-03-18 07:47:11 -0000 (Tue, 18 Mar 2025)
EllapsedTime: 446.8 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.12.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.20-bioc/meat/FindIT2.Rcheck’
* using R version 4.4.3 (2025-02-28)
* 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)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.12.0’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘FindIT2’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking 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 7.655  0.031   7.704
calcRP_region   7.230  0.108   7.354
calcRP_coverage 6.321  0.151   6.497
calcRP_TFHit    4.607  0.325   5.141
* 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-4.4.3/site-library’
* installing *source* package ‘FindIT2’ ...
** using staged installation
** R
** data
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (FindIT2)

Tests output

FindIT2.Rcheck/tests/testthat.Rout


R version 4.4.3 (2025-02-28) -- "Trophy Case"
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

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

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database000
calcRP_TFHit4.6070.3255.141
calcRP_coverage6.3210.1516.497
calcRP_region7.2300.1087.354
enhancerPromoterCor3.6150.0923.715
findIT_MARA0.6230.0000.624
findIT_TFHit2.2150.0952.315
findIT_TTPair0.0950.0000.096
findIT_enrichFisher0.2120.0000.213
findIT_enrichWilcox0.2360.0000.237
findIT_regionRP7.6550.0317.704
getAssocPairNumber1.5190.0081.530
integrate_ChIP_RNA2.7080.0162.730
integrate_replicates0.0030.0000.003
jaccard_findIT_TTpair0.1380.0040.141
jaccard_findIT_enrichFisher0.3210.0120.334
loadPeakFile0.0780.0120.090
mm_geneBound1.6260.0081.637
mm_geneScan1.6190.0441.666
mm_nearestGene1.4720.0161.492
peakGeneCor3.1700.0243.201
plot_annoDistance1.9900.0041.998
plot_peakGeneAlias_summary1.7860.0161.806
plot_peakGeneCor4.0360.0164.060
test_geneSet0.0010.0000.001