Thank you for your outstanding work on RNA summary generation! It has been very helpful for my research. I have two specific questions regarding the usage of your RNA summarizing API:
-
When I submit a job using the following command from the README file:
curl -H "Content-Type:application/json" -d "{\"id\": \"bta-mir-16a\"}" localhost:8080/api/submit-job
How can I determine when the summary for this RNA has been completed, so that I can safely submit the next job? Is there an endpoint or a recommended workflow for checking the job status?
-
How long does it generally take to perform a literature scan (litscan) for a single RNA? I tried submitting a large number of jobs in a relatively short period of time using the above command, but noticed that the summarizer keeps outputting “Polling for new jobs” in the logs. I am wondering if this means the generation step is stuck at the litscan literature search stage, or if there could be another bottleneck.
Thank you again for your great work. I look forward to your response!
Thank you for your outstanding work on RNA summary generation! It has been very helpful for my research. I have two specific questions regarding the usage of your RNA summarizing API:
When I submit a job using the following command from the README file:
curl -H "Content-Type:application/json" -d "{\"id\": \"bta-mir-16a\"}" localhost:8080/api/submit-jobHow can I determine when the summary for this RNA has been completed, so that I can safely submit the next job? Is there an endpoint or a recommended workflow for checking the job status?
How long does it generally take to perform a literature scan (litscan) for a single RNA? I tried submitting a large number of jobs in a relatively short period of time using the above command, but noticed that the summarizer keeps outputting “Polling for new jobs” in the logs. I am wondering if this means the generation step is stuck at the litscan literature search stage, or if there could be another bottleneck.
Thank you again for your great work. I look forward to your response!