At 07:13 PM 11/6/2002 +0000, you wrote:

This is not strictly a ConTeXt problem, but I was hoping there were enough MetaPost experts on the list that I might get an idea of what's going on, or at the least, where to go for more information.

I think the MetaPost graphing features are fantastic. It produces very nice output, and automatically handles a lot of axis labelling that other packages don't bother with.

However, it auto-labels the y-axis on the following three graphs very differently. I was wondering if this is a strict limitation in the axis ranges that MetaPost deals with gracefully, or if it might be a bug. I haven't seen any reference to the correct range for graph axes. I've tried many ranges, and some work, some don't.

looks like some problem in interpreting the big numbers, (mp can handle only numbers <4000 and some string trickery is used in the graph package); does this also happens in stand alone graphics or is it context specific? Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

On Thu, 07 Nov 2002 09:55:29 +0100 Hans Hagen wrote:

looks like some problem in interpreting the big numbers, (mp can handle only numbers <4000 and some string trickery is used in the graph package); does this also happens in stand alone graphics or is it context specific?

no, the problem is not specific to ConTeXt. The problem is in the Gipick_ macro. There a logarithm is calculated: n = 1 for i=1 upto mlog(xpart Gmhh_-xpart Gmll_)/Mten - mlog m/(Mten-epsilon): *10 endfor; The problem is that the argument of mlog becomes <0, thus it is not defined. Here is the error message for the 3rd graph: ! Logarithm of -1385.99995 has been replaced by 0. Gipick_->...i=1upto.mlog(xpart.Gmhh_-xpart.Gmll_)/ Mten-mlog.m/(Mten-epsilon)... auto->...fi.else:hide(Gme_:=Gesame_)Gigen_(Gipick_ ,Gcma_.Gpack_(m,Gme_))fi <to be read again> I spend some time yesterday, but the package is a little tricky and uses some not intuitive variable names. so... Jens

At 03:03 PM 11/7/2002 +0000, you wrote:

Hi Jens.

Thanks for those insights. Perhaps ironically (perhaps not), I don't encounter the problem when I put the axes on a log-scale.

Is MP-graph being actively maintained? Is this something that I could push to get fixed?

since hobby published the manual in a recent tugboat ... i suggest that you send him a mail with a test.mp file demoing the problem; afaik normally he's responsive to real bugs (you can cc to me) "John Hobby" Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------