Activity for IMS Open Corpus Workbench
-
Andrew Hardie committed [r1906] on Code
fix tiny but horrible bug where integer data was sometimes being transmitted to the browser as strings
-
Stephanie Evert committed [r1905] on Code
Fix spurious test error in Perl CWB package
-
Philipp Heinrich created ticket #81
Missing warning message for p- and s-attributes with the same name
-
I properly buggered up the try-catch logic round mysqli-rollback. so let's give that one more go, shall we.
-
my 2nd effort to stop PHP8's mysqli extension spilling exceptions all over the damn place by try-catching every call to a mysqli func that might possibly throw, hopefully thus keeping the madness contained in sql-lib. [THANKS PHP8svn diff rss.php svn diff rss.php ] ...plus a tiny fix to the rss generator.
-
tiny fix for stupid utf8 bug in php 8
-
CWB/Perl: fix option specification in cwb-make
-
Add requested feature to allow disabling of email confirmation on signup.
-
Make Perl/CWB utility cwb-convert-to-utf8 more compatible with iconv implementations
-
Check in older modifications in CWB/Perl branch v3.0
-
Fix bug in CWB::RegistryFile so that NAME with backslash-escapes round-trips correctly
-
fix some bloody obvious errors in the test implementation of soft keyboards, including (\!) having somehow missed adding the needed javascript file to make them actually work
-
Fix ShowTargets option to work with Highlight off (shown as parenthesised numbers then)
-
Document new hidden KnitWithEcho option in CQP manual
-
Add hidden `KnitWithEcho` option to control whether CQP code blocks are included in markdown knit mode (-N) output.
-
three minor bugs: in SQL server connection, in colleaguate config, in allowing indexing of CWB IDs that the CL reg parser can't handle
-
Fix CWB::CL test that returns different result with PCRE2 (in CWB >= 3.5.1), so CWB::CL now also provides version information.
-
amend previous commit
-
don't install signal handlers in CQP batch mode
-
fix bug in cwb-s-encode
-
Document experimental markdown mode in CQP Manual (now updated to v3.5.1)
-
CQP v3.5.1: experimental markdown mode, which reads markdown files and executes fenced code block of type "cqp"
-
init implementation of soft keyboards (much work remains) and as a fun extra, a rainbow background feature
-
Enhance CQP with custom SpheroscopeDebug option (experimental)
-
CQPweb: more elaborate customisable header for corpus homepage
-
Make sure cwb-encode aborts with meaningful error message if there are unparseable arguments
-
a bundle of fairly small tweraks and bugfixes
-
Encourage users to upgrade to v3.5.1
-
small php 8.2 incompatibility fixed
-
minor lost comment tweak
-
add cronjob to check for overrunning CQP processes
-
Fix bug in cl_string_canoncial(), which would fail on diacritic-folding of long strings (where NFC exceeds CL_MAX_LINE_LENGTH)
-
CQPweb: per-user tabulation templates
-
fix to breaking bug in BasicVrtInstaller
-
No there's not, because it's (a) really far in the future and (b) not going to be remotely difficult when we actually get there.
-
ram posted a comment on ticket #72
Yes, I had to found a work around the attribute separator. My suggestion about FreeLing was mainly for the possibility to display the token and its attributes as nodes, instead of plain text. But it seems it implies a lot of fixes and that is something that is going to be fix in version 4. Is that the case, is there any draft for the XML output?
-
Thanks, sorry for the mistake
-
1. MAke code closer to PHP8-ready by declaring all config variables in the global Config object's class def. 2. Initial implementation of classification-type metadata as SQL-level enums, not varchar columns (for more compact storage).
-
add ability to probe data for XML structure rather than it needing to be defined. Bump version to 3.3.18
-
A kwic concordance (where left and right context might not even contain complete tokens!) is very different from a list of sentences with pre-determined annotation as in the FreeLing output. I don't think we can learn much from it to help us address the challenges of kwic XML output. SGML print mode is really badly broken if you display s-attributes in the concordance. It also includes them (and any p-attributes) as plain text in the tokens rather than in a way that allows them to be processed e.g....
-
You seem to have forgotten to activate the corpus: info PRUEBA; but PRUEBA; show cd;
-
Thanks for your response! cwb-describe-corpus -s works perfectly. For show cd I still get incomplete information: ===Context Descriptor======================================= left context: 25 characters right context: 25 characters corpus position: shown target anchors: not shown Positional Attributes: <none> Structural Attributes: <none> Aligned Corpora: <none> ============================================================
-
About the DTD, I will use the same SGML structure but XML compliant. For more ideas about the schema, FreeLing output formats could be an useful resource.
-
Note to those not familiar with CQP print modes: Their implementation is a horrible mess, so we are reluctant to add extensions and very limited in what can be achieved. Moreover, the print modes only affect some CQP output (kwic concordances, frequency tables from group) but by far not all.
-
XML output mode for CQP
-
Because that's how the orginal developer decided to do things in 1994. It's a quirk that we live with for the sake of backwards compatibility. Note that the filename of the registry file also has to be in lowercase, while corpus IDs are to be specified in all caps everywhere else. You can get the list of attributes with show cd or using cwb-describe-corpus -s on the command line. Canonical attribute names (both positional and structural) should be all lowercase and only use ASCII characters. While...
-
Corpus info output
-
XML output mode for CQP
-
Consistent output formatting
-
SGML invalid structure
-
PS: If you want to pursue this, please add a feature request “XML output mode for CQP” for CWB v3.6.
-
Not a bug: SGML allows omission of closing tags – you just have to assume a suitable DTD for the output produced by CQP. Note that your second suggestion isn't valid SGML and would have to be written <attribute// instead. If your SGML output also included the kwic line with some s-attributes shown, you'd get many more validation errors (because nothing guarantees that open/close tags match up within a kwic line, and they can also overlap between context and match). If we ever find the nerves to implement...
-
SGML invalid structure
-
fix bug where PHP8 type stringency caused a null DB result to choke array_map() up.
-
add braces to silence complaint from GCC
-
cwb-scan-corpus now also reports type count before applying frequency filter
-
Ziggurat design: even more B-tree algorithms
-
Ziggurat design: added binsearch benchmark observations with Rust on MacOS
-
fixes for a couple fo tricksy bugs.
-
full rewrite of the url_absolutify() function to work within user corpora, plus to rationalise its overall procedure a bit.
-
Ziggurat design: try yet another binary search algo (unsuccessfully)
-
Timm Weber committed [r1865] on Code
more benchmark data
-
more rust benchmarks
-
Ziggurat design: fix uint typedef conflict (now zuint)
-
fixed bug in rust benchmarks
-
added rust implementations of the benchmarks in binsearch_bench
-
Added binary search benchmarks for random walks and exponential search algorithm
-
Convert README to Markdown + HTML for easier reading
-
Ziggurat design: estimate disk size of compressed sparse inverted index
-
Add HTML version of Markdown README for convenience
-
Ziggurat design: benchmark results for binary search in sort index, with thorough discussion
-
Ziggurat design: benchmark binary lookup in large tables vs. b-tree
-
Ziggurat design: estimate size of sparse inverted index
-
Fix extremely embarrassing as well as catastrophic bug in cwb-scan-corpus introduced by r1851
-
minor display fix in cwb-scan-corpus
-
cwb-scan-corpus now obtains total token/document counts if no regular keys are specified
-
fix query strategy bug (dropdown wasn't ignored in cqp syntax mode)
-
Error when setting up speaker metadata via IDlinks for BNC2014 spoken
-
Fixed in commit 1849. This is one of those embarrassing bugs that I would have spotted years ago if I used the embiggenable forms much myself - but I normally use templates. Alas. In any case, thanks to Fabian for the bug report.
-
fix UI bug on embiggenable tables
-
Fabian Vetter created ticket #79
Error when setting up speaker metadata via IDlinks for BNC2014 spoken
-
some fixes for small distribution / categorised query bugs
-
CQPweb: no alert on absent or malformed text + text_id attributes in input data
-
[UNREADABLE] means that the some word could not be read from the data returned by CQP. In this case, it happened because the absence of text_id mucked up the processes that break up that data for formatting. You'll note that on your installation form screenshot, there is a notice at the top of the XML table saying that <text> and its id="..." are "... compulsory".</text> So they are added to the corpus definition even if you don't speciy them on the form. Unfortunately cwb-encode doesn't issue errors...
-
Thanks for the response. I checked the api-lib.php because some days ago I tried to use the run_query function that in my current version is not implemented, but I see that right now it is implemented. I am going to report all this info, and since we stopped having issues with CQPweb, with my team we are going to see if we actually have to implement a whole new web platform with Django, or if we better work on a nice minimalist template for CQPweb. Thanks!
-
This is one of those rare occasions when I have to disagree with Stephanie - there are some things you can get from CQPweb via API that direct CWB access won't get you: collocations, distribution, linking queries to text or item metadata (and getting same in results...), user accounts, query history, case-folded frequency lists, saved and categorised queries, character set standardisation, ... See https://sourceforge.net/p/cwb/code/HEAD/tree/gui/cqpweb/trunk/lib/api-lib.php for where I'm at so far....
-
This is one of those rare occasions when I have to disagree with Stephanie - there are some things you can get from CQPweb via API that direct CWB access won't get you: collocations, distribution, linking queries to text or item metadata (and getting same in results...), user accounts, query history, case-folded frequency lists, saved and categorised queries, character set standardisation, ... See https://sourceforge.net/p/cwb/code/HEAD/tree/gui/cqpweb/trunk/lib/api-lib.php for where I'm at so far....
-
Ok, now I confirm that the [UNREADABLE] was because the text tag requires the id. With the id attribute everything work as expected. Thanks @schtepf for your patience. The only weird thing left is that I don't receive an error message or warning when I don't add the text tag.
-
I can confirm that the problem is because the lack of <text> tag. I did a test where I include that tag and it doesn't hangs. But now I have these doubts: What does the [UNREADABLE] means in the query result? Just to be sure, is the id attribute for the text tag recommended or mandatory? I attach the VRT test file and the screenshot of the result.
-
I didn't get any errors. I attach the process I am doing for the corpus installation. Thanks!
-
Re. 3: If you installed this particular corpus in CQPweb, you must have ignored all the error messages that it shot at you. It should have outright refused to install the corpus, but perhaps it went far enough to get its database into an inconsistent state that causes the lock-up.
-
Let's see: Every time it returns a match No, it works if I use CQP I did :S
-
(a) Does this happen for a specific query, or for every query that returns some matches? In the latter case there' s probably sth in the corpus that confuses CQPweb. (b) Are there also problems if you run the query directly in CQP? (c) You can't possibly have installed this corpus in CQPweb because it's lacking the mandatory <text id="..."> elements!
-
(a) Does this happen for a specific query, or for every query that returns some matches? In the latter case there' s probably sth in the corpus that confuses CQPweb. (b) Are there also problems if you run the query directly in CQP? (c) You can't possibly have installed this corpus in CQPweb because it's lacking the mandatory <text id="..."> ... </text> elements!
-
(a) Does this happen for a specific query, or for every query that returns some matches? In the latter case there' s probably sth in the corpus that confuses CQPweb. (b) Are there also problems if you run the query directly in CQP? (c) You can't possibly have installed this corpus in CQPweb because it's lacking the mandatory <text id="..."> elements!</text>
-
(a) Does this happen for a specific query, or for every query that returns some matches? In the latter case there' s probably sth in the corpus that confuses CQPweb. (b) Are there also problems if you run the query directly in CQP?
-
cwb-ccc should give you most (if not all) of what you can get from the CQPweb API, and it will be faster (as everything is directly in Python and doesn't need to be serialised and de-serialised) and more directly under your control. I think CQPweb is useful for your use case only if you need its GUI.
-
Best approach for interfacing CQP with other software
-
I forgot to put the versions: CQPweb: 3.2.43 CWB: 3.5.0
-
CQPweb hangs in an specific scenario
1 >
