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

This page was generated on 2024-05-09 11:40:50 -0400 (Thu, 09 May 2024).

HostnameOSArch (*)R versionInstalled pkgs
nebbiolo1Linux (Ubuntu 22.04.3 LTS)x86_644.4.0 (2024-04-24) -- "Puppy Cup" 4748
palomino3Windows Server 2022 Datacenterx644.4.0 (2024-04-24 ucrt) -- "Puppy Cup" 4484
lconwaymacOS 12.7.1 Montereyx86_644.4.0 (2024-04-24) -- "Puppy Cup" 4514
kunpeng2Linux (openEuler 22.03 LTS-SP1)aarch644.4.0 beta (2024-04-15 r86425) -- "Puppy Cup" 4480
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 723/2300HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
FindIT2 1.10.0  (landing page)
Guandong Shang
Snapshot Date: 2024-05-08 14:00:19 -0400 (Wed, 08 May 2024)
git_url: https://git.bioconductor.org/packages/FindIT2
git_branch: RELEASE_3_19
git_last_commit: ca624b0
git_last_commit_date: 2024-04-30 11:35:36 -0400 (Tue, 30 Apr 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
lconwaymacOS 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  
kjohnson3macOS 13.6.5 Ventura / arm64see weekly results here

CHECK results for FindIT2 on kunpeng2


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.10.0
Command: /home/biocbuild/R/R-beta-2024-04-15_r86425/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/R/R-beta-2024-04-15_r86425/site-library --no-vignettes --timings FindIT2_1.10.0.tar.gz
StartedAt: 2024-05-09 07:25:52 -0000 (Thu, 09 May 2024)
EndedAt: 2024-05-09 07:33:39 -0000 (Thu, 09 May 2024)
EllapsedTime: 467.0 seconds
RetCode: 0
Status:   OK  
CheckDir: FindIT2.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/R/R-beta-2024-04-15_r86425/bin/R CMD check --install=check:FindIT2.install-out.txt --library=/home/biocbuild/R/R-beta-2024-04-15_r86425/site-library --no-vignettes --timings FindIT2_1.10.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.19-bioc/meat/FindIT2.Rcheck’
* using R version 4.4.0 beta (2024-04-15 r86425)
* using platform: aarch64-unknown-linux-gnu
* R was compiled by
    gcc (GCC) 10.3.1
    GNU Fortran (GCC) 10.3.1
* running under: openEuler 22.03 (LTS-SP1)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘FindIT2/DESCRIPTION’ ... OK
* this is package ‘FindIT2’ version ‘1.10.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 10.893  0.380  11.295
findIT_regionRP  8.756  0.036   8.809
calcRP_region    6.819  0.107   6.942
* 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-beta-2024-04-15_r86425/bin/R CMD INSTALL FindIT2
###
##############################################################################
##############################################################################


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

Example timings

FindIT2.Rcheck/FindIT2-Ex.timings

nameusersystemelapsed
TF_target_database0.0010.0000.001
calcRP_TFHit3.8410.1274.141
calcRP_coverage10.893 0.38011.295
calcRP_region6.8190.1076.942
enhancerPromoterCor3.9020.0513.962
findIT_MARA0.5920.0350.630
findIT_TFHit1.3290.0121.343
findIT_TTPair0.0940.0040.098
findIT_enrichFisher0.270.000.27
findIT_enrichWilcox0.2540.0040.258
findIT_regionRP8.7560.0368.809
getAssocPairNumber1.7510.0401.794
integrate_ChIP_RNA3.9490.1324.089
integrate_replicates0.0020.0000.003
jaccard_findIT_TTpair0.1360.0000.136
jaccard_findIT_enrichFisher0.2720.0000.272
loadPeakFile0.0780.0000.078
mm_geneBound1.6280.0321.663
mm_geneScan1.6780.0081.689
mm_nearestGene1.5320.0001.534
peakGeneCor3.2530.0203.278
plot_annoDistance2.0140.0082.025
plot_peakGeneAlias_summary1.7820.0201.805
plot_peakGeneCor4.1500.0444.202
test_geneSet000