Closed rrwick closed 5 years ago
Hm - I'll ping @Phelimb as this code has changed since I was expert on it, but I would expect the skeleton to be in the install dir - why does it not have write access in the dir it is installed in? I think the skeleton is generated once, and is written to file. All future runs then use that skeleton.
I think the skeleton is generated once, and is written to file. All future runs then use that skeleton.
Yes, this is correct. I try to write in the install directory by default, however it looks like you don't have write permissions in there so unfortunately you'll need to use the --skeleton_dir argument for every run.
@iqbal-lab I'm not sure if there's anything that needs to be changed here. Perhaps we should use a tempfile for skeletons rather than writing to instal directory?
I don't think anything needs changing except maybe documentation.
When I ran
mykrobe predict
on a TB sample, it quickly failed with this error:The issue seems to somehow relate to mykatlas, which has the
--skeleton_dir
argument that has a default value ofatlas/data/skeletons/
. Somewhere along the way, this is becoming a path in the installation directory of Mykrobe predictor (see error above), where it doesn't have write permissions.I can avoid the issue by using a non-default value for
--skeleton_dir
, but it still feel like something is going wrong... shouldatlas/data/skeletons/
end up in the directory where I'm running Mykrobe predictor, not the directory where it's installed?