ModelParameters.jl icon indicating copy to clipboard operation
ModelParameters.jl copied to clipboard

Easy, standardised parameter get/set for heterogeneous or nested immutable models.

Results 18 ModelParameters.jl issues
Sort by recently updated
recently updated
newest added

It now clashes with the ConstructionBase extensions

Packing one or more `Param()` into an Array that also contains some other number and then accessing elements in the array turns the `Param()`s into `Float` (or whatever the parent...

Math operations with `Param`/`AbstractNumber` do not work with Unitful quantities. ```julia Param(1.0)*1.0u"m" ERROR: MethodError: *(::Param{Float64, NamedTuple{(:val,), Tuple{Float64}}}, ::Quantity{Float64, 𝐋, Unitful.FreeUnits{(m,), 𝐋, nothing}}) is ambiguous. Candidates: *(y::Number, x::Unitful.AbstractQuantity) in Unitful at...

This is a major overhaul of the model interface to better support Table-like indexing behavior, most importantly through `setindex`. The basic idea is that `AbstractModel`s should allow Cartesian indexing, i.e....

@briochemc this PR addes `select` keywords everywhere so that we can filter by other wrapper types - e.g. `AbstractParam`. (and `ignore` for the case there are types in your object...

It's kind of weird that `AbstractModel` implements a `Table` interface but the `Array` interface (`size`, `length`, `getindex`, `setindex`, etc) behaves a like a vector of `Param`s. It would be really...

`update!(ruleset,df)` is fantastic. Maybe some facilities to update `df` would be nice (maybe already implemented but I'm not aware of). Using DataFrame.jl, I do: ```julia df[(df.component .== MyRule) .& (df.fieldname...

Hi, I was wondering if you be so kind to upload an example where a table is used to update the model parameters. Also, not sure from the documentation: is...

Another possible useful thing will be able to do the following (by name) ``` m = Model(m2, m1, m3) update!(m, table) # let's say we update parameters # now I...

This is a minor issue, but I think it would make more sense to use `IntervalSets.Interval` for the `bounds` field of `Param` (this goes for `FieldMetadata` as well). As far...