Closed ohickl closed 4 years ago
Hi Oskar,
All of the issues above should hopefully be solved by using complete paths instead of relative paths in the command line.
Best regards, Harald
Hi again,
One correction. The Andromeda issues will not be solved by using complete paths, as Andromeda is only supported on Windows. :)
A version for Linux was in development, but I do not know what the status is. But we will of course update the Andromeda version in SearchGUI when/if a new version becomes available.
Best regards, Harald
Hi Harald, using absolute paths seems to work, thanks! Regarding Andromeda, didnt they release the mono version of MaxQuant some time ago? Or does that not mean that Andromeda will now also work on Linux as a standalone?
Regarding Andromeda, didnt they release the mono version of MaxQuant some time ago? Or does that not mean that Andromeda will now also work on Linux as a standalone?
They did. But the standalone version of Andromeda was never officially released as far as I know. We had access to a beta version a while back, but it had some unresolved bugs. We'll contact them again to check the status.
Hi, I'm having trouble running Comet and Andromeda on a Linux server. I am using the following command:
Using either Comet or Andromea will give me different errors while e.g. X!Tandem and MS-GF+ run fine.
Comet outputs the following when I use the default tmp folder path:
With log entry:
With custom temp and comet_temp folder I get:
With log entry:
Andromeda outputs the following when I use the default tmp folder path:
With log entry:
With custom temp and andromeda_temp folder I get:
With log entry:
Could this be a bug or might it be an error in my application of the tool? I can provide you with the .par file as well (which I created using the IdentificationParametersCLI tool), if needed.
Best
Oskar