[4775] | 1 | <model name="flddesc" title="Coupling field names" layout="flat"> |
---|
| 2 | <desc> |
---|
| 3 | Define here the coupling fields using the button "Add Coupling fields" |
---|
| 4 | and double clicking in the new row created. A "user reference name" must be given to each |
---|
| 5 | coupling field under "Field label" by filling the part "no label" |
---|
| 6 | and validated using the button "Enter" of the keyboard. This name will not appear in the namcouple and is only |
---|
| 7 | used by the GUI. |
---|
| 8 | The "load" button is useless for the OASIS3-MCT application.[] |
---|
| 9 | For each field, the symbolic name used in the source model and the symbolic name used in the target model |
---|
| 10 | must be specified as well as the associated source and target grids. |
---|
| 11 | It is also necessary to specify for each field if it is grouped or not and to which group it belongs using the names |
---|
| 12 | already defined in the Group window. |
---|
| 13 | Only the source and target symbolic field names and grid names will appear in the namcouple configuration text file.[] |
---|
| 14 | A blue (?), located at the right bottom of this window, gives more information on the data to fill up. |
---|
| 15 | </desc> |
---|
| 16 | </model> |
---|
| 17 | <model name="fldname" title="Field names" layout="flat"> |
---|
| 18 | <multiple name="flddef" title="Coupling fields" custom_label="Field label" size="1.5;1.5"> |
---|
| 19 | <info name="namefldgui" title="GUI Id (automatic)" default ="-"/> |
---|
| 20 | <param name="fldnamebef" title="Source symbolic name" type="string" /> |
---|
| 21 | <choice name="srcgrid" title="Source grid" type="string" require="grid_names_list"/> |
---|
| 22 | <param name="fldnameaft" title="Target symbolic name" type="string" /> |
---|
| 23 | <choice name="tgtgrid" title="Target grid" type="string" require="grid_names_list"/> |
---|
| 24 | <choice name="fldmult" title="Single or Group" default="single" require="mult_fields_name"> |
---|
| 25 | </choice> |
---|
| 26 | </multiple> |
---|
| 27 | <info name="field_names_list" title="List of the coupling fields" type="liststring" visibility="hidden"/> |
---|
| 28 | <docu> |
---|
| 29 | [section=Field names definition] |
---|
| 30 | In this window, you must enter the coupling fields exchanged by all the models. |
---|
| 31 | For each coupling field you must first enter a "user reference name" in the "no label" part. |
---|
| 32 | This "user reference name" is only used by the GUI and will not appear in the namcouple. |
---|
| 33 | Then for each coupling field, you must enter the symbolic name of the field used in the source model |
---|
| 34 | and the corresponding symbolic name of the field used in the target model. |
---|
| 35 | These names will appear in the configuration file.[] |
---|
| 36 | You must also specify for each field if it will be grouped or not and to which group it belongs using the names |
---|
| 37 | already defined in the Group window. |
---|
| 38 | |
---|
| 39 | If the field is read or written from/to a file, the target field name will be renamed automatically when writting the |
---|
| 40 | configuration file as the source and target symbolic names must be identical. In this case no transformations or |
---|
| 41 | only LOCTRANS transformations are allowed. |
---|
| 42 | |
---|
| 43 | More details on coupling fields are avalaible in the User Guide section 3.3 and section 5.3. |
---|
| 44 | </docu> |
---|
| 45 | </model> |
---|
| 46 | |
---|
| 47 | |
---|
| 48 | |
---|
| 49 | |
---|
| 50 | |
---|
| 51 | |
---|
| 52 | |
---|