Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Improve featureVector.py documentation #32

Open
sechkova opened this issue Feb 2, 2022 · 0 comments
Open

Improve featureVector.py documentation #32

sechkova opened this issue Feb 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@sechkova
Copy link
Contributor

sechkova commented Feb 2, 2022

Is your feature request related to a problem? Please describe.

It is not clear from the readme how the output of featureVector.py can be used to train a model in run.py since the first is missing the annotations required by the second.

Describe the solution you'd like

Have a clear description of the output format of featureVector.py, the expected input format of run.py and any potential intermediate transformations needed.

Describe alternatives you've considered

No response

Additional context

No response

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant