similar to: Is this a many to many relationship??

I am making my first attempts at using some Fortran code with R, and so far it's going OK. To print from my Fortran programs, it seems I need subroutines dblepr, realpr and intpr. From the excellent "Writing R Extensions" document: "Three subroutines are provided to ease the output of information from FORTRAN code. subroutine dblepr(label, nchar, data, ndata)

I am seeing a problem with text_field_with_auto_complete in which the input does not get populated with the selected value, but only in firefox (1.5.0.4). Works in IE just fine. I have a super-simple mockup that shows this problem below. Can anyone please confirm for me that this does/does not work in firefox or point out my mistake? I''m wondering if I need to submit a bug? The example

Is there a straightforward way to convert character information from decimal representation to the octal one used by R? I'd like something like a function ascii(number,base=10), such that > ascii(91) [1] "\133" I can easily do the mapping from 91 to 133, but what is a good way to operate on 133 to deliver "\133"? Would a lookup table be a better solution? David

I just have a few questions about join tables. From my understanding the following applies (correct me if I''m wrong): 1.Join tables are always named with the names of the two associated tables, in alphabetical order, separated by an underscore. 2.The foreign key fields are named with the name of the table they are referencing, with _id appended. 3.The foreign key is referencing a

This is some kind of follow-up to my previous posts. I have further improved the speed of my program 6 times by eliminating all the apply(). It turns out that apply is slow, is slower than direct loop, it is an order slower than a matrix operation alternative. Here is one example. The first apply version runs 19 seconds, the second loop version runs 13 seconds, the third matrix version runs 1

Hi all, Installing 5.5 on a fresh system having an Intel RAID. My 2 drives are configured as a mirror within the Intel BIOS. When starting my install, Anaconda throws an exception. After a brief goog, I see one possible fix is - at the install prompt, type; linux text nodmraid This is fine and all but Centos sees 2 disks at this point rather then 1 which is what I thought the Intel RAID

Q: Is there an easy way to plot log histograms? The command "hist" draws a standard histogram with observed frequency on the y-axis. I would like to be able to draw the log frequency on the y-axis, but I can't see whether I can use "hist" for this. The purpose of such a plot is to see whether data are normal or Laplace or something else. - and the same question for

Is there some neat way of storing the printed representation of an object as a character string? I can see how it could be done via disk using sink() and then scan(), but that's ugly. Something like Lisp-Stat's "with-output-to-string" macro perhaps? David Firth Phone +44 1865 278544 Nuffield College Fax +44 1865 278621 Oxford OX1

I am aware of the nice R package "logspline", which does smooth density estimation from interval-censored data (that is, values that are known to lie in a specified interval rather than known exactly). Function logspline.fit uses a maximum penalized likelihood method, with the penalty related to the number of knots used in a cubic regression-spline fit. I need to be able to do some

Hi David, I hope all is well w/ you. Co-operation beetwen R and Ox would be most welcome. A possible problem lies in the fact that, although free for academic use, Ox is not open source. I too have been using Ox for computer-intensive programming. I also code some of my programs in C, but I always try Ox first, and in most cases it is efficient enough. For details, see

I am having a little problem in relation to sending output to the R Console window, when a function is called by pushing a button in a Tk window. Actually there seem to be two components to the problem: -- the R prompt does not re-appear until <return> is pressed -- text output to the R Console window *disappears* after <return> is pressed The following, in R 1.1.1 under

I suppose this could be described as a feature (it seems to be similar in S-Plus), but it looks to me more like a bug. Why can't the assignment below to a row of "emptyframe" (or "anotherframe") be made? This with R --vanilla (version info below). Regards -- David David Firth Phone +44 1865 278544 Nuffield College Fax +44 1865