Hi All,

Not sure if you have encountered this before.
I have done a gauge graph, and everything seems to be working fine, excpet that for some absurd reason "5" is being displayed as "1".

If I have the axis values as 45, 50, 55, 60, 65...then it comes up like 41, 10, 11, 60, 61..

Any help/pointers?????

Can you reproduce this with the car file and show us your code?

It would be extremely difficult to put it using the CAR tale, as I have done a lot of processing on the database side for this.

I just checked the problem all over again, and it seesm there is a difference in the way -READ is treating decimals.

I have defined some variables in my table using the following code snippet.


TABLE FILE DSHDATA
SUM AVE.UTILIZATION_VALUE NOPRINT
COMPUTE GPHMIN1/A6 = GRAPHMIN;
COMPUTE REDMIN1/A6 = REDMIN;
COMPUTE AMBMIN1/A6 = AMBERMIN;
COMPUTE GRNMIN1/A6 = GREENMIN;
COMPUTE GRNMAX1/A6 = GREENMAX;
COMPUTE GPHMAX1/A6 = GRAPHMAX;
COMPUTE PROJL1/A6 = PROJECTION_VALL;
COMPUTE PROJU1/A6 = PROJECTION_VALU;
COMPUTE DWKTXT1/A21 = WEEK_OUT_TXT;
COMPUTE DAMBMN1/A7 = AMBERMINDISP;
COMPUTE DGRNMN1/A7 = GREENMINDISP;
WHERE WEEK_OUT_NUMBER EQ 1
ON TABLE HOLD AS VALUES FORMAT ALPHA
END
-RUN

-READ VALUES &GPHMIN1.A6. &REDMIN1.A6. &AMBMIN1.A6. &GRNMIN1.A6. &GRNMAX1.A6. &GPHMAX1.A6. &PROJL1.A6. &PROJU1.A6. &DWKTXT1.A21. &DAMBMN1.A7. &DGRNMN1.A7.


When I check the values that are read (using the TYPE statement), I find them as follows:

GPHMIN1 = 0084.5
REDMIN1 = 000085
AMBMIN1 = 000090
GRNMIN1 = 000095
GRNMAX1 = 000100
GPHMAX1 = 0100.5
PROJL1 = 000093
PROJU1 = 0093.1
DWKTXT1 = WAXSIN1 : 1 Week Out
DAMBMN1 = 90%
DGRNMN1 = 95%


Please take a look at the first 6 fields.

Then when I display the data in the graph, I am using the following syntax:


SET HAXIS=210, VAXIS=210
GRAPH FILE DSHDATA
SUM UTILIZATION_VALUE
ACROSS WEEK_OUT_TXT
WHERE WEEK_OUT_NUMBER EQ 1
ON GRAPH SET LOOKGRAPH GAUGE1
ON GRAPH SET GRAPHEDIT SERVER
ON GRAPH SET BARNUMB OFF
ON GRAPH SET 3D OFF
ON GRAPH SET VZERO ON
ON GRAPH SET GRID ON
ON GRAPH PCHOLD FORMAT PNG
ON GRAPH SET GRAPHSTYLE *
setDisplay(getGaugeTitle(),false);

setGaugeBandMin(getGaugeBand1(), &REDMIN1 );
setGaugeBandMax(getGaugeBand1(), &AMBMIN1 );
setGaugeBandMin(getGaugeBand2(), &AMBMIN1 );
setGaugeBandMax(getGaugeBand2(), &GRNMIN1 );
setGaugeBandMin(getGaugeBand3(), &GRNMIN1 );
setGaugeBandMax(getGaugeBand3(), &GRNMAX1 );
setGaugeBandMin(getGaugeBand4(), &PROJL1 );
setGaugeBandMax(getGaugeBand4(), &PROJU1 );
setY1ScaleMin( &REDMIN1 );
setY1ScaleMax( &GRNMAX1 );
setFillColor(getGaugeBand1(), new Color(255,0,0));
setFillColor(getGaugeBand2(), new Color(250,200,0));
setFillColor(getGaugeBand3(), new Color(0,255,0));
setFillColor(getGaugeBand4(), new Color(20,20,255));
setFillColor(getGaugeNeedle(), new Color(120,120,120));
setDisplay(getGaugeBand5(),false);

setDisplay(getGaugeTitle(),false);
setSeriesLabel(0," ");
setPlace(false);
setScaleMaxAuto(false);
setGaugeNeedleStyle(5);
setY1MajorGridDisplay(false);
setY1MajorGridStyle(0);
setY1LabelDisplay(true);
setGaugeBackgroundStyle(5);
setGaugeRelativeThickness(0.20);

ENDSTYLE
END


One thing worth noting:

When I execute the same fex by hardcoding the values (that I received using the TYPE statement), the values didplayed are proper ("5" is being displayed)

But if I go along with the mormal mode (without hardcoding; by using the variables from READ, all "5" seem to ge converted to "1" at display time).

I hope I was able to explain the scenario properly. Please suggest if I might be missing out on something

Looks like it is rounding up...Is there any reason these are alpha instead of numeric?

By mimicing your data and then running your graph against it I get no problems with the values on the bands. Although the max and mix settings didn't appear to work.

OK it's only a single row reproduction and I had to guess the AVE value but it should give an idea!

This is was I fed into the process -

FILEDEF DSHDATA DISK DSHDATA.FTM
APP FI DATAMAST DISK DSHDATA.MAS (LRECL 132
-RUN
-WRITE DATAMAST
-WRITE DATAMAST FILE=DSHDATA, SUFFIX=FIX, $
-WRITE DATAMAST SEGNAME=SEG1, SEGTYPE=S0, $
-WRITE DATAMAST   FIELD=UTILIZATION_VALUE, ALIAS=E02, USAGE=D12.2, ACTUAL=A8, $
-WRITE DATAMAST   FIELD=GRAPHMIN,          ALIAS=E03, USAGE=A6,  ACTUAL=A06, $
-WRITE DATAMAST   FIELD=REDMIN,            ALIAS=E04, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=AMBERMIN,          ALIAS=E05, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=GREENMIN,          ALIAS=E06, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=GREENMAX,          ALIAS=E07, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=GRAPHMAX,          ALIAS=E08, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=PROJECTION_VALL,   ALIAS=E09, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=PROJECTION_VALU,   ALIAS=E10, USAGE=A6,  ACTUAL=A06, MISSING=ON, $
-WRITE DATAMAST   FIELD=WEEK_OUT_TXT,      ALIAS=E11, USAGE=A21, ACTUAL=A21, MISSING=ON, $
-WRITE DATAMAST   FIELD=AMBERMINDISP,      ALIAS=E12, USAGE=A7,  ACTUAL=A07, MISSING=ON, $
-WRITE DATAMAST   FIELD=GREENMINDISP,      ALIAS=E13, USAGE=A7,  ACTUAL=A08, MISSING=ON, $
-WRITE DATAMAST   FIELD=WEEK_OUT_NUMBER,   ALIAS=E14, USAGE=I2,  ACTUAL=A02, MISSING=ON, $
-* Now write the data
-WRITE DSHDATA 000092.80084.50000850000900000950001000100.50000930093.1WAXSIN1 : 1 Week Out     90%    95% 1
-RUN

I ran it on 7.6.2 windows platform

T

Not sure if I expected this...
Just check out this car example, same issue is coming up. I used the same format, but with hardcoding of the values. But in my graph also the fives are coming up as ones.

Any suggestions???

-SET &REDMIN1 = 75.0;
-SET &AMBMIN1 = 82.5;
-SET &GRNMIN1 = 90.0;
-SET &GRNMAX1 = 97.5;
-SET &PROJL1 = 84.0;
-SET &PROJU1 = 84.1;

SET HAXIS=210, VAXIS=210
GRAPH FILE CAR
SUM COMPUTE ANY_VALUE1/D6.1 = 88.3; AS ''
ACROSS COUNTRY
WHERE COUNTRY EQ 'ENGLAND'
ON GRAPH SET LOOKGRAPH GAUGE1
ON GRAPH SET GRAPHEDIT SERVER
ON GRAPH SET BARNUMB OFF
ON GRAPH SET 3D OFF
ON GRAPH SET VZERO ON
ON GRAPH SET GRID ON
ON GRAPH PCHOLD FORMAT PNG
ON GRAPH SET GRAPHSTYLE *
setDisplay(getGaugeTitle(),false);

setGaugeBandMin(getGaugeBand1(), &REDMIN1.EVAL );
setGaugeBandMax(getGaugeBand1(), &AMBMIN1.EVAL );
setGaugeBandMin(getGaugeBand2(), &AMBMIN1.EVAL );
setGaugeBandMax(getGaugeBand2(), &GRNMIN1.EVAL );
setGaugeBandMin(getGaugeBand3(), &GRNMIN1.EVAL );
setGaugeBandMax(getGaugeBand3(), &GRNMAX1.EVAL );
setGaugeBandMin(getGaugeBand4(), &PROJL1.EVAL );
setGaugeBandMax(getGaugeBand4(), &PROJU1.EVAL );
setY1ScaleMin( &REDMIN1.EVAL );
setY1ScaleMax( &GRNMAX1.EVAL );
setFillColor(getGaugeBand1(), new Color(255,0,0));
setFillColor(getGaugeBand2(), new Color(250,200,0));
setFillColor(getGaugeBand3(), new Color(0,255,0));
setFillColor(getGaugeBand4(), new Color(20,20,255));
setFillColor(getGaugeNeedle(), new Color(120,120,120));
setDisplay(getGaugeBand5(),false);

setDisplay(getGaugeTitle(),false);
setSeriesLabel(0," ");
setPlace(false);
setScaleMaxAuto(false);
setGaugeNeedleStyle(5);
setY1MajorGridDisplay(false);
setY1MajorGridStyle(0);
setY1LabelDisplay(true);
setGaugeBackgroundStyle(5);
setGaugeRelativeThickness(0.20);

ENDSTYLE
END

If memory serves me - amper vars are integers or characters. Could this be driving the problem?

See also DMPRECISION

This message has been edited. Last edited by: jimster06,

I just checked by using Integer and Character values, but everywhere the problem persists.

-SET &REDMIN1 = '75.0';
-SET &AMBMIN1 = '82.5';
-SET &GRNMIN1 = '90.0';
-SET &GRNMAX1 = '97.5';
-SET &PROJL1 = '84.0';
-SET &PROJU1 = '84.1';

and

-SET &REDMIN1 = 75;
-SET &AMBMIN1 = 82;
-SET &GRNMIN1 = 90;
-SET &GRNMAX1 = 97;
-SET &PROJL1 = 84;
-SET &PROJU1 = 84;

Anyone got any leads on this???
I am not finding any way out of this...

Its got something to do with the way Webfocus treats the values when displaying in graphs.
Even though it is being shown as ones, it still understands and presents as if it were fives.

Simple reason being that 81 is coming right in the middle of 80 and 90, and so on...

Please help!!!

I copied in your code and ran it. The numbers looked correct (I saw displayed a 75,80,85,90,95,97.5).

Maybe there is a version difference?

Perhaps a &VAR.EVAL will help in this case