Hi, it looks like your xrange argument needs to be enclosed in quotes on
the command line.  Also the format of your dates in the range argument
(dd-mmm-yyyy) is not the same as that in your data (dd/mmm/yyyy).

Steve


On Fri, 23 Mar 2007, g0sp3r wrote:

> Hello.
>
> I am trying to graph hits per hour using the chron prefab. I am
> running into trouble with specifying an xrange. My dataset spans
> severals days over several weeks. I want to graph all hits in a single
> day specified by my xrange= . Ploticus seems to try and graph every
> day present in my dataset instead of just the day I specified with
> xrange=. Anyone have any clues?
>
> I amm calling ploticus as follows
>
> pl -backcolor black  -color white  -png -o @ARGV[1] -prefab chron
> data=@ARGV[0] xrange= 22-mar-2007.0:0:0 22-mar-2007.23:59:59
> tab=hour  datefmt=dd/mmm/yyyy xmargin=0  xinc=\"1 hour\" barwidth=line
>  stubfmt=hh unittype=datetime timefld=2  title=\"\# hits per hour\"
> color=green
>
> my dataset is as follows:
>
> 19/Mar/2007 23:04:36
> 19/Mar/2007 23:05:27
> 19/Mar/2007 23:08:27
> 19/Mar/2007 23:08:40
> 19/Mar/2007 23:11:53
> 19/Mar/2007 23:11:58
> 19/Mar/2007 23:16:55
> 20/Mar/2007 01:10:10
> 20/Mar/2007 05:40:53
> 20/Mar/2007 05:43:57
> 20/Mar/2007 12:40:25
> 20/Mar/2007 19:22:04
> 20/Mar/2007 21:14:49
> 21/Mar/2007 01:26:09
> 21/Mar/2007 09:29:03
> 21/Mar/2007 14:26:34
> 21/Mar/2007 18:10:08
> 22/Mar/2007 03:01:19
> 22/Mar/2007 11:13:51
> 22/Mar/2007 11:19:22
> 22/Mar/2007 14:12:15
> 22/Mar/2007 19:45:46
> 22/Mar/2007 22:46:19
> 23/Mar/2007 14:40:07
> 23/Mar/2007 14:40:23
> 23/Mar/2007 15:58:46
>
>
>
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi.

I found some mistake in result image after running ploticus script.
Result image have big space under the plot.
I open "mydump" file and found points with negative Y coords.
May be that thing is a source of problem?
If I filter mydump without negative points, result image is ok.

Can you check this?

simple script:

#!/bin/sh

name=$0

pl -prefab vbars data=- yrange="35 55" x=1 y=2 -drawdump mydump \
     << EOF
1991 51.7
2050 36.6
EOF

#  cut negative numbers
#sed /-/d < mydump > dump
#  rename
#mv -f dump mydump

pl -prefab draw dumpfile=mydump -eps -o ${name}.eps


P.S. Please forgive me for my bad english :)

Hi, I was able to reproduce this problem here.

I believe you are right.. not sure why those Y<0 points are in there.

Thanks for finding & reporting this bug.  I will look into it shortly.
-Steve


---------- Forwarded message ----------
From: Koval Valery <Valery.Koval@...>
Date: Apr 11, 2007 3:07 AM
Subject: ploticus v2.33
To: stevegrubb@...

Hi.

I found some mistake in result image after running ploticus script.
Result image have big space under the plot.
I open "mydump" file and found points with negative Y coords.
May be that thing is a source of problem?
If I filter mydump without negative points, result image is ok.

Can you check this?

simple script:

#!/bin/sh

name=$0

pl -prefab vbars data=- yrange="35 55" x=1 y=2 -drawdump mydump \
      << EOF
1991 51.7
2050 36.6
EOF

#  cut negative numbers
#sed /-/d < mydump > dump
#  rename
#mv -f dump mydump

pl -prefab draw dumpfile=mydump -eps -o ${name}.eps


P.S. Please forgive me for my bad english :)

Michael, I was able to reproduce this problem here... thanks for finding
& reporting this bug.  I will look into it shortly.  -Steve

On Sat, 31 Mar 2007, Michael Butscher wrote:

> Hi,
>
> because I couldn't find a bug tracker on the Sourceforge page, I write
> the following directly to you.
>
> When using floating segment bars, it seems that Ploticus draws in a bar
> a thin vertical (for horizontal bars) line at the position where the
> previous bar (above the current) ended. I don't know how to remove this.
>
> You can see this for your example "timeline2.htm" ("Gallery of ploticus
> script examples" -> "Horizontal bars" -> "Example 8").
>
> In the documentation it is right, but the attached GIF file shows how it
> looks like when I render it.
>
> I'm using version 2.33 Windows binary on Windows 2000.
>
>
>
> Kind regards,
>
> Michael
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Mike, add the 'locfield' statement eg.

   #proc bars
    color: gray(0.8)
    barwidth: 0.3
    outline: no
    horizontalbars: yes
    segmentfields: c d
locfield: 1
   #endproc

this assigns bars to positions based on your first data field.

without this, it defaults to dropping bars into the first 3 positions
including 0.

-Steve


On Mon, 5 Mar 2007, Mike Karisok wrote:

> Hi
>   I want to draw horizontal bars with several milestones on it.
> Actually everything works fine, but I always have a bar at the bottom
> of the x axis.
> I tried since hours to get rid of it but with no success.
> Any help is very much appreciated.
>
>   Kind regards,
> Mike
>
>   #proc settings
>  units: cm
> #endproc
>   #proc getdata
>  fieldnameheader: yes
>  data:
>  a b       c      d      e       f
>  1 "item"    01/03/2007 31/12/2008 01/01/0001  ""
>  2 "item"    01/03/2007 31/12/2008 01/05/2007  "M1"
>  2 "item"    01/03/2007 31/12/2008 01/08/2007  "M2"
>  3 "item"     01/03/2007 31/12/2008 01/06/2008  "M3"
>  3 "item"      01/03/2007 31/12/2008 01/04/2007  "Planned1"
>  3 "item"      01/03/2007 31/12/2008 01/07/2007  "Planned2"
>  4 "item"    01/03/2007 31/12/2008 01/01/0001  ""
> #endproc
>   #proc areadef
>    title: my Title
>    rectangle: 3 2 12 12
>    xscaletype: date dd/mm/yyyy
>    xrange: 01/03/2007 31/12/2008
>    yautorange: categories
>    ycategories:
>    1
>    2
>    3
> #endproc
>   #proc bars
>    color: gray(0.8)
>    barwidth: 0.3
>    outline: no
>    horizontalbars: yes
>    segmentfields: c d
> #endproc
>   #proc yaxis
>    stubs: categories
>    labeldetails: adjust=-0.4,0
> #endproc
>   #proc scatterplot
>    xfield: e
>    yfield: a
>    labelfield: f offset=0.2
>    textdetails: adjust=0,0.3
>    symbol: shape=triangle style=filled fillcolor=grey(0.01) radius=0.15
> #endproc
>   // Must be invoked again in order to draw the legend
> #proc scatterplot
>   xfield: e
>   yfield: a
>   symbol: shape=triangle style=filled fillcolor=grey(0.01) radius=0.15
>   legendlabel: Milestone
> #endproc
>   #proc legend
>    location: 4 1
>    format: accross
> #endproc
>
>
>
>
> ---------------------------------
> Don't be flakey. Get Yahoo! Mail for Mobile and
> always stay connected to friends.


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi,

two recently reported minor bugs have been fixed.

1) floating segment bars sometimes had an extra line glitch (try the
gallery example timeline2.htm)

2) when bar graphs produced while using -drawdump, the dumpfile had some
wild draw locations causing later result to have large area of blank space
at bottom

Both of these bugs can be fixed by getting this file:

http://ploticus.sf.net/download/proc_bars.c

putting it into your ploticus/src directory, and doing:  make clean; make

These fixes will also be present in the next release.

-Steve

Hi, Steve. Here is a minor issue with titles. The workaround is easy,
though perhaps not obvious.

The following command:

pl -gif -prefab stack data=revs title="this is a test title for this
graph" \
	 "titledet= align=right" -x=1 -y=2

(where 'rev' is a data file with two columns of numeric data)

creates a graph with the title string aligned to the left side of the
graph,
rather than the right. Using 'align=left' causes the title to be
aligned to the
right.

I am using Ploticus 2.32 on Mac OS X (10.4.9).


Josh Simons

Thanks Josh.

About as bass-ackwards as it can be isn't it...

I have fixed this.  Take the following code, put it into a file called
"chunk_title", and then put that file into your ploticus/prefabs
directory, replacing the "chunk_title" file that is already there.
No need to rebuild anything.

-Steve

//--------------------------------------------
//// chunk included by prefabs to do title...
#if @title != ""
   #proc annotate
   #set XCENTER = $arith(@AREARIGHT-@AREALEFT/2.0)
   #set XCENTER = $arith(@AREALEFT+@XCENTER)
   #set TOP = $arith(@AREATOP+0.2)
   location: @XCENTER @TOP
   #ifspec titledet textdetails
   #if $def(titledet) = 1
     #if @titledet like "*align=left"
       location: @AREALEFT @TOP
     #elseif @titledet like "*align=right"
       location: @AREARIGHT @TOP
     #endif
   #endif
   text: @title
   #endproc
#endif
//---------------------------------------------



On Wed, 18 Apr 2007, Josh Simons wrote:

> Hi, Steve. Here is a minor issue with titles. The workaround is easy,
> though perhaps not obvious.
>
> The following command:
>
> pl -gif -prefab stack data=revs title="this is a test title for this
> graph" \
>  "titledet= align=right" -x=1 -y=2
>
> (where 'rev' is a data file with two columns of numeric data)
>
> creates a graph with the title string aligned to the left side of the
> graph,
> rather than the right. Using 'align=left' causes the title to be
> aligned to the
> right.
>
> I am using Ploticus 2.32 on Mac OS X (10.4.9).
>
>
> Josh Simons
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi,

when using a crosshatch fill (eg. hatch6) and also enlarging or reducing
the overall result using -scale, a bug involving incorrect line thickness
occurs.  For example, when drawing a bar graph where the bars are filled
with hatch6 and the result is enlarged using -scale 1.5, the line
thickness grows progressively fatter (exponentially), giving an
unusable result.  The problem is that linewidth context is not being
restored properly when scalefactor is involved.


You can fix this problem by doing the following:

in your ploticus source directory edit the file stub.c

263          sprintf( buf, "%d", pattern );
264          Epcode( 'Y', linewidth, pat_dens, buf );
265          Ecurlinewidth = linewidth / Estandard_lwscale;   /* <-- */
266          Ecurlinetype = pattern;

find line 265 and change it as above.  Then do: make clean; make

-Steve


On Fri, 20 Apr 2007, Koval Valery wrote:

> Hi.
>
> First of all, thanks for you for fix previous bug with negative Y.
> Yesterday I check it - all ok.
>
> Second. I try to build figure with scale >1.0 but bar contour lines
> have doubled width after next iterations.
>
> Please check it: run script.
> If I'm use scale 1.0 - no problem.
>
> #!/bin/sh
>
> #DEV=png
> DEV=gif
>
> name=$0
>
> #if -scale 1.0 \
> #all ok
>
> pl \
>      -scale 1.5 \
>      -prefab vbars data=- \
>      x=1 y=2 color=hatch6 barwidth=0.1 \
>      rectangle="1 1 3 3" \
>      outline="color=black style=0 width=0.2" \
>      -$DEV -o ${OUTDIR}${name}.$DEV $ARGS \
>      << EOF
> 1 845
> 2 1000
> 3 5492.5
> 4 2000
> 5 4656.1
> 6 1946.63
> 7 0
> 8 1000
> 9 5492.5
> 10 2000
> 11 4656.1
> EOF
>
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

This command
ploticus  -prefab chron  data=data14  x=1  y=2  datefmt=yy/mm/dd
xinc="1 month"      stubfmt=M  xyears=yyyy  yrange="0 25"  barwidth=line
color=red       title="# hits per day"  omitweekends=yes

Gives this error

pl error 12040: X Display not properly identified.  Set DISPLAY=
Segmentation fault

Can anyone help by telling me what is wrong and how to fix it please.


Neil Jones
Neil@...

I want to try and overlay graphs using the chron prefab. I'd
like to have a legend, but haven't been able to get it to work.
I do get the legend, but the legends "overlay" each other! The
graph looks find though.

Is there a way to make the legend appear correctly when using
-drawdump?  I couldn't find anything about it in the documentation.

Also, can ploticus automatically choose different colors for the
lines on my graph, regardless of how many there are?  Or do I have
to specify the colors myself?

Thanks,

-- Greg

Greg,

this sounds like a case where the limitations of prefabs are being
encountered.. I'd recommend writing a script. You can get started by
adding the -echo command line arg when running the chron prefab ... this
dumps the underlying script to stdout which you can capture and modify.

The $icolor() function can be used (in scripts) to automatically allocate
colors.

Steve


On Thu, 10 May 2007, sitecrawl wrote:

> I want to try and overlay graphs using the chron prefab. I'd
> like to have a legend, but haven't been able to get it to work.
> I do get the legend, but the legends "overlay" each other! The
> graph looks find though.
>
> Is there a way to make the legend appear correctly when using
> -drawdump?  I couldn't find anything about it in the documentation.
>
> Also, can ploticus automatically choose different colors for the
> lines on my graph, regardless of how many there are?  Or do I have
> to specify the colors myself?
>
> Thanks,
>
> -- Greg
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

I have a data file with TCP packets arrived:
1st column is time stamp;
2nd column is the starting sequence number;
3rd column is the ending sequence number.

I would like to draw a bar graph to illustrate how packets arrived
along the time line.

2007-01-24.19:24:27.076245      1       1461
2007-01-24.19:24:27.077761      1461    2921
2007-01-24.19:24:27.107724      2921    4381
2007-01-24.19:24:27.107733      4381    5841
2007-01-24.19:24:27.107736      5841    7301
2007-01-24.19:24:27.110223      7301    8761
2007-01-24.19:24:27.110230      8761    10221
2007-01-24.19:24:27.110235      10221   11681
2007-01-24.19:24:27.139203      11681   13141

My question is that I don't know how to specify xautorange,
xaxis.stubs and xaxis.tics in this case:
I tried the following, but it didn't seem to work too graciouly.

#proc areadef
    title: received packets
    titledetails: align=C size=10
    rectangle: 1 1 8 6
    xscaletype: datetime yyyy-mm-dd.hh:mm:%2.6f
    yscaletype: linear
    //xrange: 2007-01-24.19:24:27.076245 2007-01-24.19:24:27.139203
    xautorange: datafield=1 margin=0.001second
    yautorange: datafield=2,3

#proc xaxis
    tics: yes
    minorticinc: %.1f seconds
    stubs: datematic
    //stubformat: hh:mm:%2.1f

#proc bars
    locfield: 1
    segmentfields: 2,3
    barwidth: 0.1
    color: color=red
    outline: yes


I tried to use
    xscaletype: time mm:%02.06f
It didn't seem to give me a better result either.

Can anyone help me with this? Thank you very much!

Hello,

I am trying to combine multiple plots but I guess there is some width
restriction on combined graphs because I can only combine plots
unless the image size is not exceeded to some internal limit. If I
try to combine more plots in it I get the bigger image with increased
width but with only few plots combined and rest of the image is
blank. I am using rectangle parameter as sepcified in the
documentation

pl -prefab scat "rectangle= 1 1 3 3" .... -drawdump mydump
pl -prefab scat "rectangle= 4 1 6 3" .... -drawdumpa mydump
pl -prefab draw dumpfile=mydump -png -o all.png

with this rectangle area the graphs are displayed correctly but if I
add 3 more graphs

pl -prefab scat "rectangle= 1 1 3 3" .... -drawdump mydump
pl -prefab scat "rectangle= 4 1 6 3" .... -drawdumpa mydump
pl -prefab scat "rectangle= 7 1 9 3" .... -drawdump mydump
pl -prefab scat "rectangle= 10 1 12 3" .... -drawdumpa mydump
pl -prefab scat "rectangle= 13 1 15 3" .... -drawdumpa mydump
pl -prefab draw dumpfile=mydump -png -o all.png

I get a wierd image with only first 3 graphs in it and rest of the
image is empty. The output image has enough width that it can contain
all 5 graphs easily but I dont know why the last two graphs are
skipped?

Please reply if anyone has answer to this problem.

Thanking in advance.

Shuja

Hi Shuja,

for anything wider (or higher) than 8" you need to specify -pagesizeW,H
command line arg (where W and H are width and height in inches)

To get yours to work I used pl -prefab draw .... -pagesize17,5

However, there are other problems with graphics environment carrying over
into subsequent plots... you'll notice that subsequent axis are blue..  I
have developed a source code fix for this (replaces two files, pcode.c and
proc_drawcommands.c) .... let me know if you would like me to send this.

Another option would be to simply create 4 png files and display them
using html <table>

-Steve


On Mon, 21 May 2007, sszabistian wrote:

> Hello,
>
> I am trying to combine multiple plots but I guess there is some width
> restriction on combined graphs because I can only combine plots
> unless the image size is not exceeded to some internal limit. If I
> try to combine more plots in it I get the bigger image with increased
> width but with only few plots combined and rest of the image is
> blank. I am using rectangle parameter as sepcified in the
> documentation
>
> pl -prefab scat "rectangle= 1 1 3 3" .... -drawdump mydump
> pl -prefab scat "rectangle= 4 1 6 3" .... -drawdumpa mydump
> pl -prefab draw dumpfile=mydump -png -o all.png
>
> with this rectangle area the graphs are displayed correctly but if I
> add 3 more graphs
>
> pl -prefab scat "rectangle= 1 1 3 3" .... -drawdump mydump
> pl -prefab scat "rectangle= 4 1 6 3" .... -drawdumpa mydump
> pl -prefab scat "rectangle= 7 1 9 3" .... -drawdump mydump
> pl -prefab scat "rectangle= 10 1 12 3" .... -drawdumpa mydump
> pl -prefab scat "rectangle= 13 1 15 3" .... -drawdumpa mydump
> pl -prefab draw dumpfile=mydump -png -o all.png
>
> I get a wierd image with only first 3 graphs in it and rest of the
> image is empty. The output image has enough width that it can contain
> all 5 graphs easily but I dont know why the last two graphs are
> skipped?
>
> Please reply if anyone has answer to this problem.
>
> Thanking in advance.
>
> Shuja
>
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hello,

one problem is the granularity of your time points appears to be in
microseconds.  Is a datetime x axis really what you need here?  How much
time will your presented x axis typically cover (min to max)?

With the data shown here I would split off the microsecond component into
a separate field and use that.

Steve


On Wed, 23 May 2007, Chunling Ma wrote:

> Hi,
>
>    I was trying to plot/illustrate TCP packets received on a connection using
proc bars.
>
> The data file looks like this:
> 2007-01-24.19:24:27.076245      1       1461
> 2007-01-24.19:24:27.077761      1461    2921
> 2007-01-24.19:24:27.107724      2921    4381
> 2007-01-24.19:24:27.107733      4381    5841
> 2007-01-24.19:24:27.107736      5841    7301
> 2007-01-24.19:24:27.110223      7301    8761
> 2007-01-24.19:24:27.110230      8761    10221
> 2007-01-24.19:24:27.110235      10221   11681
> 2007-01-24.19:24:27.139203      11681   13141
> 2007-01-24.19:24:27.139211      13141   14601
>
> 1st column: time stamp
> 2nd column: start sequence number
> 3rd column: end sequence number
>
> I used datetime as xscaletype. My question is that I don't know how to use
xautorange, xaxis.stubs, and xaixs.tics in this case to generate a gracious
graph.
>
> Below is some snippet of what is in my proc script file:
>
> #proc areadef
> title: received packets
> titledetails: align=C size=10
> rectangle: 1 1 8 6
> xscaletype: datetime yyyy-mm-dd.hh:mm:%2.6f
> yscaletype: linear
> //xautorange: datafield=1
> xrange: 2007-01-24.19:24:27.076245 2007-01-24.19:24:27.139211
> yautorange: datafield=2,3
>
> #proc xaxis
> tics: yes
> stubs: inc 1 second
> minorticinc: %.2f seconds
> //stubformat: yyyy-mm-dd.hh:mm:%2.6f
>
> #proc yaxis
> stubs: inc
> label: pkts recved
>
> #proc bars
> locfield: 1
> segmentfields: 2,3
> barwidth: 0.1
> color: color=red
> outline: yes
>
> Can anyone help me with that? Thank you very much!
>
> Chunling
>
>
>
>
>
>
>
>
________________________________________________________________________________\
____Pinpoint customers who are looking for what you sell.
> http://searchmarketing.yahoo.com/


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Thank you, Steve.

I would like to cover 30 seconds of packets arrivals. so I guess I
will need at least seconds and microseconds in this case, right?

What do you mean to split off the microsecond into a separate field?
You mean one field still remains as datetime such as
yyyy-mm-dd.hh:mm:ss, and another field is microsecond alone? How do I
use 2 fields combined for x aixs in this case?

Chunling

--- In ploticus@yahoogroups.com, "Stephen C. Grubb" <scg@...> wrote:
>
> Hello,
>
> one problem is the granularity of your time points appears to be in
> microseconds.  Is a datetime x axis really what you need here?  How much
> time will your presented x axis typically cover (min to max)?
>
> With the data shown here I would split off the microsecond component
into
> a separate field and use that.
>
> Steve
>
>
> On Wed, 23 May 2007, Chunling Ma wrote:
>
> > Hi,
> >
> >    I was trying to plot/illustrate TCP packets received on a
connection using proc bars.
> >
> > The data file looks like this:
> > 2007-01-24.19:24:27.076245      1       1461
> > 2007-01-24.19:24:27.077761      1461    2921
> > 2007-01-24.19:24:27.107724      2921    4381
> > 2007-01-24.19:24:27.107733      4381    5841
> > 2007-01-24.19:24:27.107736      5841    7301
> > 2007-01-24.19:24:27.110223      7301    8761
> > 2007-01-24.19:24:27.110230      8761    10221
> > 2007-01-24.19:24:27.110235      10221   11681
> > 2007-01-24.19:24:27.139203      11681   13141
> > 2007-01-24.19:24:27.139211      13141   14601
> >
> > 1st column: time stamp
> > 2nd column: start sequence number
> > 3rd column: end sequence number
> >
> > I used datetime as xscaletype. My question is that I don't know
how to use xautorange, xaxis.stubs, and xaixs.tics in this case to
generate a gracious graph.
> >
> > Below is some snippet of what is in my proc script file:
> >
> > #proc areadef
> > title: received packets
> > titledetails: align=C size=10
> > rectangle: 1 1 8 6
> > xscaletype: datetime yyyy-mm-dd.hh:mm:%2.6f
> > yscaletype: linear
> > //xautorange: datafield=1
> > xrange: 2007-01-24.19:24:27.076245 2007-01-24.19:24:27.139211
> > yautorange: datafield=2,3
> >
> > #proc xaxis
> > tics: yes
> > stubs: inc 1 second
> > minorticinc: %.2f seconds
> > //stubformat: yyyy-mm-dd.hh:mm:%2.6f
> >
> > #proc yaxis
> > stubs: inc
> > label: pkts recved
> >
> > #proc bars
> > locfield: 1
> > segmentfields: 2,3
> > barwidth: 0.1
> > color: color=red
> > outline: yes
> >
> > Can anyone help me with that? Thank you very much!
> >
> > Chunling
> >
> >
> >
> >
> >
> >
> >
> >
________________________________________________________________________________\
____Pinpoint
customers who are looking for what you sell.
> > http://searchmarketing.yahoo.com/
>
>
>   Stephen C. Grubb     scg@...                x-6633
>   Scientific Software Engineer, The Jackson Laboratory
>   600 Main Street  Bar Harbor, Maine 04609 USA
>

Chunling,

I would say that datetime scaling is overkill if you are just displaying
30 seconds worth of data at a time.

You can use proc getdata's 'filter' attribute to break up or otherwise
process your datetime field in various ways.  Check out the proc getdata
man page for some examples of this.

For instance, you might want to keep only minutes, seconds, and
microseconds.  Then you could use simple numeric scaling for the X axis.

I'm not sure how you are selecting 30 second intervals.. if they are
randomly selected then you'd have to account for the occasional boundary
condition when 59 minutes becomes 00.

Hope this is useful,

Steve


On Thu, 24 May 2007, Horsie wrote:

> Thank you, Steve.
>
> I would like to cover 30 seconds of packets arrivals. so I guess I
> will need at least seconds and microseconds in this case, right?
>
> What do you mean to split off the microsecond into a separate field?
> You mean one field still remains as datetime such as
> yyyy-mm-dd.hh:mm:ss, and another field is microsecond alone? How do I
> use 2 fields combined for x aixs in this case?
>
> Chunling
>
> --- In ploticus@yahoogroups.com, "Stephen C. Grubb" <scg@...> wrote:
> >
> > Hello,
> >
> > one problem is the granularity of your time points appears to be in
> > microseconds.  Is a datetime x axis really what you need here?  How much
> > time will your presented x axis typically cover (min to max)?
> >
> > With the data shown here I would split off the microsecond component
> into
> > a separate field and use that.
> >
> > Steve
> >
> >
> > On Wed, 23 May 2007, Chunling Ma wrote:
> >
> > > Hi,
> > >
> > >    I was trying to plot/illustrate TCP packets received on a
> connection using proc bars.
> > >
> > > The data file looks like this:
> > > 2007-01-24.19:24:27.076245      1       1461
> > > 2007-01-24.19:24:27.077761      1461    2921
> > > 2007-01-24.19:24:27.107724      2921    4381
> > > 2007-01-24.19:24:27.107733      4381    5841
> > > 2007-01-24.19:24:27.107736      5841    7301
> > > 2007-01-24.19:24:27.110223      7301    8761
> > > 2007-01-24.19:24:27.110230      8761    10221
> > > 2007-01-24.19:24:27.110235      10221   11681
> > > 2007-01-24.19:24:27.139203      11681   13141
> > > 2007-01-24.19:24:27.139211      13141   14601
> > >
> > > 1st column: time stamp
> > > 2nd column: start sequence number
> > > 3rd column: end sequence number
> > >
> > > I used datetime as xscaletype. My question is that I don't know
> how to use xautorange, xaxis.stubs, and xaixs.tics in this case to
> generate a gracious graph.
> > >
> > > Below is some snippet of what is in my proc script file:
> > >
> > > #proc areadef
> > > title: received packets
> > > titledetails: align=C size=10
> > > rectangle: 1 1 8 6
> > > xscaletype: datetime yyyy-mm-dd.hh:mm:%2.6f
> > > yscaletype: linear
> > > //xautorange: datafield=1
> > > xrange: 2007-01-24.19:24:27.076245 2007-01-24.19:24:27.139211
> > > yautorange: datafield=2,3
> > >
> > > #proc xaxis
> > > tics: yes
> > > stubs: inc 1 second
> > > minorticinc: %.2f seconds
> > > //stubformat: yyyy-mm-dd.hh:mm:%2.6f
> > >
> > > #proc yaxis
> > > stubs: inc
> > > label: pkts recved
> > >
> > > #proc bars
> > > locfield: 1
> > > segmentfields: 2,3
> > > barwidth: 0.1
> > > color: color=red
> > > outline: yes
> > >
> > > Can anyone help me with that? Thank you very much!
> > >
> > > Chunling
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
>
________________________________________________________________________________\
____Pinpoint
> customers who are looking for what you sell.
> > > http://searchmarketing.yahoo.com/
> >
> >
> >   Stephen C. Grubb     scg@...                x-6633
> >   Scientific Software Engineer, The Jackson Laboratory
> >   600 Main Street  Bar Harbor, Maine 04609 USA
> >
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi Chunling,

I understand now what you're trying to do and agree it would be nice if
ploticus could do this, but spent a few minutes trying various things and
can't get any good results.

With datetime scaling it seems to be require at least 1 second between
axis min and max.  Further, the axis routine can't operate at less than
minutes granularity.

If I were doing this I would probably write a small external filter
program (C, perl, whatever) to process the data before it reaches ploticus
(it could be invoked via proc getdata 'command').  This filter would check
for a change in the seconds field... after that occurs it would add
1000000 to the microseconds field.  This would handle all boundary issues.
It would then output the datetime and the massaged microseconds field.
Then pl could plot using the microseconds field (only) as a plain numeric.
I would then identify the date and time in the plot title.


Steve


On Tue, 29 May 2007, Chunling Ma wrote:

> Steve,
>
>     I see your point. But right now, my problem is that I collected data
> for a few seconds (at most 10 seconds actually) every 30 minutes for one
> week. So there were some data points that crossed boundaries of minutes,
> hours, even days. That's why I used the datetime format. Is there a way
> that ploticus can handle this? I used to use gnuplot, and it was able to
> plot this case. But I was thinking of converting to ploticus from now on
> since the pictures it generate look nicer. If it can't handle this case,
> I guess I would have to stay with gnuplot. Thank you very much!
>
> Chunling

Hi Steve

A couple of times now, I come up against some "hard" limits
in ploticus, specifically in:

     #proc getdata
             commandmr: perl -e '
              ...perl script...

and in

     #set variable = "Long,Comma,Separated,List"

In particular, ploticus does not "fail gracefully" if these
limits are exceeded. In the case of #set variable, ploticus
does give an error:

     pl: error 1409: value is too long and has been truncated (#set dummy
= @_SL01)

IFF you exceed the limit (250 chars) by a little bit.
However, exceed this limit by more than a little bit (using ~334 or more
chars)
ploticus just crashes.

Is there any interest in removing some of these hard-limits?
Or (in the interests of keeping ploticus CGI-friendly) making these limits
configurable in the ploticus.cnf file?

I've had a quick look at the source, to see if I could tweak this limit
anywhere, but I couldn't find a simple fix.

In general, I like the fact the ploticus is very fast, and I would not
suggest trading off speed for "features" (speed _is_ a feature :-)
But things like 'flex' (aka lex) produce fast lexical scanners, and it
should be
possible to make ploticus more robust without sacrificing speed.

Regards,
         George Hansper

Hi Steve,

I've found ploticus quite useful, but the date-time handling
is frustrating at times.

There are quite a few input and output formats, but it would be
much easier if users could just "roll there own", eg:

    xstubfmt="hhh hours"  ->   100 hours
    xstubfmt="dd Mmm hhA" ->   21 May 11am

Currently:

    xstubfmt=dd.hhA   -> 01.0AM
    xstubfmt="dd hhA" -> y3$@%  (some rubbish, no messages)

There was no error or warning that the date/time format was
incorrect.

Overall, ploticus would benefit from more informative error messages.

Are there any plans to overhaul the date-time handling, both
on the input and output sides?

I frequently plot data based on log-file output, and it's difficult
to ensure that the date-time values do not span date-boundaries or
other boundaries which might be sensible for that case. Ideally,
ploticus would cope with all such cases smoothly.

Unlike other people, I am not prepared to change to gnuplot, because
ploticus is better documented and easier to use, in general.
I'd rather iron out the bumps in ploticus.

I will echo Chunling's view that being able to handle millisecond
and microsecond resolution on time-stamps is useful.

Regards,
         George Hansper

PS: I noticed a problem with the date-time input

If the last data-point is between 23:59:30 and 23:25:59, the
last day is not rendered correctly. In this example, the
graph is truncated at the start of the last day.
In my real-life cases, the last day is truncated around 6:00am

#!/bin/bash
X_LABEL=day/month
DATE=01
MONTH=05
pl -prefab chron -o stdout -cm data=- -pagesize 20,11 \
                 rectangle="2 2 20 10" \
                 mode=line \
                 x=1 y=2 \
                 unittype=datetime \
                 datefmt=yyyy-mm-dd \
                 xstubfmt="dd hhA" \
                 xgrid=yes \
                 ygrid=yes \
                 ylbl="Mbytes" \
                 xlbl="day/month" \
                 autow=no  <<EOF
2007-${MONTH}-${DATE}.00:00:00  2
2007-${MONTH}-${DATE}.23:59:59  2
2007-${MONTH}-$(($DATE+1)).00:00:00     5
2007-${MONTH}-$(($DATE+1)).23:59:59     5
2007-${MONTH}-$(($DATE+2)).00:00:00     3
2007-${MONTH}-$(($DATE+2)).23:00:00     3
2007-${MONTH}-$(($DATE+2)).23:59:29     3
2007-${MONTH}-$(($DATE+2)).23:59:30     3
EOF

George, thanks for your comments.

The issues that can be addressed in the near term- I will try to get to,
especially the stability-related ones.  The others are more ambitious but
I will add them to the list.

Thanks again,

Steve


On Mon, 4 Jun 2007, George Hansper wrote:

> Hi Steve
>
> A couple of times now, I come up against some "hard" limits
> in ploticus, specifically in:
>
>     #proc getdata
>             commandmr: perl -e '
>              ...perl script...
>
> and in
>
>     #set variable = "Long,Comma,Separated,List"
>
> In particular, ploticus does not "fail gracefully" if these
> limits are exceeded. In the case of #set variable, ploticus
> does give an error:
>
>     pl: error 1409: value is too long and has been truncated (#set dummy
> = @_SL01)
>
> IFF you exceed the limit (250 chars) by a little bit.
> However, exceed this limit by more than a little bit (using ~334 or more
> chars)
> ploticus just crashes.
>
> Is there any interest in removing some of these hard-limits?
> Or (in the interests of keeping ploticus CGI-friendly) making these limits
> configurable in the ploticus.cnf file?
>
> I've had a quick look at the source, to see if I could tweak this limit
> anywhere, but I couldn't find a simple fix.
>
> In general, I like the fact the ploticus is very fast, and I would not
> suggest trading off speed for "features" (speed _is_ a feature :-)
> But things like 'flex' (aka lex) produce fast lexical scanners, and it
> should be
> possible to make ploticus more robust without sacrificing speed.
>
> Regards,
>         George Hansper
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi,

Can someone please help:

The plot file am currently having issues with - was working fine till
recently, and all of a sudden I am having this issue, where it throws
the error msg
pl proc getdata: error 401: Cannot execute command (cat
"DATA/coons/data")(checked the permissions, dont see any issue)

Thanks in advance,
Afsha

My Plot file:
#proc page
  color: @COLOR
  backgroundcolor: @BGCOLOR
  pagesize: 17 8

#proc settings
numbernotation: us

#proc getdata
file: @FILE
fieldnames: conns,timestamp
delim: comma
select: @@1 > 0
select: @@2 > @XMIN && @@2 <= @XMAX


My DATA file is:
20,2007-06-01.00:00:01
18,2007-06-01.00:00:06
16,2007-06-01.00:00:12
19,2007-06-01.00:00:17
17,2007-06-01.00:00:22
18,2007-06-01.00:00:27
18,2007-06-01.00:00:32
19,2007-06-01.00:00:38
15,2007-06-01.00:00:43
18,2007-06-01.00:00:48
16,2007-06-01.00:00:54
16,2007-06-01.00:01:01
14,2007-06-01.00:01:06
17,2007-06-01.00:01:11
17,2007-06-01.00:01:16
15,2007-06-01.00:01:21
17,2007-06-01.00:01:26
18,2007-06-01.00:01:32

Hi, Steve.

When I use the dist prefab with cats=yes Ploticus generates an output graph with
incorrect Y axis bounds and with a single bar that has garbage characters in it,
suggesting perhaps a memory corruption issue.  See below for details.

I am using Ploticus V2.32 on an Intel Mac running Mac OS X 10.4.9.

Using this Ploticus command:

pl -gif -prefab dist x=2 data=test.in cats=yes echodata=yes -debug

With this test.in:

1 aaa
2 aaa
3 aaa
4 bbb
5 aaa
6 bbb
7 bbb
8 bbb
9 aaa
10 aaa

I see the following output:

Device code is g
Setting output file name to dist.gif
Version: pl 2.32
Script file is: /Users/jsimons/ploticus/prefabs/dist.pl
Script file successfully opened
Executing settings
Executing getdata
filling data set# 0
getdata has read 10 records; there are 2 fields per record.
// proc getdata has read & parsed these data:
[1][aaa]
[2][aaa]
[3][aaa]
[4][bbb]
[5][aaa]
[6][bbb]
[7][bbb]
[8][bbb]
[9][aaa]
[10][aaa]
Got 10 records, 2 fields per record.
(endproc)
Executing areadef
areadef: lowerleft: 1,2  upperright: 5.5,4
areadef:   xrange is 0 to 100.   yrange is 0 to 100.
Executing tabulate
filling data set# 1 (this will now be the current data)
Executing areadef
categories in x: list of size=250 malloced
Autorange on y: min=-1.5 to max=1.5
areadef: lowerleft: 1,2  upperright: 5.5,4
areadef:   xrange is 0 to 2.   yrange is -1.5 to 1.5.
Executing yaxis
Executing xaxis
Executing bars
Done with page.  Writing out result file.  Computed bounding box is: 0.58 , 1.79
to 5.50 ,
4.10

I've uploaded the resulting graph to this URL:

http://blogs.sun.com/roller/resources/simons/test.gif

Playing with it, I also tried using cats=yes on field 1 with similar results.
Removing
cats=yes and using field 1 works as it should.

Josh Simons

Hi, you are doing this

   #proc getdata
      file: @FILE

@FILE is a variable... but where is FILE being set?  Not within the script
as shown here.. on the command line?  It looks like the problem is
occurring where you set FILE to a value.

-Steve


On Tue, 12 Jun 2007, afsha_sheikh wrote:

> Hi,
>
> Can someone please help:
>
> The plot file am currently having issues with - was working fine till
> recently, and all of a sudden I am having this issue, where it throws
> the error msg
> pl proc getdata: error 401: Cannot execute command (cat
> "DATA/coons/data")(checked the permissions, dont see any issue)
>
> Thanks in advance,
> Afsha
>
> My Plot file:
> #proc page
>  color: @COLOR
>  backgroundcolor: @BGCOLOR
>  pagesize: 17 8
>
> #proc settings
> numbernotation: us
>
> #proc getdata
> file: @FILE
> fieldnames: conns,timestamp
> delim: comma
> select: @@1 > 0
> select: @@2 > @XMIN && @@2 <= @XMAX
>
>
> My DATA file is:
> 20,2007-06-01.00:00:01
> 18,2007-06-01.00:00:06
> 16,2007-06-01.00:00:12
> 19,2007-06-01.00:00:17
> 17,2007-06-01.00:00:22
> 18,2007-06-01.00:00:27
> 18,2007-06-01.00:00:32
> 19,2007-06-01.00:00:38
> 15,2007-06-01.00:00:43
> 18,2007-06-01.00:00:48
> 16,2007-06-01.00:00:54
> 16,2007-06-01.00:01:01
> 14,2007-06-01.00:01:06
> 17,2007-06-01.00:01:11
> 17,2007-06-01.00:01:16
> 15,2007-06-01.00:01:21
> 17,2007-06-01.00:01:26
> 18,2007-06-01.00:01:32
>
>
>
>
>
>
>


   Stephen C. Grubb     scg@...                x-6633
   Scientific Software Engineer, The Jackson Laboratory
   600 Main Street  Bar Harbor, Maine 04609 USA

Hi Steve,

thanks much for the quick response,

I am setting the FILE in the command line, but that doesnt seem to be
the problem, I tried to hardcode the filename altogether in the plot
file (tried both absolute path and a relative one ) both dont seem to
work i.e, both have the same issue
pl proc getdata: error 401: Cannot execute command (cat "DATA/conns.data")

Thanks,
Afsha

--- In ploticus@yahoogroups.com, "afsha_sheikh" <afsha_sheikh@...> wrote:
Hi Steve,

I think I found the issue, the issue seems to be the maxfields option
I was passing to my script . I was using a very very large number for
maxfields as I had very huge number of rows and changing maxrows that
time did not solve our problem.

When I decreased the value now,it is working fine. I hope this is it
to this problem.

Thanks very much for ur feedback and BTW, we really like ploticus :)

Thanks,
Afsha