On 17/05/13 13:27, [email protected] wrote:
I ran tdbstats again on the fully loaded triple store (with all the patient
data as individuals and their relationships). My properties appear now in the
stats file. But only the properties with explicit triples, not the inferred
parent properties. E.g. I am using the following property type hierarchy:
What is your inference setup?
Has_Finding
- Has_Dysnpea_Score
- Has_Dysphagia_Score
- Is_Dead
There are no explicit triples stating e.g. that a patient Has_Finding
Dyspnea_Score_2. But there are triples using the sub-properties, e.g. Patient
Has_Dysnpea_Score Dyspnea_Score_2.
Can you share the stats file? I can't investigate the situation without
a test case.
The stats file now contains entries for the sub-properties, but not for
Has_Finding.
The execution plan changed slightly though, but the crucial triple patterns are still in
the "wrong" order.
It used to be:
(?pat <http://www.siemens.com/euroCAT/2011/8/euroCAT.owl/instances#Has_Id>
?patId)
The original stats file had no mention of #Has_Id and actaully said (at
the end) that missing predciates were to be counted as having zero
occurences. The optimizer puts one of these first because the rest of
the pattern will never be reached if it's accurate.
(?pat rdf:type <http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#Patient>)
(?findingProp rdfs:subPropertyOf
<http://www.siemens.com/euroCAT/2011/8/euroCAT.owl#Has_Finding>)
(?finding rdf:type ?findingType)
(?pat ?findingProp ?finding)
Now it is:
(?findingProp rdfs:subPropertyOf
<http://www.siemens.com/euroCAT/2011/8/euroCAT.owl#Has_Finding>)
(?pat rdf:type <http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#Patient>)
(?pat <http://www.siemens.com/euroCAT/2011/8/euroCAT.owl#Has_Id> ?patId)
(?finding rdf:type ?findingType)
(?pat ?findingProp ?finding)
The triple pattern for the Has_Finding sub-properties moved to the start, but the
crucial (?finding rdf:type ?findingType) is still evaluated before (?pat
?findingProp ?finding) -> the query is still taking a very long time.
I can go ahead and use "fixed.opt" instead of "stats.opt", but I am still
interested in whether there is a solution to this problem. I am using Jena 2.10.0.
Hope this info helps!
-Wolfgang
-----Original Message-----
From: hueyl16 <[email protected]>
To: users <[email protected]>
Sent: Fri, May 17, 2013 1:43 pm
Subject: Re: Unexpectedly slow query
I was wondering about that too. I could only find entries related to NCI
terms. How or when is the stats file generated?
I am using the .bat versions of the tdbloader for importing the NCIt first and
then my own ontology, which contains Has_Id and Has_Finding plus more.
I also ran tdbstats once but it did not change the stats file, just printed it.
-----Original Message-----
From: Andy Seaborne <[email protected]>
To: users <[email protected]>
Sent: Fri, May 17, 2013 1:25 pm
Subject: Re: Unexpectedly slow query
(I now have the stats file)
Wolfgang,
I don't see entries for ec:Has_Id and ec:Has_Finding.
Andy
