-
Notifications
You must be signed in to change notification settings - Fork 7
Home
See the companion MiscDocs Wiki for information about the receivers.
When using InSite GUI, whenever you save the project within the GUI, it saves corresponding XML files and place them in your project directory. This is sort of a preparation for using their command line softwares calcprop and wibatch.
The name of one of the most important of these XML files will be in the format: ProjectName.StudyAreaName.xml. For example, if the GUI project is model.setup and the study area is called "study", then the XML is named: model.study.xml
An example of running the wibatch.exe that used the mentioned XML command is as follows (from InSite Reference Manual):
"C:\Program Files\Remcom\Wireless InSite 3.1.0 \bin\calc\wibatch.exe" −f model.study.xml −out outputFolder
Obs: When using the GUI, this output directory is not specified by the user, but created as a subfolder of the project file location, with the name of the study area.
Our rwi-simulation code will take this model.study.xml and modify it, generating another XML file to be used as input to InSite. This is done also with other files (look at your config.py file).
Note that a similar copy + modify process applies also to changes in Tx / Rx pairs, etc. Assuming you changed the antennas of a Tx using the GUI. When you save, this change will be written in model.txrx for example (assuming model.setup is the GUI project). You need to provide model.txrx in config.py to properly generate the used files.
Some of the files that are inputs are: model.study.xml, model.txrx and model.object. The first two are generated by InSite GUI, while the other I do not know. It has information about materials and vehicles. The other mandatory file is random-line.object, it provides the position of the objects/vehicles generated using SUMO. The file model.vw is automatically generated and provides information about the visualization (azimuth, elevation, etc.)
Some of the files that are outputs: gen.model.txrx, gen.random-line.object and gen.study.xml. There is gen.study.diag too.
So, in summary, after making a modification using the GUI, you need to get the new XML and make sure it is being used by rwi-simulation to generate the actual XML that is adopted.
Below are some of the folders and files of interest, from a config.py:
setup_path = os.path.join(base_insite_project_path, 'model.setup') setup_path = setup_path.replace(' ', '\ ') #deal with paths with blank spaces base_x3d_xml_path = os.path.join(base_insite_project_path, 'model.Study.xml') paths_file_name = 'model.paths.t001_01.r002.p2m' simulation_info_file_name = 'wri-simulation.info' base_object_file_name = os.path.join(base_insite_project_path, "base.object") dst_object_file_name = os.path.join(base_insite_project_path, "random-line.object") base_txrx_file_name = os.path.join(base_insite_project_path, "base.object") dst_txrx_file_name = os.path.join(base_insite_project_path, 'model.txrx') dst_x3d_txrx_xpath = ("./Job/Scene/Scene/TxRxSetList/TxRxSetList/TxRxSet/PointSet/OutputID/Integer[@Value='2']" + "/../../ControlPoints/ProjectedPointList") dst_x3d_xml_path = os.path.join(base_insite_project_path, 'gen.Study.xml')