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

This page was generated on 2023-02-04 11:04:51 -0500 (Sat, 04 Feb 2023).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo1Linux (Ubuntu 22.04.1 LTS)x86_64R Under development (unstable) (2023-01-10 r83596) -- "Unsuffered Consequences" 4483
palomino3Windows Server 2022 Datacenterx64R Under development (unstable) (2023-01-10 r83596 ucrt) -- "Unsuffered Consequences" 4249
merida1macOS 10.14.6 Mojavex86_64R Under development (unstable) (2023-01-10 r83596) -- "Unsuffered Consequences" 4272
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

CHECK results for FindIT2 on nebbiolo1


To the developers/maintainers of the FindIT2 package:
- Please 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 How and When does the builder pull? When will my changes propagate? for more information.
- Make sure to use the following settings in order to reproduce any error or warning you see on this page.

raw results

Package 669/2164HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.5.0  (landing page)
Guandong Shang
Snapshot Date: 2023-02-03 14:00:22 -0500 (Fri, 03 Feb 2023)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: master
git_last_commit: db4c20d
git_last_commit_date: 2022-11-01 11:25:15 -0500 (Tue, 01 Nov 2022)
nebbiolo1Linux (Ubuntu 22.04.1 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
palomino3Windows Server 2022 Datacenter / x64  OK    OK    OK    NA  
merida1macOS 10.14.6 Mojave / x86_64  OK    OK    OK    OK  UNNEEDED, same version is already published

Summary

Package: FindIT2
Version: 1.5.0
Command: /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/bbs-3.17-bioc/R/library --timings FindIT2_1.5.0.tar.gz
StartedAt: 2023-02-03 20:42:51 -0500 (Fri, 03 Feb 2023)
EndedAt: 2023-02-03 20:50:12 -0500 (Fri, 03 Feb 2023)
EllapsedTime: 440.9 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

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


* using log directory ‘/home/biocbuild/bbs-3.17-bioc/meat/FindIT2.Rcheck’
* using R Under development (unstable) (2023-01-10 r83596)
* using platform: x86_64-pc-linux-gnu (64-bit)
* R was compiled by
    gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
    GNU Fortran (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
* running under: Ubuntu 22.04.1 LTS
* using session charset: UTF-8
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.5.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 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 6.656  0.136   6.792
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’
 OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ...
  ‘FindIT2.Rmd’ using ‘UTF-8’... OK
 NONE
* checking re-building of vignette outputs ... OK
* checking PDF version of manual ... OK
* DONE

Status: OK


Installation output

FindIT2.Rcheck/00install.out

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


* installing to library ‘/home/biocbuild/bbs-3.17-bioc/R/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) (2023-01-10 r83596) -- "Unsuffered Consequences"
Copyright (C) 2023 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

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, sort, table,
    tapply, union, unique, unsplit, which.max, which.min

Loading required package: S4Vectors

Attaching package: 'S4Vectors'

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

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database0.0010.0000.000
calcRP_TFHit4.0780.2004.294
calcRP_coverage3.3650.8524.218
calcRP_region4.7950.1824.978
enhancerPromoterCor2.7000.0442.744
findIT_MARA0.4640.0120.477
findIT_TFHit0.9960.0121.008
findIT_TTPair0.1070.0000.107
findIT_enrichFisher0.1790.0000.179
findIT_enrichWilcox0.1870.0000.187
findIT_regionRP6.6560.1366.792
getAssocPairNumber1.0420.0441.087
integrate_ChIP_RNA1.9610.0041.965
integrate_replicates0.0020.0000.002
jaccard_findIT_TTpair0.1470.0000.147
jaccard_findIT_enrichFisher0.2320.0000.231
loadPeakFile0.0550.0000.054
mm_geneBound1.0590.0081.067
mm_geneScan1.0730.0201.092
mm_nearestGene0.9650.0160.981
peakGeneCor1.9950.0202.015
plot_annoDistance1.3570.0561.413
plot_peakGeneAlias_summary1.2150.0041.219
plot_peakGeneCor2.6970.0202.718
test_geneSet000