You are not logged in. You can browse but not post. Login or Register by clicking 'Login or Register' at the top-right of this page. For more information on Statalist, see the FAQ.
I do have the same puzzling problem as Busi. I am computing gini coefficients using the bootstrap command to get standard errors. The program does not run because it stops, when trying to create a "__000000" variable that has been already created. Here is the program:
global pauv "C:\Users\Inégalités et pauvreté\Logs\Révision"
global IP "C:\Users\Inégalités et pauvreté\Bases\Révision"
clear all
capture log close
set more off
cap program drop _all
* Programmes
program define inegest, rclass
args var
ineqdeco `var' [fw=fweight]
global gini=$S_gini*100
global r9010=$S_9010
global r7525=$S_7525
global logdev=$S_i0
global theil=$S_i1
I am currently using Stata 14. But the problem is the same when running Stata 13.
I used the trace command and I found that the problem is due to an instruction in the bootstrap.ado file, on line 281:
mark `touse' `cmdif' `cmdin'
I somehow solved the problem in creating a copy of this ado file and putting it in the C:\ado\personal directory (renaming it "bootstrapm.ado") and adding a
cap drop __000000
instruction before the mark instruction. But it is obviously not really satisfactory, and I would appreciate to get some help solving this matter in a more systematic and less empirical way.
I'm late to this party but I encountered a similar issue today where I was hitting this issue in a program I wrote.
. levelsof VIETNAM , local(groups)
-------------------------------------------------------------------------------------------------------------- begin levelsof ---
01 - version 15.0
01 - syntax varname [if] [in] [, Separate(str) MISSing Local(name local) Clean MATROW(name) MATCELL(name) HEXadecimal ]
01 - if ("`missing'" == "") {
= if ("" == "") {
01 - marksample touse, strok
variable __000000 already defined
01 }
---------------------------------------------------------------------------------------------------------------- end levelsof ---
The issue was really weird because the issue was originating from within the levelsof command. It turns out that I had saved the data at an intermediate step, which had saved the temporary variables. I'm <guessing> this confused Stata as to which names it had already used, which is why it got testy when I ran the levelsof command. Once I deleted the intermediate save, there was no further issue.
Comment