-
Notifications
You must be signed in to change notification settings - Fork 566
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
CommonWL #1310
Comments
CWL is something that's been on our radar for a while and is definitely something we're interested in exploring. A few questions I have:
|
Cool, glad to hear it.
Let me know if you'd like a real time video chat, I'd be happy to go into more depth and share about how various projects have implemented CWL support so far. |
Just to chime in with my 5c: Based on my experimentation with CWL and my breif reading of Pachyderm workflow examples, I get the impression that they are actually very similar. I would even think just a converter from CWL yaml/json to Pachyderm yaml, would not be very hard at all. CWL is also doing the definition of inputs / outputs (in-ports / out-ports in some contexts) in a more re-usable and composable way, as far as I can see, so I think pachy could probably learn a thing or two there as well, for any future updates of its format. But all in all, the formats seem very similar. |
Any further thought here? Has anyone attempted a CWL to Pachyderm yaml converter? Does it seem like there's sufficient feature parity for this to work well? I think it would make Pachyderm quite appealing to interface smoothly with the CWL standard. |
Big Pachdyerm user here - we are using it throughout all of our pipelines. Are there any plans to support CWL soon? This language is becoming the lingua franca of computational genomics and support for it is extremely important for our continued use of Pachyderm. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
well that would be a shame :) |
As stated above it'd just be a matter of implementing a converter from CWL to pachyderm's pipeline def. I think it would be quite useful for pachyderm's community indeed. |
@marcadella I'm not aware of any, but that doesn't mean that such a thing hasn't been started. I am happy to assist anybody writing a CWL converter! |
While I'm not very familiar with CWL, I'm not actually sure if this would be very easy to implement as there are many concepts that don't seem to translate cleanly from CWL to Pachyderm. A first implementation of this would make for an excellent PR from someone who's more familiar with CWL and we'd be happy to give further guidance from there. |
Hi! More of a question than a issue. Currently we are modelling our data processing workflow using common workflow language (CommonWL, CWL). We hope this gives us the most portability between the various workflow management tools available. I can't really find any work or talk about integrating pachyderm with CWL. Has there ever been any thoughts about doing this? How likely is it that a 'standard' like CWL would get adopted for pachyderm?
Thanks!
The text was updated successfully, but these errors were encountered: