On Tue, Dec 11, 2018 at 6:13 AM Johannes Castner <[email protected]> wrote: > > What I'm trying to say is a user has an account and an account has points in > it that can change--just as with any computer game, really. Does that make > sense? >
OK, so here's something to ponder during system design. Atoms are meant to represent graphs, which can be walked, searched, compared-by-shape, modified. So if you can think of your data as graphs, atoms are your thing. But if our data is time-varying -- rapidly varying even, and you don't care about the above, then use values. Every atom has, attached to it, a key-value database. If you know the atom, and you know the key, you can find the value; update it, change it to your heart's content. What you cannot do is search for it (except by exhaustive brute-force.) -- if you don't know the atom or the key, you won't (easily) find it. So, if you ever need to search for everyone who's score is 23, then use a NumberNode. But if you never want to do that, use a Value. Values are an order of magnitude faster than Atoms, thinner, lighter-weight, etc. TruthValues are a special case of values. Linas. -- cassette tapes - analog TV - film cameras - you -- You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/opencog. To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CAHrUA35kqtO2eDoDsmveCMqhYRF%3D6baExyuiEE0Xjd2c-5YmaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
