verify_constraints performance about dnaweaver

[Zulko]

There are several ways to up speed computations, but that depends on your project (do you have a minimal example you could share?).

The verify_constraints method is probably called on every subsequence so it is not surprising for it to be a bottleneck. The surest way to speed up computations is to use the coarse_grain/fine_grain parameters, or the A* parameter (both approaches reduce the number of subsequences evaluated, and correspond to slides 220-250 of this slideshow).

Another optimization consists in using memoize=True in CommercialDnaOffer and DnaAssemblyStation to cache the computations of price (and assembly plans) for subsequences. but that will only speed things up if you are doing multi-level assemblies, or if you are evaluating several sequences (with common subsequences) on a same supply network.

I understand that the documentation is not as good as it could be so don't hesitate if you have more questions.

[andrewshvv]

Thank you @Zulko! I will try what you mentioned

[andrewshvv]

To be honest, code comments helping a lot, so you are a bit humble on saying that documentation is not sufficient :)