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 started a discussion in dockstore (one of the TRS implementation) repository to find out if it is possible to combine existing tools for the TRS->CWL->TES execution chain use case: dockstore/dockstore#4132
In short, there is no current support for this case. The only way is to use legacy rabix bunny (with TES support) with an outdated dockstore version while the current version does not include any CWL engines with TES support.
I used cwl-tes with funnel, and it works just fine, so I am missing only the TRS integration piece. As I understand, it is relatively easy to create an adapter for cwl-tes support for dockstore, and I want to make sure it is the right way to do it. Well, also I need to double-check with their maintainer that this feature request will be accepted.
Please share your thoughts on how feasible my use case is and your current plans for further integrations with GA4GH services.
The text was updated successfully, but these errors were encountered:
I started a discussion in dockstore (one of the TRS implementation) repository to find out if it is possible to combine existing tools for the TRS->CWL->TES execution chain use case:
dockstore/dockstore#4132
In short, there is no current support for this case. The only way is to use legacy rabix bunny (with TES support) with an outdated dockstore version while the current version does not include any CWL engines with TES support.
I used cwl-tes with funnel, and it works just fine, so I am missing only the TRS integration piece. As I understand, it is relatively easy to create an adapter for cwl-tes support for dockstore, and I want to make sure it is the right way to do it. Well, also I need to double-check with their maintainer that this feature request will be accepted.
Please share your thoughts on how feasible my use case is and your current plans for further integrations with GA4GH services.
The text was updated successfully, but these errors were encountered: