For instance, assuming that fs2000a.mod is in the current Matlab/Octave's directory and that a metropolis has been run,
the following command:
>> internals --display-mh-history fs2000a
produces the following output in the Matlab/Octave's command window:
================================
MCMC set-up for fs2000a mod file
================================
MCMC chain number 1:
--------------------
o Number of MCMC files is 1
o Number of draws is 6000
o Acceptance ratio is 35.28%
o Last value of the posterior kernel is: 1221.81656
o State of the chain:
|| Initial | Current
++++++++++++++++++++++++
e_a || 0.01570 | 0.01608
e_m || 0.00528 | 0.00512
alp || 0.35026 | 0.36909
bet || 0.99300 | 0.99308
gam || 0.00086 | 0.00038
mst || 1.00088 | 1.00147
rho || 0.65926 | 0.71132
psi || 0.66428 | 0.60611
del || 0.00977 | 0.00198
MCMC chain number 2:
--------------------
o Number of MCMC files is 1
o Number of draws is 6000
o Acceptance ratio is 33.38%
o Last value of the posterior kernel is: 1220.39229
o State of the chain:
|| Initial | Current
+++++++++++++++++++++++++
e_a || 0.01664 | 0.01576
e_m || 0.00489 | 0.00504
alp || 0.39701 | 0.36630
bet || 0.99305 | 0.99219
gam || 0.00067 | -0.00025
mst || 1.00186 | 1.00218
rho || 0.70060 | 0.63847
psi || 0.65623 | 0.74668
del || 0.00666 | 0.00842
while the command:
>> internals --load-mh-history
loads the content of the record structure (saved in the last mh-history file) in Matlab/Octave's workspace
under the name mcmc_informations.
a specific command named internals.
The internal documentation of a matlab routine can be displayed on screen using the following
syntax:
internals --info <PATH AND NAME OF THE MATLAB ROUTINE>
The unitary tests (if any) associated to a matlab routine are triggered as follows:
internals --test <PATH AND NAME OF THE MATLAB ROUTINE>
+Cosmetic changes in the headers.