Bogumił Kamiński
Bogumił Kamiński
I agree it does not work this way now. That is why I propose to change it (indeed - docstrings should be updated then; I can fix it if you...
This is not a bug but performance issue, but a `bug` label was automatically added.
In general using `gdistances` is also not optimal I think. igraph is much faster on this graph in calculation of `diameter`. I think that in general either e.g. Floyd-Warshall or...
igraph does BFS. F-W allocates but if graph is dense this should not be a problem as then |V| cannot be large anyway.
This will be conveniently done when we add metadata to DataAPI.jl (and DataFrames.jl)
I think row numbers as headers unless they are turned off - then no header. I guess for column names and eltype (unless it is turned off) we can use...
Yes - this is a good consideration. I think you should be added to JuliaData group (you definitely meet all conditions for inclusion). Then you would be allowed to do...
> However, right now, the only active developer is me, so it is not possible to change. Exactly this is what I understand (and thank you for working on this).
I like it very much. The only question is if it would be hard/needed to make it more general and allow not only pairwise but arbitrary dimensional cross-product (not sure...
Maybe for the time being we might require `FreqTables.pairwise` and `Distances.pairwise` to be written if both packages are loaded (which is somewhat likely but not super likely)? Essentially - making...