# Using existing arrays in workspace

16 views (last 30 days)
Marcus Rosales on 17 Nov 2019
Commented: Vladimir Sovkov on 19 Nov 2019
Hello,
I am currently writing some code which finds the eigenstates of a Hamiltonian, but each time I run the code I need to solve a nonlinear differential equation. The solutions of this equation are saved into an array in the workspace.
I need to trouble shoot the code constantly, so it is annoying waiting for this nonlinear equation to be solved, and I need a fairly fine mesh to get my code working properly, so I am wondering if there is a way for me to bypass the boundary value problem solver and just take the existing solution out of my work space provided it is already there?
I appreciate any help I can get!
-Marcus
*I should also add I am just commenting out the line which uses bvp4c after I get the solution in the workspace, but would like to know if there is an automatic way to do this.
##### 2 CommentsShowHide 1 older comment
Marcus Rosales on 18 Nov 2019
I believe this is what I wanted. Thank you!

Marcus Rosales on 18 Nov 2019
You might find memoize useful.

Image Analyst on 17 Nov 2019
Not exactly sure what you're asking, but if you want to export the data from your current workspace to some other function's workspace, one way is to write the variables to a .mat file with the save() function.

Vladimir Sovkov on 18 Nov 2019
A variable stored in the Matlab workspace is accessible from any Matlab script via just addressing its name. If you want it to be accessible from a Matlab function, you must declare it "global" in all the modules (the workspace and the functions).
In my undestanding, the classical eigenstate problem (including the quantum-mechanical Schrodinger equation) is linear--H*\Psi = E*\Psi,--and very many efficient methods to solve it have been developed up to now. Why are you dealing with the nonlinear differential equation?
Vladimir Sovkov on 19 Nov 2019
In order not to alter your code every time you need/don't need the differential equation solver, you can probably use the "if" construction, such as:
if ~exist('z','var') || isempty(z) % z is your precomputed solution; you can add to this "if" other conditions pointing to an incorrect solution (wrong sizes, etc.)
z = ... % your solver
end