search for: f111

Displaying 4 results from an estimated 4 matches for "f111".

Did you mean: 111
2011 Jun 22
1
question about read.columns
HI, Dear R community, I have a large data set names dd.txt, the columns are: there are 2402 variables. a1, b1, ..z1, a11, b11, ...z11, a111, b111, ..z111.. IF I dont know the relative position of the columns, but I know I need the following variables: var<-c(a1, c1,a11,b11,f111) Can I use read.columns to read the data into R? I have tried the following codes, but it does not work hh<-read.columns("/house/homedirs/c/cdu/operon/gh/dd.dimer", required.col=NULL, text.to.search=var, sep="\t", skip=0, quote="", fill=T) dim(hh) 468, 2402 hh...
2000 Jan 04
0
Stepwise logistic discrimination - II
...F63 + F64 + F65 + F66 + F67 + F68 + F69 + F70 + F71 + F72 + F73 + F74 + F75 + F76 + F77 + F78 + F79 + F80 + F81 + F82 + F83 + F84 + F85 + F86 + F87 + F88 + F89 + F90 + F91 + F92 + F93 + F94 + F95 + F96 + F97 + F98 + F99 + F100 + F101 + F102 + F103 + F104 + F105 + F106 + F107 + F108 + F109 + F110 + F111 + F112 + F113 + F114 + F115 + F116 + F117 + F118 + F119 + F120 + F121 + F122 + F123 + F124 + F125 + F126 + F127 + F128 + F129 + F130 + F131 + F132 + F133 + F134 + F135 + F136 + F137 + F138 + F139 + F140 + F141 + F142 + F143 + F144 + F145 + F146 + F147 + F148 + F149 + F150 + , data = nose126s2) # we...
2024 Feb 27
0
How to avoid the Markdown code block bug on R Bugzilla
Hello, There's a rare but annoying bug in Bugzilla 5.1.2...5.3.2+ where a Markdown code block inside a comment may be replaced by U+F111 or U+F222, and then the following code blocks may end up being replaced by the preceding ones. For example, the problem can be seen in PR16158: https://bugs.r-project.org/show_bug.cgi?id=16158. Here's how to avoid it: 1. If no code blocks have been already swallowed by Bugzilla, use the comme...
2011 Oct 26
8
IronRuby's Marshal.dump doesn't work with CLR types, or ruby types backed by a CLR type
Backstory: I''m trying to use DRb for some in-house utility code. DRb itself seems to work fine, but I found that when I misspelled a method name, instead of reporting back a NoMethodError, the IronRuby process crashed immediately to the console. This is using a relatively recent build of IronRuby from Github Steps to repro: e = RuntimeError.new ''xyz'' dumped =