I've incorporated a more correct version of 1: think about what
happens if the next method also copies over the class, for example.
(It was more complicated than that: [.AsIs was used for other classes
in R -- did you actually test your suggestion, as 'make check' failed
for me?)
But write.csv
Dear developeRs,
I have not found anything recent about how to link to a vignette or other
documentation from within Rd-files. Is this now possible with the new help
system ? For example, I would like to link to the file AlgDesign.pdf
provided within the doc directory of package AlgDesign.
Thank
Ulrike Groemping wrote:
Dear developeRs,
I have not found anything recent about how to link to a vignette or other
documentation from within Rd-files. Is this now possible with the new help
system ? For example, I would like to link to the file AlgDesign.pdf
provided within the doc directory of
Duncan Murdoch-2 wrote:
>
> Ulrike Groemping wrote:
>> Dear developeRs,
>>
>> I have not found anything recent about how to link to a vignette or other
>> documentation from within Rd-files. Is this now possible with the new
>> help
>> system ? For example, I would like to link to the file AlgD
Full_Name: Jerry W. Lewis
Version: 2.10.0
OS: Windows XP Professional
Submission from: (NULL) (96.237.55.233)
pt(0,3,200) # correctly returns 0
pt(-1000,3,200) # erroniously returns 0.003116595
Since pt(0,df,nc) = pnorm(-nc), there is an easily computed upper bound for
pt(-t,df,nc) where t
Ulrike Groemping wrote:
Duncan Murdoch-2 wrote:
Ulrike Groemping wrote:
Dear developeRs,
I have not found anything recent about how to link to a vignette or other
documentation from within Rd-files. Is this now possible with the new
help
system ? For example, I would like to link to t
Hi
I have managed to link R.dll to my Visual Studio Win32 GUI project. However
I am unable to see any of the R messages on a console.
I'm hitting a dead end trying to use R_tryEval.
Is there a way I can obtain the error message when R_tryEval fails?
Regards
Abhijit Bera
[[alternative
Duncan Murdoch schrieb:
Ulrike Groemping wrote:
Duncan Murdoch-2 wrote:
Ulrike Groemping wrote:
Dear developeRs,
I have not found anything recent about how to link to a vignette or
other
documentation from within Rd-files. Is this now possible with the new
help
system ? For example,
Ulrike Grömping wrote, On 11/18/09 13:28:
> Duncan Murdoch schrieb:
>> Ulrike Groemping wrote:
>>>
>>> Duncan Murdoch-2 wrote:
>>>
Ulrike Groemping wrote:
> Dear developeRs,
>
> I have not found anything recent about how to link to a vignette or
> other
> document
On 11/18/2009 7:28 AM, Ulrike Grömping wrote:
Duncan Murdoch schrieb:
Ulrike Groemping wrote:
Duncan Murdoch-2 wrote:
Ulrike Groemping wrote:
Dear developeRs,
I have not found anything recent about how to link to a vignette or
other
documentation from within Rd-files. Is this now po
On 11/18/2009 8:01 AM, ml-it-r-de...@epigenomics.com wrote:
Ulrike Grömping wrote, On 11/18/09 13:28:
Duncan Murdoch schrieb:
Ulrike Groemping wrote:
Duncan Murdoch-2 wrote:
Ulrike Groemping wrote:
Dear developeRs,
I have not found anything recent about how to link to a vignette or
ot
Dear all,
There appears to be a bug in how constrOptim handles ... arguments that
are suppose to be passed to optim, according to the documentation. This
means you can't get the hessian to be returned, for example (so this is
a real problem, and not just a question of mistaken documentation).
Elizabeth,
If you look at the arguments in optim(), you will see that the only
additional argument that is in optim but not in constrOptim is the
`hessian'. So, it makes sense to add that explicitly in constrOptim() as
well. The other additional arguments are passed to optim via the `control'
ar
Hi Elizabeth,
I have fixed this problem. See the attached function. There is also
another bug that can create a problem when control$fnscale = -1, i.e. when
the objective function is to be maximized. I have commented this in the
code and have also fixed this problem.
There is a word of caution
Dear list,
When calling R from C, what appears like a spurious error can be
triggered during the execution of chisq.test(x, y).
This is happening when the following conditions are met:
- x and y are "anonymous" C-level R vectors (they do not have a symbol),
but they are protected from garbag
15 matches
Mail list logo