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

refactor eval module #34

Closed
jaeddy opened this issue Aug 16, 2018 · 0 comments
Closed

refactor eval module #34

jaeddy opened this issue Aug 16, 2018 · 0 comments

Comments

@jaeddy
Copy link
Member

jaeddy commented Aug 16, 2018

For one, should use a more intuitive label than the Synapse-specific "eval" (i.e., just go with "queue"). Could also be worthwhile to switch to the adapter/wrapper pattern used with WES — potentially making it easier to plug in Synapse connectivity in place of the current file-based queueing.

jaeddy added a commit that referenced this issue Aug 27, 2018
Modify the orchestrator config for queues (renamed from 'evals')
to store basic information needed for the testbed, including
where workflow files can be retrieved and a list of WES endpoints
on which to run jobs.

See #33, #34
@jaeddy jaeddy closed this as completed Jan 21, 2019
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