SakanaAI
always backing off
The SS API should be 1 call limit per second without a key, are you running this in parallel?
That shouldn't matter, the default value will likely be fine. The only thing that matters is whether you are trying to call this more than 1/s.
No. I didn’t.
Cong Lu @.***>于2024年8月29日 周四下午4:15写道：
That shouldn't matter, the default value will likely be fine. The only thing that matters is whether you are trying to call this more than 1/s.
— Reply to this email directly, view it on GitHub https://github.com/SakanaAI/AI-Scientist/issues/78#issuecomment-2316794844, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARQNVA423CXKGMDK6X4LXJTZT24BVAVCNFSM6AAAAABNHOPT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWG44TIOBUGQ . You are receiving this because you authored the thread.Message ID: @.***>
I am experiencing the same issue. I just ran my template; I didn't specify anything regarding parallel running or the number of API calls. It is stuck for hours in this process.
Anything to change in terms of configuration to account for this?
Can you check if you are able to make an API request at all? https://www.semanticscholar.org/product/api%2Ftutorial#request
It may be a firewall issue, alternatively you may try commenting out the novelty checker for now and just let the AI Scientist execute all ideas.
I opened all port
Cong Lu @.***>于2024年8月30日 周五下午4:54写道：
Same issue boring me......
Do you have a firewall that blocks this?
— Reply to this email directly, view it on GitHub https://github.com/SakanaAI/AI-Scientist/issues/78#issuecomment-2320258516, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARQNVA6RP23XPGFJ4HC6QPTZUAJJLAVCNFSM6AAAAABNHOPT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGI2TQNJRGY . You are receiving this because you authored the thread.Message ID: @.***>
I opened all port Cong Lu @.>于2024年8月30日 周五下午4:54写道： … Same issue boring me...... Do you have a firewall that blocks this? — Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARQNVA6RP23XPGFJ4HC6QPTZUAJJLAVCNFSM6AAAAABNHOPT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGI2TQNJRGY . You are receiving this because you authored the thread.Message ID: @.>
Have you tried the tutorial here: https://www.semanticscholar.org/product/api%2Ftutorial#request
I opened all port Cong Lu @.>于2024年8月30日 周五下午4:54写道： … Same issue boring me...... Do you have a firewall that blocks this? — Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARQNVA6RP23XPGFJ4HC6QPTZUAJJLAVCNFSM6AAAAABNHOPT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGI2TQNJRGY . You are receiving this because you authored the thread.Message ID: _@**.**_>
Have you tried the tutorial here: https://www.semanticscholar.org/product/api%2Ftutorial#request
Yes. I did.
Hmm interesting, this looks like an issue on the Semantic Scholar side, or other users on your network using SS. I would comment out uses of this API while you still don’t have a key and try get one!
In the future, we can also look into other literature sources.