| 1 | === esarSectorPlan === |
| 2 | |
| 3 | Dumps CS commands and periodic SEC.Plan_Dump_Gate to sdrr message file |
| 4 | {{{ |
| 5 | Usage: esarSectorPlan -f fdswac.xml -a local_adapt sarfile[s] [ options ] |
| 6 | Extracts periodic sector plan dump from ERAM SAR and dumps CS messages required to achieve that sectorization from adapted default sector plan. |
| 7 | Dumps SDRR message file to stdout. |
| 8 | -f fdswac.xml file for national release that recorded the ERAM SAR |
| 9 | -a local adaptation to be used for base sector plan |
| 10 | -S starttime |
| 11 | -E endtime |
| 12 | }}} |
| 13 | example: |
| 14 | {{{ |
| 15 | esarSectorPlan -a /opt/adaptation/b1205ur0 -f ../SAR/fdswac.xml* `cat sector_sar` > sector.out |
| 16 | esarSectorPlan -a /opt/adaptation/b1205sr0 -f ../SAR/fdswac.xml* `cat sector_sar` > sector.out |
| 17 | }}} |
| 18 | notes: |
| 19 | {{{ |
| 20 | - the -a option specifies adaptation from which the 'base' sector plan is to be obtained (upon which sector reassignments will be made) |
| 21 | it should not matter which adaptation (site or TC) is used as long as sector plan is the same |
| 22 | - ERAM records a periodic SEC.Plan_Dump_Gate once per hour with complete sector/fav plan |
| 23 | - common use is to run esarSectorPlan on first hour of 'setup' SAR and trim out any CSes prior to sector plan dump, |
| 24 | retain CSes generated from sector plan dump, and retain any CSes after sector plan dump from merge.out |
| 25 | }}} |