Bug #2976

Specificty, index column not correctly refreshed after updating the parent lexical table

Added by Matthieu Decorde over 1 year ago. Updated 12 months ago.

Status:New Start date:12/15/2020
Priority:High Due date:
Assignee:- % Done:

0%

Category:Commands Spent time: -
Target version:TXM 0.8.3 Estimated time:20.00 hours

Description

to reproduce:

FR

- je calcule une table lexicale
- je calcule les spécificités sur cette table
- je modifie ma table lexicale en fusionnant des lignes
- je regarde mes spécificités mises à jour : mes indices de spécif sont décalés
- je recalcule les spécificités sur la table lexicale modifiée : les spécifs fraîchement calculées sont bonnes.

Solution

Check the update specificity and specificity editor steps after the Lexical table is updated.

The update process may be different if the LT is manually updated (fusion, delete) ?

Check the frequencies given to the R specificities are the right ones


Related issues

related to Bug #2626: RCP: 0.8.0, subcorpus specificities broken when intermedi... New 09/13/2019

History

#1 Updated by Matthieu Decorde 12 months ago

  • Description updated (diff)
  • Target version changed from TXM 0.8.2 to TXM 0.8.3
  • Estimated time set to 20.00

Also available in: Atom PDF