TBX: x.x, Progression computed on Sub-corpus

X-axis range

Currently, the X-axis starts with the subcorpus first word position and ends with the last word position.

The new behavior must translate the subcorpus positions so that the X-axis starts at 0.

Subcorpus continuity

Solution 1

Currently, the sub-corpus continuity test is only to verify if the CQL query result corresponding to the sub-corpus is composed of only ONE match.

Solution 2

Next step is to test the continuity of all the matches of a sub-corpus:

• if query result is composed of one match return TRUE
• else for each match
  • if last match, break
  • if current_match.end = next_match.start-1 then continue
    • else return FALSE
• return TRUE

Validation test

• Create a subcorpus with DG6 and DG7 texts of DISCOURS corpus
• run a progression with “je” query, the progression is computed and the result is the same for R and Java Graphic renderer
• Create a subcorpus with DG6 and DG11 texts of DISCOURS corpus
• run a progression: a message appears, the progression cannot be computed (fr=La fonctionnalité Progression n’est pas encore disponible pour les sous-corpus discontinues.)

MD: OK Linux64

(from redmine: issue id 841, created on 2014/06/02 by Matthieu Decorde)

• Relations:
  • relates #1296

added Commands type::feature + 1 deleted label

changed milestone to %TXM 0.7.7

I think this issue is related to a more general question about sub-corpus management. (The solution #1 and #2 don’t seem to be satisfactory)
I created an issue for this, see #1296.

(from redmine: written on 2015/04/02 by Sebastien Jacquot)

not yet commited

(from redmine: written on 2015/04/14 by Matthieu Decorde)

The TXM 0.8.1 implementation also works with contiguous matches (eg 3 following texts matches)

(from redmine: written on 2021/03/12 by Matthieu Decorde)

mentioned in issue #1296

closed

assigned to @mdecorde