Closed guillaume-millot closed 6 months ago
@kaaloo thanks for lookup into it! Can you please clarify what you mean by "catching up" with the main
branch? Perhaps give an example?
@kaaloo thanks for lookup into it! Can you please clarify what you mean by "catching up" with the
main
branch? Perhaps give an example?
Yes sure, maybe this isn't the best approach, but I noticed when running poetry install
on both branches that the dependencies in this branch are not up to date. If you look at the git graph you'll see it branches out from main at a commit which took place 4 weeks ago.
So I usually update my main branch, then merge it into my feature branch before asking for review so that we are sure that the code in your PR works with the current set of dependencies. If you try it out, you'll also see the merge conflict with eval/eval_app.py
.
@kaaloo ok thanks I see! Sorry about that, I created a new branch with hopefully all git history: https://github.com/dataforgoodfr/12_taxobservatory/pull/84 Lmk what you think!
Closing in favor of pull request https://github.com/dataforgoodfr/12_taxobservatory/pull/84
This PR contains the following fixes and improvements:
yaml
configuration file with more relevant extraction methodologies to benchmarkEval app improvements: