-
Hi, Thanks for developing this package and the example/guide. Extremely useful for someone with basic python skills. From the example, I saw that you were managing to get very high it/s speeds when calling the refine_scopus function. On my end, I'm getting max 1.5it/s when running the function for the first time, both on campus network and via university VPN remotely, which makes an initial run take very long. When I make small changes to my code, such as plot or topic changes and run it again, it refines the documents again, however much quicker.
Happy to provide more information/clarify. Thanks in advance |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi, thanks for using using litstudy and thanks for reporting this issue! Unfortunately, the Scopus API has a limit on how many requests can be performed per minute. The first time that you refine a document set, it can take a long time unfortunately (I typically get 1 request per second). However, after refining once, the Scopus results should be stored locally on you computer, so refinement should be faster after the first time (it might still take few seconds though). I would recommend working in a Jupyter notebook. There you can work interactively and make changes to the code while the documents are kept loaded all the time. |
Beta Was this translation helpful? Give feedback.
Hi, thanks for using using litstudy and thanks for reporting this issue!
Unfortunately, the Scopus API has a limit on how many requests can be performed per minute. The first time that you refine a document set, it can take a long time unfortunately (I typically get 1 request per second).
However, after refining once, the Scopus results should be stored locally on you computer, so refinement should be faster after the first time (it might still take few seconds though).
I would recommend working in a Jupyter notebook. There you can work interactively and make changes to the code while the documents are kept loaded all the time.