Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Species in core is isomorphic to species in the edge #2616

Open
PoojaNem opened this issue Feb 28, 2024 · 2 comments
Open

Species in core is isomorphic to species in the edge #2616

PoojaNem opened this issue Feb 28, 2024 · 2 comments

Comments

@PoojaNem
Copy link
Contributor

Bug Description

I am trying to generate a kinetic mechanism for CH2F2 refrigerant using RMG. After completion of the simulation, I get the following warning (image attached below):
Species NNH is isomorphic to species NNH in the edge.
image

How To Reproduce

input.py file is attached below for further investigation.

Installation Information

OS: Windows 11, WSL2, Ubuntu 22.04
Installation method: Installation by Source Using Anaconda Environment for Unix-based Systems: Linux and Mac OSX
RMG version information:
RMG-Py: Latest version
RMG-database: Latest database

input.txt

@JacksonBurns
Copy link
Contributor

@mjohnson541 I think you originally added this warning, could you take a look at this error?

(was added in this commit: 973d8bf)

@mjohnson541
Copy link
Contributor

mjohnson541 commented Feb 28, 2024

First, for this particular run for species in the edge I don't think this is something to be particularly worried about.

These two structures are the same in terms of connectivity but different electronically without any difference in multiplicity so we should consider them the same species. These kinds of issues usually occur because of how the resonance system and our reaction definitions interact. My guess is some reaction family is producing an electronic structure of NNH that isn't in the list of resonance structures for the expected NNH causing it to think they are different species, but @alongd might have a better idea what is happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants