Open Rezenders opened 1 year ago
Measured QAs are only saved if there is a FG to attach it to.
This is not true, they are saved with the prefix obs_
. Like: obs_mockiness
.
In addition, the measured QAs are being saved attached to the first FG that is being found, unless in the diagnostic msg it is explicitly written what function it should be attached to. The user should not need to add this info to the diagnostics msg, the Fgs to attach it to should be inferred given the type of the QAs.
However, this is true. This part is wrong.
def update_qa(self, diagnostic_status):
# Find the FG with the same name that the one in the QA message (in
# diagnostic_status.name)
fg = next((fg for fg in self.tomasys.FunctionGrounding.instances()
if fg.name == diagnostic_status.name), None)
if fg is None:
fg = self.tomasys.FunctionGrounding.instances()[0]
return_value = -1
Measured QAs are only saved if there is a FG to attach it to. This is not true, they are saved with the prefix obs_. Like: obs_mockiness.
Actually, this seems to be true.
Fixed at 1f36457 Measured qas are saved regardless of a FG existing or not. Then, the measured QA is associated to all FGs that need it.
We need to define a consistent model for QA values
, both in tomasys
and the implement a corresponding logic in the reasoner.
I am reopening the issue for that reason @Rezenders , also the link to this discussion would be useful when addressing it. But if you prefer to close this one and one a new Issue, that is ok with me.
Measured QAs are only saved if there is a FG to attach it to. Measured QAs are important even when there is no FG, see https://github.com/kas-lab/pipeline_inspection/issues/35. In addition, the measured QAs are being saved attached to the first FG that is being found, unless in the diagnostic msg it is explicitly written what function it should be attached to. The user should not need to add this info to the diagnostics msg, the Fgs to attach it to should be inferred given the type of the QAs.
In tomasys.py
In reasoner.py