-
Notifications
You must be signed in to change notification settings - Fork 43
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
Missing buffer state checks #21
Comments
failure is also supported (as "error"). requested and unrequested checks are not supported. I'll have to check this in the manual to see if I could add them, thanks for pointing this out! |
My reading of the manual (quoted over here) is that Maybe in practice they result in the same thing though? |
Thanks, I see (thanks also for the comment in #20). I cannot think of how |
Maybe
Also, from the visual-location section in the manual (pg. 357):
And visual buffer (pg. 369):
If we think of a generic module (not just declarative memory) - might there be other sources of error that you would set So for the declarative memory case, as implemented, it would be the same as there are no other sources of module error. Aside: I find it an odd design decision in ACT-R that one queries the module state by giving the buffer name instead of the module. Any insight into why it was done this way? I think that really confuses things. I assume if a module has two buffers that querying |
Thanks for the examples. If I get it right then buffer failure might be a more specific case, but so far from all examples it seems that whenever there is
Yeah, maybe ACT-R uses
I also find it an odd decision. And it also makes it non-trivial for pyactr implementation. pyactr currently only queries buffers, not modules (also for state) because it's the buffer, not the module, that the modeller specifies in their productionstring. pyactr gives modellers the options to connect more buffers to the same module and to create and name their own buffers. If I switch |
In the more general case with multiple buffers, I don't know if it applies or is helpful, but what I'm experimenting with in gactar is separating the two to make them clear. Something like this:
What I do internally is lookup the first buffer on the module and produce this code for ACT-R since it queries the module through the buffer (at least it says it does in the manual):
This is assuming that - if we had two buffers - querying on either of them for Essentially I'm trying to correct what I think is a confusion in ACT-R by making it explicit. |
One more tidbit I just ran across in the manual (pg. 520):
(emphasis mine) |
(Related to #20)
According to the ACT-R manual, there are 5 checks one can do on a buffer (ACT-R manual pg. 229-230):
From my reading of the pyactr code, it looks like only two buffer checks (
empty
&full
) are supported.Am I reading the code correctly? If so, does anyone know why the others were omitted?
(Context: asmaloney/gactar#221 )
The text was updated successfully, but these errors were encountered: