User Tools

Site Tools


executing_the_communicator

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
executing_the_communicator [2018/01/15 13:12]
andriesvanrenssen Views replaced to next section
executing_the_communicator [2018/02/02 22:51]
andries Example of a road network introduced
Line 10: Line 10:
 ==== DB Admin ==== ==== DB Admin ====
 === New network === === 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.  +If an update of the Gel_net_db database is 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\\ +This command ​will cause reading ​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.+The expressions in the files will be verified and the accepted expressions are integrated in a network of related things in an in-memory ​semantic network ​database.
 === Save net === === 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.\\+After completion of the import of files, the option 'Save net' can be used for exporting the in-memory database ​and storing the exported network in a new Gel_net_db database on a persistent storage medium as a binary Python Pickle file.\\
  
 ==== Read 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.\\  ​+Preparing Gellish expressions shall be done in one of the Gellish formalized languages conform the methodology that is described in the book '​Semantic Modeling Methodology'​. As demonstrator,​ the user can import the '​Semantic Model of a road network-UTF-8'​ file that is available via the website, together with a descriptive document.\\ ​  
 +Gellish files can be imported via the option 'Read file'​. ​Normally the program is started with the automatic import ​of the language definition. Thus reading files will automatically imply an addition to and integration with the existing language definition. Exceptionally,​ a manual start of the import ​of the (base) language definition shall be executed first via the 'DB Admin'​+ 'New network'​ option.\\  ​
 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.\\ 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)new version of the file, including the new UIDs is created. ​This extended ​newtwork ​can be stored on persistent storage, if required (via DB Admin + Save net).+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. ​Optionally the UIDs are preceded by a user specified prefix. If a file type is '​mapping',​ then a new version of the file, including the new UIDs is created. ​The content of read files is added to the semantic network. The extended ​network ​can be stored on persistent storage, if required (via DB Admin + Save net).
  
 After selection of the 'Read file' button, a new window will be opened that enables selection of one or more files.\\ After selection of the 'Read file' button, a new window will be opened that enables selection of one or more files.\\
Line 39: Line 40:
  
 === Left hand term === === 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.\\+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).\\ This information enables to distinguish between homonyms (the same term with a different UID) and it also shows possible synonyms (having the same UID).\\
 +When the '​Semantic model of a road network'​ is imported via the read file option, then it is recommended to try searching for concepts in that model, for example search for N51 or search for '​road'​.
  
 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.\\ 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.\\
executing_the_communicator.txt · Last modified: 2018/02/02 22:51 by andries