On 2/3/10 6:23 PM, B.A.D.C.M.D Santos wrote:
> ?! phyper is deterministic, I think. Calling it with the same parameters
> will give the same results.
>
> Good point, that it is in fact an excellent improvement. I will start
> storing everything already computed on a dictionary.
Avoiding to recompu
?! phyper is deterministic, I think. Calling it with the same parameters
will give the same results.
Good point, that it is in fact an excellent improvement. I will start
storing everything already computed on a dictionary.
Anyway I was able to easily solve the problem with the mapping by addin
On 2/3/10 3:00 PM, B.A.D.C.M.D Santos wrote:
> The main reason I was trying to move to the low level interface is
> speed. So what I am doing is calculating several times the p-value for
> the same python object.
?! phyper is deterministic, I think. Calling it with the same parameters
will give t
On 2/3/10 12:32 PM, B.A.D.C.M.D Santos wrote:
> Hello again,
>
> Today I was trying to port my phyper from the high-level interface to the
> low-level interface. My problem is again how I map the arguments with dot.
> According to the documentation I should be able to use the special **Kwargs
> aga
On 2/2/10 12:40 PM, B.A.D.C.M.D Santos wrote:
> Hello everyone,
>
> I am currently using rpy2 in order to use phyper function from R into my
> Python script. Nevertheless I have a problem because I want to use the
> argument log.p=TRUE. The last time I checked there was a problem with the
> mapping
Thank you Laurent. I had completely forget that solution. It seems to be
working know, although I am getting some weird values. But I think the
problem is on my script.
Thank you very much,
Bruno
2010/2/2 Laurent Gautier
On 2/2/10 12:40 PM, B.A.D.C.M.D Santos wrote:
Hello everyone,
I am cur
