Displaying 16 results from an estimated 16 matches for "nranges".
Did you mean:
ranges
2017 Jul 06
2
Help documentation of "The Studentized range Distribution"
Dear all,
I wanted to compare Bonferroni vs TukeyHSD correction over a range of groups and group sizes, and wanted to use the function qtukey.
In the help documentation it says
qtukey(p, nmeans, df, nranges = 1, lower.tail = TRUE, log.p = FALSE)
Arguments
q
vector of quantiles.
p
vector of probabilities.
nmeans
sample size for range (same for each group).
df
degrees of freedom for s (see below).
nranges
number of groups whose maximum range is considered.
log.p
logical; if TRUE, probabilitie...
2017 Jul 10
1
Help documentation of "The Studentized range Distribution"
...ution of the maximum of r statistics each distributed as the Studentized range of means calculated from c random samples of size n from normal populations. The rc samples are assumed to be mutually independent and a common pooled?within?samplevariance is used throughout."
So the connection is nranges == r, and nmeans == c. (n never actually factors in because sqrt(n) is part of the standardization)
For the typical application, r is 1 for the usual studentized range distribution. E.g. for two large groups:
> qtukey(.95,2,df=Inf)
[1] 2.771808
As there is only one difference to consider, thi...
2019 Jul 23
4
[PATCH] mm/hmm: replace hmm_update with mmu_notifier_range
The hmm_mirror_ops callback function sync_cpu_device_pagetables() passes
a struct hmm_update which is a simplified version of struct
mmu_notifier_range. This is unnecessary so replace hmm_update with
mmu_notifier_range directly.
Signed-off-by: Ralph Campbell <rcampbell at nvidia.com>
Cc: "Jérôme Glisse" <jglisse at redhat.com>
Cc: Jason Gunthorpe <jgg at mellanox.com>
2017 Jul 10
0
Help documentation of "The Studentized range Distribution"
...AM PDT, Ursula Garczarek <Ursula.Garczarek at cytel.com> wrote:
>Dear all,
>I wanted to compare Bonferroni vs TukeyHSD correction over a range of
>groups and group sizes, and wanted to use the function qtukey.
>
>In the help documentation it says
>
>qtukey(p, nmeans, df, nranges = 1, lower.tail = TRUE, log.p = FALSE)
>Arguments
>q
>
>vector of quantiles.
>
>p
>
>vector of probabilities.
>
>nmeans
>
>sample size for range (same for each group).
>
>df
>
>degrees of freedom for s (see below).
>
>nranges
>
>number of...
2017 Oct 13
1
Quotation marks hinder for loop
Dear mailing list members,
My question is maybe very basic, but I could not find the solution.
I would like to do the following things
1)
colnames(V1)[2] <- par$V2[1]
colnames(V2)[2] <- par$V2[2]
colnames(V3)[2] <- par$V2[3]
...
colnames(V37)[2] <- par$V2[37]
2)
V1 <- V1[,-1]
V2 <- V2[,-1]
V3 <- V3[,-1]
...
V37 <- V37[,-1]
3)
ms <- merge(V1,V2)
ms <- merge(ms,V3)
2019 Jul 24
5
[PATCH] mm/hmm: replace hmm_update with mmu_notifier_range
On Wed, Jul 24, 2019 at 09:05:53AM +0200, Christoph Hellwig wrote:
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
>
> One comment on a related cleanup:
>
> > list_for_each_entry(mirror, &hmm->mirrors, list) {
> > int rc;
> >
> > - rc = mirror->ops->sync_cpu_device_pagetables(mirror, &update);
> > +
2019 Nov 12
0
[PATCH v3 13/14] mm/hmm: remove hmm_mirror and related
From: Jason Gunthorpe <jgg at mellanox.com>
The only two users of this are now converted to use mmu_interval_notifier,
delete all the code and update hmm.rst.
Reviewed-by: J?r?me Glisse <jglisse at redhat.com>
Tested-by: Ralph Campbell <rcampbell at nvidia.com>
Signed-off-by: Jason Gunthorpe <jgg at mellanox.com>
---
Documentation/vm/hmm.rst | 105 ++++-----------
2019 Jul 24
0
[PATCH] mm/hmm: replace hmm_update with mmu_notifier_range
Looks good:
Reviewed-by: Christoph Hellwig <hch at lst.de>
One comment on a related cleanup:
> list_for_each_entry(mirror, &hmm->mirrors, list) {
> int rc;
>
> - rc = mirror->ops->sync_cpu_device_pagetables(mirror, &update);
> + rc = mirror->ops->sync_cpu_device_pagetables(mirror, nrange);
> if (rc) {
> - if
2019 Jul 24
0
[PATCH] mm/hmm: replace hmm_update with mmu_notifier_range
On Wed 24-07-19 12:28:58, Jason Gunthorpe wrote:
> On Wed, Jul 24, 2019 at 09:05:53AM +0200, Christoph Hellwig wrote:
> > Looks good:
> >
> > Reviewed-by: Christoph Hellwig <hch at lst.de>
> >
> > One comment on a related cleanup:
> >
> > > list_for_each_entry(mirror, &hmm->mirrors, list) {
> > > int rc;
> > >
2000 Jul 05
1
Tukey.aov with split-plot designs
...(res2) doesn't work and reports NULL
res2$df.residual doesn't work and reports NULL
Is this an undocumented feature or an error?
It sure plays havoc with Dr. Bates' contribution of Tukey.aov which works
with res0 and res1 but doesn't work with res2 and reports
Error in qtukey(p, nranges, nmeans, df, lower.tail, log.p) :
Non-numeric argument to mathematical function
A simple but inelegant workaround is to input mse and df.residual as
function arguments in addition to the aov object. Does anyone have a better
solution?
Thank you,
Peter B.
--
Peter B. Mandeville...
2019 Jul 24
2
[PATCH] mm/hmm: replace hmm_update with mmu_notifier_range
On Wed, Jul 24, 2019 at 07:58:58PM +0200, Michal Hocko wrote:
> On Wed 24-07-19 12:28:58, Jason Gunthorpe wrote:
> > On Wed, Jul 24, 2019 at 09:05:53AM +0200, Christoph Hellwig wrote:
> > > Looks good:
> > >
> > > Reviewed-by: Christoph Hellwig <hch at lst.de>
> > >
> > > One comment on a related cleanup:
> > >
> > >
2019 Jul 26
13
[PATCH v2 0/7] mm/hmm: more HMM clean up
Here are seven more patches for things I found to clean up.
This was based on top of Christoph's seven patches:
"hmm_range_fault related fixes and legacy API removal v3".
I assume this will go into Jason's tree since there will likely be
more HMM changes in this cycle.
Changes from v1 to v2:
Added AMD GPU to hmm_update removal.
Added 2 patches from Christoph.
Added 2 patches as
2008 Jan 22
1
Duncan's MRT: limitations to qtukey() function?
Dear all,
I'm using R to perform multiple comparison testing on agriculture
genotype trials. To perform the Duncan's MRT, I use the qtukey()
function with the following syntax:
qtukey(p = ((1 - 0.05) ^ (pos - 1)), nmeans = pos, df = ni)
I experience a strange behaviour when the number of means in the trial
and the number of residual degrees of freedom (ni) becomes high
2019 Jul 01
30
dev_pagemap related cleanups v4
Hi Dan, Jérôme and Jason,
below is a series that cleans up the dev_pagemap interface so that
it is more easily usable, which removes the need to wrap it in hmm
and thus allowing to kill a lot of code
Note: this series is on top of Linux 5.2-rc6 and has some minor
conflicts with the hmm tree that are easy to resolve.
Diffstat summary:
34 files changed, 379 insertions(+), 1016 deletions(-)
Git
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others