Hi,
I ran allValls and I just got the following:
Reading the all-against-all files...
Error, (in AssertDatabaseVersionsInSync)
Matches between AEDAE/AEDAE have been computed for different version of AEDAE
I really didn't expect the AEDAE to give an error like this because I got the same version from OMA browser. Do you know whats going on here, I'm very confused?
Thanks,
R
EDIT: in the sha2 file for AEDAE they appear the same:
AssertDatabaseVersionsInSync('0f4e3562f0f28efa','0f4e3562f0f28efa')
EDIT2:
I have dug into the Cache and it appears that the precomputed files have the appropriate database ID , e.g. All of the sha2 files (precomputed only) have AssertDatabaseVersionsInSync('0f4e3562f0f28efa', ...). However, for the additional genomes I added to the analysis all of the first Ids (mapping to AEDAE in this case) is like this AssertDatabaseVersionsInSync('1fd703c2bc10ba56') when one would presumably expect the id to be '0f4e3562f0f28efa' as in other cases. This is systematic of all the additional genomes in my dataset. This was not an error I encountered in my first run of OMA which ran on an MPI based cluster - which had the same setup but had to be restarted form fresh - now running on SGE based HPC.
1 answer
The exported, pre-computed all-against-all files refer to specific data files. To ensure consistency, OMA standalone stores and verifies the SHA2 signature of the database files.
In your case, the database files in Cache/DB/ are not the original ones, which is why you get this error. You need to either restore the original ones or recompute the part of the all-against-all comparisons that involves them.
Log in to answer this question.