Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Refactoring and merging PSL-VMI feature #335

Open
mhm90 opened this issue Aug 16, 2022 · 3 comments
Open

Refactoring and merging PSL-VMI feature #335

mhm90 opened this issue Aug 16, 2022 · 3 comments

Comments

@mhm90
Copy link

mhm90 commented Aug 16, 2022

I need some changes in PSL-VMI feature and I was wondering if you could help me with that to change implementation accordingly and apply the feature in the main repo to be released in the next version.
I am not using PSL-CLI but PSL-Java in my project. I have a standalone application which has its lifecycle beyond the PSL run and is using PSL to infer a result from some input received as a request! Consider it as a backend service which uses PSL (runs a PSL job per each request and waits for it to calculate the response). I need to track why my rules resulting this specific response (which is what PSL-VMI is doing) and log the JSON output of PSL-VMI in a searchable log container with my PSL job id like Graylog. So thats why I don't need PSL-VMI to output the debug data as a file after inference process. I need it to be like a callback after inference in java code and I use that data for my logging purposes. The callback could also handles the JSON debug file generation in the CLI.

@eriq-augustine
Copy link
Member

So it sounds like the key information that you want are the ground rules/terms associated with a specific atom/prediction.
Does that sound right?

@mhm90
Copy link
Author

mhm90 commented Aug 17, 2022

Yeah, I think I need pretty much everything for the inference debugging, but hasn't all this been implemented once in the PSL-Viz fork? Should I start from scratch?

@eriq-augustine
Copy link
Member

I would take a look at PSL-Viz and see what components you may want to bring over from that.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants