Back to Multiple platform build/check report for BioC 3.20: simplified long |
|
This page was generated on 2024-06-11 15:40 -0400 (Tue, 11 Jun 2024).
Hostname | OS | Arch (*) | R version | Installed pkgs |
---|---|---|---|---|
nebbiolo2 | Linux (Ubuntu 22.04.3 LTS) | x86_64 | 4.4.0 RC (2024-04-16 r86468) -- "Puppy Cup" | 4679 |
palomino4 | Windows Server 2022 Datacenter | x64 | 4.4.0 RC (2024-04-16 r86468 ucrt) -- "Puppy Cup" | 4414 |
merida1 | macOS 12.7.4 Monterey | x86_64 | 4.4.0 Patched (2024-04-24 r86482) -- "Puppy Cup" | 4441 |
kjohnson1 | macOS 13.6.6 Ventura | arm64 | 4.4.0 Patched (2024-04-24 r86482) -- "Puppy Cup" | 4394 |
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 700/2239 | Hostname | OS / Arch | INSTALL | BUILD | CHECK | BUILD BIN | ||||||||
FindIT2 1.11.0 (landing page) Guandong Shang
| nebbiolo2 | Linux (Ubuntu 22.04.3 LTS) / x86_64 | OK | OK | OK | |||||||||
palomino4 | Windows Server 2022 Datacenter / x64 | OK | OK | OK | OK | |||||||||
merida1 | macOS 12.7.4 Monterey / x86_64 | OK | OK | OK | OK | |||||||||
kjohnson1 | macOS 13.6.6 Ventura / arm64 | OK | OK | OK | OK | |||||||||
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. |
Package: FindIT2 |
Version: 1.11.0 |
Command: F:\biocbuild\bbs-3.20-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=F:\biocbuild\bbs-3.20-bioc\R\library --no-vignettes --timings FindIT2_1.11.0.tar.gz |
StartedAt: 2024-06-10 02:43:55 -0400 (Mon, 10 Jun 2024) |
EndedAt: 2024-06-10 02:51:28 -0400 (Mon, 10 Jun 2024) |
EllapsedTime: 453.2 seconds |
RetCode: 0 |
Status: OK |
CheckDir: FindIT2.Rcheck |
Warnings: 0 |
############################################################################## ############################################################################## ### ### Running command: ### ### F:\biocbuild\bbs-3.20-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:FindIT2.install-out.txt --library=F:\biocbuild\bbs-3.20-bioc\R\library --no-vignettes --timings FindIT2_1.11.0.tar.gz ### ############################################################################## ############################################################################## * using log directory 'F:/biocbuild/bbs-3.20-bioc/meat/FindIT2.Rcheck' * using R version 4.4.0 RC (2024-04-16 r86468 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.11.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 calcRP_region 6.92 0.50 7.42 findIT_regionRP 6.28 0.37 6.64 * 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
FindIT2.Rcheck/00install.out
############################################################################## ############################################################################## ### ### Running command: ### ### F:\biocbuild\bbs-3.20-bioc\R\bin\R.exe CMD INSTALL FindIT2 ### ############################################################################## ############################################################################## * installing to library 'F:/biocbuild/bbs-3.20-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)
FindIT2.Rcheck/tests/testthat.Rout
R version 4.4.0 RC (2024-04-16 r86468 ucrt) -- "Puppy Cup" 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 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 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-06-10 2:50:20 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-06-10 2:50:20 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:50:22 AM >> finding overlap peak in gene scan region... 2024-06-10 2:50:22 AM >> dealing with left peak not your gene scan region... 2024-06-10 2:50:22 AM >> merging two set peaks... 2024-06-10 2:50:23 AM >> calculating distance and dealing with gene strand... 2024-06-10 2:50:23 AM >> merging all info together ... 2024-06-10 2:50:23 AM >> done 2024-06-10 2:50:23 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:23 AM >> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-06-10 2:50:24 AM >> calculating RP using centerToTSS and peak score2024-06-10 2:50:24 AM >> merging all info together 2024-06-10 2:50:25 AM >> done 2024-06-10 2:50:26 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:26 AM >> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-06-10 2:50:28 AM >> calculating RP using centerToTSS and peak score2024-06-10 2:50:28 AM >> merging all info together 2024-06-10 2:50:30 AM >> done 2024-06-10 2:50:31 AM >> checking seqlevels match... 2024-06-10 2:50:31 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-06-10 2:50:31 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:50:32 AM >> finding overlap peak in gene scan region... 2024-06-10 2:50:32 AM >> dealing with left peak not your gene scan region... 2024-06-10 2:50:32 AM >> merging two set peaks... 2024-06-10 2:50:32 AM >> calculating distance and dealing with gene strand... 2024-06-10 2:50:32 AM >> merging all info together ... 2024-06-10 2:50:32 AM >> done 2024-06-10 2:50:32 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:32 AM >> calculating RP using centerToTSS and TF hit 2024-06-10 2:50:33 AM >> merging all info together 2024-06-10 2:50:33 AM >> done 2024-06-10 2:50:33 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:33 AM >> calculating RP using centerToTSS and TF hit 2024-06-10 2:50:35 AM >> merging all info together 2024-06-10 2:50:35 AM >> done 2024-06-10 2:50:35 AM >> checking seqlevels match... 2024-06-10 2:50:36 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-06-10 2:50:36 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:50:37 AM >> finding overlap peak in gene scan region... 2024-06-10 2:50:37 AM >> dealing with left peak not your gene scan region... 2024-06-10 2:50:37 AM >> merging two set peaks... 2024-06-10 2:50:37 AM >> calculating distance and dealing with gene strand... 2024-06-10 2:50:37 AM >> merging all info together ... 2024-06-10 2:50:37 AM >> done 2024-06-10 2:50:37 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:37 AM >> pre-filling 1356 noAssoc peak gene's RP with 0... 2024-06-10 2:50:38 AM >> calculating RP using centerToTSS and peak score2024-06-10 2:50:38 AM >> merging all info together 2024-06-10 2:50:39 AM >> done 2024-06-10 2:50:40 AM >> extracting RP info from regionRP... 2024-06-10 2:50:41 AM >> dealing with TF_GR_databse... 2024-06-10 2:50:41 AM >> calculating percent and p-value... 2024-06-10 2:50:41 AM >> dealing withE5_0h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_0h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_4h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_4h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_8h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_8h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_16h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_16h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_24h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_24h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_48h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_48h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_48h_R3... 2024-06-10 2:50:41 AM >> dealing withE5_72h_R1... 2024-06-10 2:50:41 AM >> dealing withE5_72h_R2... 2024-06-10 2:50:41 AM >> dealing withE5_72h_R3... 2024-06-10 2:50:41 AM >> merging all info together... 2024-06-10 2:50:41 AM >> done 2024-06-10 2:50:42 AM >> preparing gene features information... 2024-06-10 2:50:42 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:50:43 AM >> calculating p-value for each TF, which may be time consuming... 2024-06-10 2:50:43 AM >> merging all info together... 2024-06-10 2:50:43 AM >> done 2024-06-10 2:50:43 AM >> dealing with TF_GR_database... 2024-06-10 2:50:43 AM >> calculating coef and converting into z-score using INT... 2024-06-10 2:50:43 AM >> dealing with E5_0h_R1... 2024-06-10 2:50:43 AM >> dealing with E5_0h_R2... 2024-06-10 2:50:43 AM >> dealing with E5_4h_R1... 2024-06-10 2:50:43 AM >> dealing with E5_4h_R2... 2024-06-10 2:50:43 AM >> dealing with E5_8h_R1... 2024-06-10 2:50:43 AM >> dealing with E5_8h_R2... 2024-06-10 2:50:43 AM >> dealing with E5_16h_R1... 2024-06-10 2:50:44 AM >> dealing with E5_16h_R2... 2024-06-10 2:50:44 AM >> dealing with E5_24h_R1... 2024-06-10 2:50:44 AM >> dealing with E5_24h_R2... 2024-06-10 2:50:44 AM >> dealing with E5_48h_R1... 2024-06-10 2:50:44 AM >> dealing with E5_48h_R2... 2024-06-10 2:50:44 AM >> dealing with E5_48h_R3... 2024-06-10 2:50:44 AM >> dealing with E5_72h_R1... 2024-06-10 2:50:44 AM >> dealing with E5_72h_R2... 2024-06-10 2:50:44 AM >> dealing with E5_72h_R3... 2024-06-10 2:50:44 AM >> merging all info together... 2024-06-10 2:50:44 AM >> done 2024-06-10 2:50:45 AM >> checking seqlevels match... 2024-06-10 2:50:45 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-06-10 2:50:45 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:50:45 AM >> finding overlap peak in gene scan region... 2024-06-10 2:50:45 AM >> dealing with left peak not your gene scan region... 2024-06-10 2:50:45 AM >> merging two set peaks... 2024-06-10 2:50:46 AM >> calculating distance and dealing with gene strand... 2024-06-10 2:50:46 AM >> merging all info together ... 2024-06-10 2:50:46 AM >> done 2024-06-10 2:50:46 AM >> calculating peakCenter to TSS using peak-gene pair... 2024-06-10 2:50:46 AM >> calculating RP using centerToTSS and TF hit 2024-06-10 2:50:46 AM >> merging all info together 2024-06-10 2:50:46 AM >> done 2024-06-10 2:50:46 AM >> checking seqlevels match... 2024-06-10 2:50:47 AM >> your peak_GR seqlevel:5... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... >> checking seqlevels match... 2024-06-10 2:50:47 AM >> your peak_GR seqlevel:Chr5 Chr6... >> your Txdb seqlevel:Chr1 Chr2 Chr3 Chr4 Chr5 ChrM ChrC... >> checking seqlevels match... 2024-06-10 2:50:51 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-06-10 2:50:51 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-06-10 2:50:51 AM >> finding nearest gene and calculating distance... 2024-06-10 2:50:52 AM >> dealing with gene strand ... 2024-06-10 2:50:52 AM >> merging all info together ... 2024-06-10 2:50:52 AM >> done 2024-06-10 2:50:52 AM >> checking seqlevels match... 2024-06-10 2:50:52 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-06-10 2:50:52 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-06-10 2:50:52 AM >> finding nearest gene and calculating distance... 2024-06-10 2:50:53 AM >> dealing with gene strand ... 2024-06-10 2:50:53 AM >> merging all info together ... 2024-06-10 2:50:53 AM >> done 2024-06-10 2:50:53 AM >> checking seqlevels match... 2024-06-10 2:50:54 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-06-10 2:50:54 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-06-10 2:50:54 AM >> finding nearest gene and calculating distance... 2024-06-10 2:50:55 AM >> dealing with gene strand ... 2024-06-10 2:50:55 AM >> merging all info together ... 2024-06-10 2:50:55 AM >> done 2024-06-10 2:50:55 AM >> checking seqlevels match... 2024-06-10 2:50: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-06-10 2:50: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-06-10 2:50:56 AM >> finding nearest gene and calculating distance... 2024-06-10 2:50:56 AM >> dealing with gene strand ... 2024-06-10 2:50:57 AM >> merging all info together ... 2024-06-10 2:50:57 AM >> done 2024-06-10 2:50:57 AM It seems that there 1 genes have not been annotated by nearestGene mode >> checking seqlevels match... 2024-06-10 2:50:57 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-06-10 2:50:57 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-06-10 2:50:58 AM >> finding nearest gene and calculating distance... 2024-06-10 2:50:58 AM >> dealing with gene strand ... 2024-06-10 2:50:58 AM >> merging all info together ... 2024-06-10 2:50:58 AM >> done 2024-06-10 2:50:58 AM It seems that there 1 genes have not been annotated by nearestGene mode >> checking seqlevels match... 2024-06-10 2:51:00 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-06-10 2:51:00 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-06-10 2:51:01 AM >> checking seqlevels match... 2024-06-10 2:51:02 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-06-10 2:51:03 AM Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2024-06-10 2:51:04 AM >> merging all info together... 2024-06-10 2:51:04 AM >> done 2024-06-10 2:51:04 AM >> checking seqlevels match... 2024-06-10 2:51:04 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-06-10 2:51:04 AM >> checking seqlevels match... 2024-06-10 2:51:04 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-06-10 2:51:05 AM >> there are 85 gene have scaned promoter >> using scanEnhancer parameter to scan Enhancer for each gene... 2024-06-10 2:51:05 AM >> checking seqlevels match... 2024-06-10 2:51: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-06-10 2:51:07 AM >> calculating cor and pvalue, which may be time consuming... 2024-06-10 2:51:07 AM >> merging all info together... 2024-06-10 2:51:08 AM >> done 2024-06-10 2:51:08 AM Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2024-06-10 2:51:08 AM >> merging all info together... 2024-06-10 2:51:08 AM >> done 2024-06-10 2:51:08 AM >> checking seqlevels match... 2024-06-10 2:51: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 ------------ annotatePeak using geneScan mode begins >> preparing gene features information and scan region... 2024-06-10 2:51:08 AM >> some scan range may cross Chr bound, trimming... 2024-06-10 2:51:09 AM >> finding overlap peak in gene scan region... 2024-06-10 2:51:09 AM >> dealing with left peak not your gene scan region... 2024-06-10 2:51:09 AM >> merging two set peaks... 2024-06-10 2:51:09 AM >> calculating distance and dealing with gene strand... 2024-06-10 2:51:09 AM >> merging all info together ... 2024-06-10 2:51:09 AM >> done 2024-06-10 2:51:09 AM Good, your two matrix colnames matchs >> calculating cor and pvalue, which may be time consuming... 2024-06-10 2:51:10 AM >> merging all info together... 2024-06-10 2:51:10 AM >> done 2024-06-10 2:51:11 AM >> checking seqlevels match... 2024-06-10 2:51: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-06-10 2:51:11 AM >> checking seqlevels match... 2024-06-10 2:51: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-06-10 2:51:11 AM >> there are 85 gene have scaned promoter >> using scanEnhancer parameter to scan Enhancer for each gene... 2024-06-10 2:51:12 AM >> checking seqlevels match... 2024-06-10 2:51: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-06-10 2:51:13 AM >> calculating cor and pvalue, which may be time consuming... 2024-06-10 2:51:13 AM >> merging all info together... 2024-06-10 2:51:13 AM >> done 2024-06-10 2:51:13 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 62.70 6.96 69.78
FindIT2.Rcheck/FindIT2-Ex.timings
name | user | system | elapsed | |
TF_target_database | 0 | 0 | 0 | |
calcRP_TFHit | 3.46 | 0.27 | 3.81 | |
calcRP_coverage | 0.05 | 0.20 | 0.25 | |
calcRP_region | 6.92 | 0.50 | 7.42 | |
enhancerPromoterCor | 2.50 | 0.38 | 2.87 | |
findIT_MARA | 0.48 | 0.04 | 0.53 | |
findIT_TFHit | 1.00 | 0.21 | 1.20 | |
findIT_TTPair | 0.09 | 0.09 | 0.19 | |
findIT_enrichFisher | 0.19 | 0.01 | 0.20 | |
findIT_enrichWilcox | 0.17 | 0.04 | 0.20 | |
findIT_regionRP | 6.28 | 0.37 | 6.64 | |
getAssocPairNumber | 1.44 | 0.25 | 1.69 | |
integrate_ChIP_RNA | 2.19 | 0.27 | 2.45 | |
integrate_replicates | 0 | 0 | 0 | |
jaccard_findIT_TTpair | 0.17 | 0.14 | 0.31 | |
jaccard_findIT_enrichFisher | 0.27 | 0.01 | 0.28 | |
loadPeakFile | 0.06 | 0.00 | 0.07 | |
mm_geneBound | 1.36 | 0.24 | 1.59 | |
mm_geneScan | 1.38 | 0.26 | 1.64 | |
mm_nearestGene | 1.09 | 0.32 | 1.41 | |
peakGeneCor | 2.64 | 0.26 | 2.92 | |
plot_annoDistance | 1.79 | 0.19 | 2.00 | |
plot_peakGeneAlias_summary | 1.64 | 0.19 | 1.82 | |
plot_peakGeneCor | 3.24 | 0.32 | 3.60 | |
test_geneSet | 0 | 0 | 0 | |