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
This is probably something that requires a little bit of collaboration from my side to (i.e a lambda function to point at).
Given a subject id can we assume to use the latest versions of umccrise / dragen wts analysis runs?
If so, lambda should only need the subject id and the dataset and should be able to populate the ready event from that?
In principle I am OK with whatever works. Just noting that there may be other options and that we don't need to cover all use cases from the start.
If I understand your question correctly, you'd try to infer the required input values given a subject ID only?
This will "hide" the inference in the back-end and it won't be visible to the triggering user. Not sure we want / have to go that way (yet).
For example: we'd usually have the default PANCAN run triggered automatically, right?
An option might be to only allow/support a "rerun" option, i.e. select that run in the UI and say "run this again, but switch the reference", then all required inputs should be present. It also means all required pre-conditions for running RNAsum are covered by default (as otherwise the initial run would not have gone through).
We'd only be supporting a very specific use case, but there should be no guesswork / inference needed and it's the most common use case (others could be handled manually until we have a better grip on them).
A way to manually trigger RNAsum, similar to what's possible in the v1 portal, is still needed in v2.
The text was updated successfully, but these errors were encountered: