...
To help with using this tool, we also implemented Functional Unit renaming allowing you to rename Functional Units before you or after a merge.
Replicate runner - Next phase
...
...
Jira Legacy server JIRA serverId c4ca6e0f-9f42-3d1a-879c-870abe699ab1 key RM-20242
<old notes from the first phase>
We have started to implement a replicate runner within Source for applications such as a risk of spill assessment.
...
Results can be used in custom charts and viewed in the Results Manager. .res.csv now includes meta data to identify the SubRunName that will be in the export.
There are a number of limitations we are continuing to work on. These will be available in future beta releases:
- All data sources are currently cycled, this will be specified in the future Data sources can now be selected (RM-20190),
- Annual Descriptive Statistics doesn't work with sub-runs, this will be the main summary statistics available will now with across sub runs (RM-20199),.
There are limitations we are continuing to work on. This will be available in future releases:
- Runs in series and not in parallel, which is an important performance improvement (RM-20178),Limited validation in User Interface (RM-20180)
Documentation is available here: Replicate analysis simulations in Source and will be incorporated into the documentation after the production release.
Plugin Developers
As we are moving to .net 6, we have now updated the .csproj format that is used by Source. Please see: Csproj Format to go through the conversion process.
...