Skip to content

implementing associated conditionals #3

Description

@fathoni

Writing conditionals can be exhausting when many if/else clauses are involved. To simplify the writing of conditionals, the authors can choose to write them in a concise manner as an associated conditional using the /number notation after the key-value pairs, and a comment denoted by regular bracket after the intended value.

Example

*"The top five templates identified by TopDomain were {3N25_A (a), 4YJ5_A (b), 3GR4_A (c), 1A49_A (d), 6DU6_B (e)|template_pdbs}/1 with sequence identities of {99% (a), 93% (b), 93% (c), 100% (d), 63% (e)|template_identities}/1, coverages of {95% (a), 97% (b), 97% (c), 97% (d), 96%(e)|template_coverages}/1, and predicted TM-Score of {0.96 (a), 0.96 (b), 0.96 (c), 0.96 (d), 0.93(e)| template_confidences}/1, respectively."*

Explanation

From the experiment documentation above, associated key-value pairs are marked with the number after the "/" symbol, so keys with a similar number are grouped together. In the example above, template_pdbs, template_identities, template_coverages, and template_confidences belong to the same association. The values on each key are then associated according to the comment in the regular bracket. Thus, if template_pdbs = 3N25_A, then template_identities = 99%, template_coverages = 95%, and template_confidences = 0.96. In a table, the correlation is grouped as shown below.

association set 1 1 1 1 1
mapping a b c d e
template_pdbs 4YJ5_A 3N25_A 3GR4_A 1A49_A 6DU6_B
template_identities 0.99 0.93 0.93 1 0.63
template_coverages 0.95 0.97 0.97 0.97 0.96
template_confidences 0.96 0.96 0.96 0.96 0.93

Note: the user needs to adapt this by removing irrelevant values and /{number} annotations when adapting the template to an experiment.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions