Mar-17-2018, 07:36 PM
I've merged these threads. Please don't post duplicates. If no one is replying, "bump" the thread by replying to it, and if you still don't get an answer, it usually means you need to either do more research or simplify / elaborate on your problem more. (In this case, you say changing the input doesn't change the output, but you didn't provide samples for us to work against. The monstrous equations also made me glance over your thread before, but more on that below.)
I started digging in but I'm about to have to go so apologies for not being more helpful than this: take a look at the documentation for fsolve. I'm not already familiar with it, but it appears that you're providing start values, not really an input, so it actually makes sense to me that providing different inputs produces the same output (unless I'm misunderstanding, which I totally might be, but please elaborate on that). What you might want to do is try using fsolve on a simpler function (e.g. x=y or a simple quadratic or something), and see if you can reproduce your concern that way. It's often a valuable debugging skill to reproduce the issue more simply, resolve that one, and apply that knowledge to the original problem.
I started digging in but I'm about to have to go so apologies for not being more helpful than this: take a look at the documentation for fsolve. I'm not already familiar with it, but it appears that you're providing start values, not really an input, so it actually makes sense to me that providing different inputs produces the same output (unless I'm misunderstanding, which I totally might be, but please elaborate on that). What you might want to do is try using fsolve on a simpler function (e.g. x=y or a simple quadratic or something), and see if you can reproduce your concern that way. It's often a valuable debugging skill to reproduce the issue more simply, resolve that one, and apply that knowledge to the original problem.