You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...Previously while I was working on the Fusion rule that caused all the bugs and crashes in #18, I ended up with this error:
Parsing...
Error in @TABLE, line 93:
# NoTomeAtAll
^^^^^^^^^^^^^^^^^^^^^^^^^
`neighborhood` directive cannot be reassigned
The Moore and von Neumann neighborhoods overlap, so couldn't Nutshell automatically allow Moore in some places and vN in others, and just fill in the corners on all the vN ones with any automatically when it expands it to the Moore neighborhood in the output rule file?
Also, the error message is wrong either way. It should be:
Parsing...
Error in @TABLE, line 94:
neighborhood: von Neumann
^^^^^^^^^^^^^^^^^^^^^^^^^
`neighborhood` directive cannot be reassigned
The text was updated successfully, but these errors were encountered:
I'm sorry, this is the exact thing that ended up getting me in over my head a couple years ago and causing me to quit working on Nutshell :(
If I'm not remembering wrong, I think I was able to implement neighborhood-switching by itself (as well as custom neighborhoods, and building symmetries up from transformations on arbitrary neighborhoods rather than hardcoding all of them) -- but I had to combine it with the symmetry-switching that's been implemented from the start in order for it to actually be usable within Nutshell, and something about that attempt landed me in a weird hole of everything-is-wrong that I just couldn't get out of. The ghost of all this is still there on the v0.6.0 branch, although it's not documented or anything.
I'm leaving this issue open, but I'll say up front that I'm not optimistic about returning to this in the near future, and I don't want you to hold your breath on it. I hope using AlternatingPermute or a custom symmetry type is tolerable in the meantime...?
...Previously while I was working on the Fusion rule that caused all the bugs and crashes in #18, I ended up with this error:
The Moore and von Neumann neighborhoods overlap, so couldn't Nutshell automatically allow Moore in some places and vN in others, and just fill in the corners on all the vN ones with
any
automatically when it expands it to the Moore neighborhood in the output rule file?Also, the error message is wrong either way. It should be:
The text was updated successfully, but these errors were encountered: