For conservation law parameters, add to their meta data that they are conservation law parameters

[TorkelE]

Seems useful. Current example:

julia> rs = @reaction_network begin
           (k1,k2), X1 <--> X2
       end;

julia> osys = convert(ODESystem, rs; remove_conserved = true);

julia> parameters(osys)[end].metadata
Base.ImmutableDict{DataType, Any} with 3 entries:
  MTKVariableTypeCtx => PARAMETER
  VariableSource     => (:parameters, :Γ)
  ArrayShapeCtx      => (1:1,)

[isaacsas]

We have conservationlaw_constants to get them.

[isaacsas]

That said, attaching metadata to them is probably a good approach to propagate their meaning through to downstream system types and allow users to extract them from such systems.

[isaacsas]

This would be where to inject the metadata I think:

Catalyst.jl/src/networkapi.jl

Line 1225 in fc13104

constants = MT.unwrap.(MT.scalarize((@parameters Γ[1:nullity])[1]))

[TorkelE]

Yeah, I had some application in SI where you get lists of possible identifiable functions (find_identifiable_functions). Here it would be good to simply loop through the output and see whether any components are conservation law constants.

[TorkelE]

now works on master