Displaying 20 results from an estimated 48 matches for "1000.0".
Did you mean:
10.0.0
2007 Sep 10
2
Are the error messages of ConstrOptim() consisten with each other?
Dear Friends.
I found something very puzzling with constOptim(). When I change the
parameters for ConstrOptim, the error messages do not seem to be
consistent with each other:
> constrOptim(c(0.5,0.3,0.5), f=fit.error, gr=fit.error.grr, ui=ui,ci=ci)
Error in constrOptim(c(0.5, 0.3, 0.5), f = fit.error, gr = fit.error.grr, :
initial value not feasible
> constrOptim(c(0.5,0.9,0.5),
2007 Sep 09
2
What does it mean by "initial value not available"?
Dear friends.
I use ConstrOptim( ) and got error message "initial value not available".
My understanding of "initial value not available" is that one of the
following 3 cases happens:
1.The objective function is not well defined at the point of the initial
value.
2. The differentiation of the objective function is not well defined at the
point of the initial value.
3. The
2004 Feb 27
2
patch: better progress meter
Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/rsync/attachments/20040227/923b87ee/PGP.bin
2004 Mar 03
5
get.hist.quote - is great, but am I missing something?
I find it's just great to be able to say:
library(tseries)
x <- get.hist.quote(instrument="ongc.ns")
and it gets a full time-series of the stock price of the symbol
ongc.ns from Yahoo quote.
However, once my hopes have been raised by such beauty :-) I get
disappointed when I do
> plot(x)
and the annotation is horrible! The x axis is not labelled as
dates. The default
2012 Apr 17
1
[LLVMdev] some thoughts on the semantics of !fpmath
On Apr 16, 2012, at 11:50 PM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Dan,
>
>> I realize that some of these thoughts apply equally to the
>> prior !fpaccuracy metadata that's been around a while, but I
>> hadn't looked at it closely until now.
>>
>> The !fpmath metadata violates the original spirit of
>> metadata, which is that
2009 Jan 18
4
data management
Dear Rxperts,
I have a varaibles data file that looks like this
p(1) 10
p(1) 3
p(1) 4
p(2) 20
p(2) 30
p(2) 40
p(3) 4
p(3) 1
p(1) 2
I cannot process these data with R because it does not like the parentheses.
How can I get these to look like:
p1 10
p1 3
p1 4
p2 20
p2 30
p2 40
p3 4
p3 1
p3 2
The data is in a tab delimited text file and I want to get it into a
data.frame().
Many thanks in
2007 Aug 22
3
tackle memory insufficiency for large dataset using save() & load()??
Hello List, i have been agonizing over this for days, any reply would be greatly appreciated!
Situation:___________________________________
My original dataset is a .csv dataset (w/ 2M records) with 4 variables:
job_id (Primary key, won't be used for analysis, just used for join tables),
sector_id (categorical variable, for 19 industry sectors),
sqft (con't variable for square
2010 Oct 03
2
Read file
Dear R-users,
I would like to know how could I read a file with different lines lengths.
I need read this file and create an output to feed my database.
So after reading I'll need create an output like this
"INSERT INTO TEMP (DATA,STATION,VAR1,VAR2) VALUES (20100910,837460, 39,390)"
I mean, each line should be read. But I don`t how to do this when these
lines have different
2005 Mar 04
1
wierd duration shown in progress with 0 byte files
While trying out the 2.6.4-pre2, I noticed something wierd with
--progress; it shows:
ads/promotions.MYD
0 100% 0.00kB/s 519:35:46 (61, 56.3% of 597)
This is quite reproducable whenever an empty file is transferred (or
created on the receiving end).
Commandline used was:
rsync -zave 'ssh -c arcfour' --progress --stats --delete lisa:/var/lib/mysql/ .
BTW, this also
2001 Feb 01
3
summary() vs mean()
Forgive what may seem to be a trivial question/problem.
Below is some simple R 1.2.1(Windows) code with output.
> summary(mammals, digits=10)
Name Body.Weight Brain.Weight
Red Fox :1 Min. : 3.0 Min. : 26.0
Pig :1 1st Qu.: 35.5 1st Qu.: 138.5
Man :1 Median : 100.0 Median : 406.0
Kangaroo:1 Mean : 761.2 Mean :1000.0
Jaguar :1 3rd
2002 Mar 14
2
PATCH: better progress reporting
I've been looking at the --progress reporting, which is somewhat
improved these days. But look at this output of this evening rawhide
mirror update:
[...]
perl-DB_File-1.75-27.i386.rpm
73430 100% 519.63kB/s 0:00:00
perl-DB_File-1.75-28.99.3.i386.rpm
61783 100% 533.94kB/s 0:00:00
[...]
Now, while it's good to have the ETA ticking down as something is fetched,
2005 Sep 03
1
Current status on _outgoing_ Swedish/Dutch DTMF CLIP for TDM400 FXS interfaces?
Hi all,
I have been looking at the code for both the zaptel driver (wctdm.c/wcfxs.c)
and the asterisk channel driver (chan_zap.c) trying to figure out how much
of this that has been implemented. So far I can see that the current stable
1.0.9.1 zaptel driver don't have the SETPOLARITY ioctl that would be
required to properly signal the Swedish/Dutch CLIP, but the 1.2 beta1 has
this
2020 Feb 25
0
[PATCH 04/12] drm: Nuke mode->vrefresh
On Tue, Feb 25, 2020 at 05:45:06PM +0200, Ville Syrj?l? wrote:
> On Tue, Feb 25, 2020 at 04:19:27PM +0100, Andrzej Hajda wrote:
> > On 25.02.2020 12:21, Ville Syrj?l? wrote:
> > > On Mon, Feb 24, 2020 at 03:14:54PM +0100, Andrzej Hajda wrote:
> > >> On 19.02.2020 21:35, Ville Syrjala wrote:
> > >>> From: Ville Syrj?l? <ville.syrjala at
2015 Jul 04
1
[PATCH] unnecessary assignment
another small bug: in src\share\replaygain_analysis\replaygain_analysis.c
there are two assignments to sampleWindow:
sampleWindow = (int) ceil ((double)samplefreq * (double)RMS_WINDOW_TIME / 1000.0);
sampleWindow =
(replaygainfilter->rate * RMS_WINDOW_TIME + 1000-1) / 1000;
-------------- next part --------------
A non-text attachment was scrubbed...
Name:
2006 Aug 14
0
[PATCH] remove another xc_dom0_op() user
# HG changeset patch
# User john.levon@sun.com
# Date 1155596263 -3600
# Node ID dc12f0942649ee27ff2aec3e3d9c2d99746b9e58
# Parent 09bc238664cb7b6d0f960f5e135ac80a75b342f1
Remove another external-to-libxc user of xc_dom0_op().
Signed-off-by: John Levon <john.levon@sun.com>
diff -r 09bc238664cb -r dc12f0942649 tools/xenmon/xenbaked.c
--- a/tools/xenmon/xenbaked.c Mon Aug 14 15:40:36 2006
2009 Oct 19
1
How to import the large data into R
Dear,
I would like to deal with microarray data, it can run when i deal with
little data. However, the amount number of SNP data are 45181, amount
numbers of animal are 3081,it can not be allocated 1000Mb memory when
i importing them to R
Procedure sentence show:
m<-matrix(scan("D:/SNPdata.txt"),ncol=nmarkers,byrow=TRUE)
Error show:
Error: cannot allocate vector of size 1000.0 Mb
2012 Apr 17
0
[LLVMdev] some thoughts on the semantics of !fpmath
Hi Dan,
> I realize that some of these thoughts apply equally to the
> prior !fpaccuracy metadata that's been around a while, but I
> hadn't looked at it closely until now.
>
> The !fpmath metadata violates the original spirit of
> metadata, which is that metadata is only supposed to exclude
> possible runtime conditions, rather than to introduce new
> possible
2020 Feb 25
2
[PATCH 04/12] drm: Nuke mode->vrefresh
On Tue, Feb 25, 2020 at 04:19:27PM +0100, Andrzej Hajda wrote:
> On 25.02.2020 12:21, Ville Syrj?l? wrote:
> > On Mon, Feb 24, 2020 at 03:14:54PM +0100, Andrzej Hajda wrote:
> >> On 19.02.2020 21:35, Ville Syrjala wrote:
> >>> From: Ville Syrj?l? <ville.syrjala at linux.intel.com>
> >>>
> >>> Get rid of mode->vrefresh and just
2001 Nov 29
1
patch from faith@alephnull to add rate indicator to --progress
Any votes for/against?
----- Forwarded message from Rik Faith <faith@alephnull.com> -----
Date: Wed, 28 Nov 2001 12:55:29 -0500
From: Rik Faith <faith@alephnull.com>
To: mbp@samba.org
Subject: rsync patch
X-Mailer: VM 6.96; XEmacs 21.1; Linux 2.4.16 (light)
Here is a patch that adds rate information (e.g., kB/s) to the
--progress display. I just noticed that 2.4.7pre4 is coming
2012 Apr 16
6
[LLVMdev] some thoughts on the semantics of !fpmath
I realize that some of these thoughts apply equally to the
prior !fpaccuracy metadata that's been around a while, but I
hadn't looked at it closely until now.
The !fpmath metadata violates the original spirit of
metadata, which is that metadata is only supposed to exclude
possible runtime conditions, rather than to introduce new
possible runtime possibilities. The motivation for this is