docs: data-requirements spec + NIST/RI/Joback findings + GS-LF terms - #58
Merged
Merged
Conversation
…gs, GS-LF terms - DATA-REQUIREMENTS.md (new): the precise "what data unlocks each capability, in what format, and what we ask a client to provide" spec — conventions, built-on-open-data, data-gated tables (dosing thresholds, FEMA levels, RI), the aroma intake (molecules + expert odor descriptors), the customer-only unlocks (blend perception, liking, stability), and the exact loader column schemas. Doubles as the pilot data-intake sheet. - DATA-SOURCES.md: RI is NOT in PubChem (verified) and NIST RI is paid (~$595–$2,850); GRAS + BP/VP now marked BUILT; "academic-access nuance" (institutional licenses make paid data attainable in research, distinct from NC-laundering); GS-LF clarified as the GoodScents+Leffingwell *combined* NC set, distinct from the paid PMP 2001 product. - CAPABILITIES.md: Joback re-validated across 12 molecules — mean abs error 33 °C, max 89 °C; measured lookup stands. - README: input accepts a common or IUPAC name (or SMILES); pointer to DATA-REQUIREMENTS. Signed-off-by: Austin L. <86896075+rvnminers-A-and-N@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the data-completion findings and adds the client-facing data spec.
New:
docs/DATA-REQUIREMENTS.mdThe precise "what data unlocks each capability, in what format, what we ask clients for" spec — identifier conventions, what's built on open data, the data-gated tables (odor thresholds, FEMA levels, Kovats RI), the aroma intake (molecules + expert odor descriptors), the customer-only unlocks (blend perception, liking, stability), and the exact loader column schemas. Doubles as the pilot data-intake sheet.
Findings recorded
README
Input accepts a common or IUPAC name (or SMILES); pointer to the new spec.