m09

with a few env variables set, yes

To document, last version ran for 0.1.1 report before I got my access to science-3 nuked was: Outer script ```shell docker network create --driver bridge report_0.1.1 docker run --network report_0.1.1...

This is mostly what we currently have. Some problems include: - the number and location of attributes is not always the same (basic formatting classes are more numerous than merged...

Sadly this does not solve the biggest problem (potentially different number/location of annotations for each type). More generally, I don't think there is a shortcut that can reap the benefits...

By type I just mean a different annotation (so for example y and predicted would be different annotations). By different numbers and locations I mean what I already mentioned: atomic...

Don't worry, I don't get it wrong :relaxed: It's just that we should probably close this issue and open a new one with different refactoring ideas since those won't be...

It's not perfectly consistent since it doesn't implement the pattern that we wanted to implement. TBH I'm not even sure it helps compared to current codebase. The point of having...

They seem also present in 0.1.0 (even 94 instead of 59) so maybe we did not kill them after all. $ xzgrep -c imaginary 0.1.0/quality/logs.txt.xz 94 $ grep -c imaginary...

> The majority of the third-party dependencies do not specify encoding for open. `bblfsh`, the main dependency we use to parse the files, enforces utf-8 for its input. > It...

Thanks for the precisions :) To quote the comment I made on slack: > We should document that we don't use the to column (and probably remove it from csv...