search for: ponted

Good morning to you all, I have a problem with a set of matrices that I want to compare. I want to see the similarity between them, and to be able to extract the differences between them. They have all the same number of columns and rows, and correspond presence absence data: for example: m1 <- matrix(c(1,0,0,0,1,0,1,1,1,1,1,1), 3,4) m2 <- matrix(c(1,0,1,0,1,0,0,1,0,1,0,1), 3,4) I

Hello All, I have a data frame (dput information below) with food item weight for fish species. I need to calculate the Mean proportion by weight of each food item for each specie, as show in solution data frame (dput information below). I use the ddply function (plyr package) in two steps. First calculate the proportion of weight for each individual: step1 = ddply (example, .(ID), transform,

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/include/asm/pci_x86.h | 2

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/include/asm/pci_x86.h | 2

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/include/asm/pci_x86.h | 2

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG, used pcibios_last_bus] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> ---

Dear friends, I am having some doubts about the amount of memory that is being used by R in my Mac (MacBook Pro, 2Gig). Is there a way to increase the amount of memory used? When I type: > mem.limits() the result is: nsize vsize NA NA and I can't change it, tough my computing in R isn't using all the memory at it's disposal. Best regards, Carlos -- Carlos GUERRA

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Hello, I am having two difficulties with xspline: 1) Passing lty=2 (via ...) appears to have no effect 2) Apparently depending on the current plot axes, I may or may not get the failure: add_point - reached MAXNUMPTS (25200) This happens both on Linux/R 2.8.0 (details below) and Windows Vista/R 2.8.0 patched (2008-10-21 r46766) Simplest case: plot(c(0,1),c(0,1))

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

This is not a major issue, but is there any way to get the full directory name out when dir.create issues a warning? I am running R 2.8.0 patched on Windows Vista - full details below. With the following code: dir.create("test") obscure<-"test" dir.create(obscure) I get the warning message: In dir.create(obscure) : 't' already exists Session details: R

Dear Marius, In addition to that attached please find a screenshot from Proxmox on statistics. Do you know any ice cast servers that puts out more than 1 gbps for a longer period? Just curious whether anyone was able to go beyond 1 gbps for an extensive time. Thank you! Best, Zsolt zsolt makkai <gvmzsolt at gmail.com> ezt ?rta (id?pont: 2024. m?rc. 14., Cs, 23:39): > Dear Marius,

Hi Zsolt, looking at the metrics from Proxmox it doesn't look like anything breaks there. What about at the operating system level? Could there be some limits there? Have you checked corresponding kernel or system logs? Which OS/distribution are you using? Checked the logs there? If nothing screams there, maybe start looking at a load balancer and scale with several more VMs? -- Marius

A quick Google search indicates that it might be a Proxmox limitation: https://forum.proxmox.com/threads/i-cant-exceed-1gb-of-internet-with-a-10gb-network-card.128710/ On Fri, Mar 15, 2024 at 12:24?PM Marius Flage <marius at flage.org> wrote: > Hi Zsolt, > > looking at the metrics from Proxmox it doesn't look like anything breaks > there. What about at the operating

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected -

Dear useR's, I wanted to load the package GeoXP in my computer but I couldn't because this warning message appeared: > require(GeoXp) Carregando pacotes exigidos: GeoXp Carregando pacotes exigidos: tcltk Loading Tcl/Tk interface ... Erro em fun(...) : couldn't connect to display ":0" Al?m disso: Warning message: pacote 'GeoXp' foi compilado na vers?o do R 2.4.1