Comments (10)
As far as I remember, the codebase is heavily sensitive to CUDA/CUDnn versions. Perhaps Colab has updated their versions and our code does not run anymore on it :(
from palmira.
Can you please help us by suggesting how we should run the same on colab? or providing us with the correct versions of CUDA/CUDnn versions so maybe I can try running it locally.
from palmira.
- The model code might need some updating to make it work with colab so that it supports newer CUDA versions. This might need some digging into each of these functions which say they do not exist anymore and find their new equivalent APIs.
- You can find the versions with which we ran our experiments here. You can try setting this up locally and you should have it up and running!
from palmira.
Hi, there is an inherent mismatch between the torch and torch vision modules you gave. I could run the script using Pytorch 1.8.0 with torch vision 0.9.0 and Cuda toolkit 11.1 and download the detectron2 version corresponding to the same while utilising the requirements.txt file for other packages. The image is segmented for now.
However, on running the following command
input = cv2.imread("./images/test.jpg") # recieving the input image
input = input[:,:,::-1]
showoutput(input)
I get the error: No such file or directory: './outputs/data.json
please help me with this
from palmira.
No such file is generated. Is there any fix?? I need the json files so that I can have the coordinates of bounding box which I can later use for cropping.
from palmira.
Where is this showoutput(input)
?
from palmira.
It is part of your colab notebook. In your notebook itself the same error is showing as uploaded by you.
from palmira.
Is there any way that I can access the json file containing the co-ordinates for each line because I wanted use that information for further processing.
from palmira.
I see, thanks for bring this to my attention. I just realized that I am infact not the author of that colab notebook. From the
revision history, it is from my co-authors and other collaborators at the lab.
But from looking at code from colab notebook, the JSON seems to be from performing manual annotations using an annotation tool. I am not totally sure. I suppose you can find GT annotations from the dataset.
There is also an older version of the colab notebook in its revision history which I located and does not have this error: Link.
I shall get back to you on this soon!
from palmira.
I would recommend you to use Seamformer instead which is a follow-up work from our lab.
from palmira.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from palmira.