simul_run - User`s manual
Contents
1. op_runsim tool according to the specified options On the other hand the program will write several output files the most of them are really written by op_runsim ov os ef log ah and one more file generated by simul_run txt with information about the correspond ing simulation to be run Optionally if a cluster Condor is used cluster option the program simul_run will write the necessary files to launch jobs for running the simulations in parallel sh job dag and the execution of those jobs will write three more output files with messages and errors out err log The later will be written in a subdirectory below the current directory or working directory 3 3 1 Input files 1 Scenario model nt m The lt input file gt is the name of an OPNET model file option m The file name should be writen without the extension ov at the end If it contains blank spaces it should be specified within quotation marks If the scenario model specified is e g mymodel it is possible that several files will be used if the modelsuffixes is used mymodel 01 nt m mymodel 02 nt m The absolute path should be included in mod_dirs preference within OPNET The file will be searched by following the same order as in mod_dirs It is possible to specify a path for the specific file to consider i 11 simul_run User s manual which sets temporarily the mod_dirs prefe2. The following examples show how to use the simul_run program to run some typical sequence of simulations In the first one we assume that the scenario is composed of a set of nodes in which there are not any promoted attribute We are going to run the simulation of the scenario as is repeating it with five different seeds 10 20 30 40 50 in order to achieve a greater confidence degree The input file scenario is mymodel nt m and we will need to specify the list with the option seeds as shown simul_run m mymodel seeds 10 20 30 40 50 18 simul_run User s manual Please note that the nt m suffix should not be specified at the end because we are not specifying the file name but the corresponding model name By default the final nt m file used is determined by searching throught the paths listed in the mod_dirs preference within OPNET Modeler exactly in that order However you can force the file to be used by using the i opcion in order to specify the unique di rectory where to look for the nt m file as shown in the following example without needing to modify it within the OPNET Modeler GUI This directory can be either an obsolute or relative path to the working directory simul_run m mymodel seeds 10 20 30 40 50 i paper2011 models Similarly it can be specified the output directory with the options o or w That directory applies to the following output files In the following example such output
3. This can be do as explained in the following e Windows 98 or previous edit the C AUTOEXEC BAT file adding the follow ing line at the end It would be possible that the path needs to be enclosed within quotes if it is more than 8 characters length or it contains blanck spaces SET PATH PATH C Program files utils e Windows NT 2000 XP within the Control Panel choose System gt Ad vanced gt press the button Environment variables Then the path could be added to the PATH environment variable separated by a semicolon Alter natively the Autoexec NT file can be modified in a similar way as explained for the Autoexec bat file simul_run User s manual 2 3 Linux Let us suppose that the directory choosen for copying the simul_run program is SHOME bin Under Linux it is necessary to set the PATH and LD_LIBRARY_PATH environ ment variables In the later we should to add the path for the OPNET libraries as it is necessary in order to run programs compiled with the API EMA built with op_mkema This path depends on the home directory for OPNET and version The way to do that depends on the shell or command line interpreter used bash ksh Os e Linux shells bash ksh zsh sh HOME bash_profile or HOME profile PATH SPATH SHOME bin LD_LIBRARY_PATH usr opnet 16 0 A sys pc_intel_linux lib export PATH export LD_LIBRARY_PATH e Linux shells csh tesh SHHOME login
4. ef and with different random number seeds Perhaps the only manual step would be to prepare those ef files but they can be copied from a previous one created during a short simulation within the OPNET Modele GUI then changing the varying values in each case Another possibility would be to create our own program for the generation of such ef files In addition this program as the other ones within the simul_xxx package can be executed in a Condor cluster 2 by only specifing the cluster option In this way the user can execute so many simultaneous simulations as number of proces sors available limited also by the number of available OPNET Modeler licenses without needing any knowledge about launching jobs in Condor neither writing any script file needed by Condor job or dag files The set of programs simul_xxx contains the following command line tools e simul_geoloc used for generating network scenarios automatically computing the partition grade according to the transmission range e simul_ah2r used for converting the binary animation file ah to a text format as e simul_run used for program sets of simulations with OPNET Modeler without using the Graphical User Interface simul_run User s manual e simul_data used for extracting the data obtained with the simulations This program calls to ov2txt for each of the simulations run e ov2txt invoked from the simul_data for extracting data from t
5. Condor out err log during the execution of each job 13 simul_run User s manual For example if the scenario is mymodel these 5 extra files when using Condor will be named as following Note that for organization reasons these files will be written to a subdirectory named condorl1 under the output directory or working path the number 1 at the end mean the number of method used 1 script file condor1 mymodel 001 sh job file condor1 mymodel 001 job messages to stdout condor1 mymodel 001 out messages to stderr condor1 mymodel 001 err he E OS mesages from Condor condor1 mymodel 001 log As an example for a specific simulation e g 007 these 5 files would contain the following File condorl mymodel 007 sh i xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated condor_submit condorl mymodel 007 ob File condorl mymodel 007 job xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated Universe vanilla Nombre del ejecutable y argumentos Executable JOB_EXE Arguments JOB_ARGS Variables de entorno utilizadas por el proceso getenv True environment PATH common apps opnet 16 0 A sys unix bin environme
6. be similar to those in method 1 but named with a different subdirectory condor2 mymodel 001 out The contents of the unique script sh and dag files will be as shown below File condor2 mymodel sh xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated condor_submit_dag f condor2 mymodel dag maxjobs 20 File condor2 mymodel dag xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated 10 jobs JOB P1 condor2 mymodel 001 job JOB P1 condor2 mymodel 002 job JOB P1 condor2 mymodel 003 job JOB P1 condor2 mymodel 010 job PARENT P1 CHILD P2 P3 P4 P5 P6 P7 P8 P9 P10 Method 3 Parametrized DAG file In this last method only 3 files will be gener ated apart from the files generated by Condor out err log a template job which receives arguments from a dag file which contains the information of all the jobs to be launched and finally the script sh file that executes the dag file Similarly to the previous method 2 the maximun number of jobs can be limited if the number of simulations exceed the number of available OPNET Modeler licences 16 simul_run User s manual If the model is mymodel the three files will be named as condor3 mymodel sh condor3 mymode
7. files will be written to the subdirectory paper2011 results simul_run m mymodel seeds 10 20 30 40 50 i paper2011 models o paper2011 results Two options used frecuently are duration and probe_start_time which indicates the amount of time simulated and the start time for collecting the selected statistics respectively The probe_start_time is intended for allowing the sta bilization of the system Both values are measured in seconds simul_run m mymodel duration 360 probe_start_time 60 The simul_run program can run nearly silently or showing more messages by specifying the v option On the other hand by activating the option verbose_sim the op_runsim program will show periodic messages onto the screen during the simulations It is equivalent to the similar option that op_runsim can receive al though in this case it is not necessary to add true or false if that option is specified to simul_run it will be passed as verbose_sim true to op_runsim otherwise it will be passed as verbose_sim false Incase of using a cluster Condor all of those messages will be written to the out files generated by Condor In order to define sequences of simulations in addition to the option seeds ex plained above two more options are available modelsuffixes for using distint netwrok models named with a numeric suffix and ef for setting different values to any promoted attribute The sequence will have a number o
8. to op_runsim gt otherwise verbose_sim false will be sent to op_runsim anim_hist enable the animation within the simulations and be captured in animation history files ah WARNING these files could be huge NOTE contrarily to the corresponding op_runsim option the value true false should not be specified that is gt if it is specified anim_hist true will be sent to op_runsim gt otherwise anim_hist false will be sent to op_runsim all object files referenced by the network model will be recompiled and the repository rebuilt prior to running the simulations RECOMENDED NOTE recompilation only is performed before running the first Simulation in case of use a cluster for running parallel simulations the rest of the simulations within the simulation set will wait time enough before start to running m32 32 bit DES kernel will be used simul_run User s manual Simulations could use up to 4GB RAM in Solaris and 2 GB RAM in Windows 3 GB if the 3GB has been configured NOTE preferences should be used m64 Bot NOTE 64 bit DI preferences should be used distributed lt np gt this preference is mutually exclusive with m64 only one of these otherwise ES kernel will be used h the processor and operating syste this preference
9. 0 00 00 Run Remote Usage Usr 0 00 00 00 Sys 0 00 00 00 Run Local Usage Usr 0 00 00 00 Sys 0 00 00 00 Total Remote Usage Usr 0 00 00 00 Sys 0 00 00 00 Total Local Usage 84 Run Bytes Sent By Job 1593 Run Bytes Received By Job 84 Total Bytes Sent By Job 1593 Total Bytes Received By Job Method 2 DAG file Similarly to method 1 a job file will be created for each simulation but instead of creating a distinct script sh for each one in this case it will be created an unique script sh which will launch a unique dag file DAG Directed Aciclic Graph files allow to define a list ofjobs files and a set of dependences parent child between them in such way that the children jobs will wait until their parent job finishes In addition DAG files have the advantage that allow to limit the maximum number of simultaneous jobs which is necessary when there are more simulations to run that available OPNET Modeler licenses 15 simul_run User s manual So apart from the files generated by Condor out err log this method reduce nearly to the half the number of generated files because the number of job files will be the same and only one sh file will be generated For example if the model is mymodel files will be named as condor2 mymodel sh condor2 mymodel dag and the job files will be identical as in method 1 condor2 mymodel 001 job About the files generated by Condor out err log they will
10. SER_PARAM 1 VARS P10 JOB_USER_PARAM 2 PARENT P1 CHILD P2 P3 P4 P5 P6 P7 P8 P9 P10 File 17 simul_run User s manual condor3 mymodel job xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated Universe vanilla Nombre del ejecutable y argumentos Executable JOB_EXE Arguments JOB_ARGS Variables de entorno utilizadas por el proceso getenv True environment JOB_ENV Nombres para los ficheros de salida error y log Output condor3 JOB_FILENAMES JOB_ID out Error condor3 JOB_FILENAMES JOB_ID err Log condor3 JOB_FILENAMES JOB_ID log Configuracion para la transferencia de ficheros Transfer_Files Always should_transfer_files Yes when_to_transfer_output On_Exit Ficheros de entrada a transferir al nodo Transfer Input Files home user op_admin env_db16 0 JOB_FILENAMES JOB_USER_PARAM_ Ficheros de salida a transferir desde el nodo ransfer Output Files JOB_FILENAMES _promoted JOB_ID ef results JOB_FILENAME Notificaciones al usuario por correo electronico notification Never notify_user user umh es Ponemos en cola el proceso Queue 3 4 Examples
11. _des ef 4 Environment files for promoted values x5 mymodel_params 01 ef mymodel_params 02 ef mymodel_params 03 ef mymodel_params 04 ef mymodel_params 05 ef When executing a sequence of simulations it is possible that some of the simu lations fail or the user cancel it for any reason In those cases it could be useful to run a specific simulation or starting from the last simulation failed or aborted instead of repeating all the simulation set This can be achieved by specifying an interval with the options first and last For example the previous example run a simulation set composed of 75 simulations if for any reason we need to repeat the five ones 71 72 73 74 and 75 we can append the parameter first 71 to the command line If the time required to run a simulation set is high it is recommended to run the simulations in parallel if a cluster Condor is available with multiple processors The program simul_run allows to make use of the cluster easily only by appending the option cluster with the appropiate arguments So the user do not need the knowledge needed to launch jobs in such cluster The arguments for this option are the number of processors i e the maximum number of simulations simultaneously run and the method used to launch jobs explained previously in the section 3 3 2 With regards of the number of processors it is important to note that there exists the limitation of the number of OPNET Modeler licen
12. ce of simulations we have two possibilities e To use the Simulation Sequence Editor within the OPNET Modeler GUI which is shown when a new file is created File gt New File selecting Sim ulation Sequence as the type of file It also appears instead of the Config ure Run DES dialog box when the des configuration_mode preference is set to advanced e To write shell scripts Unix or batch files MS DOS which run outside the OPNET Modeler As it has been said before to use the GUI requires left less memory available to the simulations In addition the use of scripts is more flexible as they allow to run other commands before launching the simulations for example to write input files or arguments on the fly However in order to write scripts it is necessary to know the specific script language for the platform used MS DOS Unix and command line interpreter MS DOS Bourne shell sh o bash C shell csh Korn shell ksh As all of them are very different between them it is necessary to rewrite all the developed scripts in order to use other platform Moreover these languages have the drawbacks that they are very limited some more than others complicated and difficult to remember or understand syntax and the scripts are not easy to maintain Some sample scripts can be seen in the Simulation Scripts section or Simula tion Sequences gt Scripted Sequences in the on line OPNET Mode
13. ces available as each simulation need one In other words if our cluster has 96 processors and we own 20 OPNET Modeler licences available the maximum value specificed should be 20 a greater value will make that many simulations fail because of they can not get a license to run The cluster option admits two additional arguments in order to notify to the e mail specified when some event occur for example when a process final izes succesfully or aborted By default none event is notified as in the following example simul_run m mymodel modelsuffixes 1 3 ef 5 seeds 10 20 30 40 50 c cluster 20 3 Finally simul_run offers the posibility to specify the support for 64 bit platforms by default 32 bit with two mutually exclusive options m32 and m64 The distributed execution using several processors is also allowed by specifying the distributed option thanks to corresponfing options that OPNET Modeler of fers for that purpose still under development 20 Bibliography 1 Inc OPNET Technologies Opnet modeler 2 The Condor Team Condor 21
14. f simulations defined for the number of distinct combinations of those three lists sorted by the scenario name then the parameters file and finally the seed The following example shows how to define a simulation set using three distinct scenarios 5 environment files ef and 5 seeds So the sequence will be composed of 75 simulations 3x5x5 simul_run m mymodel modelsuffixes 1 3 ef 5 seeds 10 20 30 40 50 EC About the values specified with the options modelsuffixes and seeds they can be specified both by using an enumeration of values or a range between two values as can be seen in the previous example Note that it has been appended the option c at the end which force all the necessary models and object files to 19 simul_run User s manual be recompiled That option is recommended prior executing a simulation set in or der to be sure that all the files are update That option is only passed through to op_runsim in the first simulation Another posibility would be to manually exe cute the command op_mko al1l before launching the sequence It is necessary that the following files exist either in some of the paths defined in the mod_dirs preference of OPNET Modeler or in the path specified with the option i 1 Scenario models x3 mymodel 01 nt m mymodel 02 nt m mymodel 03 nt m 2 Stadistics x3 mymodel 01 pb m mymodel 02 pb m mymodel 03 pb m 3 Environment file for DES Parameters x1 mymodel
15. he binary vec torial files ov It can also be invoked for the user for extracting data for a particular simulation e simul_graphs used for generating graphs from the extracted data R or gnu plot e simul_reports used for generating a report containing the previously generated data and graph On the contrary to the conventional MS DOS Unix script languages these pro grams have been developed using the C programming language so it has been easy to migrate them to other platforms namely Windows and Unix like systems like Linux or Mac OS Currently OPNET Modeler is only available for Windows y Linux although perhaps it could be executed on Mac OS X by using X Chapter 2 Installation For the instalation of the simul_run program you only have to copy the binary to any directory and set some environment variables PATH and LD_LIBRARY_PATH In the following sections how to set these environment variables is explained 2 1 Requeriments The program simul_run requires that OPNET Modeler be installed as it makes use of the API External Model Access EMA Moreover the OPNET Modeler version installed should match with the one used for compiling this program which is spec ified in the name of the executable e g ov2txt 16 0 A bin 2 2 Windows Let us suppose that the directory choosen for copying the simul_run program is C Program files utils It is recommended to modify the PATH environment path
16. is mutually exclusive with m32 the last specified will be used m should support 64 bit only one of these otherwise the last specified will be used ejecucion distribuida de cada simulacion en varios S procesadores requier qu Arguments for the simulation set mode suffixes lt list gt Th with the same name but ef lt num file params gt values specifi modelsuffixes modelsuffixes 1 siste ma tenga multiple procesador numeric suffixes for using different scenario models different suffix at the end number of input environment files d in lt list gt can be an enumeration or a range 1 2 3 4 5 6 7 8 9 10 Tiss LO ef with values for the promoted attributes 1 200 NOTE beside thes f files one mor f file will be used with the DES parameters seed etc e g mymodel_des ef seeds lt list gt Th seeds 50 75 100 125 150 seeds 50 55 In order to use this option it seed finst lt n gt By default last lt n gt By defaul dont_run simulations to be run wit NOTE with all list of seeds to be used for generating random numbers values specified in lt list gt can be an enumeration or a range is necessary to comment the line with a index for the first since the first simul index for the last since the last t the arguments modelsuf possible combina Fo
17. is not used the current path or the working directory specified with the w option will be considered The options o and w are equivalents i e both produce the same results The difference between them is that w change temporarily the directory and with o the path is used when opening the files lt dir gt change the working directory Is the destination directory for output files ov os ef txt This directory can be relative to the current directory e g result or absolute e g home user op_models result By default the working directory is the current directory from the program simul_run has been executed It is equivalent to specify the output directory o option The w option is necessary when executing simul_run from a cluster title title or brief description for the simulation set to run It is only used for displaying information onto the screen or log files Arguments to pass through to op_runsim duration lt secs gt amount of time simulated in seconds probe_start_time lt secs gt simulation time before which no probing takes place in seconds se envia a op_runsim tal cual verbose_sim the simulation prints update messages to the standard output during the execution NOTE contrarily to the corresponding op_runsim option the value true false should not be specified that is gt if it is specified verbose_sim true will be sent
18. l dag and condor3 mymodel job and will contains File condor3 mymodel sh xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated ondor_submit_dag f condor3 mymodel dag maxjobs 20 SE O sk de SE SE de OSE de OSE OE File condor3 mymodel dag xxx WARNING xxx This file is automatically generated If you edit it your edits will be discarded next time the file is generated Se FF EHHH H H HE i 10 jobs j JOB P1 condor3 mymodel job VARS P1 JOB_ID 001 VARS P1 JOB_FILENAMES mymodel VARS P1 JOB_EXE common apps opnet 16 0 A sys pc_intel_linux bin op_runsim VARS P1 JOB_ARGS net_name mymodel seed 1 duration 360 ov_file results mymodel VARS P1 JOB_ENV PATH common apps opnet 16 0 A sys unix bin VARS P1 JOB_ENV PATH common apps opnet 16 0 A sys pc_intel_linux bin VARS P1 JOB_USER_PARAM_1 VARS P1 JOB_USER_PARAM_2 q E JOB P10 condor3 mymodel job VARS P10 JOB_ID 010 VARS P10 JOB_FILENAMES mymodel VARS P10 JOB_EXE common apps opnet 16 0 A sys pc_intel_linux bin op_runsim VARS P1 JOB_ARGS net_name mymodel seed 1 duration 360 ov_file results mymodel VARS P10 JOB_ENV PATH common apps opnet 16 0 A sys unix bin VARS P10 JOB_ENV PATH common apps opnet 16 0 A sys pc_intel_linux bin VARS P10 JOB_U
19. l spec ified is mymodel the generated files will be mymodel 001 log mymodel 002 log 5 Animation history files ah generated by op_runsim When the option anim_hist is specified a file is generated during the the simulation containing the positions of each node at any time If the scenario model specified is my model the generated files will be mymodel 001 ah mymodel 002 ah These animation history files ah contain binary data but they can be con verted into animation script files as encoded in an ASCII text file by using the op_cvanim reverse utility In this way they can be viewed within a stan dard text editor 6 Output log file txt generated by simul_run This simul_run program will generate a text file for each simulation run including some useful information namely the scenario model seed input output files complete command line etc If the scenario model specified is mymodel the generated files will be mymodel 001 txt mymodel 002 txt Output files using a cluster Condor The simul_run program invokes to op_runsim to run each simulation and waits until the end of that command to invoke it again that is simulations are executed sequentially However if a cluster Condor is used cluster option the simul_run program generates automatically all the necessary files for launching a job for each simulation and passe
20. ler documenta tion A typical situation is to run a sequence of simulations varying the seed value simul_run User s manual in order to achieve a high degree of confidence in the output mean statistic val ues For example the following script presented in that section can be rewrited to a DOS batch file bin csh seed_seq csh script to run simulations with a varying seed seedval 1 while seedval lt 101 echo Executing Simulation with Seed seedval op_runsim net_name mymodel seed seedval seedval seedval 1 end rem rem seed_seq bat batch file to run simulations with a varying seed rem rem S SEEDS 1 2 3 100 Qrem for seed in SSEEDSS do op_runsim net_name mymodel seed seed rem S SEEDS for 1 seed in 1 1 100 do op_runsim net_name mymodel seed seed rem The aim of the simul_run program is to define and run a sequence of simulations in an easier way and in the same manner in all the platforms Only is necessary to be familiarized with all the options required by simul_run and as it will be shown below a great part of those options are similar as used for op_runsim and they will be pass through to it With the execution of this program with the appropri ate arguments a complete simulations set varying the model scenario values for promoted attributes via different environment files
21. nt PATH common apps opnet 16 0 A sys pc_intel_linux bin Nombres para los ficheros de salida error y log Output condor1 mymodel 007 out Error condorl mymodel 007 err Log condorl mymodel 007 log 14 simul_run User s manual Configuracion para la transferencia de ficheros Transfer_Files should_transfer_files Yes Always when_to_transfer_output On_Exit t Ficheros de entrada a transferir al nodo notification notify_user es Notificaciones al Transfer Input Files home user op_admin env_db16 0 t Ficheros de salida a transferir desde el nodo Pransfer Output Fil mymodel_promoted 007 ef usuario por correo electronico Never user umh es Ponemos en cola el proceso results mymodel 007 ov mymodel nt m mymodel pb m myr results rt Queue lt lt lt Warning gt gt gt Time 13 41 52 Sun Jun 22 2008 Product Generic Product Package Vos Virtual Operating System x Function Function Name Unavailable Error Unable to set locale Spanish_Spain 1252 File will be parsed using current system locale setting 000 68071 000 000 05 13 19 26 46 Job submitted from host lt 193 147 148 245 32775 gt 001 68071 000 000 05 13 19 26 49 Job executing on host lt 192 168 100 23 33587 gt 005 68071 000 000 05 13 19 26 49 Job terminated 1 Normal termination return value 1 Usr 0 00 00 00 Sys 0 0
22. r example simul_run m mymodel That command means that 10 2 3 So 60 001 002 003 004 F005 006 007 in the DES simul ef file e g mymodel_des ef ation to run ation of the sequence simulatio n to run simulation of the sequence do not run any simulation f 2 just show information about the h the current specified arguments fixes f y seeds define a simulation set tions of the values specified let us suppose the following command E different scenarios environment files seeds simulations wi mymodel 01 nt m mymodel 01 nt m mymodel 01 nt m mymodel 01 nt m mymodel 01 nt m mymodel 01 nt m mymodel1 02 nt m be run my my my my my my my 3333333 odel odel odel odel odel odel odel modelsuffixes 1 10 seeds 50 75 100 he following will be used mymodel 01 nt m mymodel_params 01 ef 50 mymodel 10 nt m mymodel_params 02 ef 75 100 overall 10x2x3 _params 01 ef seed 50 _params 01 ef seed 75 _params 01 ef seed 100 _params 02 ef seed 50 _params 02 ef seed 75 _params 02 ef seed 100 _params 01 ef seed 50 10 simul_run User s manual 008 mymodel 009 mymodel 060 mymodel Arguments for run simu l O2 nt m mymodel l O2 nt m mymodel l 10 nt m mymodel ations in a cluster Condor clu
23. rence to that path 2 Selected statistics pb m If the scenario model specified is e g mymodel the file mymodel pb m will be searched using the OPNET mod_dirs pref erence too 3 Simulation DES parameters ef It will be a text file named as the model fol lowed by the suffix _des For example mymodel_des ef It contains the text got from the DES dialog within OPNET Modeler by pressing the Preview Simulation Set button The OPNET mod_dirs preference will be used too for looking the file 4 Values for promoted values ef The number of files specified with the ef option will be used for building a list of supplementary environment file names ef as follows The file names should contains the model name fol lowed by the suffix _params ef If the scenario model specified is mymodel mymodel_params 01 ef mymodel_params 02 ef until the lt num file params gt specified value If the value of lt num file params gt is 1 unique file the name will not include the index mymodel_params ef All of these files should ex ist and they will be used to define a simulation set together with the different scenario models and seeds 5 Trajectories for mobile nodes trj All the trj files assigned to the trajectory property of mobile nodes in the network This assignment can be done both directly in the model or in the ef files for promoted attributes 3 3 2 Outp
24. s the control to Condor finishing nearly immediately The cluster option allows to choose between 3 possibilities for launching jobs in Condor All of them have the same goal but do it in a different way generating more or less files 1 Independent jobs is the one that generates the greatest number of files 2 DAG file and 3 Parametrized DAG file is the method that generates the fewest number of files In the following each of the methods is detailed showing an example of every file generated in each case Method 1 Independent jobs In this method both a job file and a script file sh are created for each of the simulations to run The job file contains all the neces sary parameters for the simulation executable arguments files to transfer to and from Condor etc whereas the script sh include only the command line to launch the previous job file Then the simul_run program will invoke repeatly each script sh for queueing each job After a job is launched Condor write 3 more files 1 output messages out from the executed program op_runsim 2 error messages and warnings err from the executed program op_runsim and 3 messages from Condor log Thus in addition to the files generated by the programs simul_run and op_runsim enumerated in the previous section this method could generate a great number of files two per simulation run sh job generated by simul_run plus three more files generated by
25. setenv PATH PATH SHOME bin setenv LD_LIBRARY_PATH usr opnet 16 0 A sys pc_intel_linux lib Some Linux distributions have problems with the LD_LIBRARY_PATH and user cannot set the value This is why it is necessary to execute that each time that either you are going to execute the program or you open the console In order to simplify the process you can write a little script called ov2txt sh simi lar to the following and put it together to the binary In order to pass the arguments from the script to the executable you can use Se with the quotes instead of too bin sh export LD_LIBRARY_PATH usr opnet 16 0 A sys pc_intel_linux lib exec simul_run en 16 0 A x86 bin x Chapter 3 Usage of the program In this chapter the usage of the simul_run program is explained It is supposed that we have written the simul_run sh script explained in the previous chapter 3 1 Syntax simul_run simul_run m lt input file gt i lt input path gt o lt output path gt w lt working path gt v t lt title gt duration lt secs gt probe_start_time lt secs gt verbose_sim anim_hist c m32 m64 distributed lt np gt ef lt file des ef gt lt num file params gt modelsuffixes lt list gt seeds lt list gt first lt n gt last lt n gt dont_run cluster lt np gt lt met gt lt notif gt lt email gt 3 2 Description The simul_run program exec
26. simul_run User s manual Miguel Hernandez University 1 April 19 2011 1Copyright c 2008 P Pablo Garrido Abenza All rights reserved CL Abstract In this manual the installation and usage of the simul_run program is described which is included within the simul_xxx set of programs It has been developed by pgarrido umh es as a member of the GATCOM at the Contents 1 Introduction 3 2 Installation 2I REQUENA i s See e 16 do Sie aah ac soy Ge isa ee Wow Ge antalya ae Acme Hee 2 2 Windows 5 scsi ies da bed ee a N DD BS ee 3 Usage of the program A os be he Sa abe cay og ae omy Siete ey Se ahs He woah a en HE ah SN aoe ye my fac es A 3 2 Description errar wR HOR WR REE aeai 3 3 IGS 3 eu csaka esas ose les cdr Res de Qe ge Bede By ee Be ee a ae ae a 11 3 3 1 MOU Mes ode 224 224 ouk oboe hate eau ee 11 3 3 22 Output files sis 4 s neg be a bbe ee Ee BES ES 12 A si hao a ee ee ook oh ae Oe hh i a e San se ey Bk 18 Chapter 1 Introduction For executing simulations with OPNET Modeler 1 it can be used e The OPNET Modeler Graphical User Interface GUI e From the command line with the op_mksim or op_runsim tools Although using interactively the GUI is easier than the other options it has the disadvantage of the overhead of memory used by the graphical application itself whereas from command line more memory is available On the other hand in order to execute a sequen
27. ster lt np gt lt met gt cl in parallel lt notif gt lt email gt luster Condor l_params Ol ef seed 75 l_params Ol ef seed 100 l_params 02 ef seed 100 run the specified simulation set If simul_run is and this option is not specified the simulatio xecuted sequ The arguments lt np gt lt met gt lt notif gt lt e mail gt 3 3 Files ntially in the same processor for this option are number of p of simultan Since OPN licenses t available 1 method used 1 independe In Case the lt np gt metho there is no If that cas F ai rocessors to be used eous jobs Modeler users must ow icenses otherwise ma nt jobs 2 DAG number of simulations d 1 can not be used t enough OPN one per simulation executed in a cluster ns jobs will be maximun number np gt 0 n a number of valid that is he lt np gt value should be less or equal than the ny Simulations will fail to launch the necessary jobs in Condor 3 Parametrized DAG jobs be greater than as it could mean that ET licenses for them is detected method 2 will be used events to notify to the indicated lt email gt O Never 1 e mail addr Completed 2 3 ess to send t Errors Always he notifications The simul_run program will check if all the necessary input files nt m pb m ef trj exist before running any simulations invoking the
28. ut files 1 Output Vector files ov generated by op_runsim They contains vector data recorded from each simulation run If the scenario model specified is e g mymodel the generated files will be numerated with an numeric index mymodel 001 ov mymodel 002 ov 2 Output Scalar files os generated by op_runsim They contains scalar statis tic values recorded from one simulation min max It will be generated one os file for each simulation run If the scenario model specified is e g my model the generated files will be numerated with an numeric index mymodel 001 08 mymodel 002 0s 3 Output environment files ef generated by op_runsim It will be an envi ronment file that will save attribute requests for each simulation in the sim ulation set that is the real value assigned to each promoted attribute in the scenario model It is automatically specified by simul_run when invoking to op_runsim with the attr_reqs_attr option If the scenario model spec ified is mymodel the generated files will be mymodel_promoted 001 ef mymodel_promoted 002 ef These files allow to check if the real values assigned to each of the promoted attributes match with the intended values especified in the input environment files ef 12 simul_run User s manual 4 Output log files log generated by op_runsim If the scenario mode
29. utes a OPNET Modeler simulations sequence either se quentially or in parallel cluster Condor or distributed still under development The program allows to specify a set of scenarios to use different input parameters files input files ef and to set a list of seeds All of that define the simulations sequence to run in every distinct combination The program does not run interactively Instead the program begins to extract data immediately upon invocation and goes on until the process finishes without interruption Because of that it is necessary to specify some options when invoking the program These are the options to simul_run Overall arguments help paths shows this help v verbose mode i lt dir gt input directory for the input files nt m pb m ef 8 simul_run User s manual If this option is not used the input files will be searched in the paths specified in the mod_dirs OPNET preference in the same order The use of the i option has the advantage that the files processed will be the desired one as it could exists another files with the same name but in different path previously defined in the mod_dirs preference lt dir gt output directory Is the destination directory for output files ov os ef txt This directory can be relative to the current directory e g result or absolute e g home user op_models result If this option
Download Pdf Manuals
Related Search