Closed ccaitlien closed 7 months ago
@mjohnson541 could you take a look at this?
Broadly, we add the initial species to the edge early during initialization because we currently don't add them to core until we call enlarge (which generates reactions so we don't want to call it until all seed mechanisms and reaction libraries have been added). Later the function for adding seed mechanisms searches for the "site" species and finds it (it is in the edge), since it finds it, as best I can tell it assumes because that species was found it doesn't need to do anything about it, which becomes a problem when it tries to add the associated reaction directly to core since "site" isn't in the core.
@ccaitlien the fix has now been merged into the main branch. You can use the latest
Docker image to try it out or install RMG from source using main
, or wait for this to make it into an official release (could be a while).
@JacksonBurns @mjohnson541 thanks for fixing the issue! Appreciate all the work y'all have done maintaining this package :)
Bug Description
In my RMG input file, I'm trying to use the Surface/Methane/Deutschmann_Ni reaction library as a seed mechanism for a simulation involving a SurfaceReactor but I'm getting a ValueError saying that 'site' is not in list. This is what the full traceback looks like:
How To Reproduce
I'm using the methane steam reforming example in the RMG docs here, except I'm using Surface/Methane/Deutschmann_Ni as a seed mechanism instead of a reaction library:
Expected Behavior
I expect
add_seed_mechanism_to_core
to add all of the species in my seed mechanism into the core, however it doesn't seem to be working correctly because the model can't find 'site' in the species list. I also have 'site' as an input species since it's required for a SurfaceReactor, but it looks like having it as an input species doesn't add it into the core either.Installation Information