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

Implement Asynchronous Execution for the "Staging" Function in Genomeshader #13

Open
3 tasks
bshifaw opened this issue Jun 20, 2024 · 0 comments
Open
3 tasks

Comments

@bshifaw
Copy link

bshifaw commented Jun 20, 2024

Problem:

The "staging" function in Genomeshader is computationally expensive and can take a significant amount of time to complete. In an interactive environment like Jupyter notebooks, this can block the user from executing other tasks while waiting for the "staging" function to complete.

Proposed Solution:

Implement asynchronous execution for the "staging" function. This would allow the function to run in the background, freeing up the user to execute other tasks in the meantime. The user can then check back later to see if the "staging" function has completed.


Tasks:

  • Refactor the "staging" function to support asynchronous execution. This may involve using Python's built-in asyncio library or a similar library.
  • Update any calls to the "staging" function to handle the asynchronous execution. This may involve using await or similar syntax.
  • Test the updated "staging" function in a Jupyter notebook to ensure that it runs in the background and allows other tasks to be executed while it is running.

Acceptance Criteria:

  • The "staging" function should support asynchronous execution.
  • Calls to the "staging" function should not block the execution of other tasks.
  • The user should be able to check the status of the "staging" function and retrieve the results when it has completed.
  • The updated functionality should be covered by tests to ensure it works as expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant