search for: logi

...ith Matlab, so changing the mat file or saving it in a different format is not an option for me. Kind regards, Claude > foo <- readMat("riversurveyor.mat", verbose=TRUE) Trying to read MAT v5 file stream... List of 7 $ type : chr "miMATRIX" $ signed : logi NA $ sizeOf : int 0 $ what : num 0 $ nbrOfBytes: int 2848 $ padding : num 0 $ compressed: logi FALSE List of 7 $ type : chr "miMATRIX" $ signed : logi NA $ sizeOf : int 0 $ what : num 0 $ nbrOfByt...

Hello R experts, I have go this data frame: 'data.frame': 1 obs. of 20 variables: $ Anno : chr "PREVISIONI VS TARGET" $ OreTot: num 41 $ GioTot: logi NA $ OrGTot: logi NA $ OreCli: num 99 $ GioCli: logi NA $ OrGCli: logi NA $ OreFor: num -27 $ GioFor: logi NA $ OrGFor: logi NA $ OreOrt: num -18 $ GioOrt: logi NA $ OrGOrt: logi NA $ OreSpo: num -6 $ GioSpo: logi NA $ OrGSpo: logi NA $ OreUff: num -7 $ GioUff: logi NA $ OrGUff: log...

...y." [1][1] "part 8 written successfully." "part 69 written successfully." [1] "part 59 written successfully." [1] "part 25 written successfully." [1] "part 49 written successfully." [1] "part 52 written successfully." List of 88 $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi TRUE $ : logi...

...n successfully." "part 69 written successfully." > > [1] "part 59 written successfully." > [1] "part 25 written successfully." > [1] "part 49 written successfully." > [1] "part 52 written successfully." > List of 88 > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi TRUE > $ : logi...

Hi Andreas, the error is reported when some child process cannot send results to the master process, which originates from an error returned by write() - when write() returns -1 or 0. The logic around the writing has not changed since R 3.5.2. It should not be related to the printing in the child, only to returning the value. The problem may be originating from the execution environment, virtualization, and/or possibly from a lack of robustness in R. To resolve this we need to find o...

I have test environment to determine what would be best settings. I have been told that enabling zlib compression would be good to save iops on storage. But doing the test now, I get worse results. [@test2 ~]# pr -m -t mail04-mdbox-vdb-append-64kb-6.log mail04-mdbox-vdb-append-64kb-8.log |less Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 1 1 6 1/ 1 1 1 6 1/ 1 0 0 9 1/ 1 0 0 8 1/ 1 0 0 7 1/ 1 0 0 8 1/ 1 0 0 10 1/ 1...

...ve looked like Zimbra was buggy, but I didn't look at them too closely. STORE command also seemed to be buggy, giving lots of "STORE failed" errors, even with just one connection. Zimbra uses 500MB of memory just to start up, so it's not exactly for hosting small installations. Login+Logout ------------ Dovecot: ./imaptest - select=0 secs=10 seed=0 clients=1 Logi Logo 100% 100% 3439 6878 ./imaptest - select=0 secs=10 seed=0 clients=10 Logi Logo 100% 100% 4415 8830 Zimbra: ./imaptest - select=0 secs=10 seed=0 clients=1 Logi Logo 100% 100% 18032 36064 ./imaptest - s...

...ect, now I find myself having problems saving it. this is the data i´d like to save: str(DATA) List of 3 $ virtual: 'data.frame': 6 obs. of 7 variables: .. $ VirtualVmode : chr "double" "short" "integer" "integer" ... .. $ AsIs : logi FALSE FALSE FALSE FALSE FALSE FALSE .. $ VirtualIsMatrix : logi FALSE FALSE FALSE FALSE FALSE FALSE .. $ PhysicalIsMatrix : logi FALSE FALSE FALSE FALSE FALSE FALSE .. $ PhysicalElementNo: int 1 2 3 4 5 6 .. $ PhysicalFirstCol : int 1 1 1 1 1 1 .. $ PhysicalLastCol : int 1 1 1 1 1 1 ....

...db) n 674 } (gdb) n mc_send_master (what=<optimized out>) at fork.c:699 699 for (R_xlen_t i = 0; i < len; i += n) { (gdb) n 700 n = writerep(master_fd, b + i, len - i); (gdb) n 701 if (n < 1) { (gdb) n 699 for (R_xlen_t i = 0; i < len; i += n) { (gdb) n 707 return ScalarLogical(1); (gdb) n 708 } ### second child (write fails with EBADF): (gdb) break mc_send_master Breakpoint 1 at 0x7f5016f3e0a0: file fork.c, line 681. (gdb) c Continuing. Breakpoint 1, mc_send_master (what=0x563382a71910) at fork.c:681 warning: Source file is more recent than executable. 681 { (gdb)...

...optimized out>) at fork.c:699 > 699 for (R_xlen_t i = 0; i < len; i += n) { > (gdb) n > 700 n = writerep(master_fd, b + i, len - i); > (gdb) n > 701 if (n < 1) { > (gdb) n > 699 for (R_xlen_t i = 0; i < len; i += n) { > (gdb) n > 707 return ScalarLogical(1); > (gdb) n > 708 } > > > > ### second child (write fails with EBADF): > (gdb) break mc_send_master > Breakpoint 1 at 0x7f5016f3e0a0: file fork.c, line 681. > (gdb) c > Continuing. > > Breakpoint 1, mc_send_master (what=0x563382a71910) at fork.c:681 > war...

...; len; i +=3D n) { >>> (gdb) n >>> 700 n =3D writerep(master_fd, b + i, len - i); >>> (gdb) n >>> 701 if (n < 1) { >>> (gdb) n >>> 699 for (R_xlen_t i =3D 0; i < len; i +=3D n) { >>> (gdb) n >>> 707 return ScalarLogical(1); >>> (gdb) n >>> 708 } >>> >>> >>> >>> ### second child (write fails with EBADF): >>> (gdb) break mc_send_master >>> Breakpoint 1 at 0x7f5016f3e0a0: file fork.c, line 681. >>> (gdb) c >>> Continuing. &gt...

...; len; i +=3D n) { >>> (gdb) n >>> 700 n =3D writerep(master_fd, b + i, len - i); >>> (gdb) n >>> 701 if (n < 1) { >>> (gdb) n >>> 699 for (R_xlen_t i =3D 0; i < len; i +=3D n) { >>> (gdb) n >>> 707 return ScalarLogical(1); >>> (gdb) n >>> 708 } >>> >>> >>> >>> ### second child (write fails with EBADF): >>> (gdb) break mc_send_master >>> Breakpoint 1 at 0x7f5016f3e0a0: file fork.c, line 681. >>> (gdb) c >>> Continuing. &gt...

> On Nov 5, 2017, at 6:03 AM, G?ran Bergqvist <Goran.Bergqvist at jagareforbundet.se> wrote: > > I am using the function logi.hist.plot in package popbio. I want to change the colour of the probability line from the default red to black. I have not been able to find out how to do that. If you look at the code for that function you see this line: logi.curve <- function(independ, depend, mod = logi.mod, col.cu...

...v, stdout = output, stderr = output) on entry args : chr [1:5] "CMD" "INSTALL" "-l" "\"C:\\Users\\askers\\AppData\\Local\\Temp\\RtmpoRb97l\"" ... command : chr "C:/PROGRA~1/R/R-34~1.3/bin/x64/R" env : chr(0) input : NULL invisible : logi TRUE minimized : logi FALSE stderr : logi FALSE stdin : chr "" stdout : logi FALSE wait : logi TRUE Warning messages: 1: running command '"C:/PROGRA~1/R/R-34~1.3/bin/x64/R" CMD INSTALL -l "C:\Users\askers\AppData\Local\Temp\RtmpoRb97l" "partDF_1.0.0.900...

...actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 291 303 So that's 10 messages/sec saved. Now how about with 5 concurrent clients? Logi Sele Appe 100% 100% 100% 5% 5 1259 1332 Pretty well. Then something more generic: ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logou...

I am using the function logi.hist.plot in package popbio. I want to change the colour of the probability line from the default red to black. I have not been able to find out how to do that. [[alternative HTML version deleted]]

...ermine what would be best settings. I have > been told that enabling zlib compression would be good to save iops on > storage. But doing the test now, I get worse results. > > [@test2 ~]# pr -m -t mail04-mdbox-vdb-append-64kb-6.log > mail04-mdbox-vdb-append-64kb-8.log |less > Logi Sele Appe Logi Sele Appe > 100% 100% 100% 100% 100% 100% > 1 1 6 1/ 1 1 1 6 1/ 1 > 0 0 9 1/ 1 0 0 8 1/ 1 > 0 0 7 1/ 1 0 0 8 1/ 1 >...

...ry >> args : chr [1:5] "CMD" "INSTALL" "-l" "\"C:\\Users\\askers\\AppData\\Local\\Temp\\RtmpoRb97l\"" ... >> command : chr "C:/PROGRA~1/R/R-34~1.3/bin/x64/R" >> env : chr(0) >> input : NULL >> invisible : logi TRUE >> minimized : logi FALSE >> stderr : logi FALSE >> stdin : chr "" >> stdout : logi FALSE >> wait : logi TRUE >> Warning messages: >> 1: running command '"C:/PROGRA~1/R/R-34~1.3/bin/x64/R" CMD INSTALL -l "C:\Users\aske...

..., 2GB memory, 300GB Seagate ATA disk with XFS Linux 2.6.19.2, x86-64 SMP, Debian unstable Dovecot: CVS HEAD unless specified otherwise Cyrus: v2.2.13-10 (Debian) - NOTE: comparable to fsync_disable:no Courier: v4.1.1.20060828-2 (Debian) - NOTE: comparable to fsync_disable:yes! Settings: Dovecot: login_process_per_connection=no, login_processes_count=10, mail_drop_priv_before_exec=yes, passdb+userdb = passwd-file Cyrus: Default Debian settings, except sasl_pwcheck_method: alwaystrue Courier: Default Debian settings, using PAM + passwd Results: imaptest parameters: clients=1 msgs=30 secs=120...

...thread that increasing it from 2MB, could give problems when deleting messages, can someone explain this? Does anyone have this on a cephfs mount, does it make sense to set this to 4MB? [@test2 ~]# pr -m -t mail04-mdbox-vdb-append-64kb-4MB-6.log mail04-mdbox-vdb-append-64kb-16MB-7.log |less Logi Sele Appe Logi Sele Appe 100% 100% 100% 100% 100% 100% 1 1 6 1/ 1 1 1 8 1/ 1 0 0 9 1/ 1 0 0 9 1/ 1 0 0 7 1/ 1 0 0 7 1/ 1 0 0 10 1/ 1...