Azzera filtri
Azzera filtri

Variables Not Showing in Workspace After Clearing/Workspace Won't Update Varaibles

42 visualizzazioni (ultimi 30 giorni)
Hello, I am pretty new to Matlab. I have an issue. I am working on some code and want to verify my outputs as I go in the workspace. Let's say I have an array of elements that I modify in 4 different lines. I would comment out certain ones, press run, and check them in the workspace, than I would uncomment other lines working on this array to check any changes, but none are showing in the workspace even though they should. How do I get them to update in workspace after making changes to a code and pressing run?
Also, I thought clearing the workspace might help with refreshing them. I thought after I clear the workspace and run my code again, the values would appear updated. Instead, no variables are showing anymore. Can anyone help?

Risposta accettata

Steven Lord
Steven Lord il 9 Set 2019
My guess is that you're working with function files rather than script files. One of the key differences between scripts and functions is that "Functions have their own workspace, separate from the base workspace. Therefore, none of the calls to the function triarea overwrite the value of a in the base workspace."
You could call your function with output arguments. If you want to see the values of the internal variables created in the function's workspace during its execution but not returned from that function as outputs you could debug the function using breakpoints.

Più risposte (2)

Ted Shultz
Ted Shultz il 9 Set 2019
You should be able to type a variable name into the command window, and have it display the value, or open a variable from workspace to inspect it. To do this, you may want to add breakpoints in your code (click to the left of the code, but the right of the line number). Then you can step throught your code.
This link has more tips for you:

Theresa Mrazkova
Theresa Mrazkova il 9 Set 2019
Thank you everyone! It seems that my issue was working with function instead of a file script. This actually ended up happening because the code I am running was a script with a function definition, originally coded in MT2018. I am running it on a version R2016a and had to modify the file to look like functions so that it runs.


Scopri di più su Workspace Variables and MAT-Files in Help Center e File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by