export_scenario_to_ASI: Writes your scenario as an ASI file

In battleVerse/sandTable: Data visualization and data import/export for the battleVerse

Writes your scenario as an ASI file

Description

Exports a scenario to a .asi file, which can be opened with SIMDIS for event visualization

Usage

export_scenario_to_ASI(
  scenario,
  outFileName,
  referenceYear = 1970,
  drawEngagements = TRUE,
  drawSensorTracks = FALSE,
  persistPosition = FALSE,
  prefFile = NA
)

Arguments

scenario	must have targetTruth and/or ownShipTruth as well as platformInfo
outFileName	output file name (including path if desired) for the ASI. Optional to include '.asi' in the output
referenceYear	(default=1970) SIMDIS uses this to interpret ambiguous dates. If you're using POSIX, then 1970 is correct
drawEngagements	(default=TRUE) if the scenario includes engagementData, the engagements will be drawn in the asi file (it's okay if drawEngagements=TRUE but no engagementData exists in the scenario)
drawSensorTracks	(default=FALSE) if the scenario includes sensorData, the tracks will be drawn in the asi file (it's okay if drawSensorTracks=TRUE but no sensorData exists in the scenario)
persistPosition	(boolean) if true, will persist all platforms until the end of the file (and gray out the title at their last position) (default=false)
prefFile	(default=NA) specify name of preference file (must be in same folder as the ASI output when you open it in SIMDIS)

battleVerse/sandTable documentation built on July 16, 2024, 4:20 a.m.