search for: halves

I am trying to code a steepest ascent algorithm to optimize parameters used in a survivor function type problem. My unknown parameters (alpha, Beta0, and Beta1) for which I have been able to optimize using Newton's method. I keep getting an error because my alpha becomes negative and I can't calculate the likelihood. Here is my log likelihood I am optimizing (in LaTex): l=\sum _{ i=1 }^{

Dear R-users, I want to draw a barplot with beside=TRUE. One halve of the bars are drawn with a border, while the other halve are drawn without a border (i.e. filled bars vs. non-filled bars next to each other). Because borders are drawn around the bars, doing this leads to one halve of the bars being wider than the other halve, expanding across the 0-point of the y-axis. This problem emerges

Hi all, I'm working with a dataset from 10 treatments, each treatment with 30 subjects, each subject measured 5 times. The plot of the dataset suggests that a 3-parameter logistic could be a reasonable function to describe the data. When I try to fit the model using gnls I got the message 'Step halving factor reduced below minimum in NLS step'. I´m using as the initial values of the

Dear Splus and R users: I have a problem in fitting a NLME model, the error message is: "step halving factor reduced below minimum in PNLS step" What does it mean and how to fix the problem, could anyone help me about it? Any suggestion/help would be greatly appreciated. Mei

Hi R-users, Could you give me some advice in solving the problem of such error message from gnls and nls? ## begin error message "Problem in gnls(y1 ~ glogit4(b, c, m, t, x), data.frame(x..: Step halving factor reduced below minimum in NLS step " ##and "Problem in nls(y ~ 1/(1 + exp((xmid - x)/scal)), data = x..: step factor reduced below minimum "? Thank you in

vmwrite higher 32 bits of 64bit VMCS fields when in PAE mode. Signed-off-by: Xin Li <xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello,   I am attempting to use nlme to model the response of 19 groups.  I am able to get a reasonable fit of all of the groups to the observed data using an exponential decay model (a*exp-x*b).  The problem is that when I plot the fitted values to residuals, it demonstrates a pattern of increasing variance.   I attempt to model this variance using   Sig3.nlme <- update(Sig2.nlme, weights =

I recommend instead of no border, that you use a border with the same color as the fill. I do this in the likert functions in the HH package. Rich On Mon, May 21, 2018 at 10:59 AM, Martin Batholdy via R-help <r-help at r-project.org> wrote: > Dear R-users, > > I want to draw a barplot with beside=TRUE. > One halve of the bars are drawn with a border, while the other halve are

...ifier - Write Only */ > > > +#define VIRTIO_MDEV_QUEUE_NOTIFY 0x050 > > > + > > > +/* Device status register - Read Write */ > > > +#define VIRTIO_MDEV_STATUS 0x060 > > > + > > > +/* Selected queue's Descriptor Table address, 64 bits in two halves */ > > > +#define VIRTIO_MDEV_QUEUE_DESC_LOW 0x080 > > > +#define VIRTIO_MDEV_QUEUE_DESC_HIGH 0x084 > > > + > > > +/* Selected queue's Available Ring address, 64 bits in two halves */ > > > +#define VIRTIO_MDEV_QUEUE_AVAIL_LOW 0x090 > > > +#...

...ifier - Write Only */ > > > +#define VIRTIO_MDEV_QUEUE_NOTIFY 0x050 > > > + > > > +/* Device status register - Read Write */ > > > +#define VIRTIO_MDEV_STATUS 0x060 > > > + > > > +/* Selected queue's Descriptor Table address, 64 bits in two halves */ > > > +#define VIRTIO_MDEV_QUEUE_DESC_LOW 0x080 > > > +#define VIRTIO_MDEV_QUEUE_DESC_HIGH 0x084 > > > + > > > +/* Selected queue's Available Ring address, 64 bits in two halves */ > > > +#define VIRTIO_MDEV_QUEUE_AVAIL_LOW 0x090 > > > +#...

merijnv@sci.kun.nl pondered the following.... Subject: [OT] Re: [vorbis] Format comparison >Eh, just a (seemingly offtopic) question, but how do you create a 4 channel >lp ? With just one needle ? >-- Merijn In a nutshell. Normal LP has two halves in the groove - the L and R channel. A Quad channel LP still has to 'halves' in the groove. Each channel is actually BOTH the front channel added in a linear fashion to the BACK channel information which is riding on a 'carrier wave.' If I recall correctly (and I probably don'...

On Tue, Dec 9, 2008 at 6:11 AM, Zoltan Varga <vargaz at gmail.com> wrote: >> It would be better to implement a target-independent check for >> overflow for the "Legal" case (like how SADDO does). Hacker's > Delight >> has some hints on how to do this. It's not easy for the signed case, >> but is do-able. > > It can be lowered to a division +

Hi, I''m trying to modify the Wondershaper script so achieve the following. 1. Prioritize traffic to the few IP addresses. 2. Everyone else should get a fair amount of bandwidth The problem I am facing is when I run this script is that the bandwidth seems to get halved. I tried to apply this script to a site where the upstream and downstream were fully saturated. I immediately saw

Hi to All, I am fitting some models to a data using non linear least square, and whenever i run the command, parameters value have good convergence but I get the error in red as shown below. Kindly how can I fix this problem. Convergence of parameter values 0.2390121 : 0.1952981 0.9999975 1.0000000 0.03716107 : 0.1553976 0.9999910 1.0000000 0.009478433 : 0.2011017 0.9999798 1.0000000

Hi, Here is the next iteration of the patch. The only comment not addressed is this one: > It would be better to implement a target-independent check for > overflow for the "Legal" case (like how SADDO does). Hacker's > Delight > has some hints on how to do this. It's not easy for the signed case, > but is do-able. It can be lowered to a division + a branch,

...48 >> + >> +/* Queue notifier - Write Only */ >> +#define VIRTIO_MDEV_QUEUE_NOTIFY 0x050 >> + >> +/* Device status register - Read Write */ >> +#define VIRTIO_MDEV_STATUS 0x060 >> + >> +/* Selected queue's Descriptor Table address, 64 bits in two halves */ >> +#define VIRTIO_MDEV_QUEUE_DESC_LOW 0x080 >> +#define VIRTIO_MDEV_QUEUE_DESC_HIGH 0x084 >> + >> +/* Selected queue's Available Ring address, 64 bits in two halves */ >> +#define VIRTIO_MDEV_QUEUE_AVAIL_LOW 0x090 >> +#define VIRTIO_MDEV_QUEUE_AVAIL_HIGH...

When I encode a monophonic wav file, I would expect the resulting ogg file to be at about half the bit rate specified on the command line, as stated in the "oggenc -h" help text: "The 6 modes are approximately 112, 128, 160, 192, 256, and 350 kbps (for stereo 44.1kHz input. Halve these numbers for mono input).". This doesn't seem to be happening, though. I took a 16-bit,

...ine VIRTIO_MDEV_QUEUE_ALIGN 0x048 > + > +/* Queue notifier - Write Only */ > +#define VIRTIO_MDEV_QUEUE_NOTIFY 0x050 > + > +/* Device status register - Read Write */ > +#define VIRTIO_MDEV_STATUS 0x060 > + > +/* Selected queue's Descriptor Table address, 64 bits in two halves */ > +#define VIRTIO_MDEV_QUEUE_DESC_LOW 0x080 > +#define VIRTIO_MDEV_QUEUE_DESC_HIGH 0x084 > + > +/* Selected queue's Available Ring address, 64 bits in two halves */ > +#define VIRTIO_MDEV_QUEUE_AVAIL_LOW 0x090 > +#define VIRTIO_MDEV_QUEUE_AVAIL_HIGH 0x094 > + > +/* Se...

...ine VIRTIO_MDEV_QUEUE_ALIGN 0x048 > + > +/* Queue notifier - Write Only */ > +#define VIRTIO_MDEV_QUEUE_NOTIFY 0x050 > + > +/* Device status register - Read Write */ > +#define VIRTIO_MDEV_STATUS 0x060 > + > +/* Selected queue's Descriptor Table address, 64 bits in two halves */ > +#define VIRTIO_MDEV_QUEUE_DESC_LOW 0x080 > +#define VIRTIO_MDEV_QUEUE_DESC_HIGH 0x084 > + > +/* Selected queue's Available Ring address, 64 bits in two halves */ > +#define VIRTIO_MDEV_QUEUE_AVAIL_LOW 0x090 > +#define VIRTIO_MDEV_QUEUE_AVAIL_HIGH 0x094 > + > +/* Se...

Hi all, I'm currently working on an out-of-tree backend and am trying to improve the debug experience when debugging optimized code. Our backend only has 8-bit and 16-bit legal types, so any larger values are expanded. The behavior I am currently seeing is that the expanded halves of an illegal type lose their debug information. Is this the expected behavior? For example, if I have an ISD::DBG_VALUE SDNode associated with a value, and that value is split up (for example a i64 load expanded into two i32 loads), I would expect to see a new ISD::DBG_VALUE tracking each fragmen...