In the current implementation, HDF groups are named by simulation tasks, which may include a period ('.') or other characters that prevent names from being used as attributes. E.g. a name upstream.phi_2.4<mix> triggers the following warning:
NaturalNameWarning: object name is not a valid Python identifier:
'upstream.phi_2.4<mix>'; it does not match the pattern ``^[a-zA-Z_][a-zA-Z0-9_]*$``;
you will not be able to use natural naming to access this object;
using ``getattr()`` will still work, though
Once the code is migrated to Cantera 2.5, this warning will likely be triggered from upstream cantera (write_hdf). It may be better to enter conditions as description and avoid the warning.
In the current implementation, HDF groups are named by simulation tasks, which may include a period ('.') or other characters that prevent names from being used as attributes. E.g. a name
upstream.phi_2.4<mix>
triggers the following warning:The warning is inconsequential but annoying ...