Jeffrey-Simpson
commented
4 years ago I don't know about REST error.
But does the tap pos change?
The outage event should like this if you are sending it from the Simulation run configuration: Outage_event = { "allOutputOutage": False, "allInputOutage": False, "inputOutageList": [{"objectMRID": ""_CE091BBD-77FD-4E8D-8815-EEF79D540108", "attribute": " TapChanger.step"}, ], "outputOutageList": [], "event_type": "CommOutage", "occuredDateTime": 1358179260 "stopDateTime": 1358180260 }
Thanks, -Jeff
From: Brandon Thayer notifications@github.com Reply-To: GRIDAPPSD/gridappsd-forum reply@reply.github.com Date: Friday, November 8, 2019 at 2:18 PM To: GRIDAPPSD/gridappsd-forum gridappsd-forum@noreply.github.com Cc: "Simpson, Jeff" Jeff.Simpson@nrel.gov, Mention mention@noreply.github.com Subject: [GRIDAPPSD/gridappsd-forum] Regulator outage event doesn't work and platform throws error (#49)
https://github.com/Jeffrey-Simpson https://github.com/craig8 https://github.com/poorva1209 Platform version: v2019.10.0 Simulation run configuration: {
"power_system_config": {
"GeographicalRegion_name": "_73C512BD-7249-4F50-50DA-D93849B89C43",
"SubGeographicalRegion_name": "_A1170111-942A-6ABD-D325-C64886DC4D7D",
"Line_name": "_AAE94E4A-2465-6F5E-37B1-3E72183A4E44"},
"application_config": {
"applications": []},
"simulation_config": {
"start_time": "1358179200",
"duration": "1200",
"simulator": "GridLAB-D",
"timestep_frequency": "1000",
"timestep_increment": "1000",
"run_realtime": true,
"simulation_name": "ieee8500",
"power_flow_solver_method": "NR",
"model_creation_config": {
"load_scaling_factor": "1",
"schedule_name": "ieeezipload",
"z_fraction": "0",
"i_fraction": "1",
"p_fraction": "0",
"randomize_zipload_fractions": false,
"use_houses": false
}},
"test_config": {
"events": [
{
"message": {
"forward_differences": [
{
"object": "_CE091BBD-77FD-4E8D-8815-EEF79D540108",
"attribute": "TapChanger.step",
"value": 10
}
],
"reverse_differences": [
{
"object": "_CE091BBD-77FD-4E8D-8815-EEF79D540108",
"attribute": "TapChanger.step",
"value": 5
}
]
},
"event_type": "ScheduledCommandEvent",
"occuredDateTime": 1358179260,
"stopDateTime": 1358180260
},
{
"allOutputOutage": false,
"allInputOutage": false,
"tag": "mc45mjk2",
"inputList": [
{
"name": "vreg3_a",
"type": "Regulator",
"mRID": [
"_CE091BBD-77FD-4E8D-8815-EEF79D540108"
],
"attribute": "TapChanger.step",
"phases": [
{
"phaseLabel": "A",
"phaseIndex": 0
}
]
}
],
"outputList": [],
"event_type": "CommOutage",
"occuredDateTime": 1358179260,
"stopDateTime": 1358180260
}
],
"appId": ""},
"service_configs": []
} As can be deduced from the run configuration, the regulator position change and lockout should occur 60 seconds into the simulation. At that time (I can tell from my own logs), the platform errors out: Thread-54 ERROR [gov.pnnl.proven.api.exchange.RestExchange] -
Error while calling REST Service
Thread-54 ERROR [gov.pnnl.proven.api.exchange.RestExchange] - Exception: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1098)
at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:883)
at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:767)
at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
at org.glassfish.jersey.internal.Errors.process(Errors.java:229)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414)
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:765)
at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:456)
at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:357)
at gov.pnnl.proven.api.exchange.RestExchange.addProvenData(RestExchange.java:293)
at gov.pnnl.proven.api.producer.ProvenSession.sendMessage(ProvenSession.java:191)
at gov.pnnl.proven.api.producer.Producer.sendMessage(Producer.java:379)
at gov.pnnl.proven.api.producer.ProvenProducer.sendBulkMessage(ProvenProducer.java:133)
at gov.pnnl.goss.gridappsd.data.ProvenTimeSeriesDataManagerImpl$1.onMessage(ProvenTimeSeriesDataManagerImpl.java:172)
at pnnl.goss.core.client.GossClient$1.run(GossClient.java:351)
at java.lang.Thread.run(Thread.java:748)At https://github.com/poorva1209's request, here is my output of docker ps -a before the error: thay838@ubuntu:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4a1e7cb59234 gridappsd/pyvvo:latest "python -u /opt/.pyc…" 3 minutes ago Up 3 minutes 0.0.0.0:53581->53581/tcp pyvvo_pyvvo_1
27443f7f11f3 gridappsd/pyvvo:mysql-latest "docker-entrypoint.s…" 3 minutes ago Up 3 minutes 3306/tcp, 33060/tcp pyvvo_db_1
b7061fb11673 gridappsd/viz:v2019.10.0 "npm start" 4 minutes ago Up 4 minutes 0.0.0.0:8080->8082/tcp gridappsd-docker_viz_1
6d81a31fdb3b gridappsd/pyvvo:latest "python /usr/src/gri…" 4 minutes ago Up 4 minutes gridappsd-docker_pyvvo_1
e3f1df71da3f gridappsd/gridappsd:v2019.10.0 "/gridappsd/entrypoi…" 5 minutes ago Up 4 minutes 0.0.0.0:8000->8000/tcp, 8001-8887/tcp, 0.0.0.0:8888->8888/tcp, 0.0.0.0:61613-61614->61613-61614/tcp, 0.0.0.0:61616->61616/tcp, 8889-9000/tcp gridappsd-docker_gridappsd_1
5effe522e0e6 gridappsd/blazegraph:v2019.10.0 "/docker-entrypoint.…" 5 minutes ago Up 5 minutes 0.0.0.0:8889->8080/tcp gridappsd-docker_blazegraph_1
a598a2b0e6f2 gridappsd/influxdb:v2019.10.0 "/entrypoint.sh infl…" 5 minutes ago Up 5 minutes 0.0.0.0:8086->8086/tcp gridappsd-docker_influxdb_1
d9c7950dcedf gridappsd/proven:v2019.10.0 "java -jar /opt/paya…" 5 minutes ago Up 5 minutes 4848/tcp, 8009/tcp, 8181/tcp, 0.0.0.0:18080->8080/tcp gridappsd-docker_proven_1
87b163e191eb mysql/mysql-server:5.7 "/entrypoint.sh mysq…" 5 minutes ago Up 5 minutes (healthy) 0.0.0.0:3306->3306/tcp, 33060/tcp gridappsd-docker_mysql_1
35175147d5dd gridappsd/pyvvo:mysql-latest "docker-entrypoint.s…" 5 minutes ago Up 5 minutes 3306/tcp, 33060/tcp gridappsd-docker_pyvvo-db_1
7786922ad4d0 redis:3.2.11-alpine "redis-server --appe…" 5 minutes ago Up 5 minutes 0.0.0.0:6379->6379/tcp gridappsd-docker_redis_1
1621c5ab696e aaa5a6a31acc "/bin/sh" 6 minutes ago Created pycharm_helpers_PY-192.7142.42
And after the error: thay838@ubuntu:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4a1e7cb59234 gridappsd/pyvvo:latest "python -u /opt/.pyc…" 5 minutes ago Up 5 minutes 0.0.0.0:53581->53581/tcp pyvvo_pyvvo_1
27443f7f11f3 gridappsd/pyvvo:mysql-latest "docker-entrypoint.s…" 5 minutes ago Up 5 minutes 3306/tcp, 33060/tcp pyvvo_db_1
b7061fb11673 gridappsd/viz:v2019.10.0 "npm start" 6 minutes ago Up 6 minutes 0.0.0.0:8080->8082/tcp gridappsd-docker_viz_1
6d81a31fdb3b gridappsd/pyvvo:latest "python /usr/src/gri…" 6 minutes ago Up 6 minutes gridappsd-docker_pyvvo_1
e3f1df71da3f gridappsd/gridappsd:v2019.10.0 "/gridappsd/entrypoi…" 6 minutes ago Up 6 minutes 0.0.0.0:8000->8000/tcp, 8001-8887/tcp, 0.0.0.0:8888->8888/tcp, 0.0.0.0:61613-61614->61613-61614/tcp, 0.0.0.0:61616->61616/tcp, 8889-9000/tcp gridappsd-docker_gridappsd_1
5effe522e0e6 gridappsd/blazegraph:v2019.10.0 "/docker-entrypoint.…" 7 minutes ago Up 6 minutes 0.0.0.0:8889->8080/tcp gridappsd-docker_blazegraph_1
a598a2b0e6f2 gridappsd/influxdb:v2019.10.0 "/entrypoint.sh infl…" 7 minutes ago Up 6 minutes 0.0.0.0:8086->8086/tcp gridappsd-docker_influxdb_1
d9c7950dcedf gridappsd/proven:v2019.10.0 "java -jar /opt/paya…" 7 minutes ago Up 6 minutes 4848/tcp, 8009/tcp, 8181/tcp, 0.0.0.0:18080->8080/tcp gridappsd-docker_proven_1
87b163e191eb mysql/mysql-server:5.7 "/entrypoint.sh mysq…" 7 minutes ago Up 6 minutes (healthy) 0.0.0.0:3306->3306/tcp, 33060/tcp gridappsd-docker_mysql_1
35175147d5dd gridappsd/pyvvo:mysql-latest "docker-entrypoint.s…" 7 minutes ago Up 6 minutes 3306/tcp, 33060/tcp gridappsd-docker_pyvvo-db_1
7786922ad4d0 redis:3.2.11-alpine "redis-server --appe…" 7 minutes ago Up 6 minutes 0.0.0.0:6379->6379/tcp gridappsd-docker_redis_1
1621c5ab696e aaa5a6a31acc "/bin/sh" 8 minutes ago Created pycharm_helpers_PY-192.7142.42
Additionally, it's worth noting that my application can still command that regulator after the 60 second mark. — You are receiving this because you were mentioned. Reply to this email directly, https://github.com/GRIDAPPSD/gridappsd-forum/issues/49?email_source=notifications&email_token=AFSH6WAOVKVCMA5EEZB5TBDQSXJRNA5CNFSM4JK62PA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYCGOCQ, or https://github.com/notifications/unsubscribe-auth/AFSH6WBQKSGZKWTIBPGKHXDQSXJRNANCNFSM4JK62PAQ.
AAndersn
poorva1209
@Jeffrey-Simpson @craig8 @poorva1209 Platform version:
v2019.10.0Simulation run configuration:
As can be deduced from the run configuration, the regulator position change and lockout should occur 60 seconds into the simulation.
At that time (I can tell from my own logs), the platform errors out:
At @poorva1209's request, here is my output of
docker ps -abefore the error:And after the error:
Additionally, it's worth noting that my application can still command that regulator after the 60 second mark.