Closed Parsa2018 closed 1 year ago
Hello @Parsa2018, this was a bug in napari
that was recently addressed; I'll push a new release of napari-deeplabcut
soon so we fully support 0.4.18. Meanwhile, you could drag and drop the video onto the canvas, as you do with the config, data file or folder of images.
Thank you so much for your kind response, @jeylau. However, I am unable to drag and drop the video onto napari, (neither can I do it with config file or folder of images).
Also, I had one more quick question: When I am labelling on the napari, What is the keyboard command for copying/pasting the previous annotation for the next frame?
Ctrl+C, Ctrl+V. This functionality too will be available in the coming release (today or tomorrow). 😊
@Parsa2018, the new version is online, you can install it with pip install napari-deeplabcut==0.2.0
!
Hi deeplabcut team,
I recently transitioned from the wxpython gui to napari gui with deeplabcut (v. 2.3.5), latest version. Usually, at the stage of
deeplabcut.extract_frames(config_path, mode="manual")
, I do manual frame extraction of the videos. However, after installing the 2.3.5 version of deeplabcut in a new anaconda environment, whenever I want to manually extract frames from my video, on napari, I go to the top corner, in Files, I click on 'open file(s)', and I get an error on the anaconda terminal.Now, do note that opening folders is totally fine. For example, if I automatically extract frames, then I can easily use the napari to label the selected frames.
Another question I have is, in wxpython, I was able to use 'Ctrl+C' to copy my previous annotations to the next frame. Is there such a command for napari as well.
Here's the error: Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\envs\DLC\lib\site-packages\napari_qt\qt_viewer.py", line 735, in _open_filesdialog filenames, = dlg.getOpenFileNames(
AttributeError: PySide6.QtWidgets.QFileDialog.getOpenFileNames(): unsupported keyword 'directory' If you suspect this is an IPython 8.12.2 bug, please report it at: https://github.com/ipython/ipython/issues
or send an email to the mailing list at ipython-dev@python.org You can print a more detailed traceback right now with "%tb", or use "%debug"
to interactively debug it. Extra-detailed tracebacks for bug-reporting purposes can be enabled via:
%config Application.verbose_crash=True
My system versions: Python 3.8.17 Windows 11 DLC 2.3.5 napari 0.4.17 PySide 6.3.1
Thanks so much for all the kind help! Let me know if you need more detailed information regarding the error!