-
Notifications
You must be signed in to change notification settings - Fork 7
Description
It isn't clear how hierarchical designs are handled in terms of strand directionality. So if there is an engineered region in the top level that then has its orientation flipped to the lower strand, when navigating into this to define the parts they automatically get added in the conventional top strand approach - but is the assumption that we are looking at the reverse complement (i.e. they are reversed because the parent object is reversed - this is what I assumed would be the case), or is it still looking in the top strand (not reversed) orientation.
I couldn't find any information to give the user any clues .
When I created a combinatorial design with one of the top levels reversed, but the lower layer following the 'forward' notation, the CSV file listed them all in top strand format i.e. the reversed component was not reversed from a part order level.
There may be a discrepance between CSV and SBOL output - I didn't check the latter.
In BASIC assembly we have linkers that can reverse parts or assemblies, and Golden Gate also has reversing destination constructs, so somehow tagging this in CSV files that can produce output would be an interesting proposition. I'm not sure how this would work though!