Use sensor channel instead of file configuration #87
Conversation
josephmckinsey
changed the title
There was a problem hiding this comment.
I think this looks good, although I haven't tested it locally to see if it works as intended. Only question I have is about the output of the sensors. Is this just for the iee123 system or more generally? Is that why the naming change has been done for sensors?
| @@ -65,7 +64,7 @@ | |||
| "use_smartds": false, | |||
| "profile_location": "gadal_ieee123/profiles", | |||
| "opendss_location": "gadal_ieee123/qsts", | |||
| "sensor_location": "gadal_ieee123/sensors.json", | |||
| "sensor_location": "sensors.json", | |||
There was a problem hiding this comment.
Why is this location modified by the opendss and profile names still include the gadal_iee123 name?
There was a problem hiding this comment.
Ok I figured out what was happening here. The problem is this existing_feeder_file just out of frame.
We use the sensor_location in two different ways right now. In one way, we specify where the sensors are on AWS. In the other way, we use it put it on the channel. I was using it for both, which is why is became a problem.
Gets sensor information over a helics bus instead of a file. This makes it more robust in multi-container environments.