I had the same problem of processing hundreds of Datasets to produce images and movies. To change filenames of the datasets and values of text output I was using the macroprocessor m4 out of a shell script to change keywords in the .net and .cfg files. Seems to me a solution with a minimum of coding.
Alex Am Freitag, 25. Juli 2003 17:31 schrieb Sharon Gibson: > Yes, I am in the practice of doing this and there are others (maybe using a > different scripting language). In the archives, there has been some past > discussion about the idea of altering nets (or something to get the same > effect) and using dx in batch mode. One thread I think was called something > like 'parameterizing a net', and another about 'scripting'. > > When I first started doing this it took a while to catch on to the idea of > when to alter the net and when to alter the .cfg (I can't think of a > purpose for which both are needed). But I'll assume for now that you're > smarter than I was and don't need that explanation. I'll just say that it > depends on whether you are just trying to save on the number of user > button-pushing (gui) actions for a large number of cases, or want a > completely automated process (e.g. run overnight and look at output files > or images rather than the screen). > > I'm not sure what you mean exactly by "autogenerate", but if your net/cfg > is of any substantial size, then you will want to merely change the lines > that are needed rather than output the entire code. For this it is best to > get in the habit of naming anything important using a Transmitter. Then it > is much easier to search for and change the value assignments of each item. > > -Sharon > > >Hi- > > > >Has anyone ever written any perl modules for OpenDX? I would imagine that > > if one had a batch of data to visualize, it would be nice to have a > > script which could auto-generate the network and config files. > > Cheers, > Dan
