This is in response to a user request on slack. This minor change will allow non-Enzo simulations to use the yt fields feature of Pygrackle. Currently, we only have a map between simulation parameter names and grackle parameter names for Enzo, but users can still provide them by hand, or at least they could if we didn't raise an exception if a parameter map is not found. This removes the exception and simply prints a warning, allowing the user to proceed.
All of this is fairly undocumented outside of the example Python scripts provided, but I intend to improve that moving forward, but ideally not a part of this pull request.
This is in response to a user request on slack. This minor change will allow non-Enzo simulations to use the yt fields feature of Pygrackle. Currently, we only have a map between simulation parameter names and grackle parameter names for Enzo, but users can still provide them by hand, or at least they could if we didn't raise an exception if a parameter map is not found. This removes the exception and simply prints a warning, allowing the user to proceed.
All of this is fairly undocumented outside of the example Python scripts provided, but I intend to improve that moving forward, but ideally not a part of this pull request.