On Wed, 28 Mar 2007, Benilton Carvalho wrote:
> Hi,
>
> (I tried looking for it, but I don't think it was discussed before...
> or maybe I didn't use the correct keywords).
>
> I have a package (say, pkg1), which uses NAMESPACE. This package
> contains a bunch of functions the are used internally,
Hi,
(I tried looking for it, but I don't think it was discussed before...
or maybe I didn't use the correct keywords).
I have a package (say, pkg1), which uses NAMESPACE. This package
contains a bunch of functions the are used internally, therefore
they're not exported (say, internalFunc1).
Has anybody tried to use Rmpi with the OpenMPI library instead of LAM/MPI?
LAM appears to be somewhat hardcoded in the Rmpi setup. Before I start to
experiment with changing this, has anybody else tried Rmpi with non-LAM MPI
implementations?
Dirk
--
Hell, there are no rules here - we're trying
Hi
Prof Brian Ripley wrote:
> On Wed, 28 Mar 2007, Paul Murrell wrote:
>
>> Hi
>>
>>
>> Prof Brian Ripley wrote:
>>> [Moved to R-devel to ask a policy question.]
>>>
>>> On Fri, 16 Mar 2007, Duncan Murdoch wrote:
>>>
On 3/16/2007 8:02 AM, [EMAIL PROTECTED] wrote:
> Hi all:
>
> I
On Wed, 28 Mar 2007, Paul Murrell wrote:
> Hi
>
>
> Prof Brian Ripley wrote:
>> [Moved to R-devel to ask a policy question.]
>>
>> On Fri, 16 Mar 2007, Duncan Murdoch wrote:
>>
>>> On 3/16/2007 8:02 AM, [EMAIL PROTECTED] wrote:
Hi all:
I'm using 'persp' for 3D graphics.
I
On Mar 27, 2007, at 5:42 PM, Herve Pages wrote:
> Simon Urbanek wrote:
>> Your proposed behavior is inconsistent, anyway. The purpose of
>> dirname is to return parent directory of the entity represented by
>> the pathname.
>
> Mmmm, I don't think this is true:
>
>> dirname("aaa/..")
> [1]
Simon Urbanek wrote:
>
> On Mar 27, 2007, at 2:49 PM, cstrato wrote:
>
>> Hin-Tak Leung wrote:
>>> cstrato wrote:
1. I did read the help file.
2. I have my own workaround, using e.g.
file.info("/my/path/")[,"isdir"]
3. This was a suggestion.
4. If you agree with me that "/m
Hi,
Simon Urbanek wrote:
> Your proposed behavior is inconsistent, anyway. The purpose of
> dirname is to return parent directory of the entity represented by
> the pathname.
Mmmm, I don't think this is true:
> dirname("aaa/..")
[1] "aaa"
"aaa" is not the parent directory of "aaa/.."
S
On Mar 27, 2007, at 2:49 PM, cstrato wrote:
> Hin-Tak Leung wrote:
>> cstrato wrote:
>>> 1. I did read the help file.
>>> 2. I have my own workaround, using e.g.
>>> file.info("/my/path/")[,"isdir"]
>>> 3. This was a suggestion.
>>> 4. If you agree with me that "/my/path/" is a path, then both
>>
Hi
Prof Brian Ripley wrote:
> [Moved to R-devel to ask a policy question.]
>
> On Fri, 16 Mar 2007, Duncan Murdoch wrote:
>
>> On 3/16/2007 8:02 AM, [EMAIL PROTECTED] wrote:
>>> Hi all:
>>>
>>> I'm using 'persp' for 3D graphics.
>>>
>>> I need the axis's labels smaller than by defect.
>>>
>>> I
Gabor Grothendieck wrote:
> On 3/27/07, cstrato <[EMAIL PROTECTED]> wrote:
>> Hin-Tak Leung wrote:
>> > cstrato wrote:
>> >> 1. I did read the help file.
>> >> 2. I have my own workaround, using e.g.
>> >> file.info("/my/path/")[,"isdir"]
>> >> 3. This was a suggestion.
>> >> 4. If you agree with m
On 3/27/07, cstrato <[EMAIL PROTECTED]> wrote:
> Hin-Tak Leung wrote:
> > cstrato wrote:
> >> 1. I did read the help file.
> >> 2. I have my own workaround, using e.g.
> >> file.info("/my/path/")[,"isdir"]
> >> 3. This was a suggestion.
> >> 4. If you agree with me that "/my/path/" is a path, then
Hin-Tak Leung wrote:
> cstrato wrote:
>> 1. I did read the help file.
>> 2. I have my own workaround, using e.g.
>> file.info("/my/path/")[,"isdir"]
>> 3. This was a suggestion.
>> 4. If you agree with me that "/my/path/" is a path, then both
>>"dirname()" and "dirname" give an incorrect an
Dear members of the R Development Team,
I am looking for people with a deep understanding of R internals to
assist in bridging R to OpenOffice.
While R is a state of the art statistical environment, less experienced
users often find it difficult to work with R. Therefore, I believe that
a brid
cstrato wrote:
> 1. I did read the help file.
> 2. I have my own workaround, using e.g.
>file.info("/my/path/")[,"isdir"]
> 3. This was a suggestion.
> 4. If you agree with me that "/my/path/" is a path, then both
>"dirname()" and "dirname" give an incorrect answer.
> 5. Maybe, you can giv
1. I did read the help file.
2. I have my own workaround, using e.g.
file.info("/my/path/")[,"isdir"]
3. This was a suggestion.
4. If you agree with me that "/my/path/" is a path, then both
"dirname()" and "dirname" give an incorrect answer.
5. Maybe, you can give me a logical reason (beside
Liaw, Andy wrote:
> Given that the behavior is exactly as I expected it be, I would call
> that "feature" (and IMHO not a very special one). The two data frames
> are just different (try str() on them: A in dd is factor, while A in
> dd2 is character), so I don't know why you'd expect unlist() on
> "Herve" == Herve Pages <[EMAIL PROTECTED]>
> on Mon, 26 Mar 2007 20:48:33 -0700 writes:
Herve> Hi,
>> dd <- data.frame(A=c("b","c","a"), B=3:1) dd
Herve> A B 1 b 3 2 c 2 3 a 1
>> unlist(dd)
Herve> A1 A2 A3 B1 B2 B3 2 3 1 3 2 1
Herve> Someone else might get
Given that the behavior is exactly as I expected it be, I would call
that "feature" (and IMHO not a very special one). The two data frames
are just different (try str() on them: A in dd is factor, while A in
dd2 is character), so I don't know why you'd expect unlist() on them to
give you the same
19 matches
Mail list logo