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
Right now it's difficult to know what types of jobs I need to submit to a cromwell server to hit the various pieces of code in the package. Maybe we just need a few complex WDL/json files, or possibly many of them doing different things?
Some of the WILDS WDL scripts would probably be ideal for these kinds of tests. Definitely important and feels like this package won't change much in v2.0, but similar to CRAN submission, the effort seems a little high for v1.X. Very open to moving this up to v1.2 or v1.3 if people feel strongly, but setting as v2.0 for now.
This is definitely something we should work on to test the limits of PROOF v1 or v2. Its fair to label it as a medium priority but testing the limits of Cromwell integration will be crucial. WILDS WDL scripts or the complex one we are running for single cell should be good. But need to chalk out a plan that tests particular sections of PROOF very specifically would be important.
Right now it's difficult to know what types of jobs I need to submit to a cromwell server to hit the various pieces of code in the package. Maybe we just need a few complex WDL/json files, or possibly many of them doing different things?
Gather from @vortexing and @sitapriyamoorthi
The text was updated successfully, but these errors were encountered: