Thanks for the help! I looked at the bessel sample and was able to program the transform and postion for my plot elements. I have been able to do the X vs Y1,Y2,Y3 task. I am working on X1 vs Y1, X2 vs Y2, etc. and have got that programmedusing theObject Model as well. I did run into a "hard limit" of 100 XY plots in the AViz model. However, I could generate more than 200 data sets.

Some things that could be better explained in the helpconcern transform vs. position. I now understand that transform istruly a lineartransform of scale, and origin, as I suspected. Postion, however, is actually a viewing window definition (I recall all the old manuals for graphics from HP, Tektronix, AutoCad, etc.and it was spelled out a little moreclearly how the workspace was being modeled).

My final challenge is getting labels to behave since I have to plot stress (values like 2500.0) vs strain (values like 1.3e-4) and the transforms are many orders of magnitude different. Calculating a good font height is difficult. It would be nice if fonts were *not* tranformable so that they would always appear with a predictable size.

I will post the code from this project when I am finished(before next week)

Finally finished the code for a tabular XY data plot. Specifically this code reads from a text file built by another program. The file used for input is a .csv file that can be read by other software as well. My data is from an earthquake response program that looks at stress and strain at many (hundreds) of depths below the ground surface. The structure of the input file consistes of several lines of header material (character string data, either echoed or ignored, a value for the number of data columns to follow (usually somewhere between 20 and 1000) then the data columns. Column 1 is time, column 2 is stress at top-most location, column 3 is strain at top-most location, column 4 stress at location just below, column 5 strain etc..

The duration of the problem is typically 20-40 seconds which works out to about 50,000 "rows" of data. Aviz doesnt care about data sizes, and the user can increase dimensions of the main data array by changing parameter values. I have included a much-shorter data file for the user to play with.

The environment set-up is identical to the "Three-sine" sample, and this version runs from the command line. Note especially the generation of handles for axes and scaling work done. Scaling labels may have to be adjusted "by hand" in Aviz since one may need scientific notation or other, larger formats.

Enjoy! and send me any questions P.S. there was some difficulty uploading the data folder (about 6 MBytes)

Profray

Here are two files. The first shows a plot of 3 stress-strain curves as they first appear after running the code and plotting reaches 5,6,7. They overlap, and I did not set the width right in the vertical and horizontal axes so the labels are not the correct size to handle the numbers. The second plot is after I widened the labels and changed colors on the plot. One reason I dont like changing plot colors is that I still publish in black and white. I have a workaround for adding markers by plotting the same data twice, once as a line, the second time setting the stride variable to, say 50 or 100, then plotting only markers. Of course this doubles the number of plots to do, but its not too bad.
P.S. that would be a nice feature upgrade, like Axum used to do where you could plot a marker every 10 or 20 or 200 data points so you dont have a huge glob of x's on your plot.

Here are two files. The first shows a plot of 3 stress-strain curves as they first appear after running the code and plotting reaches 5,6,7. They overlap, and I did not set the width right in the vertical and horizontal axes so the labels are not the correct size to handle the numbers. The second plot is after I widened the labels and changed colors on the plot. One reason I dont like changing plot colors is that I still publish in black and white. I have a workaround for adding markers by plotting the same data twice, once as a line, the second time setting the stride variable to, say 50 or 100, then plotting only markers. Of course this doubles the number of plots to do, but its not too bad.
P.S. that would be a nice feature upgrade, like Axum used to do where you could plot a marker every 10 or 20 or 200 data points so you dont have a huge glob of x's on your plot.