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
Reported by tiberium87 on 2014-07-02 01:54 UTC
want to parse the att, anti, and rbs strings based on some logic, instead of listing special cases. Would probably do this in a module based fashion: att calls a function which goes and sets up some att capability, anti, calls an antisense function with sets up the relevant antisense logic. Then can have any number of att, anti and rbs to get any logic.
The text was updated successfully, but these errors were encountered:
murrayrm
changed the title
Add module based handling of antisense and attenuator sequences
Add module based handling of antisense and attenuator sequences [sf#13]
Jul 28, 2017
Removed this completely from the toolbox, so that it can be re-added in a more generalizable fashion (the previous code was becoming an unwieldy set of special cases).
Can you reference the commit in which this was removed, so that someone looking at this issue in the future can see how it was handled in the past (and hopefully re-introduce in a more generalizable way)?
Reported by tiberium87 on 2014-07-02 01:54 UTC
want to parse the att, anti, and rbs strings based on some logic, instead of listing special cases. Would probably do this in a module based fashion: att calls a function which goes and sets up some att capability, anti, calls an antisense function with sets up the relevant antisense logic. Then can have any number of att, anti and rbs to get any logic.
The text was updated successfully, but these errors were encountered: