|
Size: 1631
Comment:
|
Size: 2254
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
A single procedure named "ccm" is used to ingest the MIB into both the operations and the CUS development databases. |
|
| Line 25: | Line 22: |
| Line 27: | Line 25: |
| The MIB must be already ingested into the database using the above procedure. Depending from the source for the initial CUS definitions two command options are available. * Using an existing version from the CUS CVS repository specified by a CVS tag name which is formed like a MissionConfigurationLabel. {{{ ccm -createmodel -usemib=MIB_LABEL -usecus=cvs=CvsTagName CVScomment }}} * Using the current CUS definitions from an existing (modifiable) instrumentModel in the database specified by an InstrumentModelLabel name. {{{ ccm -createmodel -usemib=MIB_LABEL -usecus=im=InstrumentModelLabel CVScomment }}} Each of these options will create an instrumentModel, load it with the specified MIB, load the requested CUS definitions (also updating the CVS repository) and create the first missionConfiguration for this new instrumentModel. Finally the property file will be updated with the new instrumentModel and missionConfiguration and the test-control server will be restarted. <!> '''Note:''' The CUS editor "cusgui" must be restarted to view (and edit) the new modifiable instrumentModel. == Publish CUS modifications for the current instrumentModel == Whenever you want to make the CUS modification edited with the CUS editor available for commanding you must commit your changes to the database to update the instrumentModel and you must use the following command to create a new missionConfiguration and make it available. |
|
| Line 28: | Line 54: |
| ccm -createmodel -usemib=MIB_LABEL -usecus=cvs=CVS_TAG comment | ccm -updatecus CVScomment |
| Line 31: | Line 57: |
| This command will create a new modifiable instrumentModel in the operations database. The corresponding MIB will automatically associated with this new instrumentModel. |
= Recovery Procedures = |
| Line 35: | Line 59: |
| The [:InstrumentModelLabel: instrumentModel label] in the database will be formed according the given [:MibLabels: MibLabel]. If there is already an instrumentModel with this label the command will fail. To create a new version use the ''--force'' option. {{{ createInstrumentModel --create MIB_LABEL --force }}} |
== Reloading a MIB for an already existing instrumentModel == |
| Line 42: | Line 61: |
| To load the initial CUS definitions (procedures and table) two options exist. Either copy the CUS definitions from an existing instrumentModel or use a tagged version from the CVS repository. {{{ createInstrumentModel --loadcus=cvs=tagname instrumentModelLabel }}} or {{{ createInstrumentModel --loadcus=instmodel=label instrumentModelLabel }}} |
== Ingesting a MIB version which is already in the database == |
Describe PACS/FM ILT Procedures/CCMprocedures here.
Standard Procedures
A new MIB (combination) is available and ready to be used
The MIB to be ingested can be specified in two different ways, either by the CVS MibTags or by the database MibLabels.
ccm -loadmib PACS_MIB_TAG EGSE_MIB_TAG CDMSSIM_MIB_TAG
or
ccm -loadmib=MIB_LABEL
The MIB loading does not affect any ongoing operation. It can be executed at any time.
A new (modifiable) instrumentModel shall be created using new MIB definition
The MIB must be already ingested into the database using the above procedure.
Depending from the source for the initial CUS definitions two command options are available.
Using an existing version from the CUS CVS repository specified by a CVS tag name which is formed like a MissionConfigurationLabel.
ccm -createmodel -usemib=MIB_LABEL -usecus=cvs=CvsTagName CVScomment
Using the current CUS definitions from an existing (modifiable) instrumentModel in the database specified by an InstrumentModelLabel name.
ccm -createmodel -usemib=MIB_LABEL -usecus=im=InstrumentModelLabel CVScomment
Each of these options will create an instrumentModel, load it with the specified MIB, load the requested CUS definitions (also updating the CVS repository) and create the first missionConfiguration for this new instrumentModel. Finally the property file will be updated with the new instrumentModel and missionConfiguration and the test-control server will be restarted.
Note: The CUS editor "cusgui" must be restarted to view (and edit) the new modifiable instrumentModel.
Publish CUS modifications for the current instrumentModel
Whenever you want to make the CUS modification edited with the CUS editor available for commanding you must commit your changes to the database to update the instrumentModel and you must use the following command to create a new missionConfiguration and make it available.
ccm -updatecus CVScomment
Recovery Procedures
Reloading a MIB for an already existing instrumentModel