-
Notifications
You must be signed in to change notification settings - Fork 14
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
Ambiguous truth table / minterms / maxterms #22
Comments
It might just be me, but it isn't obvious to me what you are asking here... Care to clarify? |
Another way of asking the same thing is that with your package when you define Is that clearer? I was thinking this could be clarified by including a truth table in the docs, but maybe there's a better way. |
Maybe another way of saying it is this -- I am taking a class where the instructor provides this example problem in the lecture, which also matches how an example is given with a truth table on Wikipedia https://en.wikipedia.org/wiki/Karnaugh_map#Example While trying to do this example and similar problems for myself in LaTeX with your package, I enter this code which is intuitive to me and find the variables are unexpectedly swapped. Of course I noticed this right away, but assumed it was just another re-arrangement of variables and the minterm cell positions would also move accordingly. Just like the minterms are in a different position for this German K-map. https://de.wikipedia.org/wiki/Datei:Karnaugh_map_KV_4mal4_Gruppe102.svg I believe that if I had seen in the documentation the equation |
Reading the documentation, it is not immediately obvious to me to which truth table the examples correspond. Knowing the corresponding truth table is critical for knowing which cells correspond to which minterms/maxterms.
After some initial research, I gathered that these examples corresponded to these truth tables:
However after further research, I believe those are exactly reversed from what they should be:
I am still not 100% sure, though. It would be helpful if the documentation made this unambiguous.
The text was updated successfully, but these errors were encountered: