Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 1
    Hi. How woul you use it as an input for other packages such as zoo, designed to be used with all data simultenously? Commented Mar 27, 2013 at 1:15
  • @skan the end object is a data frame. So you have to convert it to a zoo object in order to use it with zoo. Look at the examples in the zoo docs for illustrations. Commented Apr 2, 2013 at 12:48
  • @JD Long. Hi, the problem is that when you convert it to a zoo object it tries to fit it on the memory. If it's too big it produces an error. And if the result of the zoo object (for example an aggregation of two series) is also too it would need to be a sql or ff object too. Commented Apr 3, 2013 at 14:03
  • I don't know what's wrong with sqldf. I've created a simple 1GB file on disk (with 2 numerical columns) and used DTSQL <- read.csv.sql("f2.txt",dbname=tempfile()) and it tries to load the whole data on memory. Tomorrow I'll try ff and revoscaler instead. Commented Apr 4, 2013 at 0:38
  • 1
    @what m is thousand so mm is thousand thousand, or million. I probably should have capitalized it as MM. But I find that just about any million abbreviation can be confusing to someone if you have a diverse enough audience. In my attempt to be overly verbose, I'm sorry that I made it more confusing! accountingcoach.com/blog/what-does-m-and-mm-stand-for Commented Jan 4, 2016 at 19:13