similar to: Linking to the BH package introduces CRAN warnings

Displaying 20 results from an estimated 5000 matches similar to: "Linking to the BH package introduces CRAN warnings"

2011 Oct 04
1
a question about sort and BH
Hi, I have two questions want to ask. 1. If I have a matrix like this, and I want to figure out the rows whose value in the 3rd column are less than 0.05. How can I do it with R. hsa-let-7a--MBTD1 0.528239197 2.41E-05 hsa-let-7a--APOBEC1 0.507869409 5.51E-05 hsa-let-7a--PAPOLA 0.470451884 0.000221774 hsa-let-7a--NF2 0.469280186 0.000231065 hsa-let-7a--SLC17A5
2013 Jul 20
1
BH correction with p.adjust
Dear List, I have been trying to use p.adjust() to do BH multiple test correction and have gotten some unexpected results. I thought that the equation for this was: pBH = p*n/i where p is the original p value, n is the number of tests and i is the rank of the p value. However when I try and recreate the corrected p from my most significant value it does not match up to the one computed by the
2002 Sep 23
1
Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
I use redhat7.3 . Sep 20 20:39:31 Xhwsrhtrs2 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Sep 20 20:39:31 Xhwsrhtrs2 kernel: ------------[ cut here ]------------ Sep 20 20:39:31 Xhwsrhtrs2 kernel: kernel BUG at commit.c:535! Sep 20 20:39:31 Xhwsrhtrs2 kernel: invalid operand: 0000 Sep 20 20:39:31 Xhwsrhtrs2 kernel: autofs eepro100
2002 May 19
1
Kernel bug in RedHat 7.3 -- Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
Hello: My RedHat 7.3 machine just locked up and I could not reboot it. I had to punch the reset button. Here is what I found in the /var/log/messages file: May 19 12:50:16 server1 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" May 19 12:50:16 server1 kernel: ------------[ cut here ]------------ May 19 12:50:16 server1 kernel: kernel BUG
2002 Jul 22
1
Re:Kernel bug in RedHat 7.3 -- Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
Hello,ext3-users: Yep, We meet the same problem. Jul 17 22:41:40 sh_intel5 kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Jul 17 22:41:40 sh_intel5 kernel: ------------[ cut here ]------------ Jul 17 22:41:40 sh_intel5 kernel: kernel BUG at commit.c:535! Jul 17 22:41:40 sh_intel5 kernel: invalid operand: 0000 Jul 17 22:41:40 sh_intel5
2005 Apr 07
2
Samba-Squid-AD: Error returned 'BH NT_STATUS_ACCESS_DENIED'
Hi everybody, I setup squid-2.5.STABLE9 with samba-3.0.13 to use winbind authentication over a Windows 2003 Active Directory. Web users' authentication from my proxy server box succeedes. But when a remote user try to authenticate himself, authentication failes and Squid return the following: authenticateNTLMHandleReply: Error validating user via NTLM. Error returned 'BH
2023 Feb 27
0
[ANNOUNCE] font-bh-lucidatypewriter-75dpi 1.0.4
This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient and using the -n flag to gzip to improve build reproducibility. Alan Coopersmith (10): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update configure.ac bug URL for gitlab migration gitlab CI: add a basic build test
2023 Feb 27
0
[ANNOUNCE] font-bh-lucidatypewriter-100dpi 1.0.4
This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient and using the -n flag to gzip to improve build reproducibility. Alan Coopersmith (10): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration
2023 Feb 27
0
[ANNOUNCE] font-bh-ttf 1.0.4
This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient. Alan Coopersmith (9): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration gitlab CI: add a basic build test Build xz tarballs
2011 Apr 20
4
[PATCH 1/5] Btrfs: fix bh leak on __btrfs_open_devices path
''bh'' is forgot to release if no error is detected Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> --- fs/btrfs/volumes.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index 8b9fb8c..69fc902 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -631,6 +631,7 @@ static int
2006 Dec 07
7
[LLVMdev] #include <iostream>
Hi all, With the newest patches to LLVM, there should be no reason for having "#include <iostream>" in any library source code file, except for lib/ Support/Streams.cpp. Please use the following instead: OLD NEW --- --- std::ostream llvm::OStream std::istream llvm::IStream std::cerr llvm::cerr std::cerr llvm::cout
2010 Nov 11
0
[ANNOUNCE] font-bh-ttf 1.0.3
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This package contains the Luxi family of TrueType fonts contributed by Bigelow & Holmes to the XFree86 Project. This bug-fix release fixes the installation path of the fontconfig 42-luxi-mono.conf files introduced in 1.0.2, plus adds support for finding the correct fontconfig path from the fontconfig.pc file variables added recently in fontconfig
2011 May 03
1
[LLVMdev] Using Bugpoint to debug miscompilation
Hi, I am trying to reduce what I believe to be a miscompilation bug. Running lli on my bitcode file causes a segmentation fault. However, running bugpoint as bugpoint file.bc gives me the following errors, /tmp/ccAdmNqH.o: In function `_ZL17bus_error_handleriP7siginfoPv': bugpoint-test-program.bc-Vega5s.cbe.c:(.text+0x1b4e1): undefined reference to `std::cerr' /tmp/ccAdmNqH.o: In
2011 Mar 03
3
top and allocation issues
In a context where exceptions are caught, I ran the fragment: cerr << "allocating" << endl; char* arr[100]; for (int jj = 0; jj < 10; ++jj) { cerr << "jj = " << jj << endl; arr[jj] = new char[2000000000]; sleep (30); } sleep (10); for (int jj = 0; jj < 10; ++jj) delete[] arr[jj]; cerr
2006 Sep 20
1
help with function
Hello everyone, I have a function here that I wrote but doesn't seem to work quite right. Attached is the code. In the calib funcion under the for loop Bt[i+2]<-(1-m)*Bt[i+1]+Rt[i]*Rerr-Ct[i+1] returns NA's for everything after years 1983 and 1984. However the code works when it reads Bt[i+2]<-(1-m)*Bt[i+1]+Rt[i]*Rerr-Ct[i]. I don't quite understand why since it should be
2009 Feb 27
3
[LLVMdev] warning from -instcombine
Hi, I noticed this code in lib/Transforms/Scalar/InstructionCombining.cpp: cerr << "WARNING: While resolving call to function '" << Callee->getName() << "' arguments were dropped!\n"; If you're using LLVM as a static compiler, this warning is a bit incongruous, because it's not formatted in the same way as warnings from
2007 Nov 08
3
[LLVMdev] Newbie JITter
Hi, I'm experimenting with using LLVM to generate dynamic FFI bridges in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from dynamically generated assembler source to machine code, and I have that all working, copied from the llc tool and the JIT example. I have two questions: 1. What optimization passes, if any, should I run on the module before I pass it to the
2006 Sep 19
1
-Need help with function
Hello everyone, I have a function here that I wrote but doesn't seem to work quite right. Attached is the code. In the calib funcion under the for loop Bt[i+2]<-(1-m)*Bt[i+1]+Rt[i]*Rerr-Ct[i+1] returns NA's for everything after years 1983 and 1984. However the code works when it reads Bt[i+2]<-(1-m)*Bt[i+1]+Rt[i]*Rerr-Ct[i]. I don't quite understand why since it should be
2009 Jul 13
1
[PATCH] ocfs2: Add extra credits and access the modified bh in update_edge_lengths.
In normal tree rotation left process, we will never touch the tree branch above subtree_index and ocfs2_extend_rotate_transaction doesn't reserve the credits for them either. But when we want to delete the rightmost extent block, we have to update the rightmost records for all the rightmost branch(See ocfs2_update_edge_lengths), so we have to allocate extra credits for them. What's more,
2006 Dec 08
0
[LLVMdev] #include <iostream>
On Thu, 7 Dec 2006, Bill Wendling wrote: > With the newest patches to LLVM, there should be no reason for having > "#include <iostream>" in any library source code file, except for lib/ > Support/Streams.cpp. Please use the following instead: > > OLD NEW > --- --- > std::ostream llvm::OStream > std::istream