Start with the property, skip the database rabbit hole
#2
by mailcomsims - opened
The property-first approach is the bit that makes sense to me: define what the material needs to do, then explore candidate compositions. Much nicer than starting with a mountain of records. How much detail should the target specification include?
Thanks for reaching out, and glad the property-first workflow works for you!
To answer your question: you can start with as little as 1–2 target properties and their acceptable ranges — that's enough for the model to generate a first round of candidates.
If you have a specific application scenario, feel free to share it here — we're happy to walk you through setting up your first specification.