TMT User Guide - Revision history

Shawn Allen: /* Creating Output add object ID info */

2021-08-18T14:52:22Z

‎Creating Output add object ID info

Shawn Allen: /* Getting Started */

2016-07-18T19:03:17Z

‎Getting Started

Shawn Allen: /* File Transfer to MiniSim™ */

2016-07-18T19:00:24Z

‎File Transfer to MiniSim™

Shawn Allen: /* File Transfer to MiniSim™ */

2016-07-18T19:00:04Z

‎File Transfer to MiniSim™

Shawn Allen: /* File Transfer to MiniSim™ */

2016-07-18T18:58:58Z

‎File Transfer to MiniSim™

Shawn Allen: /* File Transfer to MiniSim™ */

2016-07-18T18:58:22Z

‎File Transfer to MiniSim™

Shawn Allen: /* File Transfer to MiniSim™ */

2016-07-18T18:56:17Z

‎File Transfer to MiniSim™

Shawn Allen: /* Associated file set */

2016-07-18T18:52:53Z

‎Associated file set

Shawn Allen: /* Included Databases */

2016-07-18T18:51:56Z

‎Included Databases

Shawn Allen: /* Script Utilities */

2016-07-18T18:51:17Z

‎Script Utilities

← Older revision		Revision as of 14:52, 18 August 2021
Line 40:		Line 40:

	'''All steps must be completed in order to view the created world on the MiniSim simulator.'''		'''All steps must be completed in order to view the created world on the MiniSim simulator.'''
		+
		+	'''Note: Object IDs of -1 in the LRI file means those objects cannot be controlled by miniSim. You can search for objects by running a grep command on the LRI file as shown below:
		+	grep s_ <your_lri_file_here>.lri <Enter>
		+
		+	The results will echo to the screen (example - your results will be different objects and IDs):
		+
		+	TrafSign s_r1_0_0_0_0 TileOptionOneTwo 173.833 220.000 0.012 0.000 12
		+	TrafSign s_r1_1_0_0_0 TileOptionOneTwo 221.833 220.000 0.012 0.000 13
		+	TrafSign s_r2_0_0_0_0 TileOptionOneTwo 173.833 284.690 0.012 0.000 14
		+	TrafSign s_r2_1_0_0_0 TileOptionOneTwo 221.833 284.690 0.012 0.000 15
		+	'''

	To generate files for use on the MiniSim™, you will use the TMT Output menu. Environment creation workflow consists of building the visual database first. The MiniSim™ will render these output files after they are optimized and installed. You must also process these files to produce a scenario control list (SCL) file. After the SCL file has been created, you can choose Output >> Scenario LRI file from the TMT to create a Logical Road Information (LRI) correlated database file. It will be necessary to convert the LRI file into a Binary LRI file (BLI), since that is the format the MiniSim™ uses during simulation. It can be useful to be able to read the text form of the LRI file when troubleshooting.		To generate files for use on the MiniSim™, you will use the TMT Output menu. Environment creation workflow consists of building the visual database first. The MiniSim™ will render these output files after they are optimized and installed. You must also process these files to produce a scenario control list (SCL) file. After the SCL file has been created, you can choose Output >> Scenario LRI file from the TMT to create a Logical Road Information (LRI) correlated database file. It will be necessary to convert the LRI file into a Binary LRI file (BLI), since that is the format the MiniSim™ uses during simulation. It can be useful to be able to read the text form of the LRI file when troubleshooting.

@@ Line 13: / Line 13: @@
 '''NOTE:''' Each tile must be unique – you should not have two tiles within the library with the same name.
-Start the TMT&trade; by double-clicking the icon.  You may want to open existing databases, or create a new terrain database.  To create a new terrain, choose New from the File menu (File >> New).  If the TMT&trade; has not been used on this computer before, you’ll have to preprocess the tile library in order to proceed.  Click Preprocess to load the tile library.  This procedure will occur only when the TMT&trade; is first used on your system, or when a tile geometry file (.FLT) has been modified.  The TMT&trade; loads the Tile Library automatically in normal use.
+Start the TMT&trade; by double-clicking the icon.  You may want to open existing database worlds, or create a new world (terrain database).  To create a new world, choose New from the File menu (File >> New).  If the TMT&trade; has not been used on this computer before, you’ll have to preprocess the tile library in order to proceed.  Click Preprocess to load the tile library.  This procedure will occur only when the TMT&trade; is first used on your system, or when a tile geometry file (.FLT) has been modified.  The TMT&trade; loads the Tile Library automatically in normal use.
 To open an existing terrain database/world file, choose File >>Open and navigate to the database location on your computer.

← Older revision		Revision as of 19:00, 18 July 2016
Line 206:		Line 206:

	To install a database world, run the following script from the database directory:		To install a database world, run the following script from the database directory:
		+
	'''dbinstall''' <DB_NAME><Minisim™ Version Number><ENTER>		'''dbinstall''' <DB_NAME><Minisim™ Version Number><ENTER>

@@ Line 205: / Line 205: @@
 A script has been provided to copy files for user convenience, although it is advisable to be aware of the various file types and locations where these files are to be placed for proper configuration.
-Run the following script from the database directory:
+To install a database world, run the following script from the database directory:
-dbinstall <DB_NAME><Minisim&trade; Version Number><ENTER>
+'''dbinstall''' <DB_NAME><Minisim&trade; Version Number><ENTER>
 This script expects the database files will be available from the location the script is activated, which means the default configuration as installed and described in this document.  In the event of an error, the script will discontinue operation and inform the user it has encountered a problem.

@@ Line 201: / Line 201: @@
 ==  '''File Transfer to MiniSim&trade;''' ==
-Databases that are created using the TMT&trade; must be copied into the MiniSim&trade; directory tree before they are available for use within the MiniSim&trade; simulator.
+Database worlds that are created using the TMT&trade; must be copied into the MiniSim&trade; directory tree before they are available for use within the MiniSim&trade; simulator.
 A script has been provided to copy files for user convenience, although it is advisable to be aware of the various file types and locations where these files are to be placed for proper configuration.

@@ Line 213: / Line 213: @@
 The following files are copied (version refers to the installed software version number):
-DB_NAME.scl	C:/MiniNads_version	bin/
+DB_NAME.scl	C:/MiniSim&trade;_version/bin.x64/
-<nowiki>*</nowiki>.FLT	C:/MiniNads_version	visuals/db_name/
+<nowiki>*</nowiki>.FLT	C:/MiniSim&trade;_version/visuals/db_name/
-DB_NAME.BLI	C:/MiniNads_version	data /
+DB_NAME.BLI	C:/MiniSim&trade;_version/data /
-DB_NAME.FTR	C:/MiniNads_version	bin/
+DB_NAME.FTR	C:/MiniSim&trade;_version/bin.x64/
 '''TMT&trade; Reference'''

@@ Line 225: / Line 225: @@
 The Tile Library contains a number of related files, all of which are necessary to the use of the TMT&trade; and creation of Minisim&trade; environments:
-.	allTiles.txt – this text file contains a list of the tile library tiles and categories (configuration file for the TMT&trade;).
+#	allTiles.txt – this text file contains a list of the tile library tiles and categories (configuration file for the TMT&trade;).
-.	CD1 – A text file containing a list of the Tile Library Tiles used in the MOS.
+#	CD1 – A text file containing a list of the Tile Library Tiles used in the MOS.
-.	CD2 – A text file that defines the connective edges between tiles.
+#	CD2 – A text file that defines the connective edges between tiles.
-.	DDS – these are compressed texture files for use on the MiniSim&trade;.
+#	DDS – these are compressed texture files for use on the MiniSim&trade;.
-.	FLT – These are binary OpenFlight&trade; files that contain geometry and references to image texture files.  These files are necessary for MiniSim&trade; simulator operation.
+#	FLT – These are binary OpenFlight&trade; files that contain geometry and references to image texture files.  These files are necessary for MiniSim&trade; simulator operation.
-.	FTR – This is a TMT&trade; support file that contains all the tile references necessary for a terrain configuration including XYZ offset, rotation, and tile category type.  This file is necessary for MiniSim&trade; simulator operation.
+#	FTR – This is a TMT&trade; support file that contains all the tile references necessary for a terrain configuration including XYZ offset, rotation, and tile category type.  This file is necessary for MiniSim&trade; simulator operation.
-.	ICN – this is a binary file that is used for the TMT&trade; tile icon.
+#	ICN – this is a binary file that is used for the TMT&trade; tile icon.
-.	Intersection.map – a text file that contains terrain data and specifications for unique elevation maps applied inside intersections.
+#	Intersection.map – a text file that contains terrain data and specifications for unique elevation maps applied inside intersections.
-.	IVE – these are binary converted files optimized for MiniSim&trade; use.
+#	IVE – these are binary converted files optimized for MiniSim&trade; use.
-.	JPG – this is a binary snapshot view of the tile from an overhead view.
+#	JPG – this is a binary snapshot view of the tile from an overhead view.
-.	LatProfileList.lat – this text file contains all the lateral specifications for every road type.  It includes a cross-section profile and a material code index.
+#	LatProfileList.lat – this text file contains all the lateral specifications for every road type.  It includes a cross-section profile and a material code index.
-.	MOS – this binary file is a TMT&trade; project file, also referred to as a world or project file.
+#	MOS – this binary file is a TMT&trade; project file, also referred to as a world or project file.
-.	PATH/CORR – these are text data files that contain coordinate data describing either roads or intersection corridors.
+#	PATH/CORR – these are text data files that contain coordinate data describing either roads or intersection corridors.
-.	PET – this text file contains logical database tag information.
+#	PET – this text file contains logical database tag information.
-.	RGB, RGBA, DDS –binary image texture files.  The RGB and RGBA files may also have associated .attr files: these files are produced from the modeling environment tools and are not currently used by the TMT&trade; or MiniSim&trade;.  However, the RGB, RGBA and DDS files are necessary for MiniSim&trade; simulator operation.  These files will already be present in the MiniSim&trade; configuration, but additional (new) files must be copied to the proper location.
+#	RGB, RGBA, DDS –binary image texture files.  The RGB and RGBA files may also have associated .attr files: these files are produced from the modeling environment tools and are not currently used by the TMT&trade; or MiniSim&trade;.  However, the RGB, RGBA and DDS files are necessary for MiniSim&trade; simulator operation.  These files will already be present in the MiniSim&trade; configuration, but additional (new) files must be copied to the proper location.
-.	SUP – this binary file is used by the TMT&trade;.
+#	SUP – this binary file is used by the TMT&trade;.
-.	SurfaceMaterialSpecifications.xlsx – an Excel&trade; document that contains surface material codes for road surfaces.
+#	SurfaceMaterialSpecifications.xlsx – an Excel&trade; document that contains surface material codes for road surfaces.
-.	tileSizes.txt – this text file contains a list of tile library tiles and their dimensions, given in Tile Units (increments of 660 ft; a 1 x 1 tile = 660ft x 660ft).  Secondary configuration file for the TMT&trade;.
+#	tileSizes.txt – this text file contains a list of tile library tiles and their dimensions, given in Tile Units (increments of 660 ft; a 1 x 1 tile = 660ft x 660ft).  Secondary configuration file for the TMT&trade;.
-.	TXT – this text file contains TMT&trade; information.  The TXT file will be updated when the binary FLT file changes, and should remain read/write.  If you want to force the TMT&trade; to re-process the tile library or any particular tile, delete the TXT files and the TMT&trade; will re-create them.
+#	TXT – this text file contains TMT&trade; information.  The TXT file will be updated when the binary FLT file changes, and should remain read/write.  If you want to force the TMT&trade; to re-process the tile library or any particular tile, delete the TXT files and the TMT&trade; will re-create them.
 ==  '''Included Databases''' ==

@@ Line 248: / Line 248: @@
 The following is a list of databases installed with the TMT&trade; with general descriptions:
-.	day_night_01: A long environment containing urban, residential, highway and rural environment.  This database is designed for day or night use from the highway to rural area only.  The urban environment is a night-only area.
+#	day_night_01: A long environment containing urban, residential, highway and rural environment.  This database is designed for day or night use from the highway to rural area only.  The urban environment is a night-only area.
-.	day_night_snow_01: The same environment as day_night_01 but with snow effects and roadways for the highway and rural roads.
+#	day_night_snow_01: The same environment as day_night_01 but with snow effects and roadways for the highway and rural roads.
-.	nadsdemo_dsc: A demonstration database containing dry, wet, and snow environments.  This database includes a small urban area, a small rural area, and a small mountainous area.
+#	nadsdemo_dsc: A demonstration database containing dry, wet, and snow environments.  This database includes a small urban area, a small rural area, and a small mountainous area.
-.	nadsdemo_geospecific: A small, geo-specific database built to match a real-world location in Iowa.
+#	nadsdemo_geospecific: A small, geo-specific database built to match a real-world location in Iowa.
-.	nadsdemo_kiosk: A small, geo-typical database containing 3 separated environments.  Contains rural and urban environments.
+#	nadsdemo_kiosk: A small, geo-typical database containing 3 separated environments.  Contains rural and urban environments.
-.	simple_rural1: a basic, small rural environment
+#	simple_rural1: a basic, small rural environment
-.	simple_rural2: a basic, small rural environment with unique tiles enabled.
+#	simple_rural2: a basic, small rural environment with unique tiles enabled.
-.	rural_long: A simple rural environment intended for longer simulation drives.  It begins with a long, straight roadway and contains varying curves and hills, with some intersections and one cross-road.
+#	rural_long: A simple rural environment intended for longer simulation drives.  It begins with a long, straight roadway and contains varying curves and hills, with some intersections and one cross-road.
-.	test_all: A database that contains all the TMT tiles.  Tiles are connected to each other for each category, and connections have been forced.  This makes it possible to create a scenario for each tile category and to drive all the tiles, to become familiar with each tile and roadway type.  The original tile orientation has been preserved where possible.  Each tile category reads from top to bottom, left to right where possible.
+#	test_all: A database that contains all the TMT tiles.  Tiles are connected to each other for each category, and connections have been forced.  This makes it possible to create a scenario for each tile category and to drive all the tiles, to become familiar with each tile and roadway type.  The original tile orientation has been preserved where possible.  Each tile category reads from top to bottom, left to right where possible.
 <image_here>

@@ Line 277: / Line 277: @@
 A number of script utilities have been developed to assist with the terrain generation process. These files are located within the utils directory.  In addition to the scripts mentioned within this document, the following scripts are included:
-mlri.bat – This script will generate a .BLI file from a .LRI file, and is run from the same folder as the db_world.mos file.  The lri file can be published from the TMT&trade; or created using the lg.bat script.
+*lg.bat – This script will generate an LRI file from within the database project folder.  In order to use this script the TMT&trade; must have already published the tile models, and the user should also have created the db_world.scl file from the TMT&trade; tile models located in the flt folder.  This script is run from the same folder location as the db_world.mos file.
-view.bat – This script allows the user to review an object or tile model without having to create a database and scenario and driving them on the MiniSim&trade;.  The viewer is only for reviewing models, it cannot be used to review a scenario.  This command should be run from a command (DOS) window that is opened to the folder containing the models to be viewed.  In the event this command does not work, the user should run nadsconfig_system.bat and then use the osg_viewer.exe application to view the model, and then communicate the script failure to NADS so the error may be corrected.
+*mlri.bat – This script will generate a .BLI file from a .LRI file, and is run from the same folder as the db_world.mos file.  The lri file can be published from the TMT&trade; or created using the lg.bat script.
 ==  '''Lessons Learned: Things that can go wrong'''  ==