-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple 2bit references being loaded for hg19 #320
Comments
The loc files from galaxy's tool-data path are being read |
@mvdbeek So Galaxy is finding |
No, you did read the log messages correctly, but what I think what is happening is that any one entry references a |
The duplicate entry for hg19 should be gone now, and I also added mm7-mm10 |
Fixed, closing, thanks all! |
There are two entries for hg19 twobit in the
.loc
files on main. But it's not clear where those entries are coming from.This causes Extract Genomic DNA to fail, because it gets handed two paths joined with a comma.
- But it doesn't understand comma-delimited paths.
- Help issue caused by it: https://help.galaxyproject.org/t/extract-genomic-dna-issue/5012
The first entry is
/cvmfs/data.galaxyproject.org/byhand/hg19/seq/hg19.2bit
- found in
/cvmfs/data.galaxyproject.org/byhand/location/twobit.loc
- ..which is itself loaded by
/srv/galaxy/main/config/tool_data_table_conf.xml
- ..which is one of the values of the
tool_data_table_config_path
key inconfig/galaxy.yml
.The second entry is
/galaxy/data/hg19/seq/hg19.2bit
- this is found in
/galaxy-repl/main/tool_data/twobit.loc
- which is loaded by
/cvmfs/main.galaxyproject.org/config/shed_tool_data_table_conf.xml
, according to the startup logs- but
/galaxy-repl/main/tool_data/twobit.loc
isn't found anywhere inside that xml.So why does Galaxy think that
/galaxy-repl/main/tool_data/twobit.loc
is in/cvmfs/main.galaxyproject.org/config/shed_tool_data_table_conf.xml
?Or is that incorrect and it's coming from somewhere else?
Note: A current workaround for the problem this causes in Extract Genomic DNA is to use bedtools GetFastaBed instead, as mentioned in #286.
@natefoo @jennaj
The text was updated successfully, but these errors were encountered: