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
Reported by fleischhauf on 12 May 44022099 07:14 UTC
I am working with HMMs for chord recognition and the limited precision of the save restore utility gave me some headaches.
It would be nice to have an option for saving floating point numbers with higher precision.
This could easily be done with std::setprecision(number) in the save restore utility for the file output stream.
The text was updated successfully, but these errors were encountered:
Commented by rcurtin on 13 Nov 44026748 07:19 UTC
Hello there,
The correct solution to this is to store the transition matrix values and the emission probability values in binary instead of as a string, but for now I've done what you suggested and added a std::setprecision(15) to the relevant calls. I've attached a patch you can apply (or modify if 15 isn't enough). The reason I didn't go through and start storing HMM values in binary format is that the SaveRestoreUtility is going through a bit of overhaul right now, so I don't want to make an svn merging nightmare for the guy working on it. If you're using svn trunk already, I merged these changes in in r16136.
Definitely in the future, though, binary saves is the right way to go. Feel free to reopen the ticket if this doesn't solve the problem.
Reported by fleischhauf on 12 May 44022099 07:14 UTC
I am working with HMMs for chord recognition and the limited precision of the save restore utility gave me some headaches.
It would be nice to have an option for saving floating point numbers with higher precision.
This could easily be done with std::setprecision(number) in the save restore utility for the file output stream.
The text was updated successfully, but these errors were encountered: