Dear Galaxy dev,
I have two problems, which might be related to each other.
1) For a long time already, I continuously have ‘left over’ data allocation
after deleting and purging histories. Someone from your team has repeatedly
resolved that problem, but it root of the problem still persists. I know have
91% allocation, when only having two histories of 67.48 and 59.45 GB. The fix
for automatic recalculation doesn’t seem to work…?
2) I recently performed SNP mapping using a CloudMap based pipeline. The
problem: the SNP mapping plots shows the exact same mapping/plots of the SNPs.
They can not be the same. What is not the problem: the input files, as they are
different in size, first and last lines of the files, and they produce very
different SNP mapping mutation tables. Therefore, I think there might be a
problem that the workflow somehow uses the same intermediate file for
generating the SNP mapping plots. I already re-uploaded and rerun the workflows
in new histories multiple times, but the same result each time. I would upload
and run another data set for which I already have SNP mapping plots to see
whether I again get the same plots or not, but that is now not possible as I am
close to the data quota.
I hope you can help solve these problems.
Felix Mayr, MSc.
Max Planck Institute for Biology of Ageing
Research Group of Dr. Martin Denzel
Metabolic and Genetic Regulation of Ageing
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: