-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new option under actions tab #4933
Comments
Hey! You can look on actions-menu component and actions-menu container |
Hey thanks for that @klakhov , could you please tell me the next action to this. After making the changes do I need to do npm version patch or npm start from the cvat-ui address ?? |
@himanshudw That depends on how you are using CVAT. If you are using docker, you need to build images locally with
If you are using development environment, refer to dev docs, all changes in cvat-ui will be automatically detected and applied. |
Thanks a lot for those, it worked this way. |
I have been able to add a button to navigate from the CVAT UI. Just would like to understand how can we access the dataset from the UI point of view, yeah I understand http://localhost:8080/api/swagger/#/tasks/tasks_retrieve_dataset can manually download the dataset but how can we access it from the UI directly and upload on cloud. |
Few questions here
EDIT1 docker run -it --entrypoint python3 -v ~/Documents/data/:${HOME}/manifest/:rw cvat/server /Documents/data- is where CVAT store data. that would be home/Django/data inside container but where can I get it in VM. Is there a demo around this and specifically speaking about each of these locations in some detail I am running CVAT on Virtual machine and want to mount azure container as cloud storage |
@Marishka17 could you please help with answering these questions? |
@himanshudw, Hi
In the current implementation, it's impossible to attach cloud storage without a manifest file (but it's in our future plans). As a workaround, you can put the empty file to your bucket and specify it when attaching storage to CVAT.
The manifest file is used for another functionality. If you want to use data on your bucket, you can attach this bucket to CVAT. In this case, you should prepare a manifest file that will specify bucket content. If you have several datasets on your bucket and want to create annotation tasks with these data you can prepare one manifest or several for each dataset.
Source storage specifies the location from which annotations and backups will be uploaded to CVAT. |
Hi @Marishka17 Thank you so much for that clarification. I have been able to add the cloud storage with a blank manifest file but then it is giving error as per the below image The main intent for me is to upload the annotation for the task in TFrecord 1.0 format to the azure container so as per the demo in on of the above comment I could see it happening. Now as you rightly mentioned that the dataset on the azure cloud could be used to create a task and for that we need the manifest file so while creating a task I request you to kindly clarify the paths for manifest file else a way out for me to upload the annotations directly to the cloud storage using the UI. I tried to create the manifest file using the documentation using Alternative way to use with cvat/server but then the paths mentioned are not very clear and my understanding are in the above comments, kindly clarify on those too please. Thanks in advance |
@himanshudw , please discuss questions in any of our public channels: https://github.com/opencv/cvat#contact-us. I will close the issue. |
My actions before raising this issue
Intend to add train button on the UI of CVAT under the Actions tab
Expected Behaviour
The click on the train button should take the dataset along with the annotation to a new page.
Current Behaviour
Unable to locate the procedure to make these changes
Context
Trying to add a train button under the dropdown in the actions tab
In the earlier version it is reflected as below but not sure about the changes need to be done in this new version
Your Environment
docker version
:20.10.17The text was updated successfully, but these errors were encountered: