Sébastien Villemot (9a557165) at 18 Mar 16:53
Windows package: bump to Octave 9.1.0
... and 1 more commit
Sébastien Villemot (9d3c3917) at 18 Mar 15:02
Bytecode / conditional forecast: fix test over consistency of varia...
... and 1 more commit
Dear Dynare Team,
I hope this message finds you well. I am reaching out to discuss an observation regarding the plot() function as described in the Dynare documentation. It is mentioned that the function "overloads MATLAB/Octave’s plot
function for dseries
objects. Returns a MATLAB/Octave plot handle, that can be used to modify the properties of the plotted time series. If only one dseries
object, A
, is passed as argument, then the plot function will put the associated dates on the x-abscissa". However, in practice, when plotting a simple dseries, the x-axis displays the periods numerically (e.g., 1, 2, 3, etc.) rather than showing the specific dates as intended.
I've managed to devise a workaround for this issue and am sharing it here, hoping it might benefit others facing the same problem.
A=dseries([1;2;3],'2020Y','toto');
% This plot doesn't show dates
plot(A)
% Dates for the plot's legend
DsDates = firstobservedperiod(A):lastobservedperiod(A);
x_Labels= cell(1,length(DsDates));
% Transforms dseries dates into characters
for i = 1:length(DsDates)
x_Labels{i} = char(DsDates(i));
end
% This one does
figure()
hold on
xticks(1:length(DsDates));
xticklabels(x_Labels);
plot(A)
Sébastien Villemot (a3bb1810) at 15 Mar 17:25
Bytecode / FBEGINBLOCK: remove duplicate information w.r.t. variabl...
... and 2 more commits
Sébastien Villemot (dda2b0b3) at 14 Mar 13:04
manual: clarify treatment of missing data in Inversion Filter
Sébastien Villemot (91eabcdc) at 13 Mar 09:34
Merge branch 'IF_doc' into 'master'
... and 1 more commit
Dear Dynare Team,
As a new user of Dynare, I'm reaching out to report a potential bug I've encountered while working with dseries objects in Matlab, specifically using the latest unstable version of Dynare. This is my first time reporting an issue, so please excuse any inadvertent mistakes in my submission. I've noticed an issue where modifying the value of a second dseries object (which was initially set to be equal to a first dseries object) inadvertently alters the values of the first dseries object as well. This behavior is unexpected and seems to occur when the modifications are made within a loop. Here is a quick code snippet illustrating this bug :
addpath 'C:\Produits\dynare\dynare-7-unstable-2024-03-04-1703-7d332dee'
dynare_config;
A=dseries([0;0;0],'2020Y','toto');
B=A;
for i=1:length(B.dates)
B(B.dates(i))=B(B.dates(i))+1;
end
disp(A)
disp(B)
Stéphane Adjemian (d6033211) at 12 Mar 07:58
Add missing option (auxname) in pac_model documentation.
Stéphane Adjemian (2e8ced89) at 12 Mar 07:57
Add missing option (auxname) in pac_model documentation.
You also need to update the manual's list of examples provided.
flexibly
That note seems wrong.
Stéphane Adjemian (57636760) at 08 Mar 16:12
Bug fix in the definition of the PAC expectation (MCE version).
Sébastien Villemot (b90ef427) at 08 Mar 09:59
Build system: enforce minimal GCC version
Stéphane Adjemian (798b5601) at 07 Mar 21:07
Bug fix in the definition of the PAC expectation (MCE version).