search for: colorging

Good day, Sometimes, sparse.model.matrix outputs a dgCMatrix which has column names consisting of factor levels that were not in the original dataset. The first factor appears to be correctly transformed, but the following factors don't. For example: diamonds <- as.data.frame(ggplot2::diamonds) > colnames(sparse.model.matrix(~ . -1, diamonds)) [1] "carat"

...he source tree? Will it be replaced with something similar, e.g. with another kind of spiller and register tracking mechamism? Please keep in mind that some other allocators being currently developed use VirtRegMap with all its pros and cons. These allocators include an iterated coalescing graph colorging register allocator (Lang), a chordal graph register allocator (Fernando), a puzzle solving register allocator (Fernando), a PQBP register allocaor (Lang) and an extended linear scan register allocator (Roman). May be there are some other allocators as well. And BTW, some other parts of the LLVM A...

color and clarity are ordered factors, so sparse.model.matrix is generating orthogonal-polynomial contrasts (see ?contr.poly). This is by design ... what are you trying to do? Are you interested in fac2sparse? On 18-02-07 11:00 PM, Dario Strbenac wrote: > Good day, > > Sometimes, sparse.model.matrix outputs a dgCMatrix which has column names consisting of factor levels that were not