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

partial workflow invocation #416

Closed
lstrgar opened this issue Jan 25, 2022 · 9 comments
Closed

partial workflow invocation #416

lstrgar opened this issue Jan 25, 2022 · 9 comments

Comments

@lstrgar
Copy link

lstrgar commented Jan 25, 2022

I'm having trouble invoking and running the entirety of my workflow with bioblend.

My pipeline is (1) input collection --> (2) BaSiC correction --> (3) Ashlar for stitching

(3) depends on (1) and (2) while (2) only depends on (1).

Step (1) is working correctly but (3) never gets run. It's not even included in the history.

Any suggestions for how to debug this? Or what the problem might be?

Thanks in advance.

@simonbray
Copy link
Member

Can you provide some code please? (if it's possible to share the workflow, that would be helpful as well)

Are you able to run the workflow successfully in the UI?

Best wishes,

Simon

@lstrgar
Copy link
Author

lstrgar commented Jan 25, 2022

    gi = bioblend.galaxy.GalaxyInstance(url=config["galaxyUrl"], key=config["apikey"])
    ## workflow_args is a generator yielding tuples of history_id and hdca data description 
    workflow_args = upload_dir(config['datapath'], config['libraryId'], config['folderId'], config['workflow'], gi)
    wfdesc = get_workflow_description(gi, config['workflow'])
    workflow_id = wfdesc["uuid"]

    for hid, data in workflow_args:
        inputs = {
            '0': {
                "src": data['src'],
                "id": data['id'],
            },
        }
        res = gi.workflows.invoke_workflow(workflow_id, inputs, history_id=hid, import_inputs_to_history=False)

@lstrgar
Copy link
Author

lstrgar commented Jan 25, 2022

Does this link work for you?

https://galaxydev.ohsu.edu/u/strgar/w/crc-r01

Invoking the workflow in the browser successfully completes the entire pipeline.

@simonbray
Copy link
Member

I cannot access that link - I get Server Not Found.

If you can invoke it in the UI, I would suggest looking up the successful invocation id with gi.invocations.show_invocations() and checking that the inputs and input_step_parameters fields match what you are submitting via the API.

@lstrgar
Copy link
Author

lstrgar commented Jan 26, 2022

I had previously check input but I'll look at input_step_parameters.

If they differ how can I adjust the invocation to specify step parameters?

@simonbray
Copy link
Member

simonbray commented Jan 27, 2022

You should be able to add params=input_step_parameters to gi.workflows.invoke_workflow().

@lstrgar
Copy link
Author

lstrgar commented Jan 27, 2022

There are no differences in the input fields for jobs invoked from the command line and those invoked from the GUI.

@simonbray
Copy link
Member

If you could share the workflow and some test data with me (either via a public Galaxy instance, or a chat like gitter or matrix, or in this issue, whatever you prefer) I can have a look. Not sure what else to suggest right now.

@lstrgar
Copy link
Author

lstrgar commented Jan 31, 2022

Sure gitter works. Thanks for your offer. Presumably your handle is gitter.im/simonbray? Message sent.

@lstrgar lstrgar closed this as completed Jan 31, 2022
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

2 participants