It seems like the exception used to be thrown in StarAMR 0.8.0 but (probably) not in 0.9.0. I wrote a test to ensure this specific case is being handled as expected, and it appears we are already merging duplicate entries as expected on the development branch.
This issue might already be resolved in 0.9.0 (unconfirmed), but development looks to have it resolved already. I also removed an import of the previous exception, as it is no longer thrown by PointfinderDatabaseInfo.
Addressing #174
It seems like the exception used to be thrown in StarAMR 0.8.0 but (probably) not in 0.9.0. I wrote a test to ensure this specific case is being handled as expected, and it appears we are already merging duplicate entries as expected on the development branch.
This issue might already be resolved in 0.9.0 (unconfirmed), but development looks to have it resolved already. I also removed an import of the previous exception, as it is no longer thrown by
PointfinderDatabaseInfo.