Re: [NTG-context] MP graph auto axes

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? (It *is* something I can work around in this particular application, I think, but it would be nice if it worked in a predictable manner.) Cheers, adam Jens-Uwe Morawski said this at Thu, 7 Nov 2002 14:36:50 +0100:

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 _______________________________________________ ntg-context mailing list ntg-context@ref.ntg.nl http://ref.ntg.nl/mailman/listinfo/ntg-context

-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay atl@comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-