<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><div><br></div><blockquote type="cite"><div><span style="caret-color: rgb(0, 0, 0); font-family: ArialMT; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Incidentally, this UI was inherited from BNCweb, which was designed with hardware limitations of 20+ years ago in mind. (Thus the need to set the collocation data just once when entering the collocation screen; thus the avoidance of compiling data for attributes/spans that weren't needed, in order to keep things fast.)</span><br style="caret-color: rgb(0, 0, 0); font-family: ArialMT; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br style="caret-color: rgb(0, 0, 0); font-family: ArialMT; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: ArialMT; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">On today's systems it is probably safe to recalculate the data between displays of the collocation screen if necessary. That would allow all the options to be moved into the Collocations screen, without the separate little popup. (I'd probably then segment the Collocation controls into "Basic" - the span and stats - and "Detailed" - minima, p-attribute, etc, only appearing when invoked.)</span><br style="caret-color: rgb(0, 0, 0); font-family: ArialMT; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"></div></blockquote></div><br><div>My impression is that building the collocation database can still take a substantial amount of time for a node with tens or hundreds of thousands of occurrences, but I haven't actually checked this in a current version of CQPweb running on current hardware. If we could avoid MySQL and do computations in memory with something like NumPy, this might indeed be faster in the end.</div><div><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><blockquote type="cite"><span style="font-family: ArialMT;">The TLDR is that your users should set the max span to L10 R10 in order to get the flexibility to use large spans once they are on the collocations screen.</span></blockquote></div><div><span style="font-family: ArialMT;"><br></span></div><div><span style="font-family: ArialMT;">Given that hardware limitations aren't as tight as 20 years ago, perhaps a very simple change would be to make this the default setting for the collocation database? I.e. maximal supported span + include all annotations. Users would still be able to change these options to more conservative settings when running a very large collocation analysis.</span></div><div><span style="font-family: ArialMT;"><br></span></div><div><span style="font-family: ArialMT;">Best,</span></div><div><span style="font-family: ArialMT;">Stephanie</span></div></body></html>