Joshua Pulsipher
Joshua Pulsipher
We can generalize our treatment of measures to allow constraint-like expressions as input to enable things like chance-constraints and exceedance probabilities, since all of these entities essentially implement a measure...
We should build in some interpolation functionality to automatically construct start value functions and optionally return infinite variable solutions as functions.
Our various measure tests only check that a measure is created. They don't check its contents. More rigorous testing should be implemented.
It would be useful to allow the user to exclude particular points (in terms of the infinite parameters) from being included in the constraint.
Following #189 and #131, a useful feature would be to add transformation support for infinite domains with infinite bounds (e.g., infinite time horizon problems). This could entail making a new...
Currently, spatial and space-time parameters are defined as independent parameters with independent infinite domains (which means they are combined via Cartesian products). Ideally, we would like to define domains of...
Following #293, we should have integrals and expectations be supported for numerical values.
There are several newish features from JuMP that are not supported yet. This issue will try to help keep track of these. Features to add: - [ ] Multi-objectives -...
When measures are expanded within an `InfiniteModel` via `expand_all_measures!`, any measure inside a derivative is skipped. ```julia model = InfiniteModel() @infinite_parameter(m, t in [0, 1]) @infinite_parameter(m, x in [0, 1])...
Following #301 and #207, we should add a tutorial to the documentation how how to go about incorporating discrete data into an InfiniteOpt formulation.