Displaying 20 results from an estimated 433 matches for "unavoidably".
Did you mean:
unavoidable
2004 Nov 13
2
unavoidable loop? a better way??
Hi all, I have the following problem, best expressed by my present
solution:
# p is a vector
myfunc <- function (p) {
x[1] <- p[1]
for (i in c(2:length(p))) {
x[i] <- 0.8*p[i] + 0.2*p[i-1]
}
return (x)
}
That is, I'm calculating a time-weighted average. Unfortunately the scale
of the problem is big. length(p) in this case is such that each call takes
about 6
2013 Nov 12
2
Expanding legacy gluster volumes
Hi there,
This is a hypothetical problem, not one that describes specific hardware
at the moment.
As we all know, gluster currently usually works best when each brick is
the same size, and each host has the same number of bricks. Let's call
this a "homogeneous" configuration.
Suppose you buy the hardware to build such a pool. Two years go by, and
you want to grow the pool. Changes
2018 Dec 04
3
Bug report: Function ppois(0:20, lambda=0.9) does not generate a non-decreasing result.
Le 04/12/2018 ? 11:27, I?aki Ucar a ?crit?:
> On Tue, 4 Dec 2018 at 11:12, <qweytr1 at mail.ustc.edu.cn> wrote:
>> function ppois is a function calculate the CDF of Poisson distribution, it should generate a non-decreasing result, but what I got is:
>>
>>> any(diff(ppois(0:19,lambda=0.9))<0)
>> [1] TRUE
>>
>> Actually,
>>
>>>
2018 May 28
3
Problem in Pigeonhole sievec
Dear all,
I stumbled upon the following behaviour of Pigeonhole, which I consider
to be problematic. A user deployed a Sieve script similar to the following
snippet
if not anyof (address :is ["from","cc"] ["...", ..., "... at ...
GARBAGE", ...] {
fileinto "inbox.Trash";
stop;
}
Note the extra line break before GARBAGE. This script is
2017 Sep 01
3
side-effect of calling functions via `::`
Dear list
I'm not sure whether this is a bug or an unavoidable consequence of the
way packages are loaded, but there can be surprising side effects of
calling a function via package::function. Here's an example using the
formula.tools package:
form <- a ~ b
as.character(form)
formula.tools::lhs(form)
as.character(form)
The first call to as.character returns:
[1] "~"
2018 Dec 03
2
Bug report: Function ppois(0:20, lambda=0.9) does not generate a non-decreasing result.
function ppois is a function calculate the CDF of Poisson distribution, it should generate a non-decreasing result, but what I got is:
> any(diff(ppois(0:19,lambda=0.9))<0)
[1] TRUE
Actually,
> ppois(19,lambda=0.9)<ppois(18,lambda=0.9)
[1] TRUE
Which could not be TRUE.
Code is tested in both R 3.5.1 and Microsoft R Open 3.5.1.
_
2017 Jan 18
2
[PATCH v6 kernel 3/5] virtio-balloon: speed up inflate/deflate process
On Wed, Jan 18, 2017 at 04:56:58AM +0000, Li, Liang Z wrote:
> > > - virtqueue_add_outbuf(vq, &sg, 1, vb, GFP_KERNEL);
> > > - virtqueue_kick(vq);
> > > +static void do_set_resp_bitmap(struct virtio_balloon *vb,
> > > + unsigned long base_pfn, int pages)
> > >
> > > - /* When host has read buffer, this completes via balloon_ack */
>
2017 Jan 18
2
[PATCH v6 kernel 3/5] virtio-balloon: speed up inflate/deflate process
On Wed, Jan 18, 2017 at 04:56:58AM +0000, Li, Liang Z wrote:
> > > - virtqueue_add_outbuf(vq, &sg, 1, vb, GFP_KERNEL);
> > > - virtqueue_kick(vq);
> > > +static void do_set_resp_bitmap(struct virtio_balloon *vb,
> > > + unsigned long base_pfn, int pages)
> > >
> > > - /* When host has read buffer, this completes via balloon_ack */
>
2019 Nov 04
2
Comments on GitHub commits?
On Sat, Nov 2, 2019 at 4:26 AM Mehdi AMINI via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> On Wed, Oct 30, 2019 at 10:59 PM David Zarzycki via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>>
>>
>> On Oct 30, 2019, at 5:57 PM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> On 10/30/2019 03:09 AM, Stephan Bergmann
2018 Feb 15
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Hi,
I was unable to find a bug report for this with a cursory search, but would
like clarification if this is intended or unavoidable behaviour:
```{r}
# Create example data.frames
parents <- data.frame(name=c("Sarah", "Max", "Qin", "Lex"),
sex=c("F", "M", "F", "M"),
2016 Sep 10
2
defaults for FP contraction [e.g. fused multiply-add]: suggestion and patch to be slightly more aggressive and to make Clang`s optimization settings closer to having the same meaning as when they are given to GCC [at least for "-O3"]
> On Sep 9, 2016, at 3:27 PM, Steve Canon via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
>
>
> Sent from my iPhone
>
> On Sep 9, 2016, at 6:21 PM, Abe Skolnik <a.skolnik at samsung.com <mailto:a.skolnik at samsung.com>> wrote:
>
>> On 09/09/2016 04:31 PM, Stephen Canon wrote:
>>
>>> Gating this on -Owhatever is dangerous, .
2015 Apr 16
3
quota_over_flag examples?
I can't find any posts on this list for peoples using quota_over_flag
http://wiki2.dovecot.org/Quota/Configuration#Overquota-flag_.28v2.2.16.2B-.29
If my userdb is sql what would be best script to use in terms of performance?
(I mean if over-quota-flag triggers script every time it changes and the script
calls CLI mysql client isn't all this so expensive to spawn a new shell session
2011 Apr 08
5
Avoiding a loop
Friends.
I cannot simplify this much, and I think the loop is unavoidable. As a
recovering C programmer I want to avoid loops and in cases like this I
almost allways can by using an apply function. But I suspect in this case
there is nothing I can do.
It is a finance example where a price series is compared to a moving
average. If the price goes above the average, plus a bit, buy the
2015 Mar 18
4
Windows gcc toolchain for R 3.2.0
To anyone following the Windows toolchain saga:
The gcc 4.9.2 toolchain that is currently in Rtools33 has too many
incompatibilities with existing code, so we won't be using it in the R
3.2.0 build. I will soon be uploading to CRAN a new version of Rtools33
that is very similar to Rtools32, containing gcc 4.6.3.
We are continuing to work on the new toolchain, and hope to have it
ready
2010 Mar 19
0
[LLVMdev] 2.7 Pre-release1 available for testing
Hi Tanya,
On darwin9, the binaries in the darwin10 packages give:
$ /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as --help
dyld: unknown required load command 0x80000022
Trace/BPT trap
That could be unavoidable, of course.
Also, could you document what build mode the packages use (or release
both Debug and Release-Asserts packages)? Since +Asserts and -Asserts
have different ABIs, I'd have
2010 Mar 19
1
[LLVMdev] 2.7 Pre-release1 available for testing
Hm, I also note that:
$ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as
/opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64
Why's the i386 package have an x86_64 binary in it? That could explain
why it doesn't work on darwin9.
On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote:
> Hi Tanya,
>
> On darwin9, the
2006 Mar 10
1
XenMon''s first reading
In XenMon''s file appending mode, a lot of times I''ll get a strange first data
point, e.g., the cpu% for dom0 will be 99.9 but the rest of the readings will be
19-21 which are sane for the run. I''ve been throwing the data point out, but
was curious about it. Is it unavoidable?
Thanks,
Tim
_______________________________________________
Xen-devel mailing list
2008 Aug 14
1
Security leak in map_nt_perms?
In map_nt_perms any of FILE_READ_DATA, FILE_READ_EA or
FILE_READ_ATTRIBUTES is mapped unconditionally to Unix read permission
and similarly for write permission
This means that if I put a file on a samba share where I explicitly left
*only* FILE_READ_ATTRIBUTES and FILE_READ_EA the file content becomes
hiddenly readable also if I decided (for very good reasons) otherwise.
I'd say that when a
2006 Jan 11
1
problem with replicate and "..." (PR#8472)
I am using R version 2.0.0 (2004-10-04) on Fedora Core 2.
This works correctly:
> foo <- function(x=1,y=2) { c(x,y) }
> bar <- function(n,...) c(n,foo(...))
> bar(10,3)
[1] 10 3 2
But it goes wrong if I replace "c" in bar with "replicate":
> foo <- function(x=1,y=2) { c(x,y) }
> bar <- function(n,...) replicate(n,foo(...))
> bar(10,3)
2008 Jun 05
1
memory.size() for large memory usage (PR#11596)
This amusing behaviour is from R2.6.1 on WinXP Pro SP2 running with boot.in=
i /3GB flag, exploring memory limits.
=20
When actual (object, not total) memory usage hits 2048 MB, memory.size star=
ts counting down again, but reports a negative amount, e.g. -2046.333. Is t=
his an intended (or unavoidable) feature?)
=20
Thanks,
=20
Rory Bowden
bowden at stats.ox.ac.uk
=20
[[alternative