You are here: Manual / Scenario/ Sharing


Sharing Scenarios

When SEAMCAT workspace (version 3 and 4) is saved into a file with 'sws' extension, it includes in itself also all scenario information. Therefore any SEAMCAT workspace file by itself constitutes the shareable object, i.e. copies of the workspace file may be shared between SEAMCAT users wishing to discuss a particular scenario. This approach of saving workspaces as separate files is different from SEAMCAT-2 where all workspaces were kept as a part of an internal database, and if you wanted to share scenario with others, this had to be done via 'Scenario export' function, which was saving scenario information into a stand-alone 'txt' file.

When you are sharing your workspace containing your own plugin propagation model, do not forget to embed your propagation model. It is easier for users to share the information since the plug-in used in a specific workspace are not installed on the machine (without embedement), the default (e.g. Extended Hata) is used if the plug-in is not embedded in the workspace. If you still do not want to embed your plugins into your workspaces, follow the instruction on how to use your plugin without embeddement.

Note that it is also possible in SEAMCAT to re-create a scenario based on the scenario file, which was exported from SEAMCAT-2. This may be done through the menu option Legacy and Import of Scenario, then in file selection window browse to the 'txt' file containing scenario exported from SEAMCAT-2. Upon completion of import, SEAMCAT will notify you if any problems were encountered, e.g. specifying the line number, where data transfer action was not possible. However it is important that after importing the SEAMCAT-2 scenario,you review both victim and interfering links to inssure that the imported scenario is loaded correctly.