giffordlabcvr / digs-tool Goto Github PK

I was trying to extract E-values for DIGS hits and noticed that there are two columns for E-value in the digs_resuts: evalue_num and evalue_exp. It looks like E-value is split into numerical and exponential parts when it is found in the form like 3e-15, so that evalue_num = 3 and evalue_exp = 15. In other cases (e.g. when E-value is 0.001) it is supposed to be stored in the evalue_num (evalue_num = 0.001) while evalue_exp = 1.

However, all evalue_num in the digs_resuts table are integer numbers (not floating-point numbers). It causes a problem. Since BLAST assigns E-value of 0.0 to all E-values below 1e-180 and DIGS loses information about E-values with floating point, now I have the same evalue_num = 0 and evalue_exp = 1 for hits with extremely high bitscore (>498) and extremely low (<30).

Good afternoon,

I am wondering if there is a possibility to turn OFF the filtering of low-complexity regions in DIGS or make the filtering optional (e.g. in the control file). I am searching for a protein with a region of lox complexity, and unfortunately, this region cannot be found unless the filtering is switched off. I tested it using DIGS, NCBI tblastn, and Ensembl tblastn. NCBI and Ensembl allow me to find the exon corresponding to this region only when I deselect the "Filter low complexity region" option, while I cannot find the region at all using DIGS. I hope it makes sense.

Thanks a lot in advance!

Hi. I've recently updated DIGS to the latest version from GitHub and noticed that the bitscore threshold is no longer working. Now digs_results table in the MySQL database contains all DIGS hits, no matter whether their bitscore is higher than the threshold specified in the control file or not. For instance, here is what I found in my digs_results table after I specified the bitscore of 31 as the threshold. Before that, I was using the DIGS version that I installed from GitHub in January 2023. It was the latest version back then and the bitscore threshold worked fine. Thanks a lot!

I've created a Dockerfile for DIGS-tool to easily install and use it.

There are three additional files:

1. start.sh - it starts the mysql server
2. results.R - Grab data from the database and save it into a file
3. example_ctl.txt - control file for DIGS-tool

I have some experiences with Docker, however, I'm not an expert.
DIGS-tool_Dockerfile.zip

If you think that it can be a new and useful feature then I'm more than happy to help to develop it.

Hi. I've recently updated DIGS to the latest version from GitHub and noticed that a new global variable called DIGS_HOME2 has been introduced. This variable is not mentioned in the DIGS manual, so I just duplicated the path to my DIGS-tool directory to it (the same path that was assigned to the DIGS_HOME) keeping DIGS_HOME unchanged. It looks like DIGS is working fine (apart from the bitscore threshold), so I am flagging this up just in case.