10 months ago by
I suspect there is a format, content, or metadata problem interfering with the query. A tool issue is a potential, but checking the inputs first is where to start. If there is a tool problem, we want to learn about it and fix it.
I cannot find your account at Galaxy Main https://usegalaxy.org to troubleshoot whether it is the datatype assignments, true tool error, or input content/corruption (possibly an incomplete data transfer from UCSC - the export file line limit is around 100k from the Table browser - for anyone, not just Galaxy). For most MAF data, it is so large that it needs to be loaded from the UCSC downloads server, not the Table Browser. How-to: locate the files at UCSC (genome name > conservation tracks), download locally using their instructions, then FTP the data to Galaxy.
- You can try to troubleshoot yourself with this FAQ help: https://galaxyproject.org/support/#troubleshooting
- Or if your account is at Galaxy Main, send us an email at email@example.com from your registered account email asking for help (private list) and that will help us to locate it. Including a share link to the history in the email would be helpful but is not necessary, you could also note the history/dataset names/numbers in the email text (but do not delete these problematic datasets or histories if you want feedback). FAQ: https://galaxyproject.org/issues/#usage-problem-reporting
- Or, if you are not working at Galaxy Main right now, you could try to reproduce the problem there. If you can, please ask for help as in #2. If you cannot reproduce the problem, then you will need to contact the admins of the server you are working on. If you are the admin, make sure you are running the latest version of Galaxy (these tools are part of the core distribution) after first checking the inputs.
Please let us know how this works out! The tools are known to work when given the proper inputs but a new tool problem is always a possibility. We can help to figure out which and resolve it.
Thanks, Jen, Galaxy team