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

'mv' is not recognized as an internal or external command, operable program or batch file. #497

Open
weaversd opened this issue Jun 21, 2024 · 1 comment

Comments

@weaversd
Copy link

Hello,

I am encountering an error where I get the message "'mv' is not recognized as an internal or external command, operable program or batch file" in the peptide prophet portion of my workflow. I found two other issues on GitHub from 2018 that looked like similar problems that seemed like they were windows compatibility problems, although those were on much older versions so I am not sure.

I used a colleague's computer also on Windows 11 and ran the exact same workflow and input files with the same versions of FragPie, MSFragger, and Philosopher and experienced no issues. That makes me think it is a problem with my installation or file permissions, although I have double checked those to the best of my ability and everything seems ok. I tried un-installing and re-installing FragPipe and all the tools and the problem persisted. Here is my version information and I'm attaching the output log.

Version info:
FragPipe version 22.0
MSFragger version 4.1
IonQuant version 1.10.27
diaTracer version 1.1.3
Philosopher version 5.1.1

I also noticed that in my log it says '.NET Core Info: N/A', could that be an issue with my installation?

Any advise on troubleshooting would be appreciated!

log_2024-06-21_12-08-48.txt

Many thanks,
Simon

@fcyu fcyu transferred this issue from Nesvilab/FragPipe Jun 21, 2024
@weaversd
Copy link
Author

weaversd commented Aug 1, 2024

Hello, just checking in to see if there are suggestions for me to troubleshoot this issue. I have tried re-installing everything and the problem persists. Thank you!

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