Cache is not invalidated on changes in tunables

Reported by @ chrisp87

If a user changes tunables without either deactivating caching or deleting the cache files inbetween runs, they might be puzzled by the lack of changes in results.

Possible fix: Store a hash of tunables alongside the caches, automatically invalidate them if tunables are changed.