Fortuna 2.4 User's Guide: Difference between revisions

Line 205:

[....]

The ~~field~~ <code>EXPID</code> must match the name of the experiment <code>HOME</code> directory; this is only an issue if you copy the <code>HISTORY.rc</code> from a different experiment. The <code>EXPDSC</code> ~~field~~ is used to label the plots. The <code>COLLECTIONS</code> ~~field~~ contains list of strings indicating the output collections to be created. The content of the individual collections are determined after this ~~field~~. Individual collections can be "turned off" by commenting the relevant line with a <code>#</code>.

The attribute <code>EXPID</code> must match the name of the experiment <code>HOME</code> directory; this is only an issue if you copy the <code>HISTORY.rc</code> from a different experiment. The <code>EXPDSC</code> attribute is used to label the plots. The <code>COLLECTIONS</code> attribute contains list of strings indicating the output collections to be created. The content of the individual collections are determined after this list. Individual collections can be "turned off" by commenting the relevant line with a <code>#</code>.

The following is an example of a collection specification:

Line 229:

</pre>

The individual ~~specification fields~~ are described below, but what users modify the most are the <code>fields</code> ~~specification~~. Each ~~entry~~ is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it. The entries with a third column include the name by which that export in saved in the collection file.

The individual collection attributes are described below, but what users modify the most are the <code>fields</code> attribute. Each field is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it, separated by a comma. The entries with a third column include the name by which that export in saved in the collection file.

== Optimizing a Run ==

@@ Line 205: / Line 205: @@
 [....]
-The field <code>EXPID</code> must match the name of the experiment <code>HOME</code> directory; this is only an issue if you copy the  <code>HISTORY.rc</code> from a different experiment.  The <code>EXPDSC</code> field is used to label the plots.  The <code>COLLECTIONS</code> field contains list of strings indicating the output collections to be created.  The content of the individual collections are determined after this field.  Individual collections can be "turned off" by commenting the relevant line with a <code>#</code>.
+The attribute <code>EXPID</code> must match the name of the experiment <code>HOME</code> directory; this is only an issue if you copy the  <code>HISTORY.rc</code> from a different experiment.  The <code>EXPDSC</code> attribute is used to label the plots.  The <code>COLLECTIONS</code> attribute contains list of strings indicating the output collections to be created.  The content of the individual collections are determined after this list.  Individual collections can be "turned off" by commenting the relevant line with a <code>#</code>.
 The following is an example of a collection specification:
@@ Line 229: / Line 229: @@
 </pre>
-The individual specification fields are described below, but what users modify the most are the <code>fields</code> specification.  Each entry is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it.  The entries with a third column include the name by which that export in saved in the collection file.
+The individual collection attributes are described below, but what users modify the most are the <code>fields</code> attribute.  Each field is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it, separated by a comma.  The entries with a third column include the name by which that export in saved in the collection file.
 == Optimizing a Run ==