Exception: Nothing to convert

[udacityyy]

Hello, first of all thank you for this app

I tried using it, I imported my pcd files, annotated them using supervisely, but when I try to download via the app, I got this error message : 000000.pcd is missing photo context, can't generate calibration file, item will be skipped Warn2022.06.16 17:49:36 000001.pcd is missing photo context, can't generate calibration file, item will be skipped Warn2022.06.16 17:49:36 000002.pcd is missing photo context, can't generate calibration file, item will be skipped Warn2022.06.16 17:49:36 000003.pcd is missing photo context, can't generate calibration file, item will be skipped Error2022.06.16 17:49:36 Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/supervisely/app/v1/app_service.py", line 254, in handle_message_sync self.callbacks[command](api=user_public_api, File "/usr/local/lib/python3.8/dist-packages/supervisely/decorators/profile.py", line 11, in wrapper_timer value = func(*args, **kwargs) File "/sessions/416507/repo/src/main.py", line 13, in export_kitti convert_sly_to_kitti3d.convert(g.sly_base_dir, g.kitti_base_dir, []) File "/sessions/416507/repo/src/convert_sly_to_kitti3d.py", line 240, in convert raise Exception("Nothing to convert") Exception: Nothing to convert

Even though I have already imported the pcd files Thank you again

[IzzeddinTeeti]

I had the same issue

[udacityyy]

I still haven't solved it yet

[castaway2000]

this is persistent in version 1.3 as well. see the logs: task_464741.txt task_468645.log.txt

1668296800.127048000.pcd is missing photo context, can't generate calibration file, item will be skipped

it does this for every file resulting in an empty dir and subsequently throws the nothing to convert error.

@mkolomeychenko @TDionis ^^^

[cxnt]

The error occurs because your point clouds don't have photo context, which is necessary to create a calibration file for the KITTI 3D format, all point clouds without photo context will be ignored. We have updated error message to be more clarifying. Please make sure that your point clouds have photo context. It's also has been stated in the readme for this application, that all files without photo context will be ignored.

[castaway2000]

The error occurs because your point clouds don't have photo context, which is necessary to create a calibration file for the KITTI 3D format, all point clouds without photo context will be ignored. We have updated error message to be more clarifying. Please make sure that your point clouds have photo context. It's also has been stated in the readme for this application, that all files without photo context will be ignored.

@cxnt exacerbating the problem, my engineer is having issues with downloading in supervisely format but the data we have been able to get has been converted to kitti successfully without photo context via our own process.

i know now that photo context is required on supervisely, however, the errors and the versions suggest that there is a fix to handle no photo context. this is where the confusion on our end lies. the documentation is not clear. it looks as though it will convert without photo context as of version 1.10

at this point, we cant download any of the data we have in supervisely and it is a huge problem. major major blocker. enough that we are considering finding a different tool to do annotation with going forward as a simple download of a dataset is both not intuitive and overly complex. I simply want to click download and have it downloaded to my laptop with or without converting to another format.

at the very least I would like to intercept it at our own hosted agent as the set needs to download before being reuploaded to the API. (I traversed the code in both export to supervisely format and kitti) but this is not clear where the files are being stored on the agent either. at this point, I'm diverging from the topic at hand but I feel like this should not be as big of an issue as it has been engineered into. If we had simple download access to a non-shared local machine we would be able to be unblocked.

[mkolomeychenko]

@cxnt exacerbating the problem, my engineer is having issues with downloading in supervisely format but the data we have been able to get has been converted to kitti successfully without photo context via our own process.

KITTY 3d format by default requires photo context. So if you don't have it - it is not an official KITTY 3d format. This export app supports only the official format. If you have your custom format modifications, please do it on your side or you can create your own export app and share it with us and the entire CV community. Any contribution is appreciated.

i know now that photo context is required on supervisely, however, the errors and the versions suggest that there is a fix to handle no photo context. this is where the confusion on our end lies. the documentation is not clear. it looks as though it will convert without photo context as of version 1.10

It is not correct. Photo context in Supervisely is optional. It is required in this export app to follow official KITTY format guidelines.

at this point, we cant download any of the data we have in supervisely and it is a huge problem. major major blocker. enough that we are considering finding a different tool to do annotation with going forward as a simple download of a dataset is both not intuitive and overly complex. I simply want to click download and have it downloaded to my laptop with or without converting to another format.

If you find some bugs or issues in Supervisely, it will be greate to report them to us with minimum reproducible example. It will help us to make the platform better, and you also will benefit from it. I dont get your idea about complext download process. You can download the project in a few clicks from the context menu, where is the complexity?

You can just download data in Supervisely JSON format and then convert it to any format you prefer.

enough that we are considering finding a different tool to do annotation with

Our Community Edition is free and almost has no limitations. We are doing our best to provide convenient tools for CV community. In return, we expect contribution and valuable feedback on how to make the tool better. If you don't like what we are doing, you can switch to another product or platform (it is your choice).

at the very least I would like to intercept it at our own hosted agent as the set needs to download before being reuploaded to the API. (I traversed the code in both export to supervisely format and kitti) but this is not clear where the files are being stored on the agent either. at this point, I'm diverging from the topic at hand but I feel like this should not be as big of an issue as it has been engineered into. If we had simple download access to a non-shared local machine we would be able to be unblocked.

We are working on our documentation, but advanced storage options with priority technical support are in our Enterprise Edition. So if you are going to use Supervisely for commercial projects, it is better to switch to Enterprise Edition.

[castaway2000]

@mkolomeychenko thanks for the reply. i have added logs and screenshots and details in slack for you to review... my account is being plagued by a laundry list of issues. we are trying to evaluate for enterprise atm but cant come to a conclusive answer because of these issues I listed in slack.