[FIX] Reuse weights calculation instead of raising error on hash mismatch #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Improved weights caching behavior by recalculating weights when hash mismatch occurs instead of raising an error, and added automatic cache directory initialization.
What changed?
interpolate_scalar_fieldto recalculate weights when a hash mismatch is detected instead of raising a "Cache is corrupted" errorcompute_modelfunction by callingWeightCache.initialize_cache_dir()WeightCachein the model_api.py fileHow to test?
Why make this change?
This change improves the user experience by making the caching system more robust. Instead of failing with an error when cached weights don't match the current model configuration, the system now gracefully recalculates the weights. Additionally, automatic cache directory initialization prevents errors that could occur if the directory doesn't exist.