About the estimate Command #406
Unanswered
adhranneto
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Before we go deeper, could you please extract the following pieces of code:
* the *verbatim* lines of code as used with the older iris that set up the
estim struct (initial, lower, upper, prior)
* the *verbatim* line of code. as used with the older iris to run the
estimate command
Then, the same for what you use with the newer version iris.
Thanks
Jaromir
…On Thu, Jun 27, 2024 at 3:21 PM adhranneto ***@***.***> wrote:
Hello. I am trying to perform Bayesian estimation and maximum likelihood
estimation using the estimate command. Using the same data and the same
model, there is a difference in results when using the old version and the
latest version of the command. Apparently, the old version of the command
performed the optimizations correctly. I might be mistaken, but is there
any significant difference in the optimization process or parameterization,
or something that I am not noticing?
For the older estimate command, the maximum likelihood estimates of the
parameters are:
a1 = 0.23
a2 = 0.065
a3 = 0.58
std shock = 1.34
and, moreover, the values are located at the lowest point of the
likelihood function. (I plot the neighborhood). In the new estimate
command, this does not happen. The parameter estimates, besides being
different, are far from the minimum of the likelihood function.
When performing Bayesian estimation, in the old command, the mode of the
posterior distribution coincides with that calculated by the
Metropolis-Hastings algorithm. In the new command, this coincidence does
not occur. The values are very disparate.
Thank you very much in advance for your attention.
estimatemodel.txt
<https://github.com/user-attachments/files/16014502/estimatemodel.txt>
kalm_his.csv
<https://github.com/user-attachments/files/16014504/kalm_his.csv>
model.model.txt
<https://github.com/user-attachments/files/16014505/model.model.txt>
myzif.txt <https://github.com/user-attachments/files/16014507/myzif.txt>
readmodel.txt
<https://github.com/user-attachments/files/16014510/readmodel.txt>
—
Reply to this email directly, view it on GitHub
<#406>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCVKKQKTGTDYY37RDXLJFTZJQGVLAVCNFSM6AAAAABJ75UY7CVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWHA3DSNRYGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. I am trying to perform Bayesian estimation and maximum likelihood estimation using the estimate command. Using the same data and the same model, there is a difference in results when using the old version and the latest version of the command. Apparently, the old version of the command performed the optimizations correctly. I might be mistaken, but is there any significant difference in the optimization process or parameterization, or something that I am not noticing?
For the older estimate command, the maximum likelihood estimates of the parameters are:
a1 = 0.23
a2 = 0.065
a3 = 0.58
std shock = 1.34
and, moreover, the values are located at the lowest point of the likelihood function. (I plot the neighborhood). In the new estimate command, this does not happen. The parameter estimates, besides being different, are far from the minimum of the likelihood function.
When performing Bayesian estimation, in the old command, the mode of the posterior distribution coincides with that calculated by the Metropolis-Hastings algorithm. In the new command, this coincidence does not occur. The values are very disparate.
Thank you very much in advance for your attention.
estimatemodel.txt
kalm_his.csv
model.model.txt
myzif.txt
readmodel.txt
Beta Was this translation helpful? Give feedback.
All reactions