I know people are working hard on reconciling changes w.r.t. Rmath split off as a package and the Distributions package, and converting DataFrames to use CategoricalArrays and NullableArrays. I don't want to cause anyone even more work to respond to repeated questions but it would be handy to have an ETA on when DataFrames and Distributions will be able to pass Pkg.test on version 0.5 and/or v0.4.Also are there things other can do to help - reviewing and revising documentation, reviewing and revising tests, etc.?
--
You received this message because you are subscribed to the Google Groups "julia-stats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to julia-stats...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Distributions should work as of this morning. I think the only thing left for DataFrames is to tag a version for Distributions so we should be pretty close as that could be done now.
julia> versioninfo()Julia Version 0.5.0-dev+5484Commit eec64e1* (2016-07-18 14:47 UTC)Platform Info: System: Linux (x86_64-linux-gnu) CPU: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz WORD_SIZE: 64 BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Sandybridge) LAPACK: libopenblas64_ LIBM: libopenlibm LLVM: libLLVM-3.7.1 (ORCJIT, ivybridge)
julia> Pkg.status("Distributions") - Distributions 0.9.0
julia> Pkg.status("Rmath")
julia> Pkg.status("StatsFuns") - StatsFuns 0.2.2
But note that everything is broken on Windows until Rmath.jl works on Windows. Rmath was removed from Base last week without Rmath.jl being ready on Windows…
You mean it should work on Win? How so? Distributions depends on StatsFun, StatsFun depends on Rmath and Rmath doesn’t work on Windows. So nothing precompiles and nothing can be used on Windows, right?
You mean it should work on Win? How so? Distributions depends on StatsFun, StatsFun depends on Rmath and Rmath doesn’t work on Windows. So nothing precompiles and nothing can be used on Windows, right?
From worker 2: testing Weibull(20.0, 1.0) From worker 2: testing Weibull(1.0, 2.0) From worker 2: testing Weibull(5.0, 2.0) From worker 2:ERROR: LoadError: On worker 3:LoadError: assertion failed: |cov(Xs,2) - cov(g)| <= 0.01 cov(Xs,2) = [1.55864 0.529817; 0.529817 4.52288] cov(g) = [1.5605 0.53; 0.53 4.508] difference = 0.014877712873417437 > 0.01 in test_approx_eq at ./test.jl:843 in test_mixture at /home/bates/.julia/v0.5/Distributions/test/mixture.jl:121 in include_string at ./loading.jl:380 in include_from_node1 at ./loading.jl:429 in #5 at /home/bates/.julia/v0.5/Distributions/test/runtests.jl:44 in #501 at ./multi.jl:1193 in run_work_thunk at ./multi.jl:844 in macro expansion at ./multi.jl:1193 [inlined]
Yep, Tony saved the world (for Windows users, at least)! Thanks, David
--
bates@thin206:~/.julia/v0.5/DataFrames⟫ git rebase masterFirst, rewinding head to replay your work on top of it...Applying: Refactor ModelMatrix - still pending contrast changesUsing index info to reconstruct a base tree...M src/statsmodels/formula.jlFalling back to patching base and 3-way merge...Auto-merging src/statsmodels/formula.jlCONFLICT (content): Merge conflict in src/statsmodels/formula.jlerror: Failed to merge in the changes.Patch failed at 0001 Refactor ModelMatrix - still pending contrast changesThe copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git rebase --continue".If you prefer to skip this patch, run "git rebase --skip" instead.To check out the original branch and stop rebasing, run "git rebase --abort".
--
It seems to me that contrasts should be defined in defined in the array packages and not in DataFrames. We'd probably need the functions to be defined in an upstream package like StatsBase or (ArrayBase/DataBase?) such that all array packages can extend them.
We have the usual problem of optional dependencies. Should DataFrames depend on any data array package or all of them? Is it possible the DataFrames doesn't use any features of concrete data array types and only define methods for abstract types? Then the user would have to load a specific array package. This might be a bit demanding to keep working and from a user perspective, a single good implementation might be better.What are the specific issues you are having right now? Are the things that are broken things that used to work or is work in progress towards using Nullable and Categorical arrays?