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:10 -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 kjohnson1

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.12.0
Command: /Library/Frameworks/R.framework/Resources/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/Library/Frameworks/R.framework/Resources/library --no-vignettes --timings FindIT2_1.12.0.tar.gz
StartedAt: 2025-03-18 19:43:14 -0400 (Tue, 18 Mar 2025)
EndedAt: 2025-03-18 19:49:39 -0400 (Tue, 18 Mar 2025)
EllapsedTime: 385.2 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /Library/Frameworks/R.framework/Resources/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/Library/Frameworks/R.framework/Resources/library --no-vignettes --timings FindIT2_1.12.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/Users/biocbuild/bbs-3.20-bioc/meat/FindIT2.Rcheck’
* using R version 4.4.3 (2025-02-28)
* using platform: aarch64-apple-darwin20
* R was compiled by
    Apple clang version 14.0.0 (clang-1400.0.29.202)
    GNU Fortran (GCC) 12.2.0
* running under: macOS Ventura 13.7.1
* 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 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.199  0.248   7.456
calcRP_region   6.170  0.157   6.335
calcRP_coverage 4.296  0.772   5.084
* 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:
###
###   /Library/Frameworks/R.framework/Resources/bin/R CMD INSTALL FindIT2
###
##############################################################################
##############################################################################


* installing to library ‘/Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/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-apple-darwin20

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

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database0.0000.0000.001
calcRP_TFHit4.1400.1404.315
calcRP_coverage4.2960.7725.084
calcRP_region6.1700.1576.335
enhancerPromoterCor3.0550.0883.154
findIT_MARA0.4430.0160.458
findIT_TFHit1.0000.0321.032
findIT_TTPair0.1030.0070.111
findIT_enrichFisher0.1620.0040.166
findIT_enrichWilcox0.1820.0060.188
findIT_regionRP7.1990.2487.456
getAssocPairNumber1.2570.0541.311
integrate_ChIP_RNA2.2280.0542.286
integrate_replicates0.0020.0010.003
jaccard_findIT_TTpair0.1090.0070.116
jaccard_findIT_enrichFisher0.2050.0040.210
loadPeakFile0.0580.0020.060
mm_geneBound1.3590.0931.452
mm_geneScan1.3210.0321.356
mm_nearestGene1.1860.0331.219
peakGeneCor3.5680.1333.720
plot_annoDistance1.5640.0631.628
plot_peakGeneAlias_summary1.3690.0491.420
plot_peakGeneCor2.9840.1183.105
test_geneSet0.0000.0010.000