So far, so good!
Now I have another question, and it's of a more logistical, lazy nature.
I noticed that the options file for ACT is actually the same as one for
ARTEMIS. The run scripts looked awfully similar too.
Given my natural inclination to never configure the same thing twice, I
just went ahead and made symbolic links from the ARTEMIS config files to
the ACT folder, and they seem to work just fine. Is doing this sort of
thing safe, or will there be a gotcha somewhere down the road?
Thanx,
anja
P.S. This ACT viewer *rocks*.
--
Angela M. Baldo, PHD
Microbial Food Safety
ERRC, NAA
ARS, USDA
600 East Mermaid Lane
Wyndmoor, PA 19038-8598
[EMAIL PROTECTED]
voice: (215) 233-6587
fax: (215) 233-6581
- [artemis-users] Invoking Blastall Angela M. Baldo
- [artemis-users] passing blastall output to ACT Angela M. Baldo
- [artemis-users] p.s. (using only blastn) Angela M. Baldo
- [artemis-users] never mind about how to invoke bl... Angela M. Baldo
- Re: [artemis-users] never mind about how to i... Kim Rutherford
- Re: [artemis-users] options and run scripts f... Angela M. Baldo
- Re: [artemis-users] options and run scrip... Kim Rutherford
- [artemis-users] Row width in "v... Angela M. Baldo
- Re: [artemis-users] Row width in... Kim Rutherford
- [artemis-users] Re: Row widt... Angela Baldo
- Re: [artemis-users] Re: Row ... Kim Rutherford
