Aborting and saving the final best model. Encountered exception:
PermissionError(13, 'Access is denied')
Full read out below with error at bottom:
Using CPU
========================= Generating Prodigy config ========================= Auto-generating config with spaCy Generated training config
=========================== Initializing pipeline ===========================
[2024-02-15 23:40:11,882] [INFO] Set up nlp object from config
Components: ner
Merging training and evaluation data for 1 components
This seems to suggest you may not have permission to write to the output folder you've specified ./tmp_model1. Can you confirm you writeable permission to this folder? If not, can you retry but pointing to a folder where you do have writeable permission?
I am using Jupyterlab/Anaconda on Windows, the folder I am saving to I can make and save files into no problem (i can make directories in it in with python on jupyterlab and write files). Just checked and I have full access on windows. Does Jupyterlab superimpose some new permissions while in an environment?
Unfortunately, I don't know. I'm not an expert on JupyterLab, especially not in Windows. Just curious are you running on a company's network? There could be a lot of background things like a virus protector that's blocking. You may want to talk to an IT admin if they know of anything blocking.
Can you run your Prodigy command in terminal? While we offer the Jupyter extension, Prodigy was really designed to be run in the command line. I've noticed in the past some users get confused thinking they must just the Jupyter notebook when in fact it may add a lot of hidden problems like this.
Ok will give that a try. I was using anaconda for the environment management. This is the second problem I have had with Jupyterlab/plugin. Back to basics it is.
Thanks Ryan. I have no idea what is going with JupyterLab as the folder I am using I have the required permissions. I can write files, delete files etc etc within JupyterLab within it but it wont play ball with prodigy doing stuff within within a JupyterLab terminal or even a completely separate windows terminal operating on that JupyterLab folder.
Anyway I copied the data into a completely different folder on a completely different drive and it worked on a windows terminal. This must be some weird permissions thing but everything looks fine when I look at the usage rights. Will battle with this when I get bored.
This looks solved from my perspective. Close this from my end. Thanks for your help Ryan.