Open fkgruber opened 3 months ago
This fixes the issue reported here: https://github.com/pirl-unc/mhcgnomes/issues/18#issue-1627352688 as well as https://github.com/pirl-unc/mhcgnomes/issues/22#issue-2220926965
I commented the self._transform_cache caching which led to the strange behavior. I'm not sure why but the sort_key function in result_sorting.py changes behavior when the we use it.
the @cache is still active in the parse function.
This fixes the issue reported here: https://github.com/pirl-unc/mhcgnomes/issues/18#issue-1627352688 as well as https://github.com/pirl-unc/mhcgnomes/issues/22#issue-2220926965
I commented the self._transform_cache caching which led to the strange behavior. I'm not sure why but the sort_key function in result_sorting.py changes behavior when the we use it.
the @cache is still active in the parse function.