Carlos Parada

Unable to use Tuples to label a KeyedArray

2

Trying to construct an array where the labels are stored in a tuple throws an error: ``` MethodError: no method matching axes(::Tuple{Symbol, Symbol, Symbol}, ::Int64) Closest candidates are: axes(::Tuple) at...

Difficulty writing into array (unsure if intentional)

1

Trying to write into an array gives an error when one of the arrays has a trailing singleton dimension: ``` julia> table(:, :total) .= sum(pointwise([:loo_score, :naive_score, :overfit]); dims=1)' ERROR: DimensionMismatch("cannot...

`@batch` slower than `Threads.@threads`

13

Tried to see if replacing `Threads.@threads` with `@batch` would improve performance on smaller workloads for a function. This seems to introduce some kind of data race (which wasn't present with...

Request: Separate Out Resampling Strategies Interface

1

I'd like to use the interface for resampling strategies separately from MLJBase in ParetoSmooth.jl, but MLJBase is a pretty big dependency to add for such a small interface. Would it...

Feature Request: No Copy Array Passing Between Julia and R

2

It's possible to pass data between Python and R without copying it by using [Arrow](https://arrow.apache.org/blog/2020/05/03/introducing-arrow-c-data-interface/#application-passing-data-between-r-and-python), and it also seems to be possible to pass data between Julia and Python doing...

Passing a `:` argument from R to Julia

1

I'm having trouble passing the `:` operator from R to Julia -- just using `:` creates an error, while `as.name(:)` results in it being interpreted as `Symbol(:)`.

Probability interface tutorial

7

First addition to the DynamicPPL tutorials; breaking this up as Hong suggested. Goes over how to use the basic interfaces (e.g. logjoint, loglikelihood, logdensityof).

Unable to sample when conditioning on an array with `|`

6

Fails: ``` julia> @model function gdemo() μ ~ Normal(0, 1) # Our prior is a standard normal x .~ Normal(μ, 1) # Our data follows a normal distribution return nothing...

Simplify `assume`/`observe` design

1

Creating this issue after @yebai asked me to -- it looks to me like `assume` and `observe` could be simplified a bit. Current thoughts: 1. We should clearly document the...