Open rudolfovic opened 7 years ago
Hi Sergey,
Apologies for the late reply
It’s difficult to answer without any detail about the task that you’re trying to solve.
Just consider that Xhail is mainly a wrapper around Gringo/Clasp therefore I think it’s likely the expected behaviour.
Try to run it with --debug option so that you can find the gringo/clasp files in the temp folder… Are these correct? Are these developing the same behaviour when run separately?
Another possibility would be, of course, a bug due to some differences between the version of Gringo/Clasp in use when I developed Xhail and the version currently available… I can’t say more, anyway, as I don’t know anything about your set-up…
In any case, I’m not maintaining Xhail anymore but I’m sure the people in Dr. Ray's Research Group at University of Bristol (https://goo.gl/vYRSNZ https://goo.gl/vYRSNZ) have improved it and solved possible known issues.
Regards and good work with Xhail, Stefano
On 18 Jun 2017, at 12:07, Sergey notifications@github.com wrote:
I tried a task with XHAIL and it ran fine taking up only about 350Mb of RAM for about 7 hours but then I started getting critical HDD space warning and had to terminate the process.
Just before killing the process, I located a file generated by XHAIL in /private/var/tmp/ sized 450GB. I am not sure if it's been slowly writing the whole time or suddenly dumped the file after 7 hours.
This was a test task where I oversimplified the bias so that XHAIL found the hypothesis I wanted it to and it contained just a single head definition and 6 body definitions (4 could appear at most once and 2 could appear at most twice).
I realise that 6 body definitions can be seen as quite considerable but I also fine-grained the typing to restrict the space further.
I know for sure that a hypothesis consisting of one rule with 8 body literals exists and I checked it using ASP directly.
Should such behaviour be possible given the size of the task and in general given that XHAIL is supposed to run iteratively?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stefano-bragaglia/XHAIL/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AEMjaosP6pfqospNkJB2ldasoAZgCM6mks5sFQTxgaJpZM4N9d6q.
I tried a task with XHAIL and it ran fine taking up only about 350Mb of RAM for about 7 hours but then I started getting critical HDD space warning and had to terminate the process.
Just before killing the process, I located a file generated by XHAIL in /private/var/tmp/ sized 450GB. I am not sure if it's been slowly writing the whole time or suddenly dumped the file after 7 hours.
This was a test task where I oversimplified the bias so that XHAIL found the hypothesis I wanted it to and it contained just a single head definition and 6 body definitions (4 could appear at most once and 2 could appear at most twice).
I realise that 6 body definitions can be seen as quite considerable but I also fine-grained the typing to restrict the space further.
I know for sure that a hypothesis consisting of one rule with 8 body literals exists and I checked it using ASP directly.
Should such behaviour be possible given the size of the task and in general given that XHAIL is supposed to run iteratively?