Timeline for How to understand this circuit?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 11, 2014 at 18:29 | comment | added | Funkyguy | @Majenko-notGoogle This kind of answer is the kind that puts my undergrad professors to shame. Thanks you! | |
Nov 11, 2014 at 16:07 | vote | accept | mastergoo | ||
Nov 11, 2014 at 16:04 | comment | added | mastergoo | Really helpful, best answer ever. Thank you. I guess the main problem for me is the bad interpretation of the picture. | |
Nov 10, 2014 at 23:02 | history | edited | Majenko | CC BY-SA 3.0 |
added 265 characters in body
|
Nov 10, 2014 at 22:59 | comment | added | Majenko | Explaining the method in a way that the OP can understand (i.e., breaking it down into steps using their data) is nigh on impossible without giving away the answer. I could have used a different, though similar, circuit as an example, but I think the OP would learn better being helped through the one example. Maybe we could set some more for him to do to see what he's learned from it? | |
Nov 10, 2014 at 22:09 | comment | added | Olin Lathrop | Shame on you for giving the complete answer to a homework problem. It's good to explain the method, but the actual solution should be kept as a exercise to the student. In this case the "solution" is the method not the final answer, since the final answer was given up front. | |
Nov 10, 2014 at 21:49 | history | answered | Majenko | CC BY-SA 3.0 |