Dear collegues,
I am in Stata 17 and two weeks ago I installed the xtcd and xtcd2 packages in a laptop and 3 days ago I did the same in a desktop computer. In the laptop, when I type
xtcd gdp
xtcd2 gdp, noestimation
I get the obvious different results (216.25 and 453.436, respectively) as the first line of code calculates the Pesaran's 2004 statistic and the second line the Pesaran's 2015 statistic. However, when I type the same commands in the desktop computer, the results are exactly the same after using both commands (216.25, in other words the result of Pesaran (2004) test). When I use the xtcdf package, I get the same result as the xtcd package, as expected. Both computers have even the same operating system (Ubuntu 20.04). I tried with other variables and the problem remains the same. Although unthinkable for me, my only guess is a possible conflict or something between xtcd and xtcd2 due to a recent update of xtcd2. But I really believe that is almost impossible. Has anyone experienced recently same odd situation? If it is not too much to request, can anyone quickly update both packages and check if they are facing the same problem?
Kind regards,
Nicole
I am in Stata 17 and two weeks ago I installed the xtcd and xtcd2 packages in a laptop and 3 days ago I did the same in a desktop computer. In the laptop, when I type
xtcd gdp
xtcd2 gdp, noestimation
I get the obvious different results (216.25 and 453.436, respectively) as the first line of code calculates the Pesaran's 2004 statistic and the second line the Pesaran's 2015 statistic. However, when I type the same commands in the desktop computer, the results are exactly the same after using both commands (216.25, in other words the result of Pesaran (2004) test). When I use the xtcdf package, I get the same result as the xtcd package, as expected. Both computers have even the same operating system (Ubuntu 20.04). I tried with other variables and the problem remains the same. Although unthinkable for me, my only guess is a possible conflict or something between xtcd and xtcd2 due to a recent update of xtcd2. But I really believe that is almost impossible. Has anyone experienced recently same odd situation? If it is not too much to request, can anyone quickly update both packages and check if they are facing the same problem?
Kind regards,
Nicole
Comment