Loss of precision of parameters in a model file
See original GitHub issueDouble precision floating-point number parameters in svm-train, such as gamma, are written to a model file in a format of %g
by svm_save_model
in svm.cpp. This causes loss of precision of parameters, hence a slight difference between the kernel function in svm-train and that of svm-predict. The effect on precision of prediction may be small, especially when Qfloat
is defined as float
, but I think the parameters should be written in a format like %.16g
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Detect precision loss - MATLAB & Simulink - MathWorks
Precision loss occurs when Simulink software encounters a parameter whose data type does not have enough precision to represent the parameter's value ...
Read more >Error generating the code: variable too large
Hi, I am generating 3 phase PWM to control an induction motor. I have generated one sine duty cycle and then I delay...
Read more >Why am I losing precision with large whole numbers (such as ...
The problem is that a float can only store an integer value with up to 7 digits of accuracy (but our id values...
Read more >How to Calculate Precision, Recall, F1, and More for Deep ...
A figure is created showing two line plots: one for the learning curves of the loss on the train and test sets and...
Read more >How can I use double as a function parameters without losing ...
Well, if double loses precision then you cannot do much about that besides changing the type of the parameters. · That's when the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, in the libsvm 3.23 released 2 days ago this has been corrected.
Tavian Barnes writes:
I think you are right… We will change the code later Tavian Barnes writes: