Andrei, Walter's solution works, as would
optionsChange = array2table(zeros(0,9), 'VariableNames',{...
or even
optionsChange = array2table(zeros(0,9));
optionsChange.Properties.VariableNames = {...
(Both of those have the advantage that they create 0x1 variables in the table, rather than 0x0, and so if you subsequently do something like
>> optionsChange.Exp(2) = 2
optionsChange =
Exp Strike Put_Mark Put_Ask Put_Bid Put_Delta Put_ImplVol Date DateNM
___ ______ ________ _______ _______ _________ ___________ ____ ______
0 0 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0 0
everything will grow in the vertical direction.)
BUT: based on your variable names, you may not end up what you're ultimately looking for. The problem is that "create an empty table" isn't really fully specified. It's kind of like saying, "create an empty variable". The question left unanswered is, what type of variables do you want in that table? The answer might be "all doubles", but it might not. The above all create nine double variables in the table, but your last two variable names indicate dates. If you're using datenums, you're fine (datenums are are just doubles, but if you want date strings, or datetimes, you'll have to either start out with the right thing, or overwrite the doubles in the table that you want to be dates. For example,
>> vnames = {'Exp', 'Strike', 'Put_Mark', 'Put_Ask', 'Put_Bid', 'Put_Delta', 'Put_ImplVol', 'Date', 'DateNM'};
>> optionsChange = array2table(zeros(0,9), 'VariableNames',vnames);
>> optionsChange.Date = datetime(zeros(0,3));
>> optionsChange.DateNM = datetime(zeros(0,3));
>> summary(optionsChange)
Variables:
Exp: 0x1 double
Strike: 0x1 double
Put_Mark: 0x1 double
Put_Ask: 0x1 double
Put_Bid: 0x1 double
Put_Delta: 0x1 double
Put_ImplVol: 0x1 double
Date: 0x1 datetime
DateNM: 0x1 datetime
And finally, as is the case with any kind of variable in MATLAB, instead of creating an empty then growing it row by row, you might consider creating a table that's the right size but filled with NaNs and empty strings or whatever. For example,
optionsChange = array2table(nan(0,9));
That may be faster in the long run, because it doesn't have to keep reallocating memory as the table grows. That may or may not be useful or even possible in your case, just a suggestion.
Hope this helps.
댓글 수: 0
댓글을 달려면 로그인하십시오.