Engineering Design Interface (EDI) Contrib Package

.gitignore

@@ -24,4 +24,7 @@ gurobi.log
 
 # Jupyterhub/Jupyterlab checkpoints
 .ipynb_checkpoints
-cplex.log
+cplex.log
+
+# Mac tracking files
+*.DS_Store*

doc/OnlineDocs/contributed_packages/edi/additionaltips.rst

@@ -0,0 +1,37 @@
+Additional Tips
+---------------
+
+* Developers may need to install the following additional packages:
+
+::
+
+   pip install pytest
+   pip install pytest-cov
+   pip install sphinx
+   pip install sphinx_rtd_theme
+   pip install sphinx_copybutton
+
+
+* If you wish to build the documentation locally, use:
+
+::
+
+   cd <path_to_pyomo>/pyomo/doc/OnlineDocs
+   make html
+
+then open the file ``<path_to_pyomo/doc/OnlineDocs/_build/html/index.html>``
+
+
+* Unit tests and coverage can be run locally using:
+
+::
+
+   cd <path_to_pyomo>/pyomo/pyomo/contrib/edi
+   pytest --cov-report term-missing --cov=pyomo.contrib.edi -v ./tests/
+
+or generating html output:
+
+::
+
+   cd <path_to_pyomo>/pyomo/pyomo/contrib/edi
+   pytest --cov-report html --cov=pyomo.contrib.edi -v ./tests/

doc/OnlineDocs/contributed_packages/edi/advancedruntimeconstraints.rst

@@ -0,0 +1,115 @@
+Advanced Runtime Constraints
+============================
+
+
+Automated unpacking for multi-use black-boxes
+---------------------------------------------
+
+Coding a black-box model often represents a significant effort, and it is therefore desirable to have the black-box work in many situations.  A common case is to have a black-box model with a scalar input variable perform vectorized operations, ie, take in a vector and return a vector.  In the more general case, this can be thought of as passing in multiple run-cases as input to the black-box model.
+
+The ``parseInputs()`` method enables this batch-like capability in a variety of forms:
+
+.. py:function:: BlackBoxFunctionModel.parseInputs(self, *args, **kwargs)
+
+    Parses the inputs to a black-box model into a list of run-cases
+
+   :param args: The self attribute in all python methods
+   :type  self: black-box model
+   :param args: index passed arguments
+   :type  args: list or tuple
+   :param kwargs: keyword passed arguments
+   :type  kwargs: dict
+
+   :return: runcases
+   :rtype: list
+   :return: returnMode
+   :rtype: int
+   :return: extras
+   :rtype:  list
+
+
+The function definition is not particularly helpful, so let's dive in a bit.  For the typical user, we recommend that the top of all ``BlackBox()`` methods appear as follows:
+
+.. literalinclude:: ../../../../pyomo/contrib/edi/tests/test_docSnippets.py
+    :language: python 
+    :dedent: 12
+    :start-after: # BEGIN: AdvancedRTC_Snippet_02
+    :end-before: # END: AdvancedRTC_Snippet_02
+
+
+Essentially, ``parseInputs()`` is a pre-processor that directly takes the inputs of the black-box.  The ``parseInputs()`` method will check all of the inputs, ensure that size and units are correct, split into run cases as appropriate, and return a run-cases list that is ready to operate on.
+
+The ``runCases`` return (which can be named as any valid python name) is a list of dicts, where the keys to the dict are the names of the inputs declared in the ``__init__()`` method.  Ex: ``runCases[0]['x']`` will give the ``'x'`` input (in units specified in the ``__init__()`` method) in the first run-case.
+
+The ``returnMode`` return (which can be named as any valid python name) is an integer that indicates how the return should be processed.  If ``returnMode`` is passed as a ``kwarg``, then the passed in value will be cast to this output.  If it is not passed in, then ``returnMode`` will be either ``-1*self.availableDerivative``, indicating that there is only a single run case, or ``self.availableDerivative`` which indicated multiple run cases.  A negative value for ``returnMode`` indicates that there will be one less layer of indexing in the output.
+
+The ``extras`` return (which can be named as any valid python name) is a dict that will include all of the additional passed in values not expected by the black-box model.  The extra ``kwargs`` will appear as normal, and extra ``args`` get put in a list in ``extras['remainingArgs']``.  If you pass in a ``kwarg`` with key name ``'remainingArgs'``, it will be overwritten.  The extras dict is the place to find options that may affect the code (ex: tolerances, run modes, etc) that are not expected inputs to the black-box model.
+
+Note that when using run case input, the output will always take the following unpacking structure:
+
+::
+
+    output[<run_case_index>][0] = <list_of_outputs_for_specified_runcase>
+    output[<run_case_index>][0][<index_of_output>] = <output_for_specified_runcase>
+
+    output[<run_case_index>][1] = <list_of_jacobians_for_specified_runcase>
+    output[<run_case_index>][1][<index_of_output>][<index_of_input>] = <d(output_of_specified_index)/d(input_of_specified_index)>
+
+
+There is **not** a shortcut for single scalar output black boxes as is the case when not using run cases, the final index to output 0 must be included.
+
+
+
+An Example
+++++++++++
+
+There are many ways this functionality can be used, we provide an example here to get new users started
+
+.. literalinclude:: ../../../../pyomo/contrib/edi/tests/test_docSnippets.py
+    :language: python 
+    :dedent: 8
+    :start-after: # BEGIN: AdvancedRTC_Snippet_01
+    :end-before: # END: AdvancedRTC_Snippet_01
+
+
+Check outputs
+-------------
+
+There is a ``checkOutputs()`` method that is not supported in the current version.  Contact the developers if you desire this functionality, but the following the practices described in this documentation should render the need for this moot.
+
+
+Cases of non-scalar inputs or outputs
+-------------------------------------
+
+Indexing can get somewhat complicated when inputs and outputs are not scalars.  Users should be warned this feature is supported, but not well tested, so please contact the developers if you encounter any unusual behavior.
+
+The following unpacking remains the same:
+
+::
+
+    output[0] = <list_of_outputs>
+    output[0][<index_of_output>] = <output>
+
+    output[1] = <list_of_jacobians>
+    output[1][<index_of_output>][<index_of_input>] = <d(output_of_specified_index)/d(input_of_specified_index)>
+
+However, for outputs, the result will be an array with dimensions equal to the size of the output.  For Jacobians, it breaks down as the following:
+
+::
+
+    jacobian_list_entry[(output_dim_1_ix, output_dim_2_ix, ..., input_dim_1_ix, input_dim_2_ix, ...)] = <scalar_d(output_of_specified_index)/d(input_of_specified_index)>
+
+For example, with an output that is 2x2 and an input that is also 2x2
+
+::
+
+    output[1][<index_of_output>][<index_of_input>][(0,0,1,1)] 
+
+is the derivative of ``output[0,0]`` with respect to ``input[1,1]``
+
+
+
+Tips
+----
+
+* A model summary can be printed by calling ``print(model_instance.summary)``