Troubleshooting

Tips, tricks, and lessons learned

Videos have been uploaded to the storage bucket, but VIAME cannot play them.

These video files need to be processed by VIAME. This will be done by the worker VM, so it needs to be running. If it is not, boot it. The jobs should then start automatically. Their status can be viewed on the “JOBS” page of DIVE.

Videos frame rate cannot be specified during upload.

Per Kitware, a short-term fix would be to create a Python script that takes in a girderId for a folder and then sets all of the DIVE datasets inside the folder or other folders below it to a specified annotation frame rate.

The long-term fix would be to update the CSV import script to read in the metadata field that specifies the annotation FPS. This should be the second line in your CSV if it is created using DIVE already. So that way when you import annotations it will adjust the frame rate automatically if it detects that FPS information in the CSV. We can also add some way to modify the annotation FPS directly in the DIVE interface instead of requiring it to be edited in girder directly.

In the meantime, the workaround is to change the frame rate in the Girder folder metadata, as described in the FAQs.