1AUG2019 SolveSys  Equation Library and Nonlinear Systems Solver

02242017, 01:59 AM
(This post was last modified: 02242017 04:21 PM by Han.)
Post: #33




RE: 20FEB2017 SolveSys  Equation Library and Multiple Equations Solver
(02232017 11:46 PM)akmon Wrote: The program is solving smoother as versions upgrades. I´ve made a quick review to the equation library, and here are the flaws I detected, to confirm with your opinion: Verified that 3, 4, 6, and 7 will not solve. This is due to conflicts with R1 and R2 app variables in the Polar graphing app. Changing them to r1 and r2 seems to get around the issue and will likely be the published change. I personally feel this should be a firmware "bug" since app variables are supposed to have higher priority than builtin variables from other apps. We'll wait and see what the developers say. Other conflict messages you can ignore if the system can still be solved. System 7 fails on initial guess of all 1's  this is due to F being undefined during the initial iteration. I'll have to chase down this bug since it should have displayed an error rather in verbose mode. I was unable to find any issues with system E (DC Inductor Voltage) in terms of solving for values. Using 1, 2, 3, ..., 8 for the 8 variables gives me a solution. Did you have a different initial set of values that failed? Quote:Fluids As mentioned above, since you can still solve your system, these conflict messages can be safely ignored. They're mainly in place to help debug which builtin variables are useable and which are problematic (such as R1 and R2). Quote:Motion Confirmed. This is due to two missing variables vx and vy not being defined in the system itself. It appears from your hard work that apps that have functions as builtin variables (e.g. Function app and F0 through F9) currently has priority over usercreated app variables of the same name. So we will have to avoid these specific variables as well. Thank you for finding these; your help is greatly appreciated. I will publish an update to the library data file. Just to give you a heads up: for systems which use functions such as ZFACTOR, SIDENS, etc. you will unlikely be able to solve for the variables that are arguments for these functions. Those variables must be set as constants. In the future (and in theory) they will be solvable once I implement a numerical Jacobian routine, since the CAS most likely does not know how to provide analytical (partial) derivatives of these custom functions. EDIT: library file updated; see http://www.hpmuseum.org/forum/thread772...l#pid68580 Graph 3D  QPI  SolveSys 

« Next Oldest  Next Newest »

User(s) browsing this thread: 1 Guest(s)