| | 1 | == NSDA Ops Eval (SIG1552) == |
| | 2 | |
| | 3 | === Scenario Locations === |
| | 4 | * sdrr4:/usr/local/scenarios/NSDA-Ops-Eval |
| | 5 | * sdrrdc:/usr/local/scenarios/NSDA-Ops-Eval |
| | 6 | |
| | 7 | === SDRR Bring Up === |
| | 8 | * For TB4 |
| | 9 | * Login to '''sdrr4''' as task23/task50 |
| | 10 | * cd NSDA-Ops-Eval |
| | 11 | * Launch sdrr: ./runsdrr |
| | 12 | * SDRR launches with the scenario loaded. No msg injector needed. |
| | 13 | |
| | 14 | === Altys Bring Up === |
| | 15 | * Open rdesktop as peer3 |
| | 16 | * Open the ''RUNALTYS - Shortcut'' folder |
| | 17 | * Select: ''NSDA-Ops-Eval.bat'' |
| | 18 | |
| | 19 | === Additional Notes === |
| | 20 | * Ensure that Altys and the scenario injector are started as close to the same time as possible. If Altys is started too far ahead of sdrr scenario then the logins will be entered before flight plans which will cause them to be rejected. |
| | 21 | |
| | 22 | [[BR]] |
| | 23 | [[BR]] |
| | 24 | back to: DatacommProcedures |
