From: montura on 19 Oct 2009 14:54 That is pretty easy with SAS/AF and SCL. I use a skeleton that remains essentially the same structure-wise for basic/everyday programs and for more advanced multi-thread/multi- application integrations. The classnotes will be posted, chapter by chapter, on KeyStoneSUG.com starting this week. Keep in mind that there are about 40ish rules to follow when it comes to advanced Object programming so it will be awhile before a decent collection is available.
From: rjf2 on 19 Oct 2009 14:46 > From: Webb Sprague > Sent: Monday, October 19, 2009 1:20 PM > Subject: SAS recipe for end-to-end workflow? > > Hi all > > (First, I am a SAS newbie, though an experienced programmer. I have > googled a little for this, I promise...) > > I would like to automate some data analysis processes in population > estimation, which would take a bunch of csv data files and some > shapefiles as the beginning, do stuff to them (including some > geographic intersections to get appropriate FIPS codes and the like), > make pretty postscript tables, surround the tables with text, and > output the final InDesign / postscript file that is ready to ship to a > customer after a quick QA on a windows desktop. > > I want all my tweaking to be done in the code, rather than by hand; so > if a border needs to be switched from 1 point to .5 point, I want to > write code to do this, not open the document and do it by hand. > > Does anyone have a skeletal recipe or a link for this? If SAS can't do > it, I don't know what can... Q: what is your desired output format? A: Post-Script? surely you jest!? http://en.wikipedia.org/wiki/PostScript * created in 1982 * stable release: PostScript 3, 1997 anyway: check out The New&Improved Output Delivery System: ODS which can provide quite a lot of micro-management such as "border needs to be switched from 1 point to .5 point" you are going to have to learn * SAS: number-crunching * ODS destinations: html, rtf, tex, xls * ODS mark-up: style sheets, templates, etc. personally I would recommend ODS LaTeX from which you can generate *.pdf pdfLaTeX My-SAS-ODS-output.tex output is My-SAS-ODS-output.pdf http://www.latex-project.org/ Ron Fehd the TeXnician but not TeX macro maven CDC Atlanta GA USA RJF2 at cdc dot gov
From: Webb Sprague on 19 Oct 2009 14:55 See below On Mon, O > Q: what is your desired output format? > > A: Post-Script? > > surely you jest!? Umm, I want something I can directly import into In Design. And I don't want to mess around with Latex > anyway: check out The New&Improved Output Delivery System: ODS > which can provide quite a lot of micro-management > such as > "border needs to be switched from 1 point to .5 point" > > you are going to have to learn > * SAS: number-crunching > * ODS destinations: html, rtf, tex, xls > * ODS mark-up: style sheets, templates, etc. Ok -- that isn't going to be a problem. Back to my original question -- is there a link or a recipe or example somewhere? Surely I am not the first to think of this. > pdfLaTeX My-SAS-ODS-output.tex > > output is My-SAS-ODS-output.pdf > > http://www.latex-project.org/ Like I say, I don't want to have an intermediate latex format, mostly because it is just one more weird hassle in a Windows environment. I want to be able to hand off a script (or whatever you call it) in SAS plus a little training and Voila! Tx
From: montura on 19 Oct 2009 15:20 Missed the part about "latex and postscript". The SAS part is easy - you should consult and consult and consult again with the Oracle of Guinness Brew before attempting that maneuver.
From: Webb Sprague on 19 Oct 2009 15:06
n Mon, Oct 19, 2009 at 12:04 PM, Mike Bohlig <bohlig(a)ccsse.org> wrote: > Regardless of the output format you use, my guess, given your description of the processing you want to do, is that you will need to implement some extensive macro coding to automate your data processing so that someone who has "a little training" can effectively use your program to generate the output. Yes, that is true. Do you know of an extended example or the like? |