Skip to content
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

Define behaviour when resuming an interupted run #27

Open
andrewphilipsmith opened this issue Apr 6, 2022 · 0 comments
Open

Define behaviour when resuming an interupted run #27

andrewphilipsmith opened this issue Apr 6, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@andrewphilipsmith
Copy link
Contributor

As a:
user who is processing large volumes of data
I want:
alto2txt to be able to resume elegantly when run on a partially complete previous run, including cases where the previous run had crashed.
so that:
I can resume it quickly without needing to manually wade through lengthy log files, nor needing to find partial, incomplete output files.

Notes:

  • We will need to consider scenarios where (i) alto2txt is run in serial and (ii) alto2txt is run in parallel.
  • The current behaviour in these scenarios is unknown.

This idea came out of a meeting with @fedenanni and @thobson88. Our notes are here https://hackmd.io/KeOzeaMYTOiF37pGUjUl7A

@andrewphilipsmith andrewphilipsmith added the enhancement New feature or request label Apr 6, 2022
andrewphilipsmith added a commit that referenced this issue May 27, 2022
Added tests to ensure that the runtime checking of CLI params is working. There is one failing test in this commit because the "correct" behaviour has not yet been agreed (see #27).
@andrewphilipsmith andrewphilipsmith added this to the v0.5 milestone Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants