similar to: A wrapper of seq.Date() encounters an issue

Hi all, I can't get the functionality of the package parallel to work. Specifically, makeCluster() hangs when I run it. I first noticed the problem when trying to run Rstan with multiple cores and the traced it back to the core package parallel. The following results in R hanging after the call to makeCluster. library(parallel) # Calculate the number of cores no_cores <-

Reproducible example: x <- list(list(list(), list())) unlist(x) *> Error in as.character.factor(x) : malformed factor* What should happen: unlist(x) > NULL R.version platform x86_64-apple-darwin15.6.0 arch x86_64 os darwin15.6.0 system x86_64, darwin15.6.0 status major 3 minor 5.0 year 2018 month 04 day

Dear Henrik, thank you, for the quick reply. Bizarrely enough, the problem vanished when I woke the computer from sleep (I had previously replicated the problem after several restarts of both R and the MacOS). I will follow-up if I can again replicate the problem. Florian On 2/10/18 4:39 PM, Henrik Bengtsson wrote: > A few quick comments: > > * You mention R --vanilla, but make sure

SNP <- read.mapmaker(dir = "~/desktop", "1674_SNP.raw?) --please do not edit the information below-- R Version: platform = x86_64-apple-darwin15.6.0 arch = x86_64 os = darwin15.6.0 system = x86_64, darwin15.6.0 status = major = 3 minor = 4.1 year = 2017 month = 06 day = 30 svn rev = 72865 language = R version.string = R version 3.4.1 (2017-06-30) nickname = Single Candle GUI:

A few quick comments: * You mention R --vanilla, but make sure to try with parallel::makeCluster(), so that you don't happen to pick up snow::makeCluster() if 'snow' is attached and ahead of parallel on the search() path. * Try creating a single background worker, i.e. parallel::makeCluster(1L). * Try with cl <- future::makeClusterPSOCK(1L, verbose = TRUE), which gives the same

Hi, I have been having issues producing plots in JPEG format, using type = "cairo" to get better anti-aliasing. When trying to set the physical size with units = "cm" or units = "mm", the width is set correctly but the height is not - it looks like the height is simply treated as pixels regardless of the 'units' argument. Example: x = 1:10 y = 2 * x

There seems to be a bug in seq.Date such that it will not allow the user to pass in length.out =3D NULL, despite the fact that this is the = default argument. For example: > dt1 <- as.Date("2004-12-31") > dt2 <- as.Date("2005-12-31") > seq.Date(dt1, dt2, length.out =3D NULL, by =3D "month") Error in seq.Date(dt1, dt2, length.out =3D NULL, by =3D

On Thu, 24 May 2018 at 18:41 Mark R Payne <markpayneatwork at gmail.com> wrote: Hi, I seem to be having a problem adding the following two raster objects together - one is a rasterLayer, the other is a rasterBrick. The extent, resolution, and origin are the same, so according to my understand it should work. The objects look like so: > obs.clim class : RasterLayer dimensions : 60, 200,

Hi, I seem to be having a problem adding the following two raster objects together - one is a rasterLayer, the other is a rasterBrick. The extent, resolution, and origin are the same, so according to my understand it should work. The objects look like so: > obs.clim class : RasterLayer dimensions : 60, 200, 12000 (nrow, ncol, ncell) resolution : 0.5, 0.5 (x, y) extent : -70,

This is now fixed in development on RForge, you can try it out by installing from there, or from the Github mirror with devtools::install_github("rforge/raster/pkg/raster"). (To get fixes into raster email the maintainer directly - you might not get a response but it'll be addressed). Cheers, Mike. On Thu, 24 May 2018 at 20:08 Michael Sumner <mdsumner at gmail.com> wrote:

Hi, What is the reason for seq.Date to require the 'by' argument and not to default it to 1 in the example below? > seq(from=as.Date("1996-01-01"), to=as.Date("1996-12-01")) Error in seq.Date(from = as.Date("1996-01-01"), to = as.Date("1996-12-01")) : exactly two of `to', `by' and `length.out' / `along.with' must be specified

> seq(as.Date("2000-1-1"), as.Date("2001-1-1"), "months") [1] "2000-01-01" "2000-02-01" "2000-03-01" "2000-04-01" "2000-05-01" [6] "2000-06-01" "2000-07-01" "2000-08-01" "2000-09-01" "2000-10-01" [11] "2000-11-01" "2000-12-01"

Hi, I have the following type of data: myData <- data.frame(x = 1:5, y = letters[1:5], xDate = seq(as.Date("2001/2/1"), as.Date("2005/2/1"), by="year") ) > myData x y xDate 1 a 2001-02-01 2 b 2002-02-01 3 c 2003-02-01 4 d 2004-02-01 5 e 2005-02-01 What I need is a new column, say xDate2, that for each xDate (or for each unique combination of

R> seq(as.Date(Sys.Date()), by="-1 months", length=6) [1] "2012-01-31" "2011-12-31" "2011-12-01" "2011-10-31" "2011-10-01" "2011-08-31" R> Notice how October appears twice. Now, date arithmetic is gruesome but the documentation for seq.Date et al does not hint it wouldn't honour the by= argument. So a bug, or

Hi all, I'm getting an issue with Rdevel where make check-recommended hangs consistently for me on Mac El Capitan when checking the Matrix package. I did svn update and tools/rsync_recommended earlier today and it didn't fix the issue. Specifically, it is hanging on the * checking dependencies in R code ... stage (while checking Matrix, it passes fine for MASS and lattice). Currently

Pardon the barrage of time series related questions, but another issue I'm trying to solve is how to determine a sequence of dates a la seq.dates() except going BACKWARDS in time, e.g. if seq.dates() allowed for the "to" variables to be set alone, rather than the from=. Ultimately, I'd like to have a set of dates preceding a given date in predefined intervals (the same ones

> On Aug 14, 2017, at 11:10 AM, David Winsemius <dwinsemius at comcast.net> wrote: > > >> On Aug 14, 2017, at 8:37 AM, Szumiloski, John <John.Szumiloski at bms.com> wrote: >> >> Thanks for the feedback Jeff. Before I pursue a bug report, let me give a full example: >> >> ###### begin console output >> >> R version 3.4.1

Hello, I''m trying to cut down the errors if the guy already getting the empty nickname, so he doesn''t get anything about the nickname is short. validates_presence_of :nickname This below is not working ? validates_length_of :nickname, :within => 4..40, :if => Proc.new { |user| user.nickname.length > 1 } nor this one below? validates_length_of :nickname, :within

Hi guys, I''m having problems with my app. First of all, I created a date_select with the code: <%= date_select(''contact'', ''birthday'', :order => [''day'',''month'',''year'']) %> In the contacts table, I create a date field: birthday DATE When I save the values goes wrong into the database.

There seem to be a bug in the seq.dates function in the chron package for R 2.0. Please see below: when the specified frequency is "months", seq.dates does not return the end of the specified interval all the time: > seq.dates(from = "05/31/04", to = "12/31/04", by = "months") [1] 05/31/04 06/30/04 07/31/04 08/31/04 09/30/04 10/31/04 11/30/04 Ciprian