01
Try an early build
Early-access builds of the Windows app go out by email. Say what you would use it for, and what machine you have.
Request early accessGet involved
Help make the chemistry right.
Valence is early. The most useful people right now are testers with Windows machines, chemists and physicists who can spot a wrong number, and teachers who know what students need to see.
02
Test it on your Windows machine
Different machines find different bugs. If something goes wrong, tell us what you did just before it.
Offer to test03
Report wrong chemistry
If a bond length, an angle, a barrier or a reaction looks wrong, say what the app shows, what it should be, and where that number comes from.
Report wrong chemistry04
Teach with it
Teachers: tell Arda what you would want to show a class, and what would stop you using it. Lesson ideas shape what gets built.
Share a lesson ideaHow it works
Bring a reference.
Valence is built on one habit: a claim about physics is settled by a measurement, not by an opinion. Reports are handled the same way.
- Physics disputes need a source. A paper, a database entry (NIST, ATcT, CCCBDB) or a textbook page. “It looks wrong” is a good start; a number with a source is what gets things fixed.
- A confirmed problem is measured first. Before the model changes, the error is reproduced and written down, and the fix is kept only if the measurements say it helps.
- No release dates are promised. Builds go out when they pass their checks.
- Be kind and specific. Criticise the model as hard as you like, never the person. Harassment of any kind means you won’t hear back.