Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

A starting point for docs related to: 

Jira Legacy
serverSystem JIRA
serverIdc4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432
keyRM-20086
 

Note: this will also need updating: Configuring Scenarios.

Existing scenarios

  • Add a new "Replicate analysis" configuration to the scenario in the configuration manager as outlined in Running Configurations Configuring Scenarios.
  • Select and edit the "Replicate analysis" running configuration from the running configurations drop down list
  • Run

...

The "Replicate analysis" running configuration includes the standard options for a "Single analysis" running configuration, and the following additional options:

OptionDescriptionExample
ReplicatesThe number of replicates that will be created / run.100
IncrementThe number of years to increment between each replicate.1
Start Cycle DateThe first data date that will be used to generate replicate data.1/1/1900
Start Report YearThe year that replicates will be reported as starting in. This must be less than or equal to the run start date's year.2000
End Report YearThe year that replicates will be reported as ending in. This must be greater than or equal to the run end date's year.2020

...

Results

The replicate analysis run will produce a single run with sub-runs for each replicate run. These can be used in custom charts. Results for the run and all sub-runs can be exported to res.csv or Source Db format. Individual sub-run results can be exported to res.csv, Source Db or other formats.

Notes and limitations:

  • All data sources in the scenario will be cycled according to the configuration options
  • All data sources should cover the same time period
  • Only whole years of data may be cycled
  • Any mismatches in data source length and/or partial year data will result in replicates using data from different years and/or months than intended
  • Results currently do not work with any statistics
  • Results cannot be saved in the project and reloaded
  • Exporting the run and sub-run results may not work for formats which don't support sub-runs (e.g. csv), and will not be able to be re-imported to Results Manager
  • Exporting of results from the command line runner is not supported