Simon Etter

FFT of transposed complex matrix

2

``` julia> fft(transpose(rand(ComplexF64,2,2))) ERROR: MethodError: no method matching plan_fft(::Transpose{Complex{Float64},Array{Complex{Float64},2}}, ::UnitRange{Int64}) Closest candidates are: plan_fft(::Union{DenseArray{T

MergeSort-style iterator

1

Adds the following function: imerge(a,b, predicate = Bool`: Whether to pick the next element of `a` (true) or `b` (false). - `fa(ak)`, `fb(bk)`: Functions to apply to the picked elements...

Jacobi elliptic functions and complete elliptic integral of the first kind

17

Implements the Jacobi elliptic functions and the complete elliptic integral of the first kind. Both sets of functions work for real and complex arguments as well as all `FloatXX` and...

``` julia> D = Interval(-2,-1), Interval(1,2); S = JacobiWeight(-0.5,-0.5, Chebyshev(D[1])) ∪ JacobiWeight(-0.5,-0.5, Chebyshev(D[2])) μ = [ DefiniteIntegral(component(S,1)); DefiniteIntegral(component(S,2)); real(Hilbert(S)) ] \ [-0.5;1;0] @show sum(components(μ)[1]) @show sum(components(μ)[2]) ; sum((components(μ))[1]) = -5.505172187825942e15...

Hilbert not implemented on Rays

1

I'm trying to compute the equilibrium measure of a positive charge supported on `[1,2]` and a negative charge on `(-∞,0]`. I believe the following code should work, but it doesn't....

Spy printing of sparse matrices is inaccurate

3

The following piece of code assembles the two-dimensional discrete Laplacian on an `n x n` grid: ``` using SparseArrays using LinearAlgebra function laplacian_2d(n) Δ = spdiagm( -1 => fill(-1.0, n-1),...

The Jacobi elliptic functions should satisfy ``` sn(0,m) == 0 cn(0,m) == 1 dn(0,m) == 1 ``` for any `m`, see Abramowitz&Stegun, "Handbook of Mathematical Functions", Sec 16.5. This is...

Allow passing a list of root manifests to Pkg.gc()

1

We are using Julia in an embedded, offline system, and therefore when we make a release we have to bundle the Julia depot into the release so all the packages...

Handle named parameters more consistently

11

The current behaviour of named parameters is quite confusing. This parameter lookup succeeds. ```groovy groovy:000> rsp = new ParameterRsp(new ParameterReq()) ===> ParameterRsp[] groovy:000> rsp.set(new NamedParameter("bar"), 42, true) ===> null groovy:000>...

Errors in parameter getters / setters are not reported

5

The current implementation does not report errors raised in parameter getter and setters. I believe the culprit is this generic `catch` clause [here](https://github.com/org-arl/fjage/blob/454ca543e83c82cf7e8cfc0632c28b7a1cd55a92/src/main/java/org/arl/fjage/param/ParameterMessageBehavior.java#L264-L266).