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

Could not use find-transport function using '-m' option for specific metabolite. #203

Closed
ashish193006 opened this issue Jan 13, 2024 · 8 comments

Comments

@ashish193006
Copy link

for bug reports and errors please report the output of: ./gapseq test
The command './gapseq find-transport -m nitrogen genome.fasta' does not work. How can I solve this issue?

@Waschina
Copy link
Collaborator

There was a bug in the transporter prediction script. Thanks for reporting!

FWIW, the option -m nitrogen won't work, because there's no metabolite to test here. The molecule $N_2$ (Dinitrogen) readily crosses cell membranes without the need for a specific transporter. If you have a specific nitrogenous compound to test you can for instance use:

gapseq find-transport -b 200 -m Ammonia genome.fasta (testing for $NH_3$).

@ashish193006
Copy link
Author

ashish193006 commented Jan 13, 2024 via email

@ashish193006
Copy link
Author

ashish193006 commented Jan 13, 2024 via email

@Waschina
Copy link
Collaborator

Hi @ashish193006

It's working as expected on the two Linux systems I tested.

Did you update gapseq to the latest development version (e.g. via git pull)?

Please provide the output of gapseq test and the exact command you used.

@ashish193006
Copy link
Author

ashish193006 commented Jan 23, 2024 via email

@jotech
Copy link
Owner

jotech commented Jan 23, 2024

hi @ashish193006
Could you please try ./gapseq find-transport -b 200 -m Ammonia toy/myb71.fna.gz?
And if this fails, can you copy and paste the output of ./gapseq test?

@ashish193006
Copy link
Author

ashish193006 commented Jan 30, 2024 via email

@jotech
Copy link
Owner

jotech commented Mar 19, 2024

hi I'm sorry for the late response!

It seems it didn't work because you forgot to update to the newest version after the initial problem was fixed.
If it is still a problem, please update to the latest gapseq version (e.g., via git pull) and try again.

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

3 participants