Debug Options

Edit Overlays

Selecting this displays the sim_map_overlay Form . This interface allows the user to create, edit or delete the overlays available for drawing on the screen when Data Driven Overlays is selected. Click here for more information.

Test Graphics

When this element is queried the Graphics Element Form appears allowing the user to enter the Class name. Basically this is a programmer interface for testing the display of various graphical items and shouldn't be of general interest.

Review FORCES Constants

This is a programmer interface to review the constants defined throughout the FORCES model. When initially picked the REVIEW GLOBAL CONSTANTS Form appears which allows the Forces Constants to be reviewed a specific procedure may be found by executing a search via four methods:

All of these fields are optional - just leave them blank unless you want to filter the results.  If you just want a general list of all registeres constants in the FORCES system just click on "Go" and the entire list will appear. The above four options were added to help the user sort through the list for data specific to his needs. The search criteria must be in SQL-compliant format (the data is stored in the adilib database). For exmaple, if the user wants to restrict his search to only constants pertinent to sensor tasking he could enter "='sensor_tasking'" and then selsect "Go", as shown in this example . The four search fields are cumulative, that is the "Value Search Criteria" field could be set to "='1'" while leaving the FileName Search Criteria as set in this example and only one line would be retrieved.

Note - You should confident that FORCES registered constants are in this list. This approach differs from most programmer documentation because the data retrieved comes from the same database tables that are used for the autogenerated code that defines the FORCES C, Fortran and TCL header files. Thus the information displayed is the code source, not an after-programming document that can get outdated quickly. This is true for all fields except the description; here you're at the mercy of the programmer. Also note that this data covers only registered FORCES constants. While this includes most constants used throughout FORCES some constants (especially in legacy applications that have been incorporated into FORCES) use more standard C or FORTRAN definitions and thus are not included in this list.

Review FORCES Public Structures

This permits the programmer to review the registered structures employed in FORCES. The Review Public Forces Structure appears.  This interface's functionality shares a lot with the " Review FORCES Cnnstants" interface described above, so the functionality will not be belabored here. In short, if you're uncertain where to begin just leave the search criteria fields blank and select the "Get Structure Names" button for the short description, or the "Get Structure Details" for the full description.  

Again, the data being listed comes directly from the source used to generate the FORCES C, FORTRAN and TCL structures using the functions in the Autegen directory, so a lot of confidence can be placed upon the results (with the possible exception of the description field) being up-to-date and accurate.

Review Forces ICDs

This interface permits the programmer to review the messages employed internally to FORCES. This is Form entitled REVIEW FORCES ICD Form allows the user to search for a specific message by either Message Name or Description. This interface's functionality shares a lot with the "Review FORCES Cnnstants" interface described above, so the functionality will not be belabored here. In short, if you're uncertain where to start, just leave the search criteria fields blank and select "Go".  The only special comment is that clicking on a specific message will result in another window being produced that defines all of the message's fields.

Again, the data being listed comes directly from the source used to generate the FORCES C, and FORTRAN message structures using the functions in the Autegen directory, so a lot of confidence can be placed upon the results (with the exception of the description field) being up-to-date and accurate. There is a caveat with this interface, however. A number of early messages where hardcoded in FORTRAN and the supporting data is not yet incorporated into the database. In these cases the field definitions are not available though this interface. This is being remedied.

Review Forces Data Dictionary

The purpose of this interface is to describe the database tables and relations employed within the two key types of FORCES databases; namely the master control database and scenario database(s). This selection will bring up the form entitled REVIEW FORCES DATA DICTIONARY Form, allowing the user to review the data already entered or to search for specific data by querying the system to find it by:

It is particularly useful to enter either "='adilib'" or "='scenario'" in the "Database Name Search Criteria" field and then selecting "Go". The first will provide a description of the master control database, the scecond the schema for any scenario database. The results have more information as well. Clicking of many tables will specify the table relationships for that table. Click here for an example. This information provides information on whether another table is a slave or master of the current table, the fields used to join the tables, and the relationship.

While efforts are made to keep this information up to date, the information that this report comes from is not used in autogeneration, so it's not guarnteed to be up to date. For a guaranteed accurate table list and specification use either the db_tables_and_columns utility or database-specific tools, e.g. pg_dump for Postgres.

Edit TCL Procs Programmer Documentation

Choosing this option first requires the user enter his password. Then a form entitled: EDIT TCL DESCRIPTIONS Form appears which allows the user to Edit TCL Procedures. Each procedure is listed along with its filename (e.g. Menu.utilities.tcl) and description (e.g. Creates a simple TBD window whenever a user hits a button (or equivalent) ties to the command TBD)

Review TCL Procs Documentation and so on...

Other interfaces of the same type are being developed for other programmer references. At this time they're not very well populated.

Report SDRs & Review SDRs

Heck, nobody's perfect. The SDR Entry Form interfaces help the user either enter Software Deficiency Reports (trouble tickets) into the system or review the status of SDR's currently being worked. Before using these verify that the "sdr" entry in your odbc interface (usually ~/.odbc.ini) is set to the FORCES central database. Call for this information. Also, this will only work if you're on the Internet. We have alternative methods for entering this information for secure installations. Call and we can discuss what would be best in your situation.

Source TCL File & Issue TCL Command

The FORCES environment incorporates significant Tcl/Tk code. There are a wide variety of benefits to the language, including the ability to create and execute new procedures dynamically during a scenario execution. This supports rapid-prototyping as well as a superior debugging environment. These interfaces support these uses.

Choosing "Source TCL File" will open the Open Form that the user may use to choose a file to learn the source. The TCL code in the selected file will be sourced and any previous procedures defined within this file will be replaced in memory with the current contents of the file. Notification will be given that the file was sourced in the Message Area of the Forces Master Controls widget.

Selecting "Issue TCL Command" will make the Interactive TCL Interface Form appear. The user can either:

This allows the programmers to rapidly modify and test code and/or interfaces. His inputs are kept in the white area so he can copy them to a file if desired to save his changes permanently.

This dynamic environment is supported though employment of Tcl/Tk. For more on Tcl/Tk go to //www.scriptics.com

SSNORR Interface

Not available in most installations.