Closed Muedi closed 10 months ago
@Muedi If I had to bet, it would be because you named it esm
. Try any other name, like fair_esm
or something. This is because the Facebook ESM pip package is also called esm
Also, I now see that we are adding all the files from the esm package into this repo. Is there a reason for that? Can't we just have esm as a dependency?
The plan was to axe down on it when it runs to make a minimal version.
However, I also asked myself if we could just use the pip package.
The issue was indeed the name! Which is weird because I do not have installed the esm package as far as I know (at least niot in the conda I use).
I missed a few args, so I need to change these. I am leaving this open for the discussion about esm pip vs minimal version in folder structure.
IMO, I think we should start off with a pip version and if we have additional requirements, we can think about a minimal version that @Muedi is referring to.
it works with the puip packge no prob. I'll try to find a fix for the multi mutant problem and make another pull rquest :)
Hi,
as discussed with @pascalnotin, I added esm to the modeling/models folder. I then added the prediction scriupt of the esm github repo to my eval script and changed the argparse stuff etc.
However, I was not able to test this and I am stuck a bit, therefore I wanted to get some input here:
When I tried to run the script, at first the imports themselves would already throw an error, warning me opf possible circular imports:
However the commit ce4702b46769b458bb309c1feaaa8ce1b90449ad contains next to my changes to the eval script itself, mutliple changes to esms codebase, trying to mitigate the problem with the circular imports and adding imports that correspond to the folder structure.
All imports eem to work well now, but I still get an import Error when I am trying to call a function from pretrained.py:
Did you run into similar Problems @pascalnotin?
I'd also like to hear @jamaliki 's input and of everyone else reading this of course :)