eScriptorium issueshttps://gitlab.inria.fr/scripta/escriptorium/-/issues2020-01-14T14:39:41+01:00https://gitlab.inria.fr/scripta/escriptorium/-/issues/137line segmentation difficulties in segmentation and in correction ergonomics2020-01-14T14:39:41+01:00daniel stoeklline segmentation difficulties in segmentation and in correction ergonomicsThis is a typical line segmentation error on a large manuscript with small script despite very high resolution photos (tiling has shown to be a good solution for better line segmentation). Even manual annotation of all marginal regions (...This is a typical line segmentation error on a large manuscript with small script despite very high resolution photos (tiling has shown to be a good solution for better line segmentation). Even manual annotation of all marginal regions (while automatic of the main columns) would be preferable because less time-consuming to correct.
![image](/uploads/fcffaab8c350cc9b62523eea403c527c/image.png)
However, there are also several strange behaviors of the interface. If I select a region (shift mouse move) it only selects some of the lines in the rectangle (the tool I use does not allow taking a snap shot when the dotted line of the rectangle is still shown by escriptorium, but the chosen area pretty much covers the snap)
![image](/uploads/3baba4b065c19c76b58aa0d969f79229/image.png)
After deletion
{{image.png}}https://gitlab.inria.fr/scripta/escriptorium/-/issues/136delete line beginning marker2020-01-14T11:31:30+01:00daniel stoekldelete line beginning markerIf one deletes a line, the vertical marker for the beginning of the line remains undeleted.If one deletes a line, the vertical marker for the beginning of the line remains undeleted.https://gitlab.inria.fr/scripta/escriptorium/-/issues/135strange panel visualization2020-01-14T12:23:50+01:00daniel stoeklstrange panel visualizationI just had this display after switching between some of the 4 panel visualization buttons
{{image.png}}I just had this display after switching between some of the 4 panel visualization buttons
{{image.png}}daniel stoekldaniel stoeklhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/133panel behavior strange2020-01-15T17:38:36+01:00daniel stoeklpanel behavior strangewhen one opens an image to view something, the page-view is always visible, even if it is turned off. When one turns it off the page-view goes, but if one goes back to document-images overview and then again to one of the images, the pag...when one opens an image to view something, the page-view is always visible, even if it is turned off. When one turns it off the page-view goes, but if one goes back to document-images overview and then again to one of the images, the page-view is again visible.https://gitlab.inria.fr/scripta/escriptorium/-/issues/132change arrow symbols2020-01-15T16:09:20+01:00daniel stoeklchange arrow symbolsin the small transcription window, for RTL texts it should be the left arrow which goes to the next line and the right which goes to previous line. This was like this previously but is no more. I think it is much preferable to switch to ...in the small transcription window, for RTL texts it should be the left arrow which goes to the next line and the right which goes to previous line. This was like this previously but is no more. I think it is much preferable to switch to arrow up and arrow down symbols which can be the same for both RTL and LTR. Also, it should be combined with the keyboard strokes arrow-up and arrow-down as shortcuts, please.https://gitlab.inria.fr/scripta/escriptorium/-/issues/131reading order confused2020-01-21T08:35:40+01:00daniel stoeklreading order confusedThe current reading order algorithm has for some reason unknown to me ceased to function. Lines are ordered in an arbitrary way.The current reading order algorithm has for some reason unknown to me ceased to function. Lines are ordered in an arbitrary way.https://gitlab.inria.fr/scripta/escriptorium/-/issues/130Cutting two lines bug2020-01-28T16:58:37+01:00daniel stoeklCutting two lines bugIf one cuts two lines, one of the lines gets multiplied into 4 or 5 different instances of the same line one above the other (visible by another type of blue).If one cuts two lines, one of the lines gets multiplied into 4 or 5 different instances of the same line one above the other (visible by another type of blue).https://gitlab.inria.fr/scripta/escriptorium/-/issues/129Segmentation annotation bug2020-01-14T14:43:54+01:00daniel stoeklSegmentation annotation bugSometimes (sorry to be imprecise but I did not understand the WHEN), one cannot draw more lines or drag more points.
E.g. after merging two lines. Then clicking on another two lines (3 and 4). Without unselecting the previous ones by err...Sometimes (sorry to be imprecise but I did not understand the WHEN), one cannot draw more lines or drag more points.
E.g. after merging two lines. Then clicking on another two lines (3 and 4). Without unselecting the previous ones by error... Merging them. clicking ctrl z - no more drawing possible. Ctrl z deleted also lines 3 and 4.https://gitlab.inria.fr/scripta/escriptorium/-/issues/128Navigation bug2020-01-17T10:31:52+01:00daniel stoeklNavigation bugSince yesterday there is a bug when pressing the error 'next page' after some interaction with the segmentation annotation. It goes to the next page but it does not change the url. After you go to the next page no further 'go to next' is...Since yesterday there is a bug when pressing the error 'next page' after some interaction with the segmentation annotation. It goes to the next page but it does not change the url. After you go to the next page no further 'go to next' is possible. Inspect element shows that there is a zero value somewhere.EL HASSANE GARGEMEL HASSANE GARGEMhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/123segmentation annotation bugs2020-01-14T14:43:22+01:00daniel stoeklsegmentation annotation bugsSince today switching to the develop branch, I had more bugs when interacting with the segmentation annotation/correction. Frequently I could not add new lines anymore or delete anymore. F5 reload would help, but that is not a good worka...Since today switching to the develop branch, I had more bugs when interacting with the segmentation annotation/correction. Frequently I could not add new lines anymore or delete anymore. F5 reload would help, but that is not a good workaround.
It has become considerably more difficult to grab the points of a line for some reason. Perhaps this depends on the width of the line??? Sometimes the cursor would not correspond to the actual coordinates of the cursor. This was visible when trying to draw the second point of a line. Especially trying to draw new lines or move points at the edges of images was difficult.https://gitlab.inria.fr/scripta/escriptorium/-/issues/119Segmentation bugs2020-01-21T08:35:19+01:00Robin TissotSegmentation bugsCreate separate issues as needed:
* ~~ctrl + move doesn't follow the mouse, when moving more than one point they get clamped up.~~
* merging lines more than once create new lines.
* ~~the sign direction should be more visible especially ...Create separate issues as needed:
* ~~ctrl + move doesn't follow the mouse, when moving more than one point they get clamped up.~~
* merging lines more than once create new lines.
* ~~the sign direction should be more visible especially on high resolution images.~~
* Sometimes when joining lines, one line seems to become shorter (result of two differing line directions???). You seem to be aware of the problem. In fact, the lines are joined and one of the lines is UNDER the other, seemingly going back. This is hard to spot because dots are on the same coordinates. One needs to move one of the points to see that there is actually sthg below.
* ~~use text direction instead of line direction (need to detect it)~~
* ~~Sometimes baselines are indicated twice, thrice or more for the same line for lines that were corrected. This is only shown when leaving the page and going back~~
* Lines are getting duplicated (when cutting/merging?)https://gitlab.inria.fr/scripta/escriptorium/-/issues/118export filename bug if contains '.'2020-01-15T15:16:46+01:00Robin Tissotexport filename bug if contains '.'> In alto, if the image filename contains ‘.‘ the xml filenames are cut too early because everything afterwards seems to be regarded as fileextension.
(probably in PageXML too)> In alto, if the image filename contains ‘.‘ the xml filenames are cut too early because everything afterwards seems to be regarded as fileextension.
(probably in PageXML too)https://gitlab.inria.fr/scripta/escriptorium/-/issues/117Make exports asynchronous2020-02-17T22:57:03+01:00Robin TissotMake exports asynchronousAnd send an email when it's done or something - and maybe add a generic end task email.And send an email when it's done or something - and maybe add a generic end task email.https://gitlab.inria.fr/scripta/escriptorium/-/issues/112Fake base direction2019-11-22T10:41:35+01:00Robin TissotFake base directionThe fake baseline created by the transcription panel in the feature/polygons branch doesn't take the writing direction into account so in r2l the text is 180° rotated.The fake baseline created by the transcription panel in the feature/polygons branch doesn't take the writing direction into account so in r2l the text is 180° rotated.https://gitlab.inria.fr/scripta/escriptorium/-/issues/107Dublin core keys are not loaded anymore2020-01-28T16:59:10+01:00Robin TissotDublin core keys are not loaded anymoreIn the metadata key list (in the document form).In the metadata key list (in the document form).https://gitlab.inria.fr/scripta/escriptorium/-/issues/105confusion between HPOs and VPOs in alto export2019-12-03T12:17:34+01:00STOKL BEN EZRA Danielconfusion between HPOs and VPOs in alto exportI tried to create image training GT from an alto export and I see that the values for vpos and hpos variables are confused. If this is only in the alto export its just a minor bug but if this is also in the main sql tables it would actua...I tried to create image training GT from an alto export and I see that the values for vpos and hpos variables are confused. If this is only in the alto export its just a minor bug but if this is also in the main sql tables it would actually be nice because maybe it could explain the bad training results...
or maybe I am doing sthg wrong?Robin TissotRobin Tissothttps://gitlab.inria.fr/scripta/escriptorium/-/issues/104Updating a model's codec2019-10-08T15:45:19+02:00Robin TissotUpdating a model's codecKraken expects ['accuracy'] to be present in the metadata everytime:
Training from a model (not created by Kraken?):
```
[2019-08-12 07:08:48,111: INFO/MainProcess] Received task: core.tasks.train[3b4b9671-d655-406a-b8f5-3f5b541ee8ed] ...Kraken expects ['accuracy'] to be present in the metadata everytime:
Training from a model (not created by Kraken?):
```
[2019-08-12 07:08:48,111: INFO/MainProcess] Received task: core.tasks.train[3b4b9671-d655-406a-b8f5-3f5b541ee8ed]
[2019-08-12 07:09:30,199: INFO/ForkPoolWorker-3] Accuracy report (0) 0.0650 569 532
'accuracy'
Traceback (most recent call last):
File "/home/robin/Projects/escriptorium/app/apps/core/tasks.py", line 328, in train
train_(qs, document, transcription, model=model, user=user)
File "/home/robin/Projects/escriptorium/app/apps/core/tasks.py", line 291, in train_
trainer.run(_print_eval, _progress)
File "/home/robin/Projects/escriptorium/app/env/lib/python3.6/site-packages/kraken/lib/train.py", line 292, in run
self.model.user_metadata['accuracy'].append((self.iterations, accuracy))
KeyError: 'accuracy'
[2019-08-12 07:09:30,207: ERROR/ForkPoolWorker-3] 'accuracy'
Traceback (most recent call last):
File "/home/robin/Projects/escriptorium/app/apps/core/tasks.py", line 328, in train
train_(qs, document, transcription, model=model, user=user)
File "/home/robin/Projects/escriptorium/app/apps/core/tasks.py", line 291, in train_
trainer.run(_print_eval, _progress)
File "/home/robin/Projects/escriptorium/app/env/lib/python3.6/site-packages/kraken/lib/train.py", line 292, in run
self.model.user_metadata['accuracy'].append((self.iterations, accuracy))
KeyError: 'accuracy'
```https://gitlab.inria.fr/scripta/escriptorium/-/issues/102Browser zoom (ctrl+-) changes the lines coordinates and mess the zoom2019-12-03T12:17:48+01:00Robin TissotBrowser zoom (ctrl+-) changes the lines coordinates and mess the zoomhttps://gitlab.inria.fr/scripta/escriptorium/-/issues/98Import failed2019-12-03T11:09:06+01:00Robin TissotImport failedThe content seems empty of canvases, cf:
http://ns342141.ip-5-196-76.eu:5555/task/ea67120d-1aa2-4820-8688-f3cc5c9ce421
http://ns342141.ip-5-196-76.eu:5555/task/7495a49c-e83f-4d5f-961f-01e16409157a
```
Traceback (most recent call l...The content seems empty of canvases, cf:
http://ns342141.ip-5-196-76.eu:5555/task/ea67120d-1aa2-4820-8688-f3cc5c9ce421
http://ns342141.ip-5-196-76.eu:5555/task/7495a49c-e83f-4d5f-961f-01e16409157a
```
Traceback (most recent call last):
File "/usr/src/app/apps/imports/parsers.py", line 217, in __init__
self.canvases = self.manifest['sequences'][0]['canvases']
IndexError: list index out of range
```https://gitlab.inria.fr/scripta/escriptorium/-/issues/94Importing from one instance of escriptorium to another fails2021-01-04T10:51:49+01:00Robin TissotImporting from one instance of escriptorium to another failsBecause the system tries to match the IDs, need to try/except that somehow?Because the system tries to match the IDs, need to try/except that somehow?