You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently provided openSesame a 4MB text file. The predicted_args.conll was about 260MB, and took about 1 complete day (24hours) to annotate entirely.
I now have a 300MB text file which I need to annotate. I am expecting the predicted_args.conll to be about 20GB. The problem here is the processing time. This may process may take-up days/months if run on a single open-sesame instance. Does anybody have any idea as to how we can implement this process as a pipeline?
Maybe run several containers with open-sesame on them, or divide the huge text files into smaller text files, and then annotate each one of them separately? Is there any way in which this task could be achieved in a smaller time duration?
Thanks...
The text was updated successfully, but these errors were encountered:
I recently provided openSesame a 4MB text file. The predicted_args.conll was about 260MB, and took about 1 complete day (24hours) to annotate entirely.
I now have a 300MB text file which I need to annotate. I am expecting the predicted_args.conll to be about 20GB. The problem here is the processing time. This may process may take-up days/months if run on a single open-sesame instance. Does anybody have any idea as to how we can implement this process as a pipeline?
Maybe run several containers with open-sesame on them, or divide the huge text files into smaller text files, and then annotate each one of them separately? Is there any way in which this task could be achieved in a smaller time duration?
Thanks...
The text was updated successfully, but these errors were encountered: