Re: [Rd] Bug in R evaluating a huge instruction (PR#14096)

2009-12-01 Thread Jean Couteau 

Thanks for your time Duncan,

I join here the instruction that is not correct, hoping that might help 
you. The file is encoded in utf-8 so you should not have any problem 
reading it.


I doubt to that it is an R bug too, but with all my tests i am less and 
less sure of that.


Best regards,
Jean Couteau


Your message has encoding problems, so it's not readable.  Could you 
put the code online somewhere where we could download it in its 
original form?  I doubt if this is an R bug, but I can't point out the 
problem in your code (or confirm that it really is an R bug) without 
an undamaged copy of the code.


Duncan Murdoch





a<-morris(model=NULL,factors=c("PecheAmateurs 
décembre.proportionMetier","PechePetitMetierMer 
mai.proportionMetier","PecheAmateurs mai.proportionMetier","PecheChalutiere 
janvier.minInactivityDays","PechePetitMetierEtang 
octobre.minInactivityDays","PechePetitMetierEtang 
décembre.minInactivityDays","FiletMer.standardisationFactor","PecheAmateurs 
juin.minInactivityDays","PechePetitMetierEtang 
novembre.minInactivityDays","PechePetitMetierMer 
septembre.minInactivityDays","PechePetitMetierMer 
avril.minInactivityDays","PecheAmateurs 
août.proportionMetier","PecheChalutiere 
novembre.minInactivityDays","PechePetitMetierMer 
février.proportionMetier","PecheChalutiere 
juillet.minInactivityDays","PechePetitMetierMer octobre.proportionMetier","CSar 
Groupe 5.reproductionRate","PechePetitMetierMer 
août.proportionMetier","PechePetitMetierMer 
janvier.minInactivityDays","PechePetitMetierEtang 
mai.minInactivityDays","PecheAmateurs octobre.minInactivityDays","PecheAmateurs 
septembre.minInactivityDays","PecheChalutiere 
juin.minInactivityDays","PecheChalutiere 
avril.minInactivityDays","PecheAmateurs 
juillet.proportionMetier","PecheChalutiere 
mai.minInactivityDays","PechePetitMetierEtang 
septembre.minInactivityDays","PechePetitMetierMer 
janvier.proportionMetier","PecheAmateurs 
septembre.proportionMetier","PechePetitMetierEtang 
février.minInactivityDays","PechePetitMetierEtang 
mars.minInactivityDays","PechePetitMetierEtang 
juillet.minInactivityDays","PechePetitMetierMer 
septembre.proportionMetier","CSar.capturability","PechePetitMetierMer 
juin.proportionMetier","PecheChalutiere 
mars.minInactivityDays","PecheChalutiere 
septembre.minInactivityDays","PecheAmateurs 
janvier.minInactivityDays","PechePetitMetierMer 
août.minInactivityDays","PechePetitMetierMer 
juillet.proportionMetier","PecheChalutiere 
décembre.minInactivityDays","PecheAmateurs 
avril.minInactivityDays","PecheAmateurs 
mars.proportionMetier","PechePetitMetierMer 
novembre.minInactivityDays","PechePetitMetierEtang 
août.minInactivityDays","CSar.recruitmentDistribution","PecheChalutiere 
février.minInactivityDays","CSar.naturalDeathRate","PecheAmateurs 
octobre.proportionMetier","PechePetitMetierMer 
mai.minInactivityDays","PechePetitMetierMer 
mars.proportionMetier","PecheAmateurs 
août.minInactivityDays","FiletEtang.standardisationFactor","PecheChalutiere 
août.minInactivityDays","PecheAmateurs 
janvier.proportionMetier","PecheAmateurs 
décembre.minInactivityDays","PechePetitMetierEtang 
avril.minInactivityDays","PecheAmateurs 
mars.minInactivityDays","PechePetitMetierMer 
décembre.minInactivityDays","PecheAmateurs 
mai.minInactivityDays","PechePetitMetierEtang 
juin.minInactivityDays","Harpon.standardisationFactor","PecheAmateurs 
novembre.minInactivityDays","PecheAmateurs 
novembre.proportionMetier","PechePetitMetierMer 
mars.minInactivityDays","Ligneemb.standardisationFactor","PecheAmateurs 
juin.proportionMetier","PecheAmateurs 
avril.proportionMetier","PechePetitMetierMer 
juillet.minInactivityDays","PechePetitMetierMer 
avril.proportionMetier","PechePetitMetierMer 
octobre.minInactivityDays","PechePetitMetierMer 
février.minInactivityDays","PecheAmateurs 
juillet.minInactivityDays","PechePetitMetierMer 
décembre.proportionMetier","PecheAmateurs 
février.proportionMetier","PecheChalutiere octobre.minInactivit

Re: [Rd] Bug in R evaluating a huge instruction (PR#14096)

2009-12-02 Thread Jean Couteau 

Thank you very much for your input Duncan and Romain.

I will try to do what you are advising. The R instruction is generated 
from java using jri (and an abstraction layer we built upon it : 
nuiton-j2r), i will try add this limitation to nuiton-j2r so that it 
split the instruction if it is too long.


Best regards,
Jean

Duncan Murdoch wrote:

On 01/12/2009 12:50 AM, Jean Couteau wrote:

Thanks for your time Duncan,

I join here the instruction that is not correct, hoping that might 
help you. The file is encoded in utf-8 so you should not have any 
problem reading it.


I doubt to that it is an R bug too, but with all my tests i am less 
and less sure of that.


I have no problem sourcing that file, but I do get an error if I try 
to cut and paste it, because it's a single line of 4890 characters, 
and that's too long.  So this is an R limitation, but it's one with an 
easy workaround:  just add some line breaks into your source.


Duncan Murdoch




Best regards,
Jean Couteau
Your message has encoding problems, so it's not readable.  Could you 
put the code online somewhere where we could download it in its 
original form?  I doubt if this is an R bug, but I can't point out 
the problem in your code (or confirm that it really is an R bug) 
without an undamaged copy of the code.


Duncan Murdoch










__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Bug in R evaluating a huge instruction (PR#14096)

2009-12-03 Thread Jean Couteau 


FWIW the restriction is only on the console input - if you send it 
directly, there is no limit (I have never heard of nuiton-j2r but if 
you use rJava to interface from Java to R there is no limit - the 
string you parse+evaluate can be of any length).

Hi Simon,

nuiton-j2r is in fact an abstraction layer to rjava or rserve so that it 
can switch between one or other implementation using simple 
configuration (http://maven-site.nuiton.org/nuiton-j2r/ sorry but this 
is in french). And in fact I encounter the problem using it.


What is done is basically creating the R instruction from java and 
sending it to R using the eval method from the Rengine object (as we use 
jri in this specific application). The R instruction should create an 
object a of class morris, and I try then to get back the a$X object (the 
X item of the morris object) but I get back a null object without any 
reason, that is why I tried copying the instruction directly in R and 
thus getting this problem.


So that is strange if you say that there is no limit using rjava/jri.

Cheers,
Jean


Cheers,
Simon



Duncan Murdoch wrote:

On 01/12/2009 12:50 AM, Jean Couteau wrote:

Thanks for your time Duncan,

I join here the instruction that is not correct, hoping that might 
help you. The file is encoded in utf-8 so you should not have any 
problem reading it.


I doubt to that it is an R bug too, but with all my tests i am less 
and less sure of that.


I have no problem sourcing that file, but I do get an error if I try 
to cut and paste it, because it's a single line of 4890 characters, 
and that's too long.  So this is an R limitation, but it's one with 
an easy workaround:  just add some line breaks into your source.


Duncan Murdoch




Best regards,
Jean Couteau
Your message has encoding problems, so it's not readable.  Could 
you put the code online somewhere where we could download it in 
its original form?  I doubt if this is an R bug, but I can't point 
out the problem in your code (or confirm that it really is an R 
bug) without an undamaged copy of the code.


Duncan Murdoch










__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel







__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel