Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

When you open a library from the workspace menu you will have the following interface (below is the antenna interface).

Figure 280: Example of the antenna interface library

 

All the library elements follow the same command feature . They are available for you to:

  • Create a new antenna, click on 
  • Delete an existing antenna, select it in the list and click on 
  • Duplicate an existing antenna, select it in the list and click on . Reference of the new antenna is derived from the reference of the selected one by incrementing the integer suffix of that reference, if any, or adding character '1' to the end of the original name.
  • Reload the pre-defined libraries (it will delete any entries that you may have made), click  ;
  • Get on-line help click 

 

When adding a new elements, you need to enter the name (unique identifier), description of the elements as well as its technical parameters.

Note: Tooltip are available on the button to remember their meaning  

Once you have created a broad library of various elements, it might be especially useful to exchange this data, e.g. share with other members of the team working on studies of similar radiocommunications systems.

To share the created library, an export file may be created by using command Export Library in menu section File. When selecting this menu option, you will be offered a choice of defining the file name and the entire current library and a library copy will be unloaded to that file.

 

Figure 281: General import/Export library

 

The SEAMCAT library exchange files are saved using XML format and with unique file extension .sli (for Seamcat Library). Such library export file may then be distributed within the group of users and may be uploaded by any users via command Import Library on the File menu.

In case of collision of imported and existing library element names (e.g, there will always be a collision between the DEFAULT library elements saved in an exchange file and those existing in target SEAMCAT copy), you will be given a choice of either overwriting the existing elements, or importing colliding elements with different names.

  • No labels