Once you've done that, you can either add to $PATH as suggested or issue the command as /path/to/owltools.
This beasty does the same GAF checks as the GO Jenkins setup. Remove the newlines so it's all one big command. You'll also have to replace "/path/to/go/" and "/path/to/output/" with the actual paths (obviously):
I've got this running on my desktop now; it turned out to be dead easy, so holler if you want any pointers.
Great. That will be very helpful. If you have any notes or command line examples, could you add them to this ticket?
Cheers.
Diff:
Sorry didn't get round to this yesterday ...
Download & install owltools for the command line. I followed the "Building from Source" instructions here and it seemed to work fine:
http://code.google.com/p/owltools/wiki/InstallOWLTools
Once you've done that, you can either add to $PATH as suggested or issue the command as /path/to/owltools.
This beasty does the same GAF checks as the GO Jenkins setup. Remove the newlines so it's all one big command. You'll also have to replace "/path/to/go/" and "/path/to/output/" with the actual paths (obviously):
Would it be OK to run these checks when loading Chado and add a new log file? It would be a convenient to run it as part of the usual load.
yep, that would make perfect sense