![]() If you love using my open-source work (e.g. Please read the contributing guide first! It will help save time for both of us. Or you can send an email to the R-SIG-Finance mailing list (you must subscribe to post). Open an issue on GitHub if you find a bug or want to request a feature. I look forward to your questions and feedback! If you have a question, please ask on Stack Overflow and use the and tags. This makes each call to the C code a few microseconds faster, which is nice. Updated C entry points so they’re not able to accidentally be found via dynamic lookup (i.e.Call("foo". Thanks to GitHub user for the suggestion! ( #307) Removed an unnecessary check in na.locf() (which is not user-facing). Thanks to GitHub user Eluvias for the suggestion! ( #299) Thanks Mark van der Loo!Īdded to the endpoints() documentation to make it clearer that the result is based on the UNIX epoch (midnight 1970, UTC) and not the first observation in the xts index. Migrated unit tests from RUnit (which is actively maintained, but no longer actively developed) to tinytest. Now it always copies those index attributes. Squashed a bug in reclass() that did not copy the tclass, tzone, or tformat from ‘match.to’ to the result object. It previously returned an xts object even if the first argument was a subclass of xts. Now it always returns an object with the same class as the first (left-hand side) argument. Smith for the report and testing! ( #222)įixed a long-standing issue with Ops.xts(). A join should include all the columns of the joined objects, regardless of the number of rows in the object. ![]() The result of merge.xts() did not include the columns of any objects that had one or more columns, but zero rows. ( #227, #379)Īlso made merge.xts() results consistent with merge.zoo() for zero-length xts objects that have columns. merge.zoo() would return a zero-width object with the correct index. Previously, merge.xts() returned an empty xts object if called on two or more zero-width xts objects. Made merge.xts() results consistent with merge.zoo() for zero-width objects. The original Description has:īut that’s not consistent with the code. Bug Fixesįixed a typo in the Description section of the documentation for period.apply() ( #205), and added detail to the argument definitions. And it adds a startup warning that dplyr::lag() breaks method dispatch, which means calls to lag(my_xts) won’t work any more, and suggests a couple ways to work around that breakage. This release also includes a new xts method for na.fill() that significantly increases performance when ‘fill’ is a scalar. It will look for a time-based column in the ame if it cannot create an index from the row names. There’s a nice improvement to as.xts() for ame and similar objects (e.g. # A zero-width xts object on / containing: # zero width - no data and has index values xts(matrix(empty, dimnames = list(NULL, "zero")), empty) # but has a column dimension and may have column names # zero length - no rows of data and a zero-length index, It differentiates between xts objects that are empty (no data and zero-length index), zero-width (no data and has index values), or zero-length (no data–but has a column dimension and may have column names–and zero-length index). Now str() outputs more descriptive information for xts objects. Times ‘max.rows’ (default 100), similar to data.table ( #321). Here’s an example: # an hourly sequence of times, and an xts object using them Thanks to Chris Katsulis for the suggestion! ( #243) So you can subset by time of day from the start/end of the day without providing the start/end times (i.e. The coolest new feature is the ability to use open-ended ranges for time-of-day subsetting. Some of the GitHub issues are open issues from when xts was still on R-Forge! The oldest issue fixed in this release was opened on, and another one was opened on ! Better late than never I guess. There are also changes to make xts more consistent with zoo, some minor speed improvements, and the usual smattering of bug fixes.įor some reason, I decided it was a good idea to go through the oldest GitHub issues and determine whether they should be fixed or closed without being fixed. This release adds several exciting changes: open-ended time-of-day subsetting, smarter conversions to xts from ames/data.tables/tibbles to.period() handles custom endpoint values, print() truncates rows like data.table, and str() provides more informative output. An updated version of xts is now on CRAN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |