-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with Factool Installation and Execution #40
Comments
it might be related to this issue: #33 |
Hello Ethan, Thank you for your reply. It works now but when I tried to run NOTES:
Thank you in advance |
I see. maybe change Also, for Scientific Literature Review, the scholarly API may have some bugs (please refer to this issue). |
Hello, I am trying to run my prompt but I got a
|
I see. Just curious, does this issue happen in other tasks (KBQA, math, code)? It is possible that the response doesn't contain any valid paper so the claim extraction process extracts nothing. The exception handling process for this part might not be robust. Also, as I mentioned earlier, there are bugs in the current scholarly code, so you might want to change to this line into |
Hello, The issue happened only in the scientific task. Thank you for the guidance. |
Thanks for the feedback! So I think the current version of FacTool inherently assumes that the given response should include at least one claim (i.e., the response contains the name of at least one paper, no matter it is a hallucinated paper or not.). It is possible that the abstract itself doesn't mention any paper, so no claims will be extracted, causing the NoneType error. Maybe you can try something like: try:
response_list = await factool_instance.run(inputs)
except TypeError:
print("no claims in the response!") |
Hello,
I'm experiencing an error after following the installation guidelines for Factool and using the code from
example.py
. Despite trying both recommended installation methods and ensuring all three API keys are correctly defined, the tool is not functioning as expected. Could you please assist in resolving this issue?The text was updated successfully, but these errors were encountered: