Integrating Twist Bioscience API for Sequence Complexity Scoring

[GeneCodeSavvy]

Twist returns a categorical string ("BUILDABLE"), whereas IDT provides a numerical score.

I was thinking of a simple approach of normalizing outputs to a common scale (e.g., mapping "BUILDABLE" to a
specific numerical score like 0.0, and 10.0 for a sequence with issues).

[GeneCodeSavvy]

@Gonza10V @jakebeal If you agree with my approach, should I move forward with this implementation ?

[Gonza10V]

One solution could be to unify the outputs for both as IDT and Twist provide a value that tell us if its "BUILDABLE" (we can chage this name), which is basically a boolean property of the sequence. Then in the case of IDT we can add the complexity score to that property and just ommit it for Twist as it is not provided.

[jakebeal]

Does IDT have a cutoff where they reject sequences as not buildable? I think that users will typically be most interested in the boolean value of "can I order this?" Accordingly, it would be better to be able to change IDT's number into a boolean (if they have documentation for doing so), rather than changing Twist's boolean into a number.