Skip to content
Snippets Groups Projects
Commit 1cf57adf authored by UnityGrunt03's avatar UnityGrunt03
Browse files

Created a README - the Program is in MAJ Furr's GIT

parent fe421715
No related branches found
No related tags found
No related merge requests found
1. Purpose - The purpose of this project was to incorporate Distributive
Interactive Simulations (DIS) protocol data units (PDU) into MAJ Furr's thesis
work. His work supports the warfighter and reveals data that will wisely inform
future decisions. It was a pleasure to support his work and to make his work
more accessible to the Modeling & Simulations and Wargaming communities of
interest.
2. Background - MAJ Furr created a discrete event simulation (DES) of the
call for fire process from the forward observation points through battalion level
fires. The DES covers multiple forms of radio frequencies and concepts. His DES
shows how the broadcasting of conventional omni-directional frequency modulation
waveforms can be intercepted by a near peer competitor. What was lacking from
his work was the ability to integrate his work with other simulations.
3. Process - Capt Jonathan Boron and Maj Daniel Yurkovich utilized an incremental
model process to incorporate the DIS PDUs into MAJ Furr's DES. The approach began
with understanding MAJ Furr's code and which java classes placed elements onto
the event list. With this understanding, a "PDU Constructor" class was created
to house all of the required PDUs. At this point, the following PDUs deemed
necessary as a proof of concept are: CreateEntityPDU, EntityStatePDU, FirePDU,
DetonationPDU, TransmitterPDU, ReceiverPDU, and SignalPDU. A major break through
that enabled quick implementation was MAJ Furr's creation of the "SimpleMover3D"
class. All moving elements, both enemy and friendly, were subclassed from the
SimpleMover3D class. Within the SimpleMover3D class we placed the PDUConstructor,
PDUSender, TransmitterPDU, and ReceiverPDU. With more refinement of the process,
the CreateEntityPDU,and EntityStatePDU should be in the SimpleMover3D class.
Since a large focus of MAJ Furr's work was how different radio procedures
influenced the battlefield, A struggle for Capt Boron and Maj Yurkovich was to
identify where radio messages were executed, broadcasted, in the DES portion of
MAJ Furr's program.
4. Future work - figure out the web of details into each PDUs. Better understanding
of how to use the IEEE & SISO standards. EntityID & serialization creation.
With more refinement of the process,
the CreateEntityPDU,and EntityStatePDU should be in the SimpleMover3D class.
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment