Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 175
    • Issues 175
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Issues
  • #115

Closed
Open
Opened Mar 18, 2022 by Quentin Lobbé@qlobbe
  • Report abuse
  • New issue
Report abuse New issue

wrong inherited status (map/candidate/stop) when grouping ngrams in the map list

This issue occurs with json map list (V4 format).

When I group two ngrams such as : [ngram 1 contains ngram 2] with ngram 1 root of ngram 2 If ngram 2 is tagged as map and ngram 1 is tagged as stop (which appends frequently), after grouping them ngram 2 will not inherits from the stop status of ngram 1.

It doesn't seem to be a problem for graph visualization, but for phylomemy visualization it breaks the text flow as ngram 1 will be (I don't know why) strangely tagged as map and not as stop. So the resulting phylomemy is wrong.

The function used for decoding ngrams tables in phylomemy visualization is import Gargantext.API.Ngrams.Prelude (toTermList) something might be wrong with this function.

Thx !

Edited Mar 18, 2022 by Quentin Lobbé
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
Critical
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#115