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

running diffexp on examples/nema.yaml doesn't do anything? #103

Open
ctb opened this issue Mar 9, 2019 · 3 comments
Open

running diffexp on examples/nema.yaml doesn't do anything? #103

ctb opened this issue Mar 9, 2019 · 3 comments

Comments

@ctb
Copy link
Member

ctb commented Mar 9, 2019

I first ran:

./run_eelpond examples/nema.yaml

which completed successfully, and then ran:

./run_eelpond examples/nema.yaml diffexp

which did... nothing?

The output did include

        deseq2: /mnt/research/ged/ctb/eelpond/nema_out/diffexp
                     for explanation of this step, see: https://dib-lab.github.i
o/eelpond/deseq2

but that directory doesn't exist.

@ctb
Copy link
Member Author

ctb commented Mar 9, 2019

I tried

./run_eelpond examples/nema.yaml quantify diffexp

and it yelled at me about missing input files, so then I tried

./run_eelpond examples/nema.yaml assemble quantify diffexp

which seems to be appropriately making use of the preexisting assembly. Yay!

@ctb
Copy link
Member Author

ctb commented Mar 9, 2019

I think the desired behavior is to produce better error messages and suggestions. Doing this in a modular way is key - I don't think run_eelpond should have this error checking in it directly! Maybe we could put in something that when a particular rule file is included, it has some high level checks that it runs, or maybe that should be connected in some way to the higher level workflows mentioned in pipeline_defaults.yaml?

@ctb
Copy link
Member Author

ctb commented Mar 9, 2019

assemble quantify diffexp worked!

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

1 participant