[GNC] Fixing bad Bayesian data

David Cousens davidcousens at bigpond.com
Tue Dec 18 18:17:47 EST 2018


Steve

These may help.
https://wiki.gnucash.org/wiki/Bayes
https://lists.gnucash.org/pipermail/gnucash-user/2016-July/066299.html
http://gnucash.1415818.n4.nabble.com/Fixing-confused-bayesian-matching-data-td4685819.html
http://blog.jdlh.com/en/2016/07/29/resetting-gnucashs-import-transaction-matching/

Make a backup of your data file and only work on a copy until you are sure
it is working after changing it if you attempt any of the solutions
mentioned in the above posts.

The importer stores the map data and probabilities during the final step of
the import process. If you let transactions go through to Imbalance then it
obviously gets no data to work with. If you assign all transactions to a
specific transfer account before import and continue to do that, it will
eventually correct itself. There are a few situations in which the bayesian
matcher does not work. I find where there is a transaction unique number
which changes with each periodic transaction the matcher seems to run into
problems. An number identifying the payer/payee and not the transaction
itself is OK. Some of mine have both. 

There will be a feature to be added in GnuCash V4 which allows multiple
selection of transactions and assignment of a single transfer account in the
import matcher which speeds up the transaction matching process
significantly. It can be incorporated in V3.x as a patch if you build
GnuCash from source, but the risk is that future bug fixes in the importer
which change the two affected files could result in a non-working GnuCash.
It incorporated in the master barnch of the GitHub repository and can be
built from that if you are comfortable working with the bleeding edge.

David Cousens




-----
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html


More information about the gnucash-user mailing list