Hi,

We have a pipeline protocol where we use a Direct Structure Search component within a Run to Completion sub protocol (RTC). We realise the RTC is not the most efficient way to run queries, however for other reasons we are forced to do it in this case.

The particular Direct search is for Markush. We noticed that it was taking a long time to search given that very few Markushes were registered in the table (in fact none at the time).

Looking at the timings for the Direct Structure Search Component in more detail it looks like the part where it checks if the DIRECT_TMPQUERIES table exists is taking most of the time. As it’s in a Run to completion in our protocol it checks this everytime.

Is there any reason why we cannot remove this line from the Direct Structure Search? We can put it outside the RTC so it only ever checks and creates the table once (although it already exists)

We think it should work and a quick test seemed to suggest it does, but I wonder if anyone knows if DIRECT_TMPQUERIES is ever deleted and if altering the Direct Structure Search component for this protocol would cause other issues?

Thanks

Joe