[Bruce Weaver]

From the help for -roctab-:

The rating or outcome of the diagnostic test or test modality is recorded in classvar, which must be at least ordinal, with higher values indicating higher risk.

Please consider adding an option to specify that lower values of classvar indicate higher risk. See the TESTPOS option for ROC in SPSS, for example.

TESTPOS(LARGE). The user can specify which direction of the test result variable indicates increasing strength of conviction that the subject is test positive. The larger the test result value is, the more positive the test result is. LARGE is the active default.

TESTPOS(SMALL). The smaller the test result value is, the more positive the test result is.

Thanks.

[Tim Huegerich]

Stata GUI currently doesn't have any dedicated notebook-like interface. It instead outsources this to Jupyter Notebook via pystata API. ... My biggest gripe with this workflow is that it doesn't allow for using browse to browse data set in Stata Data Editor. So one would need to transfer data back and forth between Python and Stata and use third-party viewers to browse the data within Jupyter. I wish there was a smoother way.

Yeah, like one way would be to add a `pystata.config.showgui()` function that opens the normal Stata window with the data and and everything else in the current state of the pystata instance.

[Gorkem Aksaray]

Stata GUI currently doesn't have any dedicated notebook-like interface. It instead outsources this to Jupyter Notebook via pystata API. (I wish StataCorp would choose to implement such a dedicated interface within the do-file editor, but I don't expect that to happen any time soon.) My biggest gripe with this workflow is that it doesn't allow for using browse to browse data set in Stata Data Editor. So one would need to transfer data back and forth between Python and Stata and use third-party viewers to browse the data within Jupyter. I wish there was a smoother way.

[Leonardo Guizzetti]

An option to reset -putexcel- so that, should an error be encountered while developing code to write Excel files that clears the file handle, one doesn't need to close and re-open Stata to re-run the code again.

[Xiaogeng Xu]

I wish for a couple of things. One is the option to have fill patterns in bar graphs so that it's friendly for color-blind users, and the other is in the tabplot/catplot, mute the very small fraction number so that it's more readable (now we have to work around by using twoway bar/scatter).

[Julian Reif]

It would be nice to add an option to collapse to make it keep variable labels. (Further discussion is available in this FAQ.)

[Eyup TANIL]

ı hope stata 18 include more panel second generation unit root tests, structural break unit root tests and cointegration tests.

[Matthew Smith Stata]

Please could we have a program to show the progress bar a programme that includes loops? There is one available (i.e., _dots) but it is undocumented and it would be nice to be able to change the layout (e.g., the number of dots on each row is currently defined as 75 but it would be nice to be able to change that).

[William Lisowski]

Include the undocumented _dots command in the output of

help undocumented

with a link to documentation.

https://www.statalist.org/forums/for...-bar-for-loops

[Luke Masha]

Stata should add a function to plot graphs that are common in research more easily. Graphs of hazard ratios with CI, forest plots etc should be given. Stata also needs to improve the process of adding curves to a single graph. For example, adding curves from multiple different regressions is quite challenging. It would be nice if you could run 4-5 regressions and stata would have a single command that would combine all these regressions on a single graph

[Bruce Weaver]

Currently, these "methods" are available for -pwcompare-:

 method                    Description
    -------------------------------------------------------------------------------------------------
      noadjust                do not adjust for multiple comparisons; the default
      bonferroni [adjustall]  Bonferroni's method; adjust across all terms
      sidak [adjustall]       Sidak's method; adjust across all terms
      scheffe                 Scheffe's method
    + tukey                   Tukey's method
    + snk                     Student-Newman-Keuls's method
    + duncan                  Duncan's method
    + dunnett                 Dunnett's method

Please consider adding Bonferroni-Holm. And yes, I do know there is another way to get this as shown in this thread. But it should be much easier than that, IMO. YMMV.

[Tobias Renkin]

I'll add a vote for native support for parquet files mentioned earlier.

[Clyde Schechter]

Re #618. -lincom- already does this. Just use -lincom- instead of -test- to get full output:

. sysuse auto, clear
(1978 automobile data)

. regress price mpg headroom

      Source |       SS           df       MS      Number of obs   =        74
-------------+----------------------------------   F(2, 71)        =     10.44
       Model |   144280501         2  72140250.4   Prob > F        =    0.0001
    Residual |   490784895        71  6912463.32   R-squared       =    0.2272
-------------+----------------------------------   Adj R-squared   =    0.2054
       Total |   635065396        73  8699525.97   Root MSE        =    2629.2

------------------------------------------------------------------------------
       price | Coefficient  Std. err.      t    P>|t|     [95% conf. interval]
-------------+----------------------------------------------------------------
         mpg |  -259.1057   58.42485    -4.43   0.000    -375.6015   -142.6098
    headroom |  -334.0215   399.5499    -0.84   0.406    -1130.701    462.6585
       _cons |   12683.31   2074.497     6.11   0.000     8546.885    16819.74
------------------------------------------------------------------------------

. lincom headroom - 1.5*mpg

 ( 1)  - 1.5*mpg + headroom = 0

------------------------------------------------------------------------------
       price | Coefficient  Std. err.      t    P>|t|     [95% conf. interval]
-------------+----------------------------------------------------------------
         (1) |   54.63702   371.9428     0.15   0.884    -686.9958    796.2699
------------------------------------------------------------------------------

. return list

scalars:
                 r(df) =  71
                 r(ub) =  796.2698594816296
                 r(lb) =  -686.9958274649326
                  r(p) =  .8836301988856576
                  r(t) =  .1468962933174717
              r(level) =  95
                 r(se) =  371.9427820432963
           r(estimate) =  54.6370160083485

[Leonardo Guizzetti]

Two little suggestions for the do-file editor:

1. Use **## as branches of **# bookmarks. In some sense, bookmarks become headings to organize long codes, not just a way to locate points of interest.
2. Affix letter "h" to **# , **##, ... to hide a section until the next same-level bookmark. For example,

Re #1: This is already how **# and **## work, unless you mean something different. **# creates a level-1 bookmark, and **## creates a level-2 bookmark, nested underneath it's parent. Visual bookmark indicators are shown in the margin in both cases.

Re #2: Wouldn't it be simpler to type any other type of comment? Why not the simple "*" or "**" if you don't care about having a bookmark for that level?

[Bing Yang]

Two little suggestions for the do-file editor:

1. Use **## as branches of **# bookmarks. In some sense, bookmarks become headings to organize long codes, not just a way to locate points of interest. [My apologies. It seems this already exists in Stata 17.]
2. Affix letter "h" to **# , **##, ... to hide a section until the next same-level bookmark. For example,

**#h Set environment parameters
[... hidden codes]
**# Set work directory and load data
cd    "C\username\"
use  "data.dta", clear

**# Regressions

...