[Bjarte Aagnes]

.ster to JSON and JSON to .ster

[Bert Lloyd]

While in mata interactively:

1. allow selecting mata code from the do-file editor and Control-D to run the selected mata code

2. if I enter do dofile.do interactively or hit Control-D from the do-file editor, quietly end mata interactive mode and run the do-file without an error.

(I realize these might be a bit contradictory, even just one of them would be helpful if it's not feasible to add both. I don't really have a preference for one over the other.)

[Bert Lloyd]

.ster to JSON and JSON to .ster

.ster and .sters (from the excellent estwrite package contributed by the most excellent Ben Jann) are underappreciated IMHO.

It would be great if there were a way to make .ster (and .sters) files more human-readable. As I understand it they are binary files, they look pretty garbled if opened in a text editor. Being able to look at the contents would help with debugging, double-checking, etc.

(Perhaps there is already a way to view these, I would be very happy to be corrected if so.)


Jann, B. 2005. estwrite: Stata module to store estimation results on disk. Available from http://ideas.repec.org/c/boc/bocode/s450201.html.

[Silvia Gib]

I really hope that Stata 19 will let us import parquet files, they are everywhere now. The only solution I found is an user written command and only works with Linux.

[Fernando Furquim]

I'd like to see the xline and yline options in graphing commands support coordinates for the length of these lines when we don't want them to span the whole graph. It'd make it much easier than current workarounds

[Stephen Jenkins]

Fernando Furquim In the meantime, check out -graph twoway pci-. (Straighforward to use in my experience.)

[George Hoffman]

regarding graph combine: an 'overlay' option woulld be great to superimpose many plots into one set of axes.
the existing xcommon and ycommon options take care of scaling; there would be some legend and labeling logic to work through, but to get the plots on one axis set would be a great step forward for at least a few of us.
thanks for considering

[Bruce Weaver]

This wish concerns explicit inclusion of default options in code and explicit labeling of the option that was used in the corresponding output. I'll use -roctab- to illustrate, but I think this issue applies to many more commands. Here is some code:

use https://www.stata-press.com/data/r18/hanley, clear
foreach method in "" bamber hanley binomial {
    roctab disease rating, summary `method'
}

And here is the output it produces:

. use https://www.stata-press.com/data/r18/hanley, clear
(Tomographic images)

. foreach method in "" bamber hanley binomial {
  2.         roctab disease rating, summary `method'
  3. }

                      ROC                     Asymptotic normal  
           Obs       area     Std. err.      [95% conf. interval]
     ------------------------------------------------------------
           109     0.8932       0.0307        0.83295     0.95339

                      ROC      Bamber         Asymptotic normal  
           Obs       area     std. err.      [95% conf. interval]
     ------------------------------------------------------------
           109     0.8932       0.0306        0.83317     0.95317

                      ROC      Hanley         Asymptotic normal  
           Obs       area     std. err.      [95% conf. interval]
     ------------------------------------------------------------
           109     0.8932       0.0320        0.83047     0.95587

                      ROC                       Binomial exact   
           Obs       area     Std. err.      [95% conf. interval]
     ------------------------------------------------------------
           109     0.8932       0.0307        0.81559     0.94180

The documentation for roctab says:

By default, roctab calculates the standard error for the area under the curve by using an algorithm suggested by DeLong, DeLong, and Clarke-Pearson (1988) and asymptotic normal confidence intervals.

But there appears to be no way to explicitly include the Delong et al method as an option in the code. E.g., this causes an error:

roctab disease rating, summary delong

More importantly, IMO, I think that the SE should be labeled as the DeLong SE when the default option is used so that users do not have to go digging into the documentation to find out what the default is. I.e., I reckon the output should look like this:

. roctab disease rating, summary

                      ROC      DeLong         Asymptotic normal  
           Obs       area     Std. err.      [95% conf. interval]
     ------------------------------------------------------------
           109     0.8932       0.0307        0.83295     0.95339

As I said above, I suspect the same general idea applies to many other commands.

[Chinh Nguyen (StataCorp)]

3) -use- and -net from- should follow http redirects. See https://curl.se/docs/comparison-table.html to see how common this feature is among libraries supporting http access.

