Difference between revisions of "Outputs"
| Line 1: | Line 1: | ||
| − | If no Outputs tag is defined, all outputs are modelled and evaluated with the default CrossValidation measure. To change this default behaviour, one must specify an Outputs tag in the Run configuration. | + | There are three levels on which you can configure the way the different outputs in the simulator file are modeller. |
| + | |||
| + | === Default behaviour, all outputs modelled === | ||
| + | |||
| + | If no Outputs tag is defined in the configuration file, all outputs are modelled and evaluated with the default CrossValidation measure and target accuracy 0.001. Complex outputs are split into a real and imaginary part, and are modeller separately. | ||
| + | |||
| + | |||
| + | === Default behaviour, selected outputs modelled === | ||
| + | |||
| + | To change this default behaviour, one must specify an Outputs tag in the Run configuration. If you just want to omit outputs and want to keep the default modelling behaviour of the toolbox (CrossValidation, 0.001 accuracy), you only have to add an Output subelement for each output that you want modelled. | ||
| + | |||
| + | An example of such a configuration for the Academic2DTwice test function is: | ||
| + | |||
| + | |||
| + | <pre><nowiki> | ||
| + | <Outputs> | ||
| + | <Output name="out" /> | ||
| + | <Output name="outinverse" /> | ||
| + | </Outputs> | ||
| + | </nowiki></pre> | ||
| + | |||
| + | === Custom behaviour for all outputs === | ||
| + | |||
| + | If you also want to change or fine-tune the behaviour of the toolbox for each output separately, you can add subelements to each Output tag to customize the toolbox for that particular output. This allows you to use different sample selectors for each output, change the default measure, or combine multiple measures. | ||
| + | |||
| + | Several examples of valid Output configurations can be found commented in default.xml. | ||
Here is an example of an output configuration for the Academic2DTwice test function: | Here is an example of an output configuration for the Academic2DTwice test function: | ||
| Line 7: | Line 32: | ||
<Output name="out"> | <Output name="out"> | ||
<SampleSelector>gradient</SampleSelector> | <SampleSelector>gradient</SampleSelector> | ||
| − | |||
<Measure type="CrossValidation" target=".0001" use="on" /> | <Measure type="CrossValidation" target=".0001" use="on" /> | ||
</Output> | </Output> | ||
| Line 13: | Line 37: | ||
<Output name="outinverse"> | <Output name="outinverse"> | ||
<SampleSelector>grid</SampleSelector> | <SampleSelector>grid</SampleSelector> | ||
| − | + | <Measure type="CrossValidation" target=".05" use="on" /> | |
| − | <Measure type=" | + | <Measure type="MinMax" /> |
</Output> | </Output> | ||
</Outputs> | </Outputs> | ||
</nowiki></pre> | </nowiki></pre> | ||
| + | |||
| + | For each output that has to be modelled, an Output tag must be added. If a tag does not contain any Measure elements, that output is modelled using the CrossValidation measure and target accuracy 0.001. If you want to change this default behaviour, you can specify as many measures as you please. | ||
Revision as of 13:13, 27 June 2007
There are three levels on which you can configure the way the different outputs in the simulator file are modeller.
Default behaviour, all outputs modelled
If no Outputs tag is defined in the configuration file, all outputs are modelled and evaluated with the default CrossValidation measure and target accuracy 0.001. Complex outputs are split into a real and imaginary part, and are modeller separately.
Default behaviour, selected outputs modelled
To change this default behaviour, one must specify an Outputs tag in the Run configuration. If you just want to omit outputs and want to keep the default modelling behaviour of the toolbox (CrossValidation, 0.001 accuracy), you only have to add an Output subelement for each output that you want modelled.
An example of such a configuration for the Academic2DTwice test function is:
<Outputs> <Output name="out" /> <Output name="outinverse" /> </Outputs>
Custom behaviour for all outputs
If you also want to change or fine-tune the behaviour of the toolbox for each output separately, you can add subelements to each Output tag to customize the toolbox for that particular output. This allows you to use different sample selectors for each output, change the default measure, or combine multiple measures.
Several examples of valid Output configurations can be found commented in default.xml.
Here is an example of an output configuration for the Academic2DTwice test function:
<Outputs> <Output name="out"> <SampleSelector>gradient</SampleSelector> <Measure type="CrossValidation" target=".0001" use="on" /> </Output> <Output name="outinverse"> <SampleSelector>grid</SampleSelector> <Measure type="CrossValidation" target=".05" use="on" /> <Measure type="MinMax" /> </Output> </Outputs>
For each output that has to be modelled, an Output tag must be added. If a tag does not contain any Measure elements, that output is modelled using the CrossValidation measure and target accuracy 0.001. If you want to change this default behaviour, you can specify as many measures as you please.
