Closed Sophietje closed 9 months ago
In GitLab by @han.kruiger.tno.nl on Feb 18, 2022, 10:08
marked this issue as related to #349
In GitLab by @barry.nouwt.tno.nl on Feb 18, 2022, 11:56
created merge request !279 to address this issue
In GitLab by @barry.nouwt.tno.nl on Feb 18, 2022, 11:59
marked this issue as related to #351
In GitLab by @han.kruiger.tno.nl on Feb 21, 2022, 10:29
marked the checklist item Han: dockerize AdminUI to easily integrate into other projects (C2-JeF) as completed
In GitLab by @han.kruiger.tno.nl on Feb 21, 2022, 10:36
Regarding this point:
Allow in the Visual Knowledge Explorer for KBs that reside in the same KERuntime as the AdminUI to trigger KIs manually.
We established on Friday that the AdminUI uses its own 'private' KE runtime. This means that there are no other KBs in there by default.
We decided that we could make it so that the AdminUI frontend can still make new KBs and KIs (and trigger them) if the AdminUI backend ships with a KE REST API. @barry.nouwt.tno.nl is working on that in !280.
I therefore moved the following point up to the MUST
priority, since it is required to create them before triggering them:
Visually create new KB with KIs.
In GitLab by @barry.nouwt.tno.nl on Feb 21, 2022, 11:12
Hey @han.kruiger.tno.nl, indeed, either we increase the priority of that point, or we use some script (for now) to initiate all the KBs and their KIs. I think this latter is a good option to begin with. What do you think?
In GitLab by @barry.nouwt.tno.nl on Mar 4, 2022, 09:09
marked the checklist item Barry: Modify connections between KB to use ReasoningProcessor and ReasoningNode. See #351 as completed
In GitLab by @barry.nouwt.tno.nl on Mar 4, 2022, 09:09
marked the checklist item Han: Move Visual Knowledge Explorer outside C2-JeF as completed
In GitLab by @barry.nouwt.tno.nl on Mar 4, 2022, 09:09
marked the checklist item Han: Polish the current Visual Knowledge Explorer as completed
In GitLab by @barry.nouwt.tno.nl on Mar 4, 2022, 09:09
marked the checklist item Barry: Run REST Developer API next to REST Admin API. as completed
In GitLab by @barry.nouwt.tno.nl on Mar 4, 2022, 09:46
Planning (10 dagen):
- (2-3 dagen) Han: Allow in the Visual Knowledge Explorer for KBs that reside in the same KERuntime as the AdminUI to trigger KIs manually.
○ trigger van proactive KIs
○ reageren op reactive KIs
○ iets om bindingsets te vullen (beginnen met JSON)
- (3 dag) Barry: Pruning om aantal verbindingen te verminderen
- (1 dag) Barry: Sequence diagrams beschikbaar stellen aan frontend (via connections, alleen plannen)
- (1 dag) Barry+Han: scenario's voorbereiden, opstellen en uitproberen.
○ 3 of 4 kleine scenario's rechtstreeks overgenomen van de vorige reasoner workshop slides
○ 1 groter scenario met realistische graph patterns gebaseerd op Aleksandar's test.
- (2 dagen) Barry+Han: laatste puntjes op de i wat betreft look&feel van de admin ui.
Sorry, Dutch.
In GitLab by @han.kruiger.tno.nl on Mar 11, 2022, 08:33
marked the checklist item Han: Allow in the Visual Knowledge Explorer for KBs that reside in the same KERuntime as the AdminUI to trigger KIs manually. as completed
In GitLab by @han.kruiger.tno.nl on Mar 11, 2022, 08:36
marked the checklist item Han: Visually create new KB with KIs. as completed
In GitLab by @barry.nouwt.tno.nl on Mar 11, 2022, 09:05
Other tasks:
In GitLab by @han.kruiger.tno.nl on Mar 25, 2022, 12:40
[{"a": "<http://example.org/maths>", "b": "<http://example.org/science>"}]
[{"a": "<http://example.org/grammar>", "b": "<http://example.org/punctuation>"}]
In GitLab by @han.kruiger.tno.nl on Mar 25, 2022, 13:15
http://example.org/sensor-1
)[
{"m": "<http://example.org/sensors/1>", "v": "12", "d": "<http://example.org/devices/1>", "r": "<http://example.org/rooms/1>"}
]
http://example.org/sensor-2
)[
{"m": "<http://example.org/sensors/2>", "v": "17", "d": "<http://example.org/devices/2>"}
]
http://example.org/rooms-kb
)[
{"d": "<http://example.org/devices/2>", "r": "<http://example.org/rooms/2>"}
]
In GitLab by @han.kruiger.tno.nl on Mar 25, 2022, 13:47
:warning: DOESN'T WORK for some reason. :warning: For some reason, it asks the sensor for its Fahrenheit measurements, but doesn't ask the converter.
Fixed after #361
[{"m": "<http://example.org/measurements/1>", "fahrenheit": "69.8"}]
[{"m": "<http://example.org/measurements/1>", "celsius": "21.0"}]
In GitLab by @barry.nouwt.tno.nl on Mar 25, 2022, 15:34
Mmm, maybe try to change the result graph pattern of the converter to only:
?m ex:hasValueInCelsius ?vc .
It might end up in a loop because the argument overlaps with the result graph pattern :smile:
In GitLab by @han.kruiger.tno.nl on Mar 25, 2022, 16:03
Loops! :ghost:
I'll give this a try!
In GitLab by @barry.nouwt.tno.nl on Mar 25, 2022, 16:17
It just tried it, but I can see the popup of the converter at the edge of my screen, but I cannot enter any fields. So, not sure if it works, but the popup location seems a bit off.
In GitLab by @han.kruiger.tno.nl on Mar 28, 2022, 11:03
(in the outgoing bindings)
[{"a": "<http://example.org/maths>", "b": "<http://example.org/science>"}]
[]
In GitLab by @han.kruiger.tno.nl on Mar 28, 2022, 11:08
Oh hey, after testing again with the updated graph patterns (without the ?m rdf:type ex:Measurement .
triple pattern in the result graph pattern) and correct JSON bindings (with a value for ?m
) it works..!
The issues with the popups 'appearing' in the bottom-left corner had to do with not cleaning up removed popups properly.
There is however the issue that Sensor 1
is called upon twice by the reasoner, and then the converter is called once. But it works!
In GitLab by @han.kruiger.tno.nl on Mar 28, 2022, 11:26
Hmmm, it doesn't work consistently though... Trying to figure out what causes it to fail now.
In GitLab by @barry.nouwt.tno.nl on Mar 29, 2022, 11:22
All Knowledge Networks above are working correctly now :smile: and can be used for the workshop.
In GitLab by @barry.nouwt.tno.nl on Mar 31, 2022, 12:29
Not all examples from the WP5 Reasoner Explanation slides are already tested. The following 4 are present in the presentation and the checked ones are tested and working.
reasoning to infer new data:
reasoning to orchestrate data exchange
The other two are not that simple for several reasons:
In GitLab by @barry.nouwt.tno.nl on Apr 4, 2022, 10:13
[
{
"l": "<lamp1>",
"o": "\"true\"^^<http://www.w3.org/2001/XMLSchema#boolean>"
},
{
"l": "<lamp2>",
"o": "\"true\"^^<http://www.w3.org/2001/XMLSchema#boolean>"
}
]
If no binding set is described here, use the empty ([]
) bindingset
[{"s":"<lamp2>"}]
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:09
marked the checklist item Import/Export of scenario with multiple KBs as completed
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:09
marked the checklist item possible GUI improvements as completed
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:09
marked the checklist item no connection to KI when other side is invisible as completed
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:09
marked the checklist item only show relevant graph pattern text boxes for different KI types. as completed
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:09
marked the checklist item extract visualization into empty git repository (for now on our internal gitlab) as completed
In GitLab by @han.kruiger.tno.nl on Apr 8, 2022, 09:15
Final fixes before the workshop:
In GitLab by @barry.nouwt.tno.nl on Apr 14, 2022, 10:21
DOES NOT WORK ENIRELY YET!! It does loop indefinitely, but the bindings seem incorrect.
http://example.org/ancestor-kb
)[
{"a": "<barry>", "b": "<fenna>"},
{"a": "<janny>", "b": "<janny>"}
]
http://example.org/transitive-ancestor-kb
)[
{"x": "<janny>", "z": "<fenna>"}
]
In GitLab by @barry.nouwt.tno.nl on Feb 18, 2022, 09:30
MoSCoW
MUST:
SHOULD:
Barry: show sequence diagram for KICOULD:
WON'T:
UNCATEGORIZED:
KI maybe without type text but different iconOther tasks: