-
Notifications
You must be signed in to change notification settings - Fork 8
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
💡 Better definition of selectivity #46
Comments
The currently existing definition for selectivity is not general enough and does not capture what we need to annotate data in existing datasets: "In photocatalytic processes where product formation is expected, selectivity describes the ability of a photocatalyst to produce only the desired product with minimal (or none) of byproducts." The definition I suggest "A property of a product that refers to the ratio of products obtained from given reactants in a chemical reaction." is more data focused. The definitions could be extended by the formula "S(product)=Amount of product/ Sum over all products" and include the ambiguity that sometimes products are assigned special weight factors depending on the number of reactant molecule that goes into each product. |
Selectivity is a complex beast to define (also IUPAC Gold Book is not so great). In my opinion selectivity is not related to the catalyst itself but is a general concept relevant for chemical reaction networks. So it could be defined as "Selectivity quantifies the ratio of a specific reaction product to a set of reaction products in a reaction network." The are various sub-concepts:
|
Hey all, best Micha |
The increase/decrease happens in a reaction network. So the definitions are very similar. Defining selectivity purely based on products has been quite common in projects I worked on which is why I avoided adding the term "reactants" to the definition explicitly. |
How do you define selectivity solely based on products? |
E.g. for the reaction network
the molar carbon-based selectivity to CO is |
it is the fraction of one product over the sum of all products, which should ideally be the same as the decrease of reactants. This is why you can also define 2 conversions - reactant based and product based. For small conversion the error is typically higher in determining a small change in a large amount of reactant, whereas the determination of a small amount of products has a smaller absolute error. |
ok cool thanks. so the question is do you normalize against the sum of releveant products or the sum of relevant reactants but i think there we have, let me try a general formulation: What do you think? |
I like the definition and would just add |
Yes, I also missed "network". My issues with this def is that it is longer but not more precise: Is the selectivity "described by a ratio" or would "is a ratio" be better? Do you mean "physical quality" in the sense of PATO? qudt uses the term "quantity kind". However, the term selectivity is neither a quantity kind nor a (PATO-)"physical quality" since it subsumes different selectivity quantity kinds. Mixing your addition of an "amount" into the short def would give my current favorite: |
Hey David, yes I used physical quality from PATO usually as a subclass of quality from BFO as it is done in the CHMO. 2 things. I think it is important to leave it open if the ratio is with respect to products or reactants. We can have more specific selectivities with a clear calculation rule additionally. As a non chemist I am still struggling with the semantic difference of a chemical reaction and a chemical reaction network. Either the latter is a model for the former or it seems to be the same thing. Or a chemical reaction is a subpart of a reaction network, which seems linguistically weird. That would be more the desired/target chemical reaction. |
To get around reaction vs. reaction network we could just use Selectivity: |
I like the new definition for selectivity. should it replace the old definition or is it a new concept? I could add it in my next PR |
I will add it along with yield and conversion. |
@schumannj see #58 Thank you all for the discussion here! |
Description
Brought up in #45
The text was updated successfully, but these errors were encountered: