Difference between revisions of "Pairviewer"

From Apertium
Jump to navigation Jump to search
(move content from Pair viewer (with space))
Line 29: Line 29:


== Using Pairviewer ==
== Using Pairviewer ==
=== Updating language data by scraping ===
Apertium language data are being continuously developed, so it is highly possible that the language data that your Pairviewer were shipped with isn't up to date.

To scrap new language data (from [https://github.com/apertium Apertium's GitHub]), run:
<pre>python3 scrape_repo_information.py</pre>

=== Navigating the user interface ===
[[File:pairviewer-pair-info.png|right|thumb|Hovering over the language pair line between tha and lao.]]
Hovering over a graph edge (language pair line) displays its language pair name, repository name, creation date, date of last update, and stem amount.

The nodes (circles representing the languages) can be dragged around to rotate the entire graph.

Stats for the number of languages and language pairs represented in the graph can be found in the bottom-left corner.

The collapsible menu on the top left lets you filter languages according to its:
* progress branch ([[Trunk|trunk]], [[Staging|staging]], [[Nursery|nursery]], or [[Incubator|incubator]])
* directionality (unidirectional, bidirectional, and direction missing)
* amount of stem count (correlated with dictionary size)
* last update
* creation date


== How Pairviewer works ==
== How Pairviewer works ==

Revision as of 15:45, 8 December 2018

The Pairviewer in action.

The Apertium Pairviewer is a HTML5/D3.js tool that depicts all Apertium language pairs in an interactive graph initially developed sometime before the Google Code-In 2013. Its source code can be found on GitHub and an online demonstration is available here.

Setting up Pairviewer locally

Clone the git repository

Enter into the folder you want it to be in and download the whole program by running

git clone https://github.com/apertium/pairviewer.git

Set up a localhost with Python

You need to set up a localhost server before you can locally run Pairviewer.

First, check whether you have Python installed on your system and if so, what version(s) it is. Install preferably the latest one (Python 3) if it had not been done already.

python -v

Then make sure to enter the folder of the git repository you have cloned.

If you have is Python 3, run:

python3 -m http.server

Otherwise, if you do have Python 2, run:

python -m SimpleHTTPServer

You should see something like this on your terminal window.

Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) <---- copy-paste this URL!

Open on browser

Paste in your localhost address (e.g. http://0.0.0.0:80000/) into a browser and run. You should see a directory listing. Click the link with the label apertium.html.

This should successfully launch the Pairviewer. This step requires downloading some D3.js resources, so if your internet connection is slow, this might take a while.

Using Pairviewer

Updating language data by scraping

Apertium language data are being continuously developed, so it is highly possible that the language data that your Pairviewer were shipped with isn't up to date.

To scrap new language data (from Apertium's GitHub), run:

python3 scrape_repo_information.py

Navigating the user interface

Hovering over the language pair line between tha and lao.

Hovering over a graph edge (language pair line) displays its language pair name, repository name, creation date, date of last update, and stem amount.

The nodes (circles representing the languages) can be dragged around to rotate the entire graph.

Stats for the number of languages and language pairs represented in the graph can be found in the bottom-left corner.

The collapsible menu on the top left lets you filter languages according to its:

  • progress branch (trunk, staging, nursery, or incubator)
  • directionality (unidirectional, bidirectional, and direction missing)
  • amount of stem count (correlated with dictionary size)
  • last update
  • creation date

How Pairviewer works

Known bugs

There are a few apparent bugs that should be fixed before the pair viewer goes public.

  • in initial view (sometimes?), quz has no line connecting it to spa
  • sometimes two- and three-letter codes don't seem to merge
    • when just trunk and staging are selected, tur/tr and nob/nb are each separate from one another
    • when trunk, staging, and nursery are selected, nob/nb are merged, but tur/tr are separate
  • when all possible pairs are viewed (including ones with missing stems, etc.), pa doesn't have a line connecting it to ur