You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
Before this batch, engineering wrote annotators as plugins in modelgauge or in the core code.
Now they're building them for us to integrate.
Their annotators need to go from modeltune to modelgauge. The approach is to build a package artifact containing the annotator files, and install them in MG via poetry from a private repo on GH.
Potential snag: they have been using modelgauge as a submodule inside modeltune, pinned to an older commit. So the steps are:
bring modelgauge up to date inside modeltune and do basic tests
package up the annotators for poetry to install into modelgauge
test poetry install and then run the modelgauge command that lists annotators (poetry run modelgauge list), and see if they show up
let Barbara know so she can run tests w/ the new annotators.
The text was updated successfully, but these errors were encountered:
The list of Ryan's annotators is in the wg meeting notes:
https://docs.google.com/document/u/2/d/1q1UPz9I_Hzft6-sS24P2TVKq6Ov7ghp-LRyVLS9rfFo/edit
Background:
Before this batch, engineering wrote annotators as plugins in modelgauge or in the core code.
Now they're building them for us to integrate.
Their annotators need to go from modeltune to modelgauge. The approach is to build a package artifact containing the annotator files, and install them in MG via poetry from a private repo on GH.
Potential snag: they have been using modelgauge as a submodule inside modeltune, pinned to an older commit. So the steps are:
poetry run modelgauge list
), and see if they show upThe text was updated successfully, but these errors were encountered: