search for: unambiguous

...the values contained in the variable: April$Order.Made.Date) I tried altering the date format but continued to receive the same error. > F.length <- difftime ("11/04/2008", April$Order.Made.Date) > Error in fromchar(as.character(x)) : character string is not in a standard unambiguous format > Order.date <- as.Date (April$Order.Made.Date) > Error in fromchar(x) : character string is not in a standard unambiguous format > Order.date <- 'as.POSIXlt' (April$Order.Made.Date) Error in fromchar(as.character(x)) : character string is not in a standard...

...when I try to install R 3.3.3 during the "make check" step. Every time a call to as.POSIXct is done in test scripts, I got the same error message: e.g. x <- as.POSIXct("2002-02-02 02:02") Error in as.POSIXlt.character(x, tz, ...) : character string is not in a standard unambiguous format It looks to be linked to localtime but when I compiled R 3.3.2 6 months ago, the same test scripts were there and succeeded. Is there an environmental variable to use to change the as.POSIXct behavior? Regards -- S?bastien

This patch changes the date format for Time, Date and DateTime #to_json from the ambiguous 10/01/2007 ...to the unambiguous 2007/10/01 http://dev.rubyonrails.org/ticket/9750 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsu...

...i, there seems to be a bug in julian(): > Sys.getlocale() [1] "LC_COLLATE=English_United States.1252;LC_CTYPE=English_United States.1252;LC_MONETARY=C;LC_NUMERIC=C;LC_TIME=English_United States.1252" > julian(Sys.time()) Error in fromchar(x) : character string is not in a standard unambiguous format > julian function (x, ...) UseMethod("julian") > julian.POSIXt function (x, origin = as.POSIXct("1970-01-01", tz = "GMT"), ...) { if (length(origin) != 1) stop("`origin' must be of length one") res <- difftime(as.POSIXct...

Hi folks, I have been tormented for some time by Excel's habit of exporting dates to CSV files as mm/dd/yyyy format even if the dates are formatted dd/mm/yyyy in the display. What's worse, if there are dates that are of ambiguous (6/6/2011) and unambiguous (16/6/2011) format in the same column, Excel reformats the unambiguous dates and leaves the ambiguous ones as they were! Yesterday I discovered that if the dates are in international format (2011-6-6) Excel seems to export them as dd/mm/yyyy, and all correctly. As I suspect that there are a lot...

R 3.1.0 OS X Colleagues, I recently updated to 3.1.0 and I have encountered Warning messages: ... Name partially matched in data frame when I do something like: DATAFRAME$colname where colname is actually something longer than that (but unambiguous). I have much appreciated the partial matching capabilities because it fits with my workflow. I often receive updated data months after the initial code is written. In order to keep track of what I did in the past, I provide lengthy (unambiguous) names for columns, then abbreviate the names as...

...e "make check" step. >> >> Every time a call to as.POSIXct is done in test scripts, I got the same error message: >> e.g. x <- as.POSIXct("2002-02-02 02:02") >> Error in as.POSIXlt.character(x, tz, ...) : >> character string is not in a standard unambiguous format >> >> >> It looks to be linked to localtime but when I compiled R 3.3.2 6 months ago, the same test scripts were there and succeeded. >> >> >> Is there an environmental variable to use to change the as.POSIXct behavior? >> >> Regards >>...

...then I'm not sure why you need the branch to actually live in the monorepo > instead of in any fork (github.com/apple/llvm-project or another)? It > seems publicly accessible the same way? > As I understand it, a key need is to explicitly contribute this to the LLVM project to make it unambiguous that it has been contributed and is completely available for folks not at Apple to iterate on the code and turn it into code-reviewable chunks. So whatever happens needs to be quite explicit in its nature as a contribution. IMO, a branch of the repository definitely qualifies. IMO, a pull request...

Passing in two dates to a sql statement (sqldf). Is returning a factor. Tried setting back to a Date via as.Date, but get an error the error: character string is not in a standard unambiguous format. Any thoughts appreciated. Code/Results listed below: > summary(df.possible.combos) Date Hour Min. :2011-03-01 Min. : 0.00 1st Qu.:2011-03-23 1st Qu.: 5.75 Median :2011-04-14 Median :11.50 Mean :2011-04-14 Mean :11.50 3rd Qu.:201...

...the list I still don't have something that works. 1. as.Date returns the error below. What am I doing wrong? As far as I can see the character strings are in standard format. d$Date <- as.Date(d$Date, format="%d-%b-%y") Error in fromchar(x) : character string is not in a standard unambiguous format 2. as.date {Survival} produces this error, d$Date <- as.date(d$Date, order = "dmy") Error in as.date(d$Date, order = "dmy") : Cannot coerce to date format 3. Assuming all else fails, is there a text function similar to SCAN in SAS? Given a string like "9-Jan-01&...

hey I am trying to turn a dataframe into xts with the function: as.xts, but it returns the error: Error in as.POSIXlt.character(x, tz, ...) : character string is not in a standard unambiguous format could someone give me some pointers please the data is coming from a spreadsheet via the excel, and has 5 columns of data (date (with the date and time), open, high, low, close) (excel format) ela

Dear All, I installed R 2.7.0 and tried to call a dataset i had ealier own called on R2.6.2 but i keep on getting an error: use("maltreat.dta") Error in fromchar(x) : character string is not in a standard unambiguous format Tried doing the same with R2.7.1 but i get the same error. However if i call the same on R 2.6.2, there is no error: use("maltreat.dta") > des() No. of observations = 670 Variable Class Description 1 scrno integer 2...

...2001") >> Prints "13-01-20" ??? >> >> as.Date("1/13/2001") >> Prints error: not in standard unambigous format >> It seems that as if both "1/1/2001" and "13/1/2001" were considered by R >> to b >> e in a standard unambiguous format (or otherwise an error be reported?) >> and yet they >> >> >> are parsed incorrectly according to what one could think is obvious. It >> is a >> lso surprizing that not only "13/1/2001" but also "1/2/2001" and >> "2/1/2001&q...

...es not work. Is this problem only in my computer? The previous version of get.hist.quote (tseries 0.7-0) did work. Sys.time and julian produce > Sys.time() [1] "2001-10-04 15:33:14 GTB Daylight Time" > julian(Sys.time()) Error in fromchar(x) : character string is not in a standard unambiguous format > get.hist.quote produces x <- get.hist.quote(instrument = "^spc", start = "1998-01-01", + quote = "Close") trying URL `http://chart.yahoo.com/table.csv?s=^spc&a=01&b=01&c=1998&d=10&e=03&f=2001&g=d&q...

Dear all, I import my data from a csv-file containing one row with date-entries. How can I tell R to treat this data as dates? I've tried to bring it in character-format (as.charachter()) followed by as.POSIXlt() but I get an error message, that the character string is not in a standard unambiguous format, although the date is of format yyyy-mm-dd (what is standard format according to R reference manual). Another thing I tried was to work with as.date() from package date. The format of the "source"-data is month, day, year (the standard format for the as.date() function and the err...

...input via the as.Date function: > as.Date(date1) However, as.Date encounters an error when the string does not represent an actual date. eg: > date1 <- "2009-02-29" # Note: 2009 not a leap year > as.Date(date1) Error in fromchar(x) : character string is not in a standard unambiguous format As I have many instances of date entries like this, date1, date2, date3, etc. , I'd like the script to error out gracefully and to be able to point the user to which date they need to correct, rather than "Error in fromchar(x)...", which doesn't make it obvious what they n...

Hey there all, Is there some way to tell rails or sql server to ignore the time in a datetime field when doing a comparison? For example, if I do something like select * from users where registration_date = ?, @date where @date might equal some user input like ''03/14/2006'' The result is nothing returned, because in my tables the datetime field looks like this: 3/14/2006

Hi all, It has been the case for quite a while that the master tree is unambiguously better than 6.03. I have thus tagged and pushed out a syslinux-6.04-pre2 release, however, due to the issues with continuing to keep the main archive on kernel.org, I have moved the release archive to: https://www.zytor.com/pub/syslinux/ Other than the URL, there is no difference from the kerne...

...CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > Hi all, > > > > It has been the case for quite a while that the master tree is > > unambiguously better than 6.03. I have thus tagged and pushed out a > > syslinux-6.04-pre2 release, however, due to the issues with continuing > > to keep the main archive on kernel.org, I have moved the release archive to: > > Please add a non ancient gnu-efi snapshot too. > > Jocke...

...matter, and could continue looking exactly like they do today.) FWIW, the conventions I've seen have been inconsistent. One possible consideration: the "-dev" suffix is sometimes used to indicate a dirty workspace, but git describe puts the --dirty suffix after the hash. (So it's unambiguous, in any case.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181213/790fc7dc/attachment.html>