Closed AlexandreCandidoXavier closed 3 years ago
Hi Alexandre
Seems that I found the "issue",
look at the file init, you will see that the lib is running an simulation!
That's why the import is taking so long kkk
I guess you can just comment this code and it's done.
Cheers
Hi as @Paloschi said, the init.py file runs a simulation as the model is loaded in. This discussion outlines the reasons why: https://github.com/thomasdkelly/aquacrop/discussions/8#discussioncomment-938418
Ultimately i though it would be cleaner to have the jit compilation take place as the module is imported rather than when the user runs their first simulation. This avoids them thinking the simulations themselves are slow or the code is broken.
Thanks Tom
Thank you!
Congratulation for the afford to do the Aquacrop available in Python. I am try to use it and I have two questions:
1) Why it take too long time to import aquacrop:
It is taken ~33 s in my computer. I am using the IDE Pycharm Community, but it is the first time I have this issue.
2) When I run the code:
In the Python console, whatever I do in the prompt line (ex: >>> 1+1) it will return the result and some garbage, as bellow:
Thanks.