-
Notifications
You must be signed in to change notification settings - Fork 2
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
user reported issue on R script command being invalid #26
Comments
Found the potential issue. It could be due to differences in the versions of the workflow. Fixed the issue and running a test now. Will update and close the issue, if the test finishes without any issues. |
Issue fixed. Replaced Rscript with a python script. |
Hi Migun,
|
@jzrapp , the code had not been transferred to front end yet when you ran it. It has been transferred and we are running some tests to see if a runs complete. Will ping here if test runs completes without any issues. Thanks for your patience. |
Hi @jzrapp , please try your run again. Our test completed without any issues. During checking the results for the test run, I also found read counts per gene were null. Please let me know if you see the same with your dataset. i will close this issue upon your successful run, and will open a different issue for tracking the read count issue. Thanks. |
Hi @mshakya, I started several metaT analysis workflows and most of them have completed successfully. Two failed (giving 2 different error logs) and I'm re-running them once more. The files should be similar to those that completed successfully, so it doesn't make sense to me that these two did not complete. |
Ok, since this issue explicitly seem to be resolved, I will go ahead and close this issue. I am curious why the other two projects didnt complete? It would be good if you can open an issue with error message and i can take a look, especially if it doesnt complete the second time. I was looking at the files output by featurecount and also RPKM values reported in the results page. I have opened an issue (#28) to keep track of this issue. |
The text was updated successfully, but these errors were encountered: