similar to: maximum allowed matrix size of R

Displaying 20 results from an estimated 10000 matches similar to: "maximum allowed matrix size of R"

2014 Oct 09
0
Write R code to feed the world!
We are hiring an R programmer to make biologists better at crop improvement: http://jobs.monsanto.com/missouri/research-and-development/jobid6130734-r-programmer-jobs Please apply if you are passionate about building R culture and infrastructure. . . .. . ... . ... . .. . . ... . ... . . . .. .. .... .. . ... . Barrett Foat, PhD Genome Data Analytics Team Lead
2010 Jun 11
0
How to code mixed model with nested factors in lmer
Hi, I have coding question on mixed model in R. I am using R2.11.0 in windows. I have an experiment with 2 fixed effect factors - A and B. The levels of B are within the levels of A factor. The model is very similar to a split plot design except the nesting relationship between the 2 fixed effect factors. For example: there are 2 levels for A - GM and ZM. There are 7 levels of B in total
2012 Aug 07
0
Bayesian estimates for the 1st-order Spatial Autoregressive model
Greetings: I am a relatively new user to R. I was wondering if anyone is familiar with MATLAB's far_g() function. If yes, is there an R equivalent to this? I would like to have the ability to input as my observation vector continuous values. I noticed that there was something close in R, sar_probit_mcmc(), but I can only use a binary vector as my observation vector. If my
2017 Jul 21
0
dynamically create columns using a function
Hi, I don't know about the lazyeval package or what you are trying to do but to answer the main question "How to create columns dynamically using a function?" I would do something like that: # dataset dem <- structure(list(id = c("L1", "L2", "L3", "M1", "M2", "M3"), TEST_SET_NAME = c("A", "A",
2017 Jul 20
2
dynamically create columns using a function
Hi, I am writing a function to dynamically create column names and fill those columns with some basic calculations. My function "demo_fn" takes argument "blup_datacut" and I like to use the contents of those arguments to dynamically create new columns in my dataset. Please note that I have another function called "calc_gg" within the function "demo_fn".
2017 Dec 14
1
help with recursive function
Your code contains the lines stopifnot(!(any(data1$norm_sd >= 1))) if (!(any(data1$norm_sd >= 1))) { df1 <- dat1 return(df1) } stop() "throws an error", causing the current function and all functions in the call stack to abort and return nothing. It does not mean to stop now and return a result. Does the function give
2017 Dec 14
0
help with recursive function
Eric: I will try and see if I can figure out the issue by debugging as you suggested. I don?t know why my code after stopifnot is not getting executed where I like the code to run the funlp2 function when the if statement is TRUE but when it is false, I like it to keep running until the stopifnot condition is met. When the stopifnot condition is met, I like to get the output from if statement
2017 Dec 14
0
help with recursive function
Eric: Thanks for taking time to look into my problem. Despite of making the change you suggested, I am still getting the same error. I am wondering if the logic I am using in the stopifnot and if functions is a problem. I like the recursive function to stop whenever the norm_sd column has zero values that are above or equal to 1. Below is the calclp function after the changes you suggested.
2017 Dec 14
0
help with recursive function
The message is coming from your stopifnot() condition being met. On Thu, Dec 14, 2017 at 5:31 PM, DIGHE, NILESH [AG/2362] < nilesh.dighe at monsanto.com> wrote: > Hi, I accidently left out few lines of code from the calclp function. > Updated function is pasted below. > > I am still getting the same error ?Error: !(any(data1$norm_sd >= 1)) is > not TRUE? > > >
2017 Dec 14
2
help with recursive function
Hi, I accidently left out few lines of code from the calclp function. Updated function is pasted below. I am still getting the same error ?Error: !(any(data1$norm_sd >= 1)) is not TRUE? I would appreciate any help. Nilesh dput(calclp) function (dataset) { dat1 <- funlp1(dataset) recursive_funlp <- function(dataset = dat1, func = funlp2) { dat2 <- dataset %>%
2017 Dec 14
3
help with recursive function
If you are trying to understand why the "stopifnot" condition is met you can replace it by something like: if ( any(dat2$norm_sd >= 1) ) browser() This will put you in a debugging session where you can examine your variables, e.g. > dat$norm_sd HTH, Eric On Thu, Dec 14, 2017 at 5:33 PM, Eric Berger <ericjberger at gmail.com> wrote: > The message is coming from
2012 Feb 14
1
help with matrix column cleaning
Dear R Group I have a matrix object in R, where i want to retain only those columns which have each row from a different group.. see the example below.. team1<-c("a1","a2","b1","b2","b3","c1","c2") teams<-combn(team1, 3) I want a function which will delete all columns in the teams matrix that have more than 1 row
2008 Jun 05
1
Matrix of data frames
Dear R-Users, Is there a way to create a matrix of data frames in R ? I am pulling in data frames from a SQL database into R using RODBC. I would like to pull in a sequence of data frames which are indexed across two dimensions, and store each data frame as an element in a matrix. I did try this: names<-c("foo","bar") years<-c("1y","2y")
2019 Apr 05
0
[PATCH RFC 3/4] vsock/virtio: change the maximum packet size allowed
On Thu, Apr 04, 2019 at 12:58:37PM +0200, Stefano Garzarella wrote: > Since now we are able to split packets, we can avoid limiting > their sizes to VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE. > Instead, we can use VIRTIO_VSOCK_MAX_PKT_BUF_SIZE as the max > packet size. > > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- >
2019 Apr 08
0
[PATCH RFC 3/4] vsock/virtio: change the maximum packet size allowed
On Mon, Apr 08, 2019 at 04:55:31PM +0200, Stefano Garzarella wrote: > > Anyway, any change to this behavior requires compatibility so new guest > > drivers work with old vhost_vsock.ko. Therefore we should probably just > > leave the limit for now. > > I understood your point of view and I completely agree with you. > But, until we don't have a way to expose
2019 Apr 08
0
[PATCH RFC 3/4] vsock/virtio: change the maximum packet size allowed
On Mon, Apr 08, 2019 at 05:17:35PM +0200, Stefano Garzarella wrote: > On Mon, Apr 08, 2019 at 10:57:44AM -0400, Michael S. Tsirkin wrote: > > On Mon, Apr 08, 2019 at 04:55:31PM +0200, Stefano Garzarella wrote: > > > > Anyway, any change to this behavior requires compatibility so new guest > > > > drivers work with old vhost_vsock.ko. Therefore we should probably
2019 Jul 17
0
[PATCH v4 5/5] vsock/virtio: change the maximum packet size allowed
Since now we are able to split packets, we can avoid limiting their sizes to VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE. Instead, we can use VIRTIO_VSOCK_MAX_PKT_BUF_SIZE as the max packet size. Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- net/vmw_vsock/virtio_transport_common.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git
2019 Jul 18
0
[PATCH v4 5/5] vsock/virtio: change the maximum packet size allowed
On Wed, Jul 17, 2019 at 5:00 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > On Wed, Jul 17, 2019 at 01:30:30PM +0200, Stefano Garzarella wrote: > > Since now we are able to split packets, we can avoid limiting > > their sizes to VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE. > > Instead, we can use VIRTIO_VSOCK_MAX_PKT_BUF_SIZE as the max > > packet size. > >
2008 Jun 28
1
Converting the results of granger.test into a matrix
Dear R Users, The granger.test command in the MSBVAR package estimates all possible bivariate Granger causality tests for m variables. If one passes a data frame with 3 rows, it returns 6 granger tests in two rows, one for the F-statistic and another for the p-value. For example: > a<-rnorm(1:10) > b<-c(lag(a),rnorm(1)) > c<-c(lag(b),rnorm(1)) >
2019 Apr 08
1
[PATCH RFC 3/4] vsock/virtio: change the maximum packet size allowed
On Mon, Apr 08, 2019 at 10:57:44AM -0400, Michael S. Tsirkin wrote: > On Mon, Apr 08, 2019 at 04:55:31PM +0200, Stefano Garzarella wrote: > > > Anyway, any change to this behavior requires compatibility so new guest > > > drivers work with old vhost_vsock.ko. Therefore we should probably just > > > leave the limit for now. > > > > I understood your point