Displaying 3 results from an estimated 3 matches for "nx10".
Did you mean:
0x10
2007 Dec 10
2
unstable kernel after update to CentOS 4.5
...o RAID, no LVM, a few partitions on an IDE disk.
I didn't file it as a bug yet. I want to first gather some more
information or get some help.
Here are some details.
Kernel was updated from 2.6.9-34.0.2.EL to 2.6.9-55.0.12.EL.
There is not a single package update missing now.
Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): htree_dirblock_to_tree: bad entry in directory
#1330023: rec_len % 4 != 0 - offset=10264, inode=808542775, rec_len=13621, name_len=100
Dec 9 04:30:35 nx10 kernel: Aborting journal on device hda3.
Dec 9 04:30:35 nx10 kernel: ext3_abort called.
Dec 9 04:30:35...
1998 May 28
5
performance of apply
I noticed that apply is VERY SLOW when applied to a "large"
dimension as for example when computing the row sums of a matrix with
thousands of rows.
To demonstrate it, I did some benchmarking for different methods of
computing the row sums of an nx10 matrix with n =3D 2000, ..., 10000.
The first method (M1) I used is the normal apply command:
y <- apply(x,1,sum)
The second method (M2) uses a for-loop for the computations, where the
memory for the resulting vector has been allocated before. That is, for
n=3D2000:
z <- numeric(2000); for...
2025 May 09
1
array-bound error with GCC 13/14
Hopefully a member of the CRAN team will tell me I'm wrong, but I
think whether or not there is a compiler bug is ultimately irrelevant
-- packages on CRAN must compile cleanly even with potentially-buggy
development versions of compilers.
So, whether or not there is a bug in gcc is moot -- you'll need to
find a way to avoid triggering this issue in your package code.
Best,
Kevin
On