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

This page was generated on 2025-01-30 12:11 -0500 (Thu, 30 Jan 2025).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo2Linux (Ubuntu 24.04.1 LTS)x86_644.4.2 (2024-10-31) -- "Pile of Leaves" 4746
palomino8Windows Server 2022 Datacenterx644.4.2 (2024-10-31 ucrt) -- "Pile of Leaves" 4494
merida1macOS 12.7.5 Montereyx86_644.4.2 (2024-10-31) -- "Pile of Leaves" 4517
kjohnson1macOS 13.6.6 Venturaarm644.4.2 (2024-10-31) -- "Pile of Leaves" 4469
taishanLinux (openEuler 24.03 LTS)aarch644.4.2 (2024-10-31) -- "Pile of Leaves" 4400
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-01-27 13:00 -0500 (Mon, 27 Jan 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 -0500 (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-01-28 07:10:16 -0000 (Tue, 28 Jan 2025)
EndedAt: 2025-01-28 07:17:24 -0000 (Tue, 28 Jan 2025)
EllapsedTime: 428.6 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.2 (2024-10-31)
* using platform: aarch64-unknown-linux-gnu
* R was compiled by
    aarch64-unknown-linux-gnu-gcc (GCC) 14.2.0
    GNU Fortran (GCC) 12.3.1 (openEuler 12.3.1-36.oe2403)
* 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
calcRP_coverage 8.168  0.607   8.799
findIT_regionRP 8.150  0.120   8.293
calcRP_region   6.613  0.052   6.685
* 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.2/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.2 (2024-10-31) -- "Pile of Leaves"
Copyright (C) 2024 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-01-28 07:16:12
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:13
>> preparing weight info...		2025-01-28 07:16:13
>> loading E50h_sampleChr5.bw info...		2025-01-28 07:16:13
------------
>> extracting and calcluating Chr5 signal...		2025-01-28 07:16:13
>> dealing with Chr5 left gene signal...		2025-01-28 07:16:20
>> norming Chr5RP accoring to the whole Chr RP...		2025-01-28 07:16:20
>> merging all Chr RP together...		2025-01-28 07:16:20
>> done		2025-01-28 07:16:20
>> checking seqlevels match...		2025-01-28 07:16: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-01-28 07:16:20
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:21
>> finding overlap peak in gene scan region...		2025-01-28 07:16:21
>> dealing with left peak not your gene scan region...		2025-01-28 07:16:21
>> merging two set peaks...		2025-01-28 07:16:21
>> calculating distance and dealing with gene strand...		2025-01-28 07:16:21
>> merging all info together ...		2025-01-28 07:16:22
>> done		2025-01-28 07:16:22
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:22
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-01-28 07:16:22
>> calculating RP using centerToTSS and peak score2025-01-28 07:16:22
>> merging all info together		2025-01-28 07:16:25
>> done		2025-01-28 07:16:26
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:26
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-01-28 07:16:27
>> calculating RP using centerToTSS and peak score2025-01-28 07:16:27
>> merging all info together		2025-01-28 07:16:30
>> done		2025-01-28 07:16:31
>> checking seqlevels match...		2025-01-28 07:16: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-01-28 07:16:31
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:32
>> finding overlap peak in gene scan region...		2025-01-28 07:16:32
>> dealing with left peak not your gene scan region...		2025-01-28 07:16:32
>> merging two set peaks...		2025-01-28 07:16:33
>> calculating distance and dealing with gene strand...		2025-01-28 07:16:33
>> merging all info together ...		2025-01-28 07:16:33
>> done		2025-01-28 07:16:33
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:33
>> calculating RP using centerToTSS and TF hit		2025-01-28 07:16:34
>> merging all info together		2025-01-28 07:16:34
>> done		2025-01-28 07:16:35
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:35
>> calculating RP using centerToTSS and TF hit		2025-01-28 07:16:35
>> merging all info together		2025-01-28 07:16:35
>> done		2025-01-28 07:16:36
>> checking seqlevels match...		2025-01-28 07:16: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-01-28 07:16:36
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:37
>> finding overlap peak in gene scan region...		2025-01-28 07:16:37
>> dealing with left peak not your gene scan region...		2025-01-28 07:16:37
>> merging two set peaks...		2025-01-28 07:16:38
>> calculating distance and dealing with gene strand...		2025-01-28 07:16:38
>> merging all info together ...		2025-01-28 07:16:38
>> done		2025-01-28 07:16:38
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:38
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2025-01-28 07:16:39
>> calculating RP using centerToTSS and peak score2025-01-28 07:16:39
>> merging all info together		2025-01-28 07:16:41
>> done		2025-01-28 07:16:41
>> extracting RP info from regionRP...		2025-01-28 07:16:42
>> dealing with TF_GR_databse...		2025-01-28 07:16:42
>> calculating percent and p-value...		2025-01-28 07:16:42
>> dealing withE5_0h_R1...		2025-01-28 07:16:42
>> dealing withE5_0h_R2...		2025-01-28 07:16:42
>> dealing withE5_4h_R1...		2025-01-28 07:16:42
>> dealing withE5_4h_R2...		2025-01-28 07:16:42
>> dealing withE5_8h_R1...		2025-01-28 07:16:43
>> dealing withE5_8h_R2...		2025-01-28 07:16:43
>> dealing withE5_16h_R1...		2025-01-28 07:16:43
>> dealing withE5_16h_R2...		2025-01-28 07:16:43
>> dealing withE5_24h_R1...		2025-01-28 07:16:43
>> dealing withE5_24h_R2...		2025-01-28 07:16:43
>> dealing withE5_48h_R1...		2025-01-28 07:16:43
>> dealing withE5_48h_R2...		2025-01-28 07:16:43
>> dealing withE5_48h_R3...		2025-01-28 07:16:43
>> dealing withE5_72h_R1...		2025-01-28 07:16:43
>> dealing withE5_72h_R2...		2025-01-28 07:16:43
>> dealing withE5_72h_R3...		2025-01-28 07:16:43
>> merging all info together...		2025-01-28 07:16:43
>> done		2025-01-28 07:16:43
>> preparing gene features information...		2025-01-28 07:16:44
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:44
>> calculating p-value for each TF, which may be time consuming...		2025-01-28 07:16:44
>> merging all info together...		2025-01-28 07:16:45
>> done		2025-01-28 07:16:45
>> dealing with TF_GR_database...		2025-01-28 07:16:45
>> calculating coef and converting into z-score using INT...		2025-01-28 07:16:45
>> dealing with E5_0h_R1...		2025-01-28 07:16:45
>> dealing with E5_0h_R2...		2025-01-28 07:16:45
>> dealing with E5_4h_R1...		2025-01-28 07:16:45
>> dealing with E5_4h_R2...		2025-01-28 07:16:45
>> dealing with E5_8h_R1...		2025-01-28 07:16:45
>> dealing with E5_8h_R2...		2025-01-28 07:16:46
>> dealing with E5_16h_R1...		2025-01-28 07:16:46
>> dealing with E5_16h_R2...		2025-01-28 07:16:46
>> dealing with E5_24h_R1...		2025-01-28 07:16:46
>> dealing with E5_24h_R2...		2025-01-28 07:16:46
>> dealing with E5_48h_R1...		2025-01-28 07:16:46
>> dealing with E5_48h_R2...		2025-01-28 07:16:46
>> dealing with E5_48h_R3...		2025-01-28 07:16:46
>> dealing with E5_72h_R1...		2025-01-28 07:16:46
>> dealing with E5_72h_R2...		2025-01-28 07:16:47
>> dealing with E5_72h_R3...		2025-01-28 07:16:47
>> merging all info together...		2025-01-28 07:16:47
>> done		2025-01-28 07:16:48
>> checking seqlevels match...		2025-01-28 07:16: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-01-28 07:16:48
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:16:49
>> finding overlap peak in gene scan region...		2025-01-28 07:16:49
>> dealing with left peak not your gene scan region...		2025-01-28 07:16:49
>> merging two set peaks...		2025-01-28 07:16:49
>> calculating distance and dealing with gene strand...		2025-01-28 07:16:49
>> merging all info together ...		2025-01-28 07:16:49
>> done		2025-01-28 07:16:49
>> calculating peakCenter to TSS using peak-gene pair...		2025-01-28 07:16:49
>> calculating RP using centerToTSS and TF hit		2025-01-28 07:16:50
>> merging all info together		2025-01-28 07:16:50
>> done		2025-01-28 07:16:50
>> checking seqlevels match...		2025-01-28 07:16:50
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-01-28 07:16:51
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2025-01-28 07:16: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
>> checking seqlevels match...		2025-01-28 07:16: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-01-28 07:16:54
>> finding nearest gene and calculating distance...		2025-01-28 07:16:55
>> dealing with gene strand ...		2025-01-28 07:16:55
>> merging all info together ...		2025-01-28 07:16:55
>> done		2025-01-28 07:16:55
>> checking seqlevels match...		2025-01-28 07:16: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
>> checking seqlevels match...		2025-01-28 07:16:56
>> your peak_GR seqlevel:Chr5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
Good, your Chrs in peak_GR is all in Txdb
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-01-28 07:16:56
>> finding nearest gene and calculating distance...		2025-01-28 07:16:56
>> dealing with gene strand ...		2025-01-28 07:16:57
>> merging all info together ...		2025-01-28 07:16:57
>> done		2025-01-28 07:16:57
>> checking seqlevels match...		2025-01-28 07:16: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
>> checking seqlevels match...		2025-01-28 07:16: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-01-28 07:16:58
>> finding nearest gene and calculating distance...		2025-01-28 07:16:58
>> dealing with gene strand ...		2025-01-28 07:16:59
>> merging all info together ...		2025-01-28 07:16:59
>> done		2025-01-28 07:16:59
>> checking seqlevels match...		2025-01-28 07:17:00
>> 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-01-28 07:17:00
>> 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-01-28 07:17:00
>> finding nearest gene and calculating distance...		2025-01-28 07:17:01
>> dealing with gene strand ...		2025-01-28 07:17:01
>> merging all info together ...		2025-01-28 07:17:01
>> done		2025-01-28 07:17:01
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-01-28 07:17: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
>> checking seqlevels match...		2025-01-28 07:17: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2025-01-28 07:17:02
>> finding nearest gene and calculating distance...		2025-01-28 07:17:03
>> dealing with gene strand ...		2025-01-28 07:17:03
>> merging all info together ...		2025-01-28 07:17:03
>> done		2025-01-28 07:17:03
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2025-01-28 07:17:04
>> 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-01-28 07:17:05
>> 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-01-28 07:17:06
>> checking seqlevels match...		2025-01-28 07:17:07
>> 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-01-28 07:17:08
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-01-28 07:17:10
>> merging all info together...		2025-01-28 07:17:10
>> done		2025-01-28 07:17:10
>> checking seqlevels match...		2025-01-28 07:17:10
>> 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-01-28 07:17:10
>> checking seqlevels match...		2025-01-28 07:17:10
>> 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-01-28 07:17:11
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-01-28 07:17:11
>> checking seqlevels match...		2025-01-28 07:17: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
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:17:12
>> calculating cor and pvalue, which may be time consuming...		2025-01-28 07:17:12
>> merging all info together...		2025-01-28 07:17:13
>> done		2025-01-28 07:17:13
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-01-28 07:17:13
>> merging all info together...		2025-01-28 07:17:13
>> done		2025-01-28 07:17:13
>> checking seqlevels match...		2025-01-28 07:17: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2025-01-28 07:17:13
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:17:14
>> finding overlap peak in gene scan region...		2025-01-28 07:17:14
>> dealing with left peak not your gene scan region...		2025-01-28 07:17:14
>> merging two set peaks...		2025-01-28 07:17:14
>> calculating distance and dealing with gene strand...		2025-01-28 07:17:14
>> merging all info together ...		2025-01-28 07:17:14
>> done		2025-01-28 07:17:15
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2025-01-28 07:17:16
>> merging all info together...		2025-01-28 07:17:16
>> done		2025-01-28 07:17:16
>> checking seqlevels match...		2025-01-28 07:17: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
>> using scanPromoter parameter to scan promoter for each gene...		2025-01-28 07:17:16
>> checking seqlevels match...		2025-01-28 07:17: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
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:17:17
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2025-01-28 07:17:17
>> checking seqlevels match...		2025-01-28 07:17: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
>> some scan range may cross Chr bound, trimming...		2025-01-28 07:17:18
>> calculating cor and pvalue, which may be time consuming...		2025-01-28 07:17:19
>> merging all info together...		2025-01-28 07:17:19
>> done		2025-01-28 07:17:19
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 
 80.518   2.601  83.364 

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database0.0010.0000.000
calcRP_TFHit3.9060.0844.155
calcRP_coverage8.1680.6078.799
calcRP_region6.6130.0526.685
enhancerPromoterCor4.6320.0914.736
findIT_MARA0.5870.0080.597
findIT_TFHit1.2470.0681.318
findIT_TTPair0.0960.0080.104
findIT_enrichFisher0.2140.0000.215
findIT_enrichWilcox0.2440.0000.245
findIT_regionRP8.1500.1208.293
getAssocPairNumber1.6370.0121.654
integrate_ChIP_RNA2.7740.0162.797
integrate_replicates0.0030.0000.003
jaccard_findIT_TTpair0.1380.0000.139
jaccard_findIT_enrichFisher0.2900.0040.295
loadPeakFile0.090.000.09
mm_geneBound1.6920.0041.700
mm_geneScan1.6980.0001.703
mm_nearestGene2.4550.0672.529
peakGeneCor3.1250.0203.153
plot_annoDistance2.0160.0402.061
plot_peakGeneAlias_summary2.7150.0122.734
plot_peakGeneCor4.0770.0124.101
test_geneSet0.0000.0000.001