ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam T. Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: MP graph auto axes
Date: Thu, 7 Nov 2002 15:03:13 +0000	[thread overview]
Message-ID: <20021107150313.29326@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <20021107143650.307f1c48.morawski@gmx.net>

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 <pragma@wxs.nl> 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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-11-07 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 19:13 Adam Lindsay
2002-11-07  8:55 ` Hans Hagen
2002-11-07 12:11   ` Adam T. Lindsay
2002-11-07 13:36   ` Jens-Uwe Morawski
2002-11-07 15:03     ` Adam T. Lindsay [this message]
2002-11-07 16:50       ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021107150313.29326@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --cc=ntg-context@ref.ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).