I should read my own postings more
carefully.
A few days ago, I pointed someone to
the -undocumented- options in this area.
Following that lead,
. gs_fileinfo <whatever>.gph
returns this information in r(command)
etc.
Nick
[email protected]
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Fred Wolfe
> Sent: 03 August 2004 18:06
> To: [email protected]
> Subject: st: added graph feature: solution??
>
>
> I opened the graph in text pad and found this:
>
> StataFileTM:00001:01000:LiveGPH: :
> 00002:00002:
> *! classname: twowaygraph_g
> *! family: twoway
> *! command: twoway lfitci haqdif haq_, sort ciplot(rline)
> blcolor(black)
> blpattern(dash) clwidth(thick) ylabel(,grid glcolor(gs8) nogmin)
> xlabel(0[.25]3,grid glcolor(gs8) nogmin) scheme(vg_s2m)
> ytitle(Change in
> HAQ) title(Regression to the mean: clinic data) xtitle(HAQ
> Disability Index
> Score) legend(off) saving(rtomeancl,replace)
> *! command_date: 2 Jul 2004
> *! command_time: 12:28:50
> *! datafile: c:/statdata/pdox232h/raoafib.dta
> *! datafile_date: 7 Feb 2004 08:01
> *! scheme: vg_s2m
> *! naturallywhite: 1
> *! xsize: 3
> *! ysize: 2
> *! end
>
> That is what I wanted. Question: is there a way to extract
> this information
> with a command?
>
> Fred
>
>
>
>
>
> At 11:48 AM 8/3/2004, you wrote:
> >Dear Nick,
> >
> >Thanks for your reply and the reply of the others. Maybe I
> wasn't clear
> >enough as to what I wanted, nothing quite so heinous as
> "information that
> >Stata can't guarantee to make sense of." Rather, I was
> thinking of an
> >addition that was equivalent to -label data- or -notes
> _dta-. Ideally, it
> >could be an option so it wouldn't inflate the size of the
> file unless
> >requested. If the option was requested it would save the
> graph command and
> >the path/filename.
> >
> >Saving the information in a do file as Richard Stoll suggests is, of
> >course, another way to do this, as is saving the information
> in a note
> >attached to the .dta file.
> >
> >Fred
> >
> >Fred
> >
> >At 11:10 AM 8/3/2004, you wrote:
> >>The very annoying answer "Don't do that then!"
> >>is nevertheless possibly the simplest advice.
> >>
> >>On your suggestion: I doubt that this is the best way
> >>for Stata to go.
> >>
> >>The command a user types that creates a graph could be
> >>a call to a .do file or a user-written program.
> >>That's likely no problem to you, assuming that you can
> >>find or re-create such a .do file or user-written
> >>program, but it is a bad principle for a Stata
> >>graph (file) to contain information that Stata
> >>can't guarantee to make sense of. For example,
> >>the other file could easily have been lost,
> >>discarded or modified.
> >>
> >>In fact, Stata graph files do contain far more
> >>information that can be used. Exploiting the way that
> >>graphs use sersets offers one path here. Vince
> >>Wiggins' talk at the London users' meeting,
> >>recently made available, offers some explanation
> >>and examples.
> >
> >
> >Fred Wolfe
> >National Data Bank for Rheumatic Diseases
> >Wichita, Kansas
> >Tel (316) 263-2125 Fax (316) 263-0761
> >[email protected]
> >
> >
> >*
> >* For searches and help try:
> >* http://www.stata.com/support/faqs/res/findit.html
> >* http://www.stata.com/support/statalist/faq
> >* http://www.ats.ucla.edu/stat/stata/
>
>
> Fred Wolfe
> National Data Bank for Rheumatic Diseases
> Wichita, Kansas
> Tel (316) 263-2125 Fax (316) 263-0761
> [email protected]
>
>
> *
> * For searches and help try:
> * http://www.stata.com/support/faqs/res/findit.html
> * http://www.stata.com/support/statalist/faq
> * http://www.ats.ucla.edu/stat/stata/
>
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
