Versions Compared

Old Version 1

changes.mady.by.user Meryl McKerrow

Saved on

compared with

New Version Current

changes.mady.by.user Rohan Thomas

Saved on

Key

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

Beta release 4.2.4beta fully implements Ordering with Priorities, and delivers additional improvements for model management. 

Ordering with Priorities

/wiki/spaces/SD41/pages/25821535 allow users in Source to specify how shortfalls in a timestep are prioritised between different water requirements in /wiki/spaces/SD41/pages/25821997ordering systems. It is set at the scenario level and influences how water is supplied to supply points and minimum flow nodes, and released by storages and splitters down different paths. It aids in providing information on how water is supplied to users along regulated river reaches between regulating structures. Without a priority system enabled, Source will shortfall all demands equally within the model. 

Scenario Options, Ordering Priorities

Image Modified


Ordering priorities have now been fully implemented in this release, with splitters and storages now recognising the priorities of orders. The minimum operating constraint at a storage now only applies to water requirements of lower priority than the storage. 

Model Management

eWater's software development team understands the importance of maintaining good practice for version control of our software code.  We believe that these principles are of value to our Source users to help them manage their Source projects. We have implemented functionality to facilitate a Source project version control system.  This will help you identify project changes over time such as model configuration, inputs and results.  

Project Options, Project Summary Export

 

Using this option, you will get a file with a relative path to the project that is a summary of the project. e.g:
For scenario summaries, you can use Tools \ Export Summary. The summary file will be generated every time you save the project. When making a commit to a version control system, you should commit the Source project file as well as the summary file.
The Source /wiki/spaces/SD41/pages/25822777 format (.res.csv) has been improved to:
  • include more metadata,
  • use ISO date formats,
  • have a consistent column order, and
  • use quotation marks "" to encapsulate all fields that may contain a comma.

These changes make it independent of the operating system specified date and number formats which can help when running a project on a number of machines or in the cloud.

If you would like more information or help setting up a version control system to use with your Source projects, please contact us.

...

Full Release Documentation

Jira Legacy
serverSystem JIRA
columnstype,key,status,summary,assignee,reporter
maximumIssues150
jqlQueryproject in (RM, Insight) AND fixVersion = 4.2.4beta AND issuetype not in subTaskIssueTypes() AND (resolution not in ("Cannot Reproduce", Duplicate, "Won't Fix", "Parked for future work", "Not A Bug") OR status in ("Hydro Testing", "Scrum Testing")) ORDER BY status ASC, issuetype DESC, priority DESC
serverIdc4ca6e0fa22b5711-9f422728-3d1a3bcc-879c860f-870abe699ab12832d905a432