RodTracker¶
v0.6.0¶
Added¶
old rod positions are displayed during editing as a visual cue
mode for automatic selection of the rod closest to the cursor
documentation with Sphinx
integration of
ParticleDetectionfunctionalitydetection of rods from images
recalculation of 3D rod positions from position updates in 2D
tracking of rods and following recalculation of 3D positions
evaluation plots for 3D position reconstruction
shortcut to fit the displayed image to its available space
added a ‘busy’ indicator for tabs running long background tasks
shortcut to delete a rod when having it selected
display of the documentation from the Help dropdown menu
loaded/changed position data is automatically saved every 60 seconds
Changed¶
rods are now displayed partially transparent while being selected
display of a folder selection dialog, if no folder is selected during saving
settings-/data-directory is now determined with
platformdirs
Fixed¶
test suite problems have been fixed
initial display of rods on Windows
rods not being completely deletable (#69)
Removed¶
function to display the README in the application
True number of rodssetting is no longer available
v0.5.8¶
Changed¶
migration from
setuptoolstopoetryas the build system
Fixed¶
bundling of the
RodTrackerto a standalone program
v0.5.7¶
Added¶
splash screen during the startup of the
RodTracker
Changed¶
each module can now access its own logger, leading to more informative log messages
Fixed¶
cropping of displayed rod numbers for font sizes >11
Removed¶
splash screen during unpacking stage of standalone programs bundled as one file
v0.5.6¶
skipped
v0.5.5¶
skipped
v0.5.4¶
Changed¶
3D rod elements are now reused instead of regenerated leading to better performance
Fixed¶
visual indicators of the experiment box are no longer extending further than the experiment’s dimensions
v0.5.3¶
Changed¶
The rod data displayed as a tree is now updated in place instead of being regenerated. This especially improves performance and responsiveness of the
RodTrackerwhen working with large datasets.
v0.5.2¶
Changed¶
rod position data is handled by a dedicated object
images datasets are handled by one dedicated object per camera view
rod data display as a tree is done by a custom
QTreeWidgetzooming and panning in the 3D environment has improved speeds for the interaction
v0.5.1¶
Added¶
Three different display modes for rods in 3D
Fixed¶
redundant settings updates are removed
v0.5.0¶
Added¶
3D view of the rod data in relation to the experimental container
warnings of the Qt framework are now also logged to the
RodTracker’s log file.
Changed¶
The right portion of the data display is now designed as tabs
Setting are now accessible in a tab on the right of the main area of the
RodTracker, instead of a dialog from a dropdown menu. The changed settings are now applied immediately.Mechanism for internal notification of successful saving
internal processes of data selection and loading are now seperated
Fixed¶
automatic rod activation during a camera change to where no rods are available
The unsaved changes indicator is now removed from all appropriate tabs, not only from the currently active one.
aborting of image selection
application crashes due to mishandled threads
cross platform path incompatibilities
v0.4¶
skipped
v0.3¶
skipped
v0.2¶
skipped
ParticleDetection¶
v0.4.0¶
Added¶
documentation with Sphinx
improved API documentation
include examples
more basic functions are available instead of just their runner functions, e.g.
project_points(...)support for python 3.8 added
possibility to define an expected number of particles when extracting rod endpoints
added automated tests
exporting detected objects to JSON format for training
support for all annotation types provided by the VGG Image Annotator in training metadata
endpoint reordering for smoother post-processing
Changed¶
now uses the headless version of OpenCV
simplified the default format for transformations from camera to world coordinate system
object detection function now accepts arbitrary saving functions instead of having one fixed saving method built into it
Fixed¶
tracking of rods over multiple frames (see here)
incomplete/incorrect setup of logging for the library
Removed¶
run_detection(...)no longer returns the raw detection results