Bug #2281
Progression on a sub-corpus : x-axis is defined by the corpus instead of sub-corpus
Status: | New | Start date: | 11/20/2017 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 10% |
||
Category: | Charts | Spent time: | - | ||
Target version: | TXM X.X |
Description
FR
BP: Calcul d'une progression sur un sous-corpus (tout simple, un texte dans un corpus) : l'axe des x commence au début du sous-corpus mais termine à la fin du corpus. Corrélaire : La valeur de T qui s'affiche sous le graphe correspond à la taille du sous-corpus augmentée de la taille de la partie du corpus qui précède le sous-corpus.
Si on utilise le bouton "Reset the chart view", l'axe des x devient celui du corpus entier.
SJ:
Behaviors described in this issue seem to have changed a few since 0.7.8.
JFC charts engine:
- x axis starting delimiter is well set to the first word number of the subcorpus in root corpus space
- x axis ending delimiter is well set to the last word number of the subcorpus in root corpus space
- when creating the chart, or reseting the view, it doesn't extend on x axis to take all the available space (maybe due of wrong T value, need to check this)
- T value is wrong (equals to the size of all token of root corpus from 0 to last subcorpus token)
Validation tests¶
- create a subcorpus of VOEUX containing the year 1973
- create a progression with the query "faire"
- the chart muse take the entire available space on x axis
- T must be equals to 705
- do some zoom and pan commands in the chart
- starting delimiter vertical dotted line should be at 15 617
- ending delimiter vertical dotted line should be at 16 321
- click on "Reset view"
- the chart muse take the entire available space on x axis (as it opened the first time)
Associated revisions
Fixes JFC Progression on sub-corpus, wrong T value (refs #2281)
History
#1 Updated by Sebastien Jacquot almost 5 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0
#2 Updated by Sebastien Jacquot over 4 years ago
- Target version changed from TXM 0.8.0 to TXM 0.8.2
#3 Updated by Sebastien Jacquot over 3 years ago
- Description updated (diff)
#4 Updated by Sebastien Jacquot over 3 years ago
- Description updated (diff)
#5 Updated by Sebastien Jacquot over 3 years ago
- Subject changed from RCP: 0.7.8, Progression on a sub-corpus : x-axis is defined by the corpus instead of sub-corpus to Progression on a sub-corpus, wrong T value using R charts engine (cumulative and density)
- Priority changed from High to Normal
- Target version changed from TXM 0.8.2 to TXM 0.8.0a (split/restructuration)
#6 Updated by Sebastien Jacquot over 3 years ago
- Subject changed from Progression on a sub-corpus, wrong T value using R charts engine (cumulative and density) to RCP: 0.7.8, Progression on a sub-corpus : x-axis is defined by the corpus instead of sub-corpus
- Description updated (diff)
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.1
#7 Updated by Sebastien Jacquot over 3 years ago
- Subject changed from RCP: 0.7.8, Progression on a sub-corpus : x-axis is defined by the corpus instead of sub-corpus to Progression on a sub-corpus : x-axis is defined by the corpus instead of sub-corpus
- Category changed from Commands to Charts
#8 Updated by Sebastien Jacquot over 3 years ago
- % Done changed from 0 to 10
New current state:
- T value has been fixed
- the chart creation and view reset are done by taking in account only the area where there are values/entity so the x starting boundary is not visible by default if there is no value near it. Progression example described in Validation tests section well shows the potential problem. Need to discuss of what we want to propose.
#9 Updated by Sebastien Jacquot over 3 years ago
- Target version changed from TXM 0.8.1 to TXM 0.8.2
#10 Updated by Sebastien Jacquot over 3 years ago
- Target version changed from TXM 0.8.2 to TXM X.X