:orphan:

.. ****************************************************************************
.. CUI
..
.. The Advanced Framework for Simulation, Integration, and Modeling (AFSIM)
..
.. The use, dissemination or disclosure of data in this file is subject to
.. limitation or restriction. See accompanying README and LICENSE for details.
.. ****************************************************************************

.. demo:: alternate_locations

.. |classification| replace:: Unclassified
.. |date|           replace:: 2018-08-01
.. |group|          replace:: Demos
.. |image|          replace:: images/alternate_locations.png
.. |tags|           replace:: n/a
.. |title|          replace:: alternate locations demo
.. |startup|        replace:: run_course.txt
.. |summary|        replace:: This demo provides examples of how to utilize alternate locations for platform initialization. 

.. |i| image:: images/alternate_locations.png
   :width:  150 px
   :height: 118 px

.. include:: demo_template.txt

| Often a threat platform's location is not concretely known from intelligence data.
| The threat may be frequently moved, may be a movable platform that relocates easily,
| or there may simply be a lack of data. All of these issues cause there to be an
| uncertainty in the placement of a platform at the start of a scenario run. It is
| necessary to implement some functionality such that platforms can have multiple
| alternate locations possible before the platform is instantiated for a given run of
| a simulation.

run_course.txt
--------------

| This scenario provides examples of how to utilize the :command:`alternate_locations`
| functionality within AFSIM. Platforms can be given a probabilistic choice of locations
| at which to be initialized in the beginning of a scenario. Additionally these locations
| do not have to be absolute but can be relative to other platforms.