Displaying 20 results from an estimated 33 matches for "bws".
Did you mean:
bus
2009 Nov 03
3
Weird operator behaviour
...et extract 2 which is blatantly wrong. Can anyone see what I'm
doing wrong?
Regards,
James
EXTRACT 1
> fish$Species
[1] ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ATO
ATO
[19] ATO ATO ATO ATO ATO ATO BIG BIG BIG BIG BIG BIG BIG BIG BIG BIG BIG
BIG
[37] BIG BIG BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS BWS
CRA
[55] CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA
CRA
[73] CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA
CRA
[91] CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA CRA
CRA
[109]...
2009 Mar 24
3
DO NOT REPLY [Bug 6209] New: rsync exiting suddenly
https://bugzilla.samba.org/show_bug.cgi?id=6209
Summary: rsync exiting suddenly
Product: rsync
Version: 3.0.5
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: mathieu.coavoux@aktor.fr
QAContact:
2016 Apr 22
1
npudens(np) Error missing value where TRUE/FALSE needed
...ame, while tdat is a 1x(2+3)
vector.
bw_cx[i,] is a 1x (2+3) vector representing the bandwidths h for each variable, which were calculated using the npcdensbw function. (no this is not a mistake, I deliberately use the conditional one)
For this I use the below function in R.
kerz <-
npudens(bws=(bw_cx[i,]),cykertype="epanechnikov",cxkertype="epanechnikov",oxkertype="liracine",tdat=tdata,edat=dat)
In version 2.15.2, this worked fine, as I was able to
retrieve the necessary density estimates with kerz$dens.
This version was installed on a very old (read very...
2008 May 19
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.0.0: Introduction
Hi everyone,
This is dm-ioband version 1.0.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 0.0.4 (24th April):
- Performance tuning
- A new bandwidth control policy is added. This policy controls
2008 May 19
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.0.0: Introduction
Hi everyone,
This is dm-ioband version 1.0.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 0.0.4 (24th April):
- Performance tuning
- A new bandwidth control policy is added. This policy controls
2008 May 19
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.0.0: Introduction
Hi everyone,
This is dm-ioband version 1.0.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 0.0.4 (24th April):
- Performance tuning
- A new bandwidth control policy is added. This policy controls
2008 Jun 02
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.1.0: Introduction
Hi everyone,
This is dm-ioband version 1.1.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 1.0.0 (posted on May 19, 2008):
- Measures against high memory pressure.
I/O requests to reclaim pages won't
2008 Jun 02
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.1.0: Introduction
Hi everyone,
This is dm-ioband version 1.1.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 1.0.0 (posted on May 19, 2008):
- Measures against high memory pressure.
I/O requests to reclaim pages won't
2008 Jun 02
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.1.0: Introduction
Hi everyone,
This is dm-ioband version 1.1.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc2-mm1.
- Changes from 1.0.0 (posted on May 19, 2008):
- Measures against high memory pressure.
I/O requests to reclaim pages won't
2011 Sep 10
0
npreg: plotting out of sample, extremely large bandwidths
...example 1: do not restrict data to x1>=x2
# calculate bandwidth using npregbw()
bandwidth <- npregbw(formula = y ~ x1 + x2,
regtype="ll",
bwmethod="cv.aic",
data=mydata)
summary(bandwidth)
# perform nonparametric regression using bandwidth
results <- npreg(bws=bandwidth)
summary(results)
# use plot to plot results
plot(results,view="fixed",theta=300)
# example 2: restrict data to observations for which x1>=x2
mydata2 <- mydata[mydata$x1>=mydata$x2,]
# calculate bandwidth
bandwidth2 <- npregbw(formula=y ~ x1 + x2,
regtype=&q...
2008 Jul 04
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.2.0: Introduction
Hi everyone,
This is the dm-ioband version 1.2.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc5-mm3.
- Changes from 1.1.0 (posted on June 2, 2008):
- Dynamic policy switching
A user can change the bandwidth control policy
2008 Jul 04
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.2.0: Introduction
Hi everyone,
This is the dm-ioband version 1.2.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc5-mm3.
- Changes from 1.1.0 (posted on June 2, 2008):
- Dynamic policy switching
A user can change the bandwidth control policy
2008 Jul 04
1
[PATCH 0/2] dm-ioband: I/O bandwidth controller v1.2.0: Introduction
Hi everyone,
This is the dm-ioband version 1.2.0 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
- Can be applied to the kernel 2.6.26-rc5-mm3.
- Changes from 1.1.0 (posted on June 2, 2008):
- Dynamic policy switching
A user can change the bandwidth control policy
2009 Feb 13
0
npindex: specifying manual bandwiths
...might be possible, but i couldn't manage so far; could you help ?
For instance,
#Simulation
n <- 200
x1 <- runif(n, min=-1, max=1)
x2 <- runif(n, min=-1, max=1)
y <- ifelse(x1 + x2 + rnorm(n) > 0, 1, 0)
#Klein and Spady estimation, letting np compute the bandwidth
npindexbw(bws=c(1,1,.5),xdat=cbind(x1,x2),ydat=y,bandwidth.compute=TRUE,method="kleinspady")
#Works fine!
#Klein and Spady estimation, attempting to constrain the bandwidth to .5
npindexbw(bws=c(1,1,.5),xdat=cbind(x1,x2),ydat=y,bandwidth.compute=FALSE,method="kleinspady")
#Returns a result w...
2008 Apr 24
2
[PATCH 0/2] dm-ioband: I/O bandwidth controller v0.0.4: Introduction
Hi everyone,
This is dm-ioband version 0.0.4 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
Changes since 0.0.3 (5th February):
- Improve the performance when many processes are issuing I/Os
simultaneously.
- Change the table format to fully support dmsetup
2008 Apr 24
2
[PATCH 0/2] dm-ioband: I/O bandwidth controller v0.0.4: Introduction
Hi everyone,
This is dm-ioband version 0.0.4 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
Changes since 0.0.3 (5th February):
- Improve the performance when many processes are issuing I/Os
simultaneously.
- Change the table format to fully support dmsetup
2008 Apr 24
2
[PATCH 0/2] dm-ioband: I/O bandwidth controller v0.0.4: Introduction
Hi everyone,
This is dm-ioband version 0.0.4 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper
driver, which gives specified bandwidth to each job running on the same
physical device.
Changes since 0.0.3 (5th February):
- Improve the performance when many processes are issuing I/Os
simultaneously.
- Change the table format to fully support dmsetup
2008 Feb 05
2
[PATCH 0/2] dm-ioband v0.0.3: The I/O bandwidth controller: Introduction
Hi everyone,
This is dm-ioband version 0.0.3 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver,
which gives specified bandwidth to each job running on the same physical
device.
Changes since 0.0.2 (23rd January):
- Ported to linux-2.6.24.
- Rename the name of this device-mapper device as "ioband."
- The output format of "dmsetup
2008 Feb 05
2
[PATCH 0/2] dm-ioband v0.0.3: The I/O bandwidth controller: Introduction
Hi everyone,
This is dm-ioband version 0.0.3 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver,
which gives specified bandwidth to each job running on the same physical
device.
Changes since 0.0.2 (23rd January):
- Ported to linux-2.6.24.
- Rename the name of this device-mapper device as "ioband."
- The output format of "dmsetup
2008 Feb 05
2
[PATCH 0/2] dm-ioband v0.0.3: The I/O bandwidth controller: Introduction
Hi everyone,
This is dm-ioband version 0.0.3 release.
Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver,
which gives specified bandwidth to each job running on the same physical
device.
Changes since 0.0.2 (23rd January):
- Ported to linux-2.6.24.
- Rename the name of this device-mapper device as "ioband."
- The output format of "dmsetup