Closed aloizel closed 3 years ago
Hey @aloizel what are you using FARM for inside databricks (notebook)? Sound amazing.
We have recently tested torch 1.8.1 in https://github.com/deepset-ai/FARM/pull/767 and also very recently released a new FARM version https://github.com/deepset-ai/FARM/releases/tag/v0.8.0
At a first glance it looks more like a torch issue, but lets figure this out together. Could you try updating and report back?
Hi ! Thanks for the answer
I found the problem it wasn't due to farm it's ok I close the issue
And yes we are using databricks but we use a library to launch our code as a job not as a notebook, it allows us to scheduled our train and follow our data life cycle
Hi guys, I'm using farm 0.7.1 on a databricks cluster, on a cpu instance (I know that gpu will be better for this but we don't have one at the moment) and I'm having trouble but I don't know if the problem is from farm or torch
My problem looks like this issue from torch : https://github.com/pytorch/pytorch/issues/15508 but it should be corrected
I'm on torch 1.7.1 because farm doesn't allow me to use a more recent version
When I launch a training I got this error message :
The Target is not always 170 it depends of the run and the model I chose to train
Have you already had this problem ?
If you need anything more to answer my question just ask
Databricks runtime version : 8.2 (includes Apache Spark 3.1.1, Scala 2.12) Worker Type Standard_DS3_v2
Thanks