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
Thought about something like that this week as well, but haven't decided on how to do it.
Initially thought about an extra API call, but it might be in order to include such info in the output as well - you'd want almost everytime anyway.
Some more thoughts, what exactly should e.g. a call to segtok return?
segtok lives inside the llt service and combines the output of the segmenter and the tokenizer, which both could have their own versioning (in fact, they have right now).
The most precise thing to do could be returning versions of all three parties involved.
The easy way out is that the llt gem determines the version number all all possibly dependent parts.
This is really only a problem in the initial phase though, where frequent bugfixes are still coming. Once this reaches some kind of stability this won't be a real issue anymore.
We haven't even reached version 0.1 yet ;)
Must add that the versioning is practically ineffective at the moment, as the deployed war is built directly from the respective master branches to avoid constant version bumping for little fixes, that are still valuable to have rather sooner than later (as in: waiting for a next release)
The radical thing to do would be to point any provenance data to specific git commits. This would certainly be the most precise way to rebuild data, but that might have practical implications.
I'd like to be able to access the version information for the llt services, either via an API call or from the output
See also perseids-project/perseids_docs#25
The text was updated successfully, but these errors were encountered: