Skip to content

R editor vs. Tinn-R

11 messages · Farrel Buchinsky, Martin Becker, BBands +4 more

#
Have you used Tinn-R and what landmines await the inexperienced?

I could not understand why a script that used to work stopped working.
Look at these two scenarios
I opened an excel spreadsheet and copied several cells to the clipboard
Then Scenario 1
Executed from Tinn-R
'data.frame':   0 obs. of  1 variable:
 $ prelim..read.delim.clipboard.: logi

Scenario 2
Executed from R editor
'data.frame':   18 obs. of  13 variables:
#
Farrel Buchinsky wrote:
Depending on which button you press in Tinn-R, the clipboard is used to 
transfer the commands to R, so sometimes you can't rely on the previous 
contents of the clipboard while using Tinn-R. If you use the 
"(source)"-versions of the buttons, the content of the clipboard should 
be preserved.

Regards,
  Martin
#
The only button I pressed was the "send line" button in version 1.19.1.5. I 
changed my command to

prelim<-read.delim(source("clipboard"))

and still got the same problem.
I do not know how to use the source versions of the buttons. Can you please 
tell me more?

Thanks

Farrel


"Martin Becker" <martin.becker at mx.uni-saarland.de> wrote in message 
news:45A79DE5.9060803 at mx.uni-saarland.de...
#
Zitat von Farrel Buchinsky <fjbuch at gmail.com>:
The problem is not using the wrong R-command, but using a (Tinn-R)  
button that leads to a replacement of the current (windows) clipboard...
There are three button groups on the left of the "Send line" button,  
containing two buttons each. The left button of each of these three  
button groups has the same name as the right button of each group,  
apart from having a "(source)" suffix. Now it should be obvious what  
was meant with '"(source)"-version of buttons'. There is no such  
version for the "Send line" button, so you have to select the  
corresponding line and use the "Send selection (source)" button, e.g.
Regards,
   Martin
#
On 1/12/07, Martin Becker <martin.becker at mx.uni-saarland.de> wrote:
Something odd is going on. I can confirm that read.delim("clipboard")
works from R, but not from Tinn-R. What seems odd is that the contents
of the clipboard _are_ preserved after the Tinn-R send, so that a
subsequent paste or read.delim("clipboard") from R works correctly.
Perhaps Tinn-R restores the contents of the clipboard after sending to
R such that the R command runs before the restore takes place?

     jab
#
Instead of discussing this odd behaviour of TINN-R, I would prefer a discussion on importing data through the clipboard. In my opinion it isn't a good a idea to import data with the clipboard. I know that it's a quick and dirty way to get your data fast into R. 
But I see two major drawbacks. First of all you have no chance of checking what data you imported. This is important when you need to check your results a few days (weeks, months or even years) later. A second drawback is that you won't feel the need to store your data in an orderly fashion. Which often leads to a huge pile of junk, instead of a valuable dataset...

Cheers,

Thierry

-----Oorspronkelijk bericht-----
Van: r-help-bounces op stat.math.ethz.ch namens BBands
Verzonden: vr 12-1-2007 19:47
Aan: R-Help
Onderwerp: Re: [R] R editor vs. Tinn-R
On 1/12/07, Martin Becker <martin.becker op mx.uni-saarland.de> wrote:
Something odd is going on. I can confirm that read.delim("clipboard")
works from R, but not from Tinn-R. What seems odd is that the contents
of the clipboard _are_ preserved after the Tinn-R send, so that a
subsequent paste or read.delim("clipboard") from R works correctly.
Perhaps Tinn-R restores the contents of the clipboard after sending to
R such that the R command runs before the restore takes place?

     jab
#
Thierry:

Instead of discussing this odd behaviour of TINN-R, I would prefer a
discussion on importing data through the clipboard. In my opinion it isn't a
good a idea to import data with the clipboard. I know that it's a quick and
dirty way to get your data fast into R. 
But I see two major drawbacks. First of all you have no chance of checking
what data you imported. This is important when you need to check your
results a few days (weeks, months or even years) later. A second drawback is
that you won't feel the need to store your data in an orderly fashion. Which
often leads to a huge pile of junk, instead of a valuable dataset...
-------------

I do not understand this. I do this all the time, easily check the data in R
(which has all sorts of powerful capabilities to do this), and easily store
the data as part of the .Rdata file that also contains functions,
transformations, analyses, etc. that I have used on the data. I do not know
what is more orderly and useful than that! So would you care to
elaborate?....

Bert Gunter
Genentech Nonclinical Statistics
South San Francisco, CA 94404
#
Zitat von BBands <bbands at gmail.com>:
Sorry, my mistake: Apparently only "Send file (source)" preserves the  
clipboard while passing the source-command to R.
Regards,
   Martin
#
Why do people post so much details about their *guesses* on R-help 
rather than looking into the sources or quickly asking the corresponding 
developers?

Anyway, before people start to mention and guess about RWinEdt:
RWinEdt uses the clipboard to transfer code from WinEdt to R, hence any 
Excel data copied to the clipboard will be lost after some code has been 
sent to R.

Uwe Ligges
Farrel Buchinsky wrote:
2 days later
#
Hi
On 12 Jan 2007 at 19:11, Martin Becker wrote:
Date sent:      	Fri, 12 Jan 2007 19:11:42 +0100
From:           	Martin Becker <martin.becker at mx.uni-saarland.de>
To:             	Farrel Buchinsky <fjbuch at gmail.com>
Copies to:      	r-help at stat.math.ethz.ch
Subject:        	Re: [R] R editor vs. Tinn-R
I also do not know about "source" buttons. I have only send buttons. 
Maybe different Tinn-R version.

I usually issue such command from Tinn-R and then by up arrow I 
execute it again with correct content of clipboard e.g. copy from 
Excel like program.

HTH
Petr
Petr Pikal
petr.pikal at precheza.cz