Skip to content

scripting and *uuid.dat files to maintain persistent mRID values#64

Merged
poorva1209 merged 7 commits intodevelopfrom
feature/mrid
Apr 14, 2020
Merged

scripting and *uuid.dat files to maintain persistent mRID values#64
poorva1209 merged 7 commits intodevelopfrom
feature/mrid

Conversation

@temcdrm
Copy link
Copy Markdown

@temcdrm temcdrm commented Dec 12, 2019

This feature will persist mRIDs in the network model for circuit components that didn't actually change. In Powergrid-Models, there are new *uuids.dat files that contain the established mRIDs, with scripts that use them and XML files that have the persisted mRIDs.

If you regenerate the CIM XML from unmodified source OpenDSS and GridLAB-D files, as described on the readme page, there should be no changes to the XML. Whenever there are changes to the source OpenDSS and GridLAB-D files, existing mRIDs will be used where possible, i.e., when the object classes and names match. If not, new mRID values will be created randomly and then saved in the *uuids.dat files.

Version 1.2.7 of opendsscmd is required from here: https://sourceforge.net/projects/electricdss/files/OpenDSSCmd/

Attached note describes how it works in opendsscmd.

App developers should see persistent mRID values for conducting equipment, connectivity nodes, terminals etc. However, this does not affect the house and measurement mRIDs, which are created by separate scripts outside of the network modeling process. In order to persist the house and measurement mRIDs, those external scripts need to be modified.
Common_Information_Model.pdf


This change is Reviewable

@poorva1209 poorva1209 merged commit eb8863a into develop Apr 14, 2020
@temcdrm temcdrm deleted the feature/mrid branch May 28, 2020 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants