similar to: matching coordinates

I am trying to simulate a self avoiding random walk in 2d of length 100. So I am using two vectors of length 100 to encode the x and y coordinates. At each step I want apply a orthogonal transformation at a random point and then check to see if the walk intersects with itself. This amounts to simply checking to see if any of the ordered pairs of (x,y) coordinates in 1:j are repeated in j+1:100.

Hi, Evaluation of pivoted normalization ("PPP") of tf-idf weighting scheme is also complete now. I have also evaluated the default tf-idf normalization ("ntn") and other normalizations combinations involving pivoted normalization in wdfn, idfn and wtn component as "Pxx", "xPx" and "xxP" normalization strings respectively to have a clear idea about

Hi Pino, On 2/26/19 5:52 PM, Mike Latimer wrote: > On 2/21/19 3:07 AM, Pino Toscano wrote: >> My question is: is using cirrus still the best choice for SUSE guests? >> If not, what about using qxl as well, as done for any non-SUSE guest? >> (We can also do that depending on the version of the guest, in case >> only newer SUSE versions work fine with qxl). > At the

On Tue, Sep 03, 2013 at 11:30:07PM -0600, Mike Latimer wrote: > On Tuesday, September 03, 2013 06:09:26 PM Mike Latimer wrote: > > However, as mentioned in the bug, this parameter is likely no longer > > required. Unless there is a use-case where this setting is required, it > > seems like a good idea to remove it completely (which should work in > > either libvirt or

Hi, I have added support for Piv normalization in Tf-Idf weighting scheme as a intermediate step to implementing the support for Piv+ normalization. All tests pass. But I'm running into some issues with Piv+ normalization. In the Piv+ formula , there are two parameters (s and delta) that control the weight assigned. I think the way I'm serialising and unserialising these parameters has

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

On 12/23/2014 05:24 PM, Gary R Hook wrote: > I read that article. > > Now shut down the domain (post-pivot) which is using the new disk file, > and start it up, without using a block device. This is the part that no > one seems to write about, nor do I see that in your example. But thank > you very much for your help and your articles; very much appreciated. What do you mean by

On Fri, Jun 30, 2017 at 09:23:29 -0400, Doug Hughes wrote: > On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > >

Ah. If FIRE doesn't have something that can show this suitably, then > maybe Parth can advise on access to TREC, as I know he's used some of > them in the past. > ?I can say FIRE is also a reliable source but INEX/TREC are better. INEX can give you free access and TREC is not freely available. I had used INEX for xapian in the past and some details are here:

The iface:ide parameter (used in the libguestfs add_drive call) does not work with a libvirt backend. The error usually seen is: 'iface' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. This issue was previously mentioned in this thread:

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic

Am 13.10.14 16:25, schrieb Eric Blake: > On 10/13/2014 03:56 AM, Thomas Stein wrote: >> Hello. >> >>> blockcommit vm1 vda --active --verbose --pivot >> >> That's where libvirt stops working at the moment, right? >> >> virsh # blockcommit puppet-test vda --active --verbose --pivot >> error: unsupported flags (0x4) in function

On Wednesday 07 January 2015 09:46:09 Eric Blake wrote: > On 01/07/2015 07:19 AM, Thomas Stein wrote: > > Hello. > > > > I'm seeing this error while doing a backup of a VM. > > > > + virsh blockcommit kaltura vda --active --verbose --pivot > > Block Commit: [100 %]error: failed to pivot job for disk vda > > error: internal error: unable to execute

In summary.glm I'm trying to get a better feel for the z output. The following lines can be found in the function 1 if (p > 0) { 2 p1 <- 1:p 3 Qr <- object$qr 4 coef.p <- object$coefficients[Qr$pivot[p1]] 5 covmat.unscaled <- chol2inv(Qr$qr[p1, p1, drop = FALSE]) 6 dimnames(covmat.unscaled) <- list(names(coef.p), names(coef.p))

Thanks, Mike. ACK to all of these, and pushed. As it happens, I'd already started breaking some of this stuff out myself when I found this patchset :/ Rather than redo it, I've kept what I'd already done and rebased on top of it. I also did some testing and fixed a couple of bugs: "/files$grub->{grub_conf}*/kernel/root" should have been "/files

Thanks, Mike. I've pushed all of these. There were a couple of trivial bugs in patch 2, but nothing worth an extra round of review. To keep things simple I pushed the fixes as separate commits. Matt On Thu, 2013-11-07 at 14:11 -0700, Mike Latimer wrote: > The following series of patches adds support for converting SUSE guests > through virt-v2v. These changes should not impact non-SUSE

Hi Eric, Thanks for the info. I see the value in this, but it isn't quite what I was looking for. Basically what I want to do is to switch between snapshots quickly. For instance, I am currently working on designing a HA SQL implementation with failover. So right now I have 5 VM's running postgresql as a replication group. I am trying a lot of different things and often have to take a

Hi, Is it possible to "pivot" to a new image without doing blockcopy or blockpull? I know how to use snapshots and blockpull to create a new image and pivot to using it live, but what I would like to do is to have a VM switch from using imageA.qcow2 to image2.qcow2 while running. I don't see why this wouldn't be possible since some of the existing libvirt tools can do this when

I'm still learning how to program with R and I was hoping someone could take the time to show me how I can rewrite this code? Many thanks Tom data.intersects<-data.frame( x=c(0.230,0.411,0.477,0.241,0.552,0.230), y=c(0.119,0.515,0.261,0.431,0.304,0.389), angle=vector(length=6), length=vector(length=6),