Stata 18 already has http redirect support.

[Stephen Weinberg]

Nick Cox in #70

1. What would be an acceptable name length limit?

500 characters

2. How is Stata going to find even more space to show such variable names fully in output?

Truncate them (which I think it does already?)

The issue of incentives is not relevant. I'm paying for software, I want features that fit my use case. Dealing with variable name length issues is a huge waste of time that could easily be resolved with no penalty to users who stay within the current limit.

When I do want to use longer variable names, they are not going to be anything I intend to put in output. Truncating is perfectly fine. This just seems like a non-starter of an objection. (Losing backwards compatibility, as was mentioned in an earlier thread, is a much more credible objection!)

[Stephen Weinberg]

I have two wishes:
1) I wish it was feasible to put text into the cells of tables using the new table or dtable commands. I have looking for workarounds, like using string formatting (but I can't get the numerical value or . to disappear), or trying to trick the table into showing the text you can put in an emptycell (but the restrictions on empty cells knock this out). I finally just put a note to myself to edit in small text notes in Word after exporting.
2) I wish that Stata supported a percentile format, for example displaying .678 as 67.8%. I have to create reports for readers who prefer such output. Yes, I can multiply things by 100, and yes I can USUALLY BUT NOT ALWAYS get the string formatting feature to add a % sign at the end, but it seems silly to have to jump through hoops for what must be a fairly standard need for people writing to non-academics.

[Erik Reinbergs]

FYI, page up key by default fills the console with the last command. I know not every keyboard has page up and I'm not sure whether or not you can change the default to up arrow.

TIL that on a mac keyboard (without the page up/down keys) fn + up_arrow does this! problem solved.

[Bader Bin Adwan]

I use ICD 10 check command to check and identify wrong codes. However, under codes not defined categories, it picked up some codes as not defined although they are found in WHO ICD 10 website. So, I am assuming there are regular updates occurring to the codes and ICD website. My question is, is it possible to update the ICD data in Stata server, if yes, how? And if not please take that into consideration as it very important especially with a lot of those who deal with it.

As an illustration:

In ICD 10 Stata, K58.9 Irritable bowel syndrome without diarrhoea, however in WHO ICD 10 website is not found.

[Leonardo Guizzetti]

I use ICD 10 check command to check and identify wrong codes. However, under codes not defined categories, it picked up some codes as not defined although they are found in WHO ICD 10 website. So, I am assuming there are regular updates occurring to the codes and ICD website. My question is, is it possible to update the ICD data in Stata server, if yes, how? And if not please take that into consideration as it very important especially with a lot of those who deal with it.

As an illustration:

In ICD 10 Stata, K58.9 Irritable bowel syndrome without diarrhoea, however in WHO ICD 10 website is not found.

Edit: I see you did post this initially as a question here.

This would better have been asked as a regular forum post (question) rather than in the wishlist. In any case, Stata has ICD-10 diagnosis codes for both the WHO and US Clinical Modification and Procedure Coding schemes. See -help icd- for more information.

K58.9 exists in ICD-10-CM (US version) but is not a valid ICD-10 (WHO) code.

. icd10 lookup k58*

    K58   Irritable bowel syndrome
    K58.1 Irritable bowel syndrome with predominant diarrhoea [IBS-D]
    K58.2 Irritable bowel syndrome with predominant constipation [IBS-C]
    K58.3 Irritable bowel syndrome with mixed bowel habits [IBS-M]
    K58.8 Other and unspecified irritable bowel syndrome

. icd10cm lookup k58*

    K58   Irritable bowel syndrome
    K58.0 Irritable bowel syndrome with diarrhea
    K58.1 Irritable bowel syndrome with constipation
    K58.2 Mixed irritable bowel syndrome
    K58.8 Other irritable bowel syndrome
    K58.9 Irritable bowel syndrome without diarrhea

[Bader Bin Adwan]

Well, as you can see I have opened a new question about it indeed, and someone advised to write it in the wish list!

I deal with ICD 10 principal diagnosis Not with ICD-10-CM. If you know how to verify ICD 10 codes for huge data without including CM codes that would be great because as I illustrate in the example above there are mistakes although I use icd10 check command not icd10cm one.