How do you store multiple variables?

Question

Duckyoon Go 2021-3-30

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/788374-how-do-you-store-multiple-variables

评论： Duckyoon Go 2021-3-31

采纳的回答： Walter Roberson

Hello,

I would like to ask how you store multiple variables and control them.

Let's say there are 26 variables.

a=123;

b=..;

c=...;

......

z=123;

variable a,b,c,d are related and e,f,g,h are related and so on.

Would you make vector A=[a,b,c,d], B=[e,f,g,h] and so on and bring them out whenever you need like A(1) or A(2)?

I am wondering if I make vector and store variables in it, how will other people know what that numbers are when they read my code? what is A(1) or A(2)?

Should I put comment for every single variables what they are next to the vector?

I woud like to know the rule of thumb when you store the variables.

THANK YOU!!

6 个评论
显示 4更早的评论隐藏 4更早的评论

dpb 2021-3-31

And, as Walter points out below, you can identify key subscripts with IDs through other variables (too bad MATLAB doesn't have enumerations for such purposes) to label things.

The key there in my mind is to:

Don't go overboard in trying to name everything; just the key elements, and
Use meaningful but still short names so code isn't cluttered by long names making even harder to read than just the integers.

Duckyoon Go 2021-3-31

Thank you so much to everybody!! I got the idea!

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Walter Roberson 2021-3-30

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/788374-how-do-you-store-multiple-variables#answer_662989

在 MATLAB Online 中打开

Your code is not required to use numeric indices in the body of the code.

pitch = 1; yaw = 2;
...
cos(A(pitch))*sin(A(yaw))

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

dpb 2021-3-31

在 MATLAB Online 中打开

I once had to maintain a production, real-time instrumentation code built around an indexing system of arrays. The original idea was one could make coding changes by changing the indexing variables. It never worked out that way in the end, but couldn't convince employer to rewrite.

It ended up with code that looked like--

FUNCTION ConvergeSelectedCentroid%
    ConvergeROI% = Calib!(228)
    DIM CalibTime AS TimeStruct, NormalTime AS TimeStruct
    CalibTime.secs = SysCon!(132)
    NormalTime.secs = SysCon!(131)
    ' Find the Carbon Escape centroid and then try to align to desired
    AdjustedPeak% = FALSE
    MaxIterations% = Calib!(219)
    FOR i% = 1 TO MaxIterations%
        Origin% = ConvergeROI% * 20
        DeltaChannel! = Calib!(Origin%+20) * 100! - Calib!(Origin%+38)
        IF ABS(DeltaChannel!)<Calib!(214) THEN
            AdjustedPeak% = TRUE
            EXIT FOR
        END IF
        Calib!(211) = Calib!(211) + DeltaChannel! * SysCon!(243) * SysCon!(244)
        HVSet
        ...