You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we found a small bug. When you use the -thresh 0.15 parameter for example during the "detector test" call.
The 0.15 gets added into input_fn in run_detector. This is due the Darknet::CfgAndState::process_arguments does not handle params and puts them into additional_arguments. I think the easiest fixt might to skip the next index if the current obj expect a parameter. But since im not quite sure i rather let you decide about the fix
sample command
.\darknet.exe detector test .\xy.data .\xy.cfg .\backup\xy_best.weights -thresh 0.1
The text was updated successfully, but these errors were encountered:
Hi,
we found a small bug. When you use the -thresh 0.15 parameter for example during the "detector test" call.
The 0.15 gets added into input_fn in run_detector. This is due the Darknet::CfgAndState::process_arguments does not handle params and puts them into additional_arguments. I think the easiest fixt might to skip the next index if the current obj expect a parameter. But since im not quite sure i rather let you decide about the fix
sample command
.\darknet.exe detector test .\xy.data .\xy.cfg .\backup\xy_best.weights -thresh 0.1
The text was updated successfully, but these errors were encountered: