Semantic caching algorithm added

[Louis-Mozart]

Code for the semantic caching paper.

[Demirrr]

@Louis-Mozart please fix the errors

[Louis-Mozart]

@Louis-Mozart please fix the errors

I think the error comes from the fact that the dice file system is not working. See below:

`
--2025-01-27 14:46:57-- (try:18) https://files.dice-research.org/projects/Ontolearn/KGs.zip
Connecting to files.dice-research.org (files.dice-research.org)|131.234.26.214|:443... failed: Connection timed out.
Retrying.

--2025-01-27 14:49:20-- (try:19) https://files.dice-research.org/projects/Ontolearn/KGs.zip
Connecting to files.dice-research.org (files.dice-research.org)|131.234.26.214|:443... failed: Connection timed out.
Retrying.

--2025-01-27 14:51:44-- (try:20) https://files.dice-research.org/projects/Ontolearn/KGs.zip
Connecting to files.dice-research.org (files.dice-research.org)|131.234.26.214|:443... failed: Connection timed out.
Giving up.
`

[alkidbaci]

Hi @Louis-Mozart, would it be possible for you to add some test cases for your code in ontolearn/tests directory?
I noticed some outdated code and made a few corrections. Would be great to have this code covered by tests so that we avoid such errors in the future :)

[Louis-Mozart]

Hi, sorry was on leave. Alright, I guess the error was because I wrote the code on an old version of Ontolearn (0.7.3), I upgraded to the latest version and added the tests as requested see tests/test_semantic_cache.

[alkidbaci]

I was having a look at the error that caused the test to fail, its because the JVM is stopped in a previous operation (and the JVM cannot be restarted - a limitation from Jpype).
I came across this file test_retrieval_eval_examples.py where you call the method execute from examples.retrieval_eval_under_incomplete where you stop the JVM in line 228. Just remove that line and everything will be fine. In general you don't need to stop the JVM because it automatically stops when the whole code has finish execution. The function stopJVM is there to use in some exceptional scenarios where the execution is computationally demanding and you know that at some point the JVM will not be used anymore so you stop it.

[Louis-Mozart]

It's done but still not working. Could it be that the test is executed on the family which requires a bit of time?