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

This page was generated on 2024-03-04 11:39:12 -0500 (Mon, 04 Mar 2024).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo1Linux (Ubuntu 22.04.3 LTS)x86_64R Under development (unstable) (2024-01-16 r85808) -- "Unsuffered Consequences" 4676
palomino3Windows Server 2022 Datacenterx64R Under development (unstable) (2024-01-14 r85805 ucrt) -- "Unsuffered Consequences" 4414
merida1macOS 12.7.1 Montereyx86_64R Under development (unstable) (2024-01-16 r85808) -- "Unsuffered Consequences" 4441
kunpeng2Linux (openEuler 22.03 LTS-SP1)aarch64R Under development (unstable) (2024-01-16 r85812) -- "Unsuffered Consequences" 4417
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 711/2251HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.9.1  (landing page)
Guandong Shang
Snapshot Date: 2024-03-01 14:00:22 -0500 (Fri, 01 Mar 2024)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: devel
git_last_commit: ad4f102
git_last_commit_date: 2024-02-27 03:41:20 -0500 (Tue, 27 Feb 2024)
nebbiolo1Linux (Ubuntu 22.04.3 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
palomino3Windows Server 2022 Datacenter / x64  OK    OK    OK    OK  UNNEEDED, same version is already published
merida1macOS 12.7.1 Monterey / x86_64  OK    OK    OK    OK  UNNEEDED, same version is already published
kunpeng2Linux (openEuler 22.03 LTS-SP1) / aarch64  OK    OK    OK  

CHECK results for FindIT2 on merida1


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.9.1
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.9.1.tar.gz
StartedAt: 2024-03-02 04:01:38 -0500 (Sat, 02 Mar 2024)
EndedAt: 2024-03-02 04:15:24 -0500 (Sat, 02 Mar 2024)
EllapsedTime: 826.1 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.9.1.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/Users/biocbuild/bbs-3.19-bioc/meat/FindIT2.Rcheck’
* using R Under development (unstable) (2024-01-16 r85808)
* using platform: x86_64-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 Monterey 12.7.1
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.9.1’
* 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 R 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     11.078  0.243  13.032
calcRP_region        9.275  0.298  11.704
plot_peakGeneCor     6.922  0.303   8.998
calcRP_TFHit         6.473  0.296   8.314
peakGeneCor          5.530  0.088   6.622
calcRP_coverage      4.642  0.708   7.734
enhancerPromoterCor  4.895  0.129   5.144
integrate_ChIP_RNA   4.075  0.096   5.068
* 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-x86_64/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 Under development (unstable) (2024-01-16 r85808) -- "Unsuffered Consequences"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-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, 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...		2024-03-02 04:13:02
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:13:05
>> preparing weight info...		2024-03-02 04:13:05
>> loading E50h_sampleChr5.bw info...		2024-03-02 04:13:05
------------
>> extracting and calcluating Chr5 signal...		2024-03-02 04:13:06
>> dealing with Chr5 left gene signal...		2024-03-02 04:13:11
>> norming Chr5RP accoring to the whole Chr RP...		2024-03-02 04:13:11
>> merging all Chr RP together...		2024-03-02 04:13:11
>> done		2024-03-02 04:13:11
>> checking seqlevels match...		2024-03-02 04:13: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...		2024-03-02 04:13:12
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:13:14
>> finding overlap peak in gene scan region...		2024-03-02 04:13:14
>> dealing with left peak not your gene scan region...		2024-03-02 04:13:14
>> merging two set peaks...		2024-03-02 04:13:15
>> calculating distance and dealing with gene strand...		2024-03-02 04:13:15
>> merging all info together ...		2024-03-02 04:13:15
>> done		2024-03-02 04:13:15
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:13:15
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-03-02 04:13:18
>> calculating RP using centerToTSS and peak score2024-03-02 04:13:18
>> merging all info together		2024-03-02 04:13:22
>> done		2024-03-02 04:13:24
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:13:24
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-03-02 04:13:26
>> calculating RP using centerToTSS and peak score2024-03-02 04:13:26
>> merging all info together		2024-03-02 04:13:31
>> done		2024-03-02 04:13:31
>> checking seqlevels match...		2024-03-02 04:13: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...		2024-03-02 04:13:32
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:13:34
>> finding overlap peak in gene scan region...		2024-03-02 04:13:34
>> dealing with left peak not your gene scan region...		2024-03-02 04:13:34
>> merging two set peaks...		2024-03-02 04:13:34
>> calculating distance and dealing with gene strand...		2024-03-02 04:13:34
>> merging all info together ...		2024-03-02 04:13:34
>> done		2024-03-02 04:13:34
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:13:34
>> calculating RP using centerToTSS and TF hit		2024-03-02 04:13:36
>> merging all info together		2024-03-02 04:13:36
>> done		2024-03-02 04:13:36
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:13:36
>> calculating RP using centerToTSS and TF hit		2024-03-02 04:13:37
>> merging all info together		2024-03-02 04:13:37
>> done		2024-03-02 04:13:38
>> checking seqlevels match...		2024-03-02 04:13:40
>> 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...		2024-03-02 04:13:40
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:13:41
>> finding overlap peak in gene scan region...		2024-03-02 04:13:41
>> dealing with left peak not your gene scan region...		2024-03-02 04:13:42
>> merging two set peaks...		2024-03-02 04:13:42
>> calculating distance and dealing with gene strand...		2024-03-02 04:13:42
>> merging all info together ...		2024-03-02 04:13:42
>> done		2024-03-02 04:13:42
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:13:42
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-03-02 04:13:44
>> calculating RP using centerToTSS and peak score2024-03-02 04:13:44
>> merging all info together		2024-03-02 04:13:49
>> done		2024-03-02 04:13:50
>> extracting RP info from regionRP...		2024-03-02 04:13:51
>> dealing with TF_GR_databse...		2024-03-02 04:13:51
>> calculating percent and p-value...		2024-03-02 04:13:52
>> dealing withE5_0h_R1...		2024-03-02 04:13:52
>> dealing withE5_0h_R2...		2024-03-02 04:13:52
>> dealing withE5_4h_R1...		2024-03-02 04:13:52
>> dealing withE5_4h_R2...		2024-03-02 04:13:52
>> dealing withE5_8h_R1...		2024-03-02 04:13:52
>> dealing withE5_8h_R2...		2024-03-02 04:13:52
>> dealing withE5_16h_R1...		2024-03-02 04:13:52
>> dealing withE5_16h_R2...		2024-03-02 04:13:53
>> dealing withE5_24h_R1...		2024-03-02 04:13:53
>> dealing withE5_24h_R2...		2024-03-02 04:13:53
>> dealing withE5_48h_R1...		2024-03-02 04:13:53
>> dealing withE5_48h_R2...		2024-03-02 04:13:53
>> dealing withE5_48h_R3...		2024-03-02 04:13:53
>> dealing withE5_72h_R1...		2024-03-02 04:13:53
>> dealing withE5_72h_R2...		2024-03-02 04:13:53
>> dealing withE5_72h_R3...		2024-03-02 04:13:54
>> merging all info together...		2024-03-02 04:13:54
>> done		2024-03-02 04:13:54
>> preparing gene features information...		2024-03-02 04:13:55
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:13:56
>> calculating p-value for each TF, which may be time consuming...		2024-03-02 04:13:56
>> merging all info together...		2024-03-02 04:13:56
>> done		2024-03-02 04:13:57
>> dealing with TF_GR_database...		2024-03-02 04:13:57
>> calculating coef and converting into z-score using INT...		2024-03-02 04:13:57
>> dealing with E5_0h_R1...		2024-03-02 04:13:57
>> dealing with E5_0h_R2...		2024-03-02 04:13:58
>> dealing with E5_4h_R1...		2024-03-02 04:13:58
>> dealing with E5_4h_R2...		2024-03-02 04:13:58
>> dealing with E5_8h_R1...		2024-03-02 04:13:58
>> dealing with E5_8h_R2...		2024-03-02 04:13:59
>> dealing with E5_16h_R1...		2024-03-02 04:13:59
>> dealing with E5_16h_R2...		2024-03-02 04:13:59
>> dealing with E5_24h_R1...		2024-03-02 04:13:59
>> dealing with E5_24h_R2...		2024-03-02 04:14:00
>> dealing with E5_48h_R1...		2024-03-02 04:14:00
>> dealing with E5_48h_R2...		2024-03-02 04:14:00
>> dealing with E5_48h_R3...		2024-03-02 04:14:00
>> dealing with E5_72h_R1...		2024-03-02 04:14:00
>> dealing with E5_72h_R2...		2024-03-02 04:14:00
>> dealing with E5_72h_R3...		2024-03-02 04:14:01
>> merging all info together...		2024-03-02 04:14:01
>> done		2024-03-02 04:14:01
>> checking seqlevels match...		2024-03-02 04:14: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...		2024-03-02 04:14:02
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:03
>> finding overlap peak in gene scan region...		2024-03-02 04:14:03
>> dealing with left peak not your gene scan region...		2024-03-02 04:14:03
>> merging two set peaks...		2024-03-02 04:14:04
>> calculating distance and dealing with gene strand...		2024-03-02 04:14:04
>> merging all info together ...		2024-03-02 04:14:04
>> done		2024-03-02 04:14:04
>> calculating peakCenter to TSS using peak-gene pair...		2024-03-02 04:14:04
>> calculating RP using centerToTSS and TF hit		2024-03-02 04:14:06
>> merging all info together		2024-03-02 04:14:06
>> done		2024-03-02 04:14:06
>> checking seqlevels match...		2024-03-02 04:14:07
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2024-03-02 04:14:08
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2024-03-02 04:14:16
>> your peak_GR seqlevel:Chr5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
Good, your Chrs in peak_GR is all in Txdb
>> checking seqlevels match...		2024-03-02 04:14:16
>> your peak_GR seqlevel:Chr5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
Good, your Chrs in peak_GR is all in Txdb
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2024-03-02 04:14:16
>> finding nearest gene and calculating distance...		2024-03-02 04:14:18
>> dealing with gene strand ...		2024-03-02 04:14:18
>> merging all info together ...		2024-03-02 04:14:18
>> done		2024-03-02 04:14:18
>> checking seqlevels match...		2024-03-02 04:14:19
>> 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...		2024-03-02 04:14:19
>> 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...		2024-03-02 04:14:19
>> finding nearest gene and calculating distance...		2024-03-02 04:14:21
>> dealing with gene strand ...		2024-03-02 04:14:21
>> merging all info together ...		2024-03-02 04:14:21
>> done		2024-03-02 04:14:21
>> checking seqlevels match...		2024-03-02 04:14:23
>> your peak_GR seqlevel:Chr5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
Good, your Chrs in peak_GR is all in Txdb
>> checking seqlevels match...		2024-03-02 04:14:23
>> your peak_GR seqlevel:Chr5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
Good, your Chrs in peak_GR is all in Txdb
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2024-03-02 04:14:23
>> finding nearest gene and calculating distance...		2024-03-02 04:14:25
>> dealing with gene strand ...		2024-03-02 04:14:25
>> merging all info together ...		2024-03-02 04:14:25
>> done		2024-03-02 04:14:25
>> checking seqlevels match...		2024-03-02 04:14: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
>> checking seqlevels match...		2024-03-02 04:14: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2024-03-02 04:14:27
>> finding nearest gene and calculating distance...		2024-03-02 04:14:29
>> dealing with gene strand ...		2024-03-02 04:14:29
>> merging all info together ...		2024-03-02 04:14:29
>> done		2024-03-02 04:14:29
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2024-03-02 04:14: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
>> checking seqlevels match...		2024-03-02 04:14: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
------------
annotating Peak using nearest gene mode begins
>> preparing gene features information...		2024-03-02 04:14:31
>> finding nearest gene and calculating distance...		2024-03-02 04:14:33
>> dealing with gene strand ...		2024-03-02 04:14:33
>> merging all info together ...		2024-03-02 04:14:33
>> done		2024-03-02 04:14:33
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2024-03-02 04:14: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...		2024-03-02 04:14: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
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:39
>> checking seqlevels match...		2024-03-02 04:14: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
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:43
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-03-02 04:14:47
>> merging all info together...		2024-03-02 04:14:47
>> done		2024-03-02 04:14:47
>> checking seqlevels match...		2024-03-02 04:14: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
>> using scanPromoter parameter to scan promoter for each gene...		2024-03-02 04:14:47
>> checking seqlevels match...		2024-03-02 04:14: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
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:49
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2024-03-02 04:14:50
>> checking seqlevels match...		2024-03-02 04:14: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
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:51
>> calculating cor and pvalue, which may be time consuming...		2024-03-02 04:14:52
>> merging all info together...		2024-03-02 04:14:52
>> done		2024-03-02 04:14:52
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-03-02 04:14:52
>> merging all info together...		2024-03-02 04:14:53
>> done		2024-03-02 04:14:53
>> checking seqlevels match...		2024-03-02 04:14: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
------------
annotatePeak using geneScan mode begins
>> preparing gene features information and scan region...		2024-03-02 04:14:53
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:14:55
>> finding overlap peak in gene scan region...		2024-03-02 04:14:55
>> dealing with left peak not your gene scan region...		2024-03-02 04:14:55
>> merging two set peaks...		2024-03-02 04:14:56
>> calculating distance and dealing with gene strand...		2024-03-02 04:14:56
>> merging all info together ...		2024-03-02 04:14:56
>> done		2024-03-02 04:14:56
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-03-02 04:14:59
>> merging all info together...		2024-03-02 04:14:59
>> done		2024-03-02 04:14:59
>> checking seqlevels match...		2024-03-02 04:14: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
>> using scanPromoter parameter to scan promoter for each gene...		2024-03-02 04:14:59
>> checking seqlevels match...		2024-03-02 04:15: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
>> some scan range may cross Chr bound, trimming...		2024-03-02 04:15:01
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2024-03-02 04:15:02
>> checking seqlevels match...		2024-03-02 04:15: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...		2024-03-02 04:15:04
>> calculating cor and pvalue, which may be time consuming...		2024-03-02 04:15:04
>> merging all info together...		2024-03-02 04:15:05
>> done		2024-03-02 04:15: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 
127.903   3.923 154.455 

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database0.0010.0020.001
calcRP_TFHit6.4730.2968.314
calcRP_coverage4.6420.7087.734
calcRP_region 9.275 0.29811.704
enhancerPromoterCor4.8950.1295.144
findIT_MARA0.8600.0260.908
findIT_TFHit1.5570.0441.624
findIT_TTPair0.1450.0110.161
findIT_enrichFisher0.2850.0100.307
findIT_enrichWilcox0.2140.0060.224
findIT_regionRP11.078 0.24313.032
getAssocPairNumber2.3390.0452.987
integrate_ChIP_RNA4.0750.0965.068
integrate_replicates0.0050.0020.006
jaccard_findIT_TTpair0.2120.0100.282
jaccard_findIT_enrichFisher0.4320.0090.550
loadPeakFile0.1250.0030.164
mm_geneBound2.4540.0492.984
mm_geneScan2.4230.0542.859
mm_nearestGene2.1320.0412.499
peakGeneCor5.5300.0886.622
plot_annoDistance3.9510.0714.690
plot_peakGeneAlias_summary2.7070.0853.264
plot_peakGeneCor6.9220.3038.998
test_geneSet0.0010.0010.003