strange :(. Unfortunately, adding the rescue statement didn't solve the problem for me.
I now send the code directly to the R.app (instead of 'run selection in R'). Hope that works.
I run Mac OS X 10.7.2.
P.S.: I execute the code four times (for four different data-sets). So I get four R instances calculating in parallel. Has it something to do with this?
I can send you the code of course. But I don't think it would help you, since it heavily relies on the data.sets. It is basically a support vector machine cross validation algorithm with three nested loops.
best, martin
On 03.02.2012, at 19:13, Hans-Jörg Bibiko wrote:
Hi,
yes, as Berend said, this issue is a bit weird to me.
Would it be possible to post a piece of R code which causes this? I tried to reproduce it but up to now without success.
Berend just wrapped the line in question by an exception catcher which should solve that effect but not the actual reason.
Thus for the time being you can change in tmR.rb in the following way:
from:
elsif io == stdout print hideStartMessageJS
to:
elsif io == stdout begin print hideStartMessageJS rescue end
[It seems to me that one should rewrite the code by using another scripting language - private opinion :) ]
I'm working now on a new version which will run with TM2.
Regards, --Hans
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate