STK DIY Series

• Create a new scenario @ Today's Date 05:00:00.000 UTCG
• Drag and Drop the SRTM terrain data into the scenario. Click Accept for analytical terrain

Build Models/Define Mission

• Use the Search Bar to insert Bagram (AFB) as a Place object.
• Insert the area target "SearchRegion.at" from the STK Data Federate.
• Create a new aircraft "UAV"
  • First Point: 15,000 ft altitude, 0.5 km turn radius over Bagram
  • Use the 2D Map to add subsequent points over the AO
  • Attitude: Coordinated Turn
• Create a 20x20 degree rectangular sensor (nadir pointing)

Evaluate unique measure of mission effectiveness with custom calculations

• Compute access from the SearchRegion area target to the UAV. This will be used to establish the interval we are over the Area of Operations (AO) for the time component below.

The Time, Vector Geometry and Calculation tools are application-wide tools designed to streamline, organize and extend the fundamental computational capabilities of STK. Users can select from a large number of installed components that suit their needs and can create custom computational flows by using the results produced by some components as inputs for others.

VGT:

• UAV/Flight Bank (type: Angle)

Calc (UAV):

• "BankAngle" (type: Scalar/Angle) <- Flight Bank
• "Collection Angle" (type: Condition/Scalar Bounds) <- Bank Angle between -3 and +3 deg

Time (Sensor):

• "On Orbit Capture" (type: Interval List/Satisfaction) <- When the Collection Angle (condition) is satisfied within the Access Intervals (advanced/time limits) for UAV-to-Area access
• Right click and create a report to show the On Orbit Capture intervals
• Add the On Orbit Capture intervals to the Timeline View and SLIDE through the timeline
• Use On Orbit Capture to set the sensor display times
• Color the UAV route based on the On Orbit Capture intervals

Calc (Sensor):

• "Data Collection Rate" (type: Scalar/Constant) <- 20 Mb/sec
• "Total Data" (type: Scalar/Integral) <- Data Collection Rate (input scalar) over the On Orbit Capture interval (advanced options/time limits)...use "Cumulative to Current" type
• "Max Data" (type: Condition/Scalar Bounds) <- Total Data Below Maximum = 6000 Mb
• Create a graph for Total Data the show the accumulation and data rate changes
• Add the Max Data time instance to the Timeline View

BONUS: Can you merge the collection opportunities with the max data span to show when the camera will shut off before leaving the region?

• "Camera Roll" (type: Interval List/Satisfaction) <- When the Max Data (condition) is satisfied within the On Orbit Capture (advanced/time limits)

1. Create a new scenario
2. Search Tool: "Eglin Air Force Base" facility
3. Search Tool: "Superdome" place
4. Drag and drop the superdome.kmz (3D Model)
5. Create a new UAV that departs from Eglin and patrols the Gulf
   • Several waypoints @ 40k ft MSL @ 10 km turn radius
   • Attitude: Coordinated Turn
   • 3D Model: MQ-9 Guardian
6. Create UAV-GCS Access Graph
7. Create a bodymask file using the AzEl Mask Tool:
   • Create a default simple conic sensor called "create"
   • 3D Vertex Offset: X = 0.00253 km, Z = 0.00052 km
   • Use the "AzEl Mask Tool" @ 800 pixels to create the .bmsk
8. Copy the sensor and paste a new one called "display"
9. Visualize the mask:
   • Basic/Location: 3D Model (draws access lines to origin point)
   • Basic/Definition: Complex Conic (Outer Half Angle = 180 deg)
   • Basic/Sensor AzEl Mask: Load *.bmsk, [ ✓ ] Use Mask for Access Constraint
   • 2D Graphics/Projection:
     • Show Intersections: None
     • Field of View Constraints/SensorAzElMask
   • 3D Graphics/Projection:
     • Show Intersections: None
     • [ ✓ ] Use Extension Distance/Space Projection = 0.01 km
10. Create Sensor-GCS Access Graph
11. Add both access Time Intervals to Timeline View @ AircraftAvailability
12. Use Interval Times to display on 3D route

Create a new scenario using default time period
Use the Search tool to create a new place "pax riv" place
Use the Search tool to create a new place "naval station norfolk" place

Insert Objects from SDF:

Insert new Aircraft object with method from SDF
Click advanced criteria, then unselect "limit search to my SDF data"
Type in "x47b", and select x47b_Pax.ac

Insert new Ship object with method from SDF
Search for "cvn" and click ok

From the search toolbar, type in 3f4

Insert new sensor, attach to aircraft, then Search for FLIR

Analyzer Route:

Use 3d editing to move the aircraft route so that it flies over the CVN.

Upload Changes to SDF:

From the File menu, select save aircraft to data federate.
Add any notes about the object, or enable revision control and add any update notes.

• Create a new scenario called "constellationDesign", accepting the default 24 hour time period
• Close timeline view
• Turn off the 3d graphics window's lighting
• Zoom in on the US in the 3d window
• Set the time units to hours

Create Coverage Definition

• Create a new area target and select the United States
• Insert a new satellite
• Open properties and click ok to propagate
• Insert the default sensor on the satellite
• Create a constellation called "SatSensors" and add the satellite sensors
• Insert a new coverage definition object and rename to US_Cov
• Open US_Cov's properties, change the type to "Custom Regions", click the "Select Regions" button and double-click the United_States area target
• Set the point granularity to 1 degree
• In the Assets Panel, double-click on the constellation to assign it as an asset

Evaluate Coverage

• Insert a new Figure of Merit object and rename to AgeOfData
• Open AgeOfData's properties and change the type to AgeOfData
• In the 2d graphics - Animation panel, enable the "Show Contours" radio button
• Set the contour levels as follows
  • Start: 0 hr
  • Stop: 2 hr
  • Step: 15 min
  • Click Add Levels
• Set the start contour to red (represents AgeOfData = 0, which means recent (hot) data)
• Set the stop contour to blue (represents AgeOfData = 2 hr, which means old (cold) data)
• In the 2d graphics – Static panel, uncheck the “Show Static Graphics” checkbox
• Click ok to dismiss the properties browser
• Right-Click on "US_Cov", select Coverage Definition, then select compute accesses
• Right-Click on "AgeOfData", select Report and Graph manager
• Scroll through the installed styles, and generate a "grid stats" report
• Save the scenario and exit STK

Load STK model into ModelCenter

• Start Modelcenter, click "Start a new model", then select Process
• Drag / Drop STK into the Process flow
• Browse to the "ConstellationDesign" scenario
• Select the satellite > propagator – inclination and drag it to the variables section to the right
• Select the US_Cov > AgeOfData – Data Providers > Overall Value – Average to the variables section to the right, then click ok
• Unnest the contents in the Component tree, then click the "play" button to execute the model

Parametric Trade Study

• From the tools menu, select the Parametric study tool
• Drag the Inclination from the Component tree and drop into the design variable, then set the following levels:
  • Start: 0
  • Stop: 180
  • Number of Samples : 10
  • Step size: 20
• Click Run to begin the trade study
• Click on the lowest value (40 deg), and click "Reload values to model"
• Double-click on Average AgeOfData to update the component tree and STK
• Animate STK to see the new results

Walker constellation design

• Click on STK in the ModelCenter analysis view, then click on the edit pencil
• Select the satellite then double click on the walker folder
• Add the coverage grid resolution as a variable
• Unnest the Walker variables in the component browser
• Set the Walker enable variable to true
• Type the name of the constellation to "SatSensors"
• Change the constellation type to Sensor
• Launch the Carpet Plot Tool
• Drag the numPlanes and numSatPerPlane into design variables from 1 to 4 step of 1
• Drag the average age of data to the responses
• Click Run

Create Excel cost model

• Open Excel and create a new spreadsheet
• Create columns for
  • numPlanes
  • numSatsPerPlane
  • numSats
  • costPerSat
  • totalCost
• Set numSats = numPlanes * numSatsPerPlane
• Set costPerSat to 20 ($ M)
• Set the total cost to costPerSat * numSats
• Add names for numPlanes, numSatPerPlane, and numsats
• Add variables for each column

Add Excel to Modelcenter

• Add Excel to the ModelCenter process
• Pick variables for costpersat, numSats, and totalcost
• From the view menu, open the link editor
• Link the numSats and numSatPerPlane variables

Perform Cost vs Performance trade study

• Open the DOE tool
• Set the grid point granularity to 2 deg, and ensure the inclination is set to 40 deg
• Drag the numPlanes and numSatPerPlane into design variables from 1 to 4 step of 1
• Drag the average age of data and cost to the responses
• Click Run
• In the data explorer create a standard plot > 2d point
• Set the basic settings - variables to x= cost and y = age of data
• Select the best design, reload those values to the model, compute age of data
• Animate the scenario in STK to visualize the best design

• Create a new scenario and set the time period with Start Time = Today, Stop Tim = +90 days.
• Insert a Place object and position it anywhere on the globe.
• Insert 2 satellites using the Standard Object Catalog, the ISS and Aqua.
• Insert a third satellite using the Orbit Wizard with the following properties:
  • Name – CalibrationSat
  • Type - Circular
  • Altitude – 700 km
  • Inclination – 90 deg
  • RAAN – 60 deg
• Add Sensors to ISS and CalibrationSat and set properties to size the sensors.

Determine simultaneous coverage calibration opportunities

• Use Constellation and Chain objects to determine when either Aqua or ISS sensor covers the POI simultaneously with the CalibrationSat.

Relax timing constraints

• Compute access between the CalibrationSat sensor and the POI.
• Compute Chain access between a Constellation containing Aqua's and ISS' sensors and the POI.
• Time Tool
  • Create a new Interval List of type Scaled to expand the Access times by 30 minutes before and after.
  • Create a new Interval List of type Merged to combine the scaled access times with the Chain access times.

Minimize approach angle difference

• Vector Geometry Tool
  • Create new Planes of type Normal to construct the orbit planes of both Aqua and CalibrationSat using their Orbit Normal vectors and any reference vector.
  • Create a new Angle of type Between Planes using the two planes just created.
• Display these planes and angles in the 3d Window by editing the properties of the Vector page.
• Calculation Tool
  • Create a new Scalar Calculation of type Angle using the angle just created.
  • Create a new Scalar Condition of type Scalar Bounds using the Scalar Calc just created to determine set the Operation to Above Minimum with a value of 10.

Output data

• Right click on CalibrationSat and Export Ephemeris/Attitude.
• Change the Start and Stop times of the data using the Time Tool components.

• app = actxserver('STK10.application')
• app.UserControl = 1

Grab a handle on the STK application root

• root = app.Personality2

Create a new Scenario, and configure its properties

• scenario = root.Children.New('eScenario','DIY_Matlab');
• scenario.SetTimePeriod('24 Feb 2012 12:00:00.000','25 Feb 2012 12:00:00.000')
  • scenario.StartTime = '24 Feb 2012 12:00:00.000'
  • scenario.StopTime = '25 Feb 2012 12:00:00.000'
• root.ExecuteCommand('Animate * Reset')

Add a satellite and a facility, and configure their properties

• facility = scenario.Children.New('eFacility','GroundSite')
  • facility.Position.AssignGeodetic(50,-100,0)
• satellite = scenario.Children.New('eSatellite','LeoSat')
  • root.ExecuteCommand(['SetState */Satellite/LeoSat Classical TwoBody "', scenario.StartTime,'" "', scenario.StopTime ,'" 60 ICRF "',scenario.StartTime,'" 7200000.0 0.0 90 0.0 0.0 0.0'])

Compute access between the satellite and facility

• access = satellite.GetAccessToObject(facility)
• access.ComputeAccess

Retrieve access interval start/stop times

• accessDP = access.DataProviders.Item('Access Data').Exec(scenario.StartTime,scenario.StopTime);
• accessStartTimes = accessDP.DataSets.GetDataSetByName('Start Time').GetValues
• accessStopTimes = accessDP.DataSets.GetDataSetByName('Stop Time').GetValues

Retrieve the altitude of the satellite during an access interval

• satelliteDP = satellite.DataProviders.Item('LLA State').Group.Item('Fixed').ExecElements(accessStartTimes{1},accessStopTimes{1},60,{'Time';'Alt'})

The STK/Coverage module allows you to analyze the global or regional coverage provided by one or more assets like facilities, vehicles, sensors, etc. Specific results are generated based on detailed access computations performed to user-defined grid points within an area of coverage.

The Coverage Module provides the necessary tools to:

• Define areas of interest
• Define coverage assets
• Define the time period of interest
• Report on the coverage quality

Coverage allows you to determine

• Quality of your coverage from the assets
• Time of Max/Min coverage
• Locations that require further analysis

Problems

Denver: High car thefts have been reported in Denver and Police have suspected that the vehicles are being taken through the mountains towards Grand Junction via I-70 west. Helicopters are loud, expensive and can tip of the suspects that they are being monitored. The Denver Police want to purchase one or more UAVs that can view license plates, identify stolen vehicles and lead troopers to the vehicles location.

Jalalabad: Afghan Security Forces are going to take full control of Afghanistan when the United States’ Forces leave the area. The United Nations wants to keep an eye on the number of troops in a disputed region near Jalalabad. The UN is requesting multiple UAVs for this region and they want to determine if UAVs will be effective in the mountainous region above Jalalabad.

Seoul: With Tensions high, the United States will be using UAV’s to monitor the border between North and South Korea. The United States Military wants to determine if UAVs can monitor the Demilitarized Zone without any gaps in coverage.

START: Do-It-Yourself

• Create New Scenario
• Timing: Use the Start Time
  • Denver: 15:00:00
  • Jalalabad: 05:00:00
  • Seoul: 00:00:00
• Drag and Drop Terrain into the scenario
• Change the Properties of the Scenario
  • Basic > Terrain Use terrain file
  • 3D Graphics > Surface Lines: Draw On Terrain.
• Search for the city of interest
  • Position > Altitude > Use Terrain Data
  • Basic AzElMask > Use > Terrain Data
  • Constraints > Elevation Angle to Max 60 degrees
    • Seoul: Min to 0 degrees
    • Denver/Jalalabad: Min to 10 degrees
  • Denver: Constraints > Azimuth: 0 to 180 degrees
  • Constraints > Basic > Enable Terrain Mask
  • Constraints > Sun > Lighting - Direct Sun
    NOTE: The new place will act as a constraints source for points in your coverage grid.
• Use Bing Maps
  • Use Hybrid, to see the roads.
• Add default area target
  • 3D object editor to create it
• Add aircraft: Define Properties
  • Add 2 Points in 3D
  • Basic Route > Change the Altitude Reference to Terrain > 5km Granularity > Terrain Height.
  • Basic Route > Change the Speed to be 85 mi/hr and Altitude to be 0.25 miles
  • 2D Graphics > Route > Lead None Trail Full.
  • 3D Graphics > Inherit from 2D Graphics
  • Add the rest of the points in 3D or 2D.
• Add Sensor on the aircraft
  • Definition Rectangular and vert 25 and horz 25
  • Pointing:
    • Denver/Jalalabad: Azimuth 0 Elevation 45
    • Seoul: Azimuth -90 Elevation 10
  • Constraint > Range, Max to 10 km
• Copy Aircraft x2
  • Change the Start Time to later in 20 minutes
• Add Coverage Definition
  • Grid > Custom Region > Area Target
  • Grid > Distance, 1 km to 5 km
  • Grid > Altitude above terrain 5 ft
  • Grid > Grid Constraint Options
    • Set to target -> Use Object
      NOTE: USE OBJECT: By selecting the place, all of the properties and constraints that apply to that one object are also applied to every point in the grid.
      NOTE: If you select Use Actual Object on the Grid Points, using the actual object speeds up coverage computations.
  • Assets > Select ALL the Sensors
  • Advanced > Disable Auto Compute
• Compute Access in Parallel (only once)
• Open the Task Manager and to show the cores are enabled and active
• Add Figure of Merit
  • Call it 1_AreaInView and show that the entire region is covered.
  • Basic > Definition > Simple Coverage, (Static)
  • 2D Graphics > Static > Select Show > Satisfaction , Add Color.
• Add Figure of Merit
  • Call it 2_TimeCoverage
  • Basic > Definition > Coverage Time > Total
  • 2D Graphics > Static > Select Show
  • Add Contours from 60 seconds to the max, with large steps
  • 2D Graphics > select Enable Sampling to be smooth.
• Add Figure of Merit
  • Call it 3_AgeOfData
  • Basic> Definition > Age of Data, Average > Min Assets 1
  • 2D Graphics > Static > Disable
  • 2D Graphics > Animation > Show
  • Show Contours with Level Attributes
  • ->Start at Zero, large time with larger time step
  • ->Start Green, End Red.
• Add Figure of Merit
  • Call it 4_AccessNum
  • Basic> Definition > Number of Accesses, Max Per Day
  • 2D Graphics > Static > Disable
  • 2D Graphics > Animation > Show
  • Show Contours with Level Attributes
  • ->Start at 1, Stop Total Num assets with 1 step
  • ->Start Purple to End Yellow
  • 2D Graphics > Animation > Accumulation > Show: Up to current time
• Use the Grid Inspector Tool for the second FOM object
  • Zoom into an area on 2D Graphics that has full coverage/half coverage/No Coverage
  • Select the points and show the data for the region.

1. Import a CAD model
2. Adjust tessellation settings
3. Polygon reduction
4. Center the model and adjust orientation
5. Confirm scale
6. Collapse mesh items
7. Export

• Create New Scenario make France in daylight.
• Drag and drop terrain into the scenario.
• Change the properties of the scenario.
• Use the search toolbar to look for Chorge and Nice.
• Create Ground Vehicle (GV) route between Chorge and Nice.
• Apply Terrain Mask or use KML data or 3D object editing to create route.
• Insert mobile ground center.
• Insert a default aircraft, use external ephemeris file, and rename.
• Change model to be helicopter and add an image sensor with half cone angle.
• Add a relay sensor with 5 deg half cone angle and targeted at MGS (Relay1).
• Sample external file to hover over same lat/lon:

  stk.v.10.0
  BEGIN Ephemeris
  NumberOfEphemerisPoints 2
  ScenarioEpoch 2 Apr 2013 01:00:00.000
  InterpolationMethod Lagrange
  InterpolationOrder 1
  DistanceUnit Kilometers
  CentralBody Earth
  CoordinateSystem Fixed
  

  EphemerisLLATimePos
  0.0000 44.3458 6.57 4
  604800.000 44.3458 6.57 4
  END Ephemeris

• Insert chain object and rename. Add objects.
• Add the MultiHopChain CompleteChainAccessIntervals and the GV EphemerisTimeSpan.
• Insert a two additional Aircraft and rename. Add an image sensor and a relay sensor.
• Create two constellations and set both constraints.
• Insert chain object and rename. Add objects.
• Add the Many2ManyChain CompleteChainAccessIntervals.
• Modify the constraint on the relay constellation.

• Create a new scenario
• Insert a facility/place as your radar site
• Insert and define the field of regard sensor
• Insert a missile that will fly through the field of regard sensor
• Compute access from the field of regard sensor to the missile
• Insert and define another sensor and use it to target your missile
• Insert and define a radar onto the targeted sensor
• Run the Radar SearchTrack access report to see if the radar can track the missile.

• Change Surface Reference of Earth Globes to Mean Sea Level.
• Add toolbars: 3D Object Editing and 3D Aircraft Mission Modeler Editing and
• Insert default Aircraft and default Ship. Zoom in the 3D window to Southern California coastal area.
• Select the Ship, and Object Edit Start. Shift-click a few points off the coast of San Diego for the Ship's route.
• Click Object Edit Accept.
• Zoom in to San Diego. Using 3D Object Editing toolbar, select the Aircraft, and Object Edit Start.
• Using the 3D AMM Editing toolbar, click Switch to AMM.
• Select Aircraft – Basic Fighter.
• Add Sites and Procedures for the Aircraft
• Show how to modify the mission using the 3D Object Editing.
• Change 3D model of Aircraft to F-18.
• Open Aircraft Basic Route Properties. Change Runway Altitude Offset. Enable checkbox for Minimize Time Difference with Procedure. Open other procedures and edit properties. Rename Aircraft. Edit the F-18's Performance Models.
• Modify the Ship's route in the 3D window.

• Get Data
  • Shapefile - Geographic Data
    • http://www.nationalatlas.gov/atlasftp.html?openChapters=chpgeol#chpgeol
  • KML - Past Flight
    • http://flightwise.com/track/ASA633
• Import Data
  • Shapefile
    • Scenario > GIS Import
    • Sort by location – choose all US items.
  • KML
    • Drag and drop
    • Open globe Manager > Right Click > Promote
• Augment with Analysis
  • Improve the model by adding a sensor
    • Import sensor from Data Federate
  • Compute Accesses with a Chain
    • Show Chain results on Timeline
• Export
  Shapefile
  • Utilities > Export > shapefile – export points and route
  • Right click Sensor menu > Export GIS > Footprint > choose 3 accesses
  • Display in ArcGIS Online
    • http://www.arcgis.com/home/webmap/viewer.html?useExisting=1
• KML
  • Launch HTML Viewer > KML Export Utility
  • Choose aircraft, sensor and targets
  • Display in Google Earth

• Open STK
• Create new Scenario (Load Terrain for Analysis and Visualization)
• Go to Search Tool type "Everest" > Enter
• In result list right-click Mount Everest and select > Create AreaTarget
• In both 2D and 3D Graphics zoom to the Mount_Everest” Area Target
• Populate Objects
• Open route5b_1979Yugoslavia Properties. Look at Altitude Reference area
• Open Basecamp Properties
• Open Sensor/Telescope Properties
• Analysis > When can I see a hiker from basecamp?
• Analysis > How does terrain obscure satellite visibility?