User Tools

Site Tools


executing_the_communicator

Executing the Communicator

When the Communicator.py module is executed it automatically imports the Formal Language definition database Gel_net_db, when available, and it presents the Main Window as follows: Main Window

The GUI language field can be used for switching the language of the user interface (the GUI language) between English and Nederlands (Dutch). The GUI language is initially set to English. The GUI language is independent of the language of the information models (the modeling language) and also independent of the language in which the query results are presented and exported (the reply language). The modeling language is determined by that Gellish expressions themselves. The reply language is by default the same as the GUI language, but it can be set in the Query Window.

The green area will be used for the display of various query result views.

DB Admin

New network

If the Gel_net_db database is not yet available, then a new database can be created via selecting the option DB Admin + New network. This will read the files that are specified in Bootstrapping.py
The expressions in the files will be verified and the accepted expressions are integrated in a network of related things in an in-memory database.

Save net

After completion of the import of files, the option 'Save net' can be used for exporting the in-memory database storing the exported network in a new Gel_net_db database on a persistent storage medium as a binary Python Pickle file.

Read file

Additional Gellish files can be imported via the option 'Read file'. This should be done after the automatic import or after import via the 'DB Admin'+ 'New network' option that imports the (base) language definition.
A Gellish file should be compliant with the Gellish Expression Format as a CSV or JSON file and be expressed in Unicode UTF-8 encoding.
If there are missing UIDs for the objects in the file, new UIDs will be added in the range that is indicated on the first line or in a default range (NOT YET FULLY IMPLEMENTED at 24 October 2017). A new version of the file, including the new UIDs is created and can be stored on persistent storage, if required).

After selection of the 'Read file' button, a new window will be opened that enables selection of one or more files.

Imported files will be verified and the correct expressions will be added as extensions to the database network in memory. The extensions are not automatically stored in the Gel_net_db database on a persistent storage medium. This enables that the entered files are modified after import and it enables re-starting the program and the re-reading the modified files, and thus recombining the content of the files with the language definition database.
If it is required to extent the database on a persistent storage medium, then the 'Save' button under the 'DB Admin' option should be used.
Note that this will overwrite the Gel_net_db database. Thus, first save a copy of the Gel_net_db database under a different name.

Query

The Query button will open a Query Window as follows: Query Window

Reply language

At the top right corner of the Query Window the reply language can be set. The reply language is the language in which the query results will be presented in the various views. The reply language may differ from the GUI language as set on the Main Window. By default the reply language is set the same as the GUI language. Queries are expected to be formulated in the GUI language.
If the reply language is set to a particular language, say German, then the views of the resulting models will depend on the availability and completeness of the dictionary in that language. The terms in the views will be primarily selected from the 'international' dictionary (with names that are language independent), then from the specified language (say German) and if not yet found, then terms will be displayed in English.

Left hand term

The left hand term field of the Query Window (initially filled with a question mark (?)) can be used to enter search string or a combination of strings that are separated by a blank space. The list of found candidates strings is displayed in a lower box under the header 'Select one of the following options'. The list of candidates shows not only the candidate terms, but also the UIDs of the objects for which the strings are names, their 'Kind' (being a name of a classifier or a supertype of the candidate object), the 'language community' of the candidate terms and the language of the terms.
This information enables to distinguish between homonyms (the same term with a different UID) and it also shows possible synonyms (having the same UID).

Selection of the required candidate by a double click will show the full name in the 'Left hand term' field, its UID in the UID field and a textual definition in the 'Def. of left hand object' field.

Model views

or

Query spec

After selection of the candidate left hand term in the Query Window there are several options to proceed:

  1. Pressing the 'Confirm' button will execute the Query and present several product or process model views under different tag names in the Main Window. Those views enable the further detailed selection of information.

Case Sensitive and First Char Match

The check button 'Case Sensitive' in the Query Window (when selected) indicates that the 'Left hand term' search string is case sensitive.
The check button 'First Char Match' (when selected) indicates that the candidate strings should start with the same characters as the search string.

Modify

This option is not implemented yet.
It is meant for editing a file with Gellish Expressions.
Modification of a model is implemented (partly) by inserting in a Product View.

Stop

The 'Stop' option terminates the execution of the Gellish Communicator program.

executing_the_communicator.txt · Last modified: 2017/11/15 11:15 (external edit)