format number properly

This commit is contained in:
Jean-Marie Mineau 2025-06-24 12:19:00 +02:00
parent 1dc9e8227e
commit d730d1f4a7
Signed by: histausse
GPG key ID: B66AEEDA9B645AD2
15 changed files with 67 additions and 29 deletions

View file

@ -1,4 +1,4 @@
#import "@local/template-thesis-matisse:0.0.1": todo, etal, eg
#import "../lib.typ": todo, etal, eg
#import "X_var.typ": *
#import "X_lib.typ": *
@ -85,7 +85,7 @@ We manually searched the tool repository when the website mentioned in the paper
- the source code of the tool;
- the documentation for building and using the tool with a MWE (Minimum Working Example).
In @tab:rasta-tools we rated the quality of these artifacts with "#ok" when available but may have inconsistencies, a "#bad" when too much inconsistencies (inaccurate remarks about the sources, dead links or missing parts) have been found, a "#ko" when no documentation have been found, and a double "#ok#ok" for the documentation when it covers all our expectations (building process, usage, MWE).
In @tab:rasta-tools we rated the quality of these artifacts with "#ok" when available but may have inconsistencies, a "#bad" when too much inconsistencies (inaccurate remarks about the sources, dead links or missing parts) have been found, a "#ko" when no documentation have been found, and a double "#okk" for the documentation when it covers all our expectations (building process, usage, MWE).
Results show that documentation is often missing or very poor (#eg Lotrack), which makes the rebuild process very complex and the first analysis of a MWE.