Thanks for the troubleshooting,
I just want to second this patch; it would be great if PATH_MAX could
be used everywhere.
In case someone else searches the archives later, but also for those
who don't know what this is about, PATH_MAX specifies the maximum
number of symbols allowed in a
Hi, can someone tell me how to use associative arrays in R? It can be
a hashtable or some kind of tree, as long as the lookups aren't O(n).
One way to do this is to use names, e.g. in:
list(a=3, ...)[[a]]
presumably looking up a is very quick. (Can someone tell me offhand
how that is
I think it's a great idea worth trying out. We have always done significance
tests just on the final frontier of models as a post processing step. Moving
this into the algorithm could focus the search more on significant higher
quality solutions. One thing to beware of though is that using
Ben,
On Mar 11, 2010, at 8:52 , Ben wrote:
Hi, can someone tell me how to use associative arrays in R? It can
be a hashtable or some kind of tree, as long as the lookups aren't
O(n).
One way to do this is to use names, e.g. in:
list(a=3, ...)[[a]]
presumably looking up a is very
On 3/11/10 12:45 AM, Henrik Bengtsson wrote:
Thanks for the troubleshooting,
I just want to second this patch; it would be great if PATH_MAX could
be used everywhere.
The patch, or at least something quite similar, was applied in r51229.
+ seth
--
Seth Falcon | @sfalcon |
lists are generic vectors with names so lookup is O(n). Environments
in R are true hash tables for that purpose:
Ahh, thanks for the information! A function I wrote before indexing
on a data frame was slower than I expected, and now I know why.
I don't quite understand - characters are
On Thu, Mar 11, 2010 at 06:09:09PM -0600, Ben wrote:
[...]
I don't quite understand - characters are (after raw vectors) the
most expressive data type, so I'm not quite sure why that would be a
limitation .. You can cast anything (but raw vector with nulls) into
to a character.
It's no
