Dear Friends
I’m studying “High Throughput Molecular Dynamics and Analysis,” and several times, using the recommended data, I have the results (in my history) in red (Error) for “Generate MD topologies for small molecules ( Galaxy version 21.3+galaxy0).”
Then, if you need more help, please share back your history so we can check if this is a server problem, or something with your data itself. The most common reason for errors with this tool is missing annotation inside the PDB and the logs will note that, but it is a bit complicated, and we can try to help to diagnose that.
How to share is in the banner at this forum, or see here directly → How to get faster help with your question. A shared history link is best for this since we’ll need access to all of the job logs, and that is difficult to capture with screenshots. But you decide how quickly you want this to be resolved.
Ok, thanks for posting back your history. The input file to the tool you are asking about what empty.
This is a screenshot from the job information view using the i-icon on the failed red dataset. This is always the place to check how the job was run, even if successful and you just forgot what parameters were used or whatever.
Then, if I look at the jobs that generated that input, it seems the problem was introduced at the start. This is what I was talking about in the other topic about the most common problem being missing annotation in the original PDB file. I think that is what is going on with your problem, too.
More screenshots, this time just of the history share link to show the status of the files along the chain. Notice how dataset 3 is empty.
Dear Jennaj
I tried several times, with different parameter combinations, to extract the ligand file from the shared history. I haven’t had any success.
It seems that the system does not recognize just AGSE or BGSE. It extracts HETATM (a mixing of AGSE, BGSE, and other HETATM). I believe I need just the ligand A (AGSE) or the ligand B (BGSE).
Can you help me?
Thank you
Henrrik
The first step in the protocol is excluding HETATM specifically.
You can customize what you want to review with the options on the form.
Also keep in mind: tools available in the Galaxy website are still the original tool, exactly how the original authors wrote them. If the underlying tool cannot process a certain type of data, then that same tool as available in Galaxy cannot process it.
Now, I don’t think that is what is going on with your data (yet). I do see that your history is now private, and that you have run the first step several times. For now I’ll just say – compare to the tutorial example and notice the “Don’t Match” option set at the very top. That means that if found, that line is not printed out into the output.
You will need to customize what to keep and what to exclude to fit your own data: use the terms in your PDB to guide what to input on the form.
If you have a term that you are not sure how to format for the perl regex, we can probably help, but will need to see those specific lines here and what your expression looks like now.