You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the following commands to generate HTML files from Foldseek result files by varying the coverage mode to output different TM scores: query-normalized, target-normalized, and both query and target-normalized TM scores.
Expected Behavior:
The generated HTML files should display different TM scores based on the specified coverage mode:
--cov-mode 0: TM score normalized by both query and target.
--cov-mode 1: TM score normalized by target.
--cov-mode 2: TM score normalized by query.
Actual Behavior:
All the generated HTML files show the same TM scores, which suggests that the coverage mode option might not be working as expected.
Has anyone else experienced a similar issue with Foldseek? Is there a workaround or a fix for ensuring that the coverage mode is properly applied to the TM score calculation?
The text was updated successfully, but these errors were encountered:
I am using the following commands to generate HTML files from Foldseek result files by varying the coverage mode to output different TM scores: query-normalized, target-normalized, and both query and target-normalized TM scores.
foldseek easy-search MW355455-CDS-0004.pdb Foldseek_db/anti_crispr_db query_target.html tmp --format-mode 3 --alignment-type 1 --cov-mode 0
foldseek easy-search MW355455-CDS-0004.pdb Foldseek_db/anti_crispr_db target.html tmp --format-mode 3 --alignment-type 1 --cov-mode 1
foldseek easy-search MW355455-CDS-0004.pdb Foldseek_db/anti_crispr_db query.html tmp --format-mode 3 --alignment-type 1 --cov-mode 2
Expected Behavior:
The generated HTML files should display different TM scores based on the specified coverage mode:
--cov-mode 0: TM score normalized by both query and target.
--cov-mode 1: TM score normalized by target.
--cov-mode 2: TM score normalized by query.
Actual Behavior:
All the generated HTML files show the same TM scores, which suggests that the coverage mode option might not be working as expected.
Has anyone else experienced a similar issue with Foldseek? Is there a workaround or a fix for ensuring that the coverage mode is properly applied to the TM score calculation?
The text was updated successfully, but these errors were encountered: