Delay between call to HelicsPublication.publish() and value update #1926
-
|
I originally asked about this on the gitter, and I thought I had it solved, but apparently not. I've got the problem down to a pretty simple example and captured some logs. I have two value federates, one managing an opendssdirect simulation, and the other managing a controller for a storage device in the opendss simulaiton. The controller federate subscribes to voltage from the grid federate and requests Sometimes, there will be anomalous spikes in the total power and voltage on the grid. I was finally able to capture logging output when one of these spikes occurred, and I think I've identified the cause. Here is a summary of the events around the spikes:
Am I missing some API call that is needed to ensure the power publication is updated at the same time as the call to Federate configsGrid Federate{
"name": "grid",
"core_name": "grid_core",
"log_level": 7,
"core_type": "zmq",
"time_delta": 1.0,
"subscriptions": [
{
"key": "S1/power",
"unit": "kW",
"type": "complex",
"default": 1.0
}
],
"publications": [
{
"key": "total_power",
"unit": "kW",
"type": "complex"
},
{
"key": "storage.S1.soc",
"unit": "",
"type": "double",
"default": 1.0
},
{
"key": "storage.S1.voltage",
"unit": "pu",
"type": "double",
"default": 0.0
},
{
"key": "storage.S1.power",
"unit": "kW",
"type": "complex"
}
]
}Storage Controller{
"name": "S1",
"core_name": "s1_core",
"log_level": 7,
"core_type": "zmq",
"time_delta": 1.0,
"wait_for_current_time_update": true,
"subscriptions": [
{
"key": "grid/storage.S1.soc",
"unit": "",
"type": "double",
"default": 0.5
},
{
"key": "grid/storage.S1.voltage",
"unit": "pu",
"type": "double",
"default": 1.0
}
],
"publications": [
{
"key": "power",
"unit": "kW",
"type": "complex"
}
]
}grid.logTimes shown in storage.log |
Beta Was this translation helpful? Give feedback.
Answered by
trevorhardy
Sep 3, 2021
Replies: 2 comments 1 reply
-
|
@wfvining, sorry for missing this when posted all these months ago. If you're still experiencing the problem I'd be happy to look into it with you. I'd also recommend that you upgrade to HELICS v3 (assuming you're going to be using HELICS for a while still). |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks @trevorhardy. @phlptp picked this up on a different thread a little while back and I believe it was resolved along with some other timing fixes at that time. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I'll close this one out for now. Glad to hear we got it fixed. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
trevorhardy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OK, I'll close this one out for now. Glad to hear we got it fixed.