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

This page was generated on 2024-11-30 12:46 -0500 (Sat, 30 Nov 2024).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo1Linux (Ubuntu 24.04.1 LTS)x86_64R Under development (unstable) (2024-10-21 r87258) -- "Unsuffered Consequences" 4748
palomino7Windows Server 2022 Datacenterx64R Under development (unstable) (2024-10-26 r87273 ucrt) -- "Unsuffered Consequences" 4461
lconwaymacOS 12.7.1 Montereyx86_64R Under development (unstable) (2024-11-20 r87352) -- "Unsuffered Consequences" 4403
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 709/2272HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.13.0  (landing page)
Guandong Shang
Snapshot Date: 2024-11-29 13:40 -0500 (Fri, 29 Nov 2024)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: devel
git_last_commit: 30235ec
git_last_commit_date: 2024-10-29 11:01:40 -0500 (Tue, 29 Oct 2024)
nebbiolo1Linux (Ubuntu 24.04.1 LTS) / x86_64  OK    OK    OK  UNNEEDED, same version is already published
palomino7Windows Server 2022 Datacenter / x64  OK    OK    OK    OK  UNNEEDED, same version is already published
lconwaymacOS 12.7.1 Monterey / x86_64  OK    OK    OK    OK  NO, package depends on 'rtracklayer' which is only available as a source package that needs compilation


CHECK results for FindIT2 on palomino7

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.13.0
Command: E:\biocbuild\bbs-3.21-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=E:\biocbuild\bbs-3.21-bioc\R\library --no-vignettes --timings FindIT2_1.13.0.tar.gz
StartedAt: 2024-11-30 00:47:58 -0500 (Sat, 30 Nov 2024)
EndedAt: 2024-11-30 00:54:30 -0500 (Sat, 30 Nov 2024)
EllapsedTime: 391.9 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   E:\biocbuild\bbs-3.21-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=E:\biocbuild\bbs-3.21-bioc\R\library --no-vignettes --timings FindIT2_1.13.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory 'E:/biocbuild/bbs-3.21-bioc/meat/FindIT2.Rcheck'
* using R Under development (unstable) (2024-10-26 r87273 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* using option '--no-vignettes'
* checking for file 'FindIT2/DESCRIPTION' ... OK
* this is package 'FindIT2' version '1.13.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 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 6.98   0.20    7.17
calcRP_region   6.44   0.27    6.71
* 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:
###
###   E:\biocbuild\bbs-3.21-bioc\R\bin\R.exe CMD INSTALL FindIT2
###
##############################################################################
##############################################################################


* installing to library 'E:/biocbuild/bbs-3.21-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) (2024-10-26 r87273 ucrt) -- "Unsuffered Consequences"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64

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
Loading required package: generics

Attaching package: 'generics'

The following objects are masked from 'package:base':

    as.difftime, as.factor, as.ordered, intersect, is.element, setdiff,
    setequal, union


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, is.unsorted, lapply,
    mapply, match, mget, order, paste, pmax, pmax.int, pmin, pmin.int,
    rank, rbind, rownames, sapply, saveRDS, table, tapply, 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

Attaching package: 'IRanges'

The following object is masked from 'package:grDevices':

    windows

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")
>> checking seqlevels match...		2024-11-30 12:53:19 AM
>> 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-11-30 12:53:19 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:53:21 AM
>> finding overlap peak in gene scan region...		2024-11-30 12:53:21 AM
>> dealing with left peak not your gene scan region...		2024-11-30 12:53:21 AM
>> merging two set peaks...		2024-11-30 12:53:22 AM
>> calculating distance and dealing with gene strand...		2024-11-30 12:53:22 AM
>> merging all info together ...		2024-11-30 12:53:22 AM
>> done		2024-11-30 12:53:22 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:22 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-11-30 12:53:23 AM
>> calculating RP using centerToTSS and peak score2024-11-30 12:53:23 AM
>> merging all info together		2024-11-30 12:53:26 AM
>> done		2024-11-30 12:53:27 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:27 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-11-30 12:53:29 AM
>> calculating RP using centerToTSS and peak score2024-11-30 12:53:29 AM
>> merging all info together		2024-11-30 12:53:32 AM
>> done		2024-11-30 12:53:32 AM
>> checking seqlevels match...		2024-11-30 12:53:32 AM
>> 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-11-30 12:53:32 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:53:33 AM
>> finding overlap peak in gene scan region...		2024-11-30 12:53:34 AM
>> dealing with left peak not your gene scan region...		2024-11-30 12:53:34 AM
>> merging two set peaks...		2024-11-30 12:53:34 AM
>> calculating distance and dealing with gene strand...		2024-11-30 12:53:34 AM
>> merging all info together ...		2024-11-30 12:53:34 AM
>> done		2024-11-30 12:53:34 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:34 AM
>> calculating RP using centerToTSS and TF hit		2024-11-30 12:53:35 AM
>> merging all info together		2024-11-30 12:53:35 AM
>> done		2024-11-30 12:53:35 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:35 AM
>> calculating RP using centerToTSS and TF hit		2024-11-30 12:53:36 AM
>> merging all info together		2024-11-30 12:53:36 AM
>> done		2024-11-30 12:53:36 AM
>> checking seqlevels match...		2024-11-30 12:53:37 AM
>> 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-11-30 12:53:37 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:53:38 AM
>> finding overlap peak in gene scan region...		2024-11-30 12:53:38 AM
>> dealing with left peak not your gene scan region...		2024-11-30 12:53:38 AM
>> merging two set peaks...		2024-11-30 12:53:38 AM
>> calculating distance and dealing with gene strand...		2024-11-30 12:53:38 AM
>> merging all info together ...		2024-11-30 12:53:38 AM
>> done		2024-11-30 12:53:38 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:38 AM
>> pre-filling 1356 noAssoc peak gene's RP with 0...		2024-11-30 12:53:39 AM
>> calculating RP using centerToTSS and peak score2024-11-30 12:53:39 AM
>> merging all info together		2024-11-30 12:53:42 AM
>> done		2024-11-30 12:53:43 AM
>> extracting RP info from regionRP...		2024-11-30 12:53:43 AM
>> dealing with TF_GR_databse...		2024-11-30 12:53:43 AM
>> calculating percent and p-value...		2024-11-30 12:53:44 AM
>> dealing withE5_0h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_0h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_4h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_4h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_8h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_8h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_16h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_16h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_24h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_24h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_48h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_48h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_48h_R3...		2024-11-30 12:53:44 AM
>> dealing withE5_72h_R1...		2024-11-30 12:53:44 AM
>> dealing withE5_72h_R2...		2024-11-30 12:53:44 AM
>> dealing withE5_72h_R3...		2024-11-30 12:53:44 AM
>> merging all info together...		2024-11-30 12:53:44 AM
>> done		2024-11-30 12:53:45 AM
>> preparing gene features information...		2024-11-30 12:53:45 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:53:46 AM
>> calculating p-value for each TF, which may be time consuming...		2024-11-30 12:53:46 AM
>> merging all info together...		2024-11-30 12:53:46 AM
>> done		2024-11-30 12:53:46 AM
>> dealing with TF_GR_database...		2024-11-30 12:53:46 AM
>> calculating coef and converting into z-score using INT...		2024-11-30 12:53:46 AM
>> dealing with E5_0h_R1...		2024-11-30 12:53:46 AM
>> dealing with E5_0h_R2...		2024-11-30 12:53:46 AM
>> dealing with E5_4h_R1...		2024-11-30 12:53:46 AM
>> dealing with E5_4h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_8h_R1...		2024-11-30 12:53:47 AM
>> dealing with E5_8h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_16h_R1...		2024-11-30 12:53:47 AM
>> dealing with E5_16h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_24h_R1...		2024-11-30 12:53:47 AM
>> dealing with E5_24h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_48h_R1...		2024-11-30 12:53:47 AM
>> dealing with E5_48h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_48h_R3...		2024-11-30 12:53:47 AM
>> dealing with E5_72h_R1...		2024-11-30 12:53:47 AM
>> dealing with E5_72h_R2...		2024-11-30 12:53:47 AM
>> dealing with E5_72h_R3...		2024-11-30 12:53:47 AM
>> merging all info together...		2024-11-30 12:53:47 AM
>> done		2024-11-30 12:53:48 AM
>> checking seqlevels match...		2024-11-30 12:53:48 AM
>> 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-11-30 12:53:48 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:53:49 AM
>> finding overlap peak in gene scan region...		2024-11-30 12:53:49 AM
>> dealing with left peak not your gene scan region...		2024-11-30 12:53:49 AM
>> merging two set peaks...		2024-11-30 12:53:49 AM
>> calculating distance and dealing with gene strand...		2024-11-30 12:53:49 AM
>> merging all info together ...		2024-11-30 12:53:49 AM
>> done		2024-11-30 12:53:49 AM
>> calculating peakCenter to TSS using peak-gene pair...		2024-11-30 12:53:49 AM
>> calculating RP using centerToTSS and TF hit		2024-11-30 12:53:50 AM
>> merging all info together		2024-11-30 12:53:50 AM
>> done		2024-11-30 12:53:50 AM
>> checking seqlevels match...		2024-11-30 12:53:51 AM
>> your peak_GR seqlevel:5...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2024-11-30 12:53:51 AM
>> your peak_GR seqlevel:Chr5 Chr6...
>> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC...
>> checking seqlevels match...		2024-11-30 12:53:55 AM
>> 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-11-30 12:53:55 AM
>> 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-11-30 12:53:55 AM
>> finding nearest gene and calculating distance...		2024-11-30 12:53:56 AM
>> dealing with gene strand ...		2024-11-30 12:53:56 AM
>> merging all info together ...		2024-11-30 12:53:56 AM
>> done		2024-11-30 12:53:56 AM
>> checking seqlevels match...		2024-11-30 12:53:56 AM
>> 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-11-30 12:53:56 AM
>> 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-11-30 12:53:56 AM
>> finding nearest gene and calculating distance...		2024-11-30 12:53:57 AM
>> dealing with gene strand ...		2024-11-30 12:53:57 AM
>> merging all info together ...		2024-11-30 12:53:57 AM
>> done		2024-11-30 12:53:57 AM
>> checking seqlevels match...		2024-11-30 12:53:58 AM
>> 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-11-30 12:53:58 AM
>> 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-11-30 12:53:59 AM
>> finding nearest gene and calculating distance...		2024-11-30 12:53:59 AM
>> dealing with gene strand ...		2024-11-30 12:54:00 AM
>> merging all info together ...		2024-11-30 12:54:00 AM
>> done		2024-11-30 12:54:00 AM
>> checking seqlevels match...		2024-11-30 12:54:01 AM
>> 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-11-30 12:54:01 AM
>> 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-11-30 12:54:01 AM
>> finding nearest gene and calculating distance...		2024-11-30 12:54:02 AM
>> dealing with gene strand ...		2024-11-30 12:54:02 AM
>> merging all info together ...		2024-11-30 12:54:02 AM
>> done		2024-11-30 12:54:02 AM
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2024-11-30 12:54:03 AM
>> 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-11-30 12:54:03 AM
>> 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-11-30 12:54:03 AM
>> finding nearest gene and calculating distance...		2024-11-30 12:54:04 AM
>> dealing with gene strand ...		2024-11-30 12:54:04 AM
>> merging all info together ...		2024-11-30 12:54:04 AM
>> done		2024-11-30 12:54:04 AM
It seems that there 1 genes have not been annotated by nearestGene mode
>> checking seqlevels match...		2024-11-30 12:54:05 AM
>> 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-11-30 12:54:06 AM
>> 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-11-30 12:54:07 AM
>> checking seqlevels match...		2024-11-30 12:54:08 AM
>> 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-11-30 12:54:09 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-11-30 12:54:11 AM
>> merging all info together...		2024-11-30 12:54:11 AM
>> done		2024-11-30 12:54:11 AM
>> checking seqlevels match...		2024-11-30 12:54:11 AM
>> 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-11-30 12:54:11 AM
>> checking seqlevels match...		2024-11-30 12:54:11 AM
>> 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-11-30 12:54:12 AM
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2024-11-30 12:54:12 AM
>> checking seqlevels match...		2024-11-30 12:54:12 AM
>> 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-11-30 12:54:13 AM
>> calculating cor and pvalue, which may be time consuming...		2024-11-30 12:54:14 AM
>> merging all info together...		2024-11-30 12:54:14 AM
>> done		2024-11-30 12:54:14 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-11-30 12:54:14 AM
>> merging all info together...		2024-11-30 12:54:14 AM
>> done		2024-11-30 12:54:14 AM
>> checking seqlevels match...		2024-11-30 12:54:14 AM
>> 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-11-30 12:54:14 AM
>> some scan range may cross Chr bound, trimming...		2024-11-30 12:54:15 AM
>> finding overlap peak in gene scan region...		2024-11-30 12:54:15 AM
>> dealing with left peak not your gene scan region...		2024-11-30 12:54:15 AM
>> merging two set peaks...		2024-11-30 12:54:16 AM
>> calculating distance and dealing with gene strand...		2024-11-30 12:54:16 AM
>> merging all info together ...		2024-11-30 12:54:16 AM
>> done		2024-11-30 12:54:16 AM
Good, your two matrix colnames matchs
>> calculating cor and pvalue, which may be time consuming...		2024-11-30 12:54:17 AM
>> merging all info together...		2024-11-30 12:54:17 AM
>> done		2024-11-30 12:54:17 AM
>> checking seqlevels match...		2024-11-30 12:54:17 AM
>> 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-11-30 12:54:17 AM
>> checking seqlevels match...		2024-11-30 12:54:17 AM
>> 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-11-30 12:54:18 AM
>> there are 85 gene have scaned promoter
>> using scanEnhancer parameter to scan Enhancer for each gene...		2024-11-30 12:54:18 AM
>> checking seqlevels match...		2024-11-30 12:54:18 AM
>> 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-11-30 12:54:19 AM
>> calculating cor and pvalue, which may be time consuming...		2024-11-30 12:54:20 AM
>> merging all info together...		2024-11-30 12:54:20 AM
>> done		2024-11-30 12:54:20 AM
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 63 ]
> 
> proc.time()
   user  system elapsed 
  73.20    2.39   75.67 

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database000
calcRP_TFHit3.700.134.09
calcRP_coverage0.080.010.09
calcRP_region6.440.276.71
enhancerPromoterCor4.450.044.50
findIT_MARA0.550.050.59
findIT_TFHit1.040.061.11
findIT_TTPair0.120.100.21
findIT_enrichFisher0.170.010.19
findIT_enrichWilcox0.210.020.22
findIT_regionRP6.980.207.17
getAssocPairNumber2.530.022.83
integrate_ChIP_RNA2.470.032.53
integrate_replicates000
jaccard_findIT_TTpair0.140.110.25
jaccard_findIT_enrichFisher0.260.000.26
loadPeakFile0.10.00.1
mm_geneBound1.560.031.59
mm_geneScan1.480.111.59
mm_nearestGene1.30.01.3
peakGeneCor2.860.082.93
plot_annoDistance1.650.031.69
plot_peakGeneAlias_summary1.710.081.78
plot_peakGeneCor3.500.123.63
test_geneSet000