similar to: Subset by string name?

Sorry to bother everyone---I realized I should have used "==" instead of "=" in the subset syntax! Quoting Ophelia Wang <opheliawang at mail.utexas.edu>: > Hi all, > > I thought this should be very simple, but I'm not sure where the > problem is. I have a .txt data file that contains X and Y coordinates > of trees and their family names: > >

Hi, look this: > summary(fam??lia) Anacardiaceae Annonaceae Bombacaceae Cecropiaceae 2 4 1 3 Chrysobalanaceae Clusiaceae Euphorbiacaea Fabacea 1 1 4 3 Fabaceae Flacourtiaceae Humiriaceae indeterminada

[This email is either empty or too large to be displayed at this time]

Hi, How to unlist list column value and add column into data frame. Data frame ID ContractDe PassengersDe TrainnerDe 1 list(ConID=c("Zx","78yu"),ConRes = c("98","Tut")) list(PassID

Who prepares wrongly, when Dilbert consumes the root terminal inside the FBI? Go interface a connector! The UDPs, webmasters, and telephones are all disgusting and untamed. To be filthy or secure will save soft iterations to lazily fetch. Never close neatly while you're formating inside a robust procedure. Why will you transport the important huge texts before Greg does? Norm wants

On Wed, 28 May 2003, Josh Coalson wrote: > interesting idea, CD-TEXT is in the subcode and if cdrdao can > split it out that's better I think than hacking the CUESHEET > block to store CD-TEXT. I suppose the ideal would be to have a metadata block to store the subcode from a CD, and something that could interpret it as CD-TEXT, if that's what it is. Then it would be possible to

I''ve followed the instructions in tools/debugger/gdb/README for building and using gdbserver-xen. While playing around with debugging a running guest or dissecting a core file, I''ve discovered that using it with a 32-bit PV domU fails but it works fine on the same guest if it''s booted with a 64-bit kernel. Is this a known limitation, or am I doing something incorrectly?

Greg, I'm going to join issue with your here! Not that I'll go near advocating "Excel-style" graphics (abominable, and the Patrick Burns URL which you cite is remarkable in its restraint). Also, I'm aware that this is potential flame-war territory -- again, I want to avoid that too. However, this is the second time you have intervened on this theme (previously Mon 6

Dear R-help, I am having trouble with your scatterplot3d program. For help with this problem I was directed to your address by Martin Maechler at " r-core-bounces at r-project.org." I'm also sending a CC to " r-core-owner at r-project.org" as I'm not yet certain of the proper address to use for this. I have R version 2.8.1 and have downloaded 'scatterplot3d.'

Definitely 2 camps on this issue; so why not compromise with a drop-down menu for the most frequently used processes, the user responds with the necessary parameters for his choice, and R then writes the source statements on the terminal and executes them. The user follows the familiar gui procedure, is thereby automatically introduced to the command statements involved, and R's

Hi, I found dirname() behaves differently on R-devel on Windows. Since I'm not sure which behavior is right, let me ask here before filing this to R's Bigzilla. On R 4.2.2., we get > dirname("C:/") [1] "C:/" However, on R-devel (r83888), we get > dirname("C:/") [1] "." ?dirname says 'dirname returns the part of the

Thanks for the prompt response, I'll confirm it after the new R-devel binary is available. Also, thanks for the detailed explanation. I agree with you in general. > "/" in "C:/" is a path separator or not, and whether it is trailing or not It seems a Windows' path basically consists of two components; a drive specification (e.g., C:) and the directory structure

I confirmed the revert fixed my failing test. Thanks! 2023?2?23?(?) 20:12 Hiroaki Yutani <yutani.ini at gmail.com>: > Thanks for the prompt response, I'll confirm it after the new R-devel > binary is available. > Also, thanks for the detailed explanation. I agree with you in general. > > > "/" in "C:/" is a path separator or not, and whether it is

Writing R Extension[1] defines "API" as: Entry points which are documented in this manual and declared in an installed header file. These can be used in distributed packages and will only be changed after deprecation. But, the document (WRE) doesn't have even a single mention of ALTREP, the term "ALTREP" itself or any entry points related to ALTREP. Does this mean,

Thanks, Hernando, Sorry, "API" is a bit confusing term in this context, but what I want to discuss is the "API" that Writing R Extension defines as quoted in my previous email. It's probably different from an ordinary sense when we casually say "R C API". You might wonder why I care about such a difference. This is because calling a "non-API" is

Thanks for your convincing comment, but it seems the R core team has a different opinion... A few hours ago, src/include/R_ext/Altrep.h got this comment: /* Not part of the API, subject to change at any time. */ commit: https://github.com/r-devel/r-svn/commit/2059bffde642f8426d1f39ab5dd995d19a575d4d While I'm glad to see their attempt to make it clear, I'm confused. That