From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Gavin via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: [NTG-context] Feynman Diagrams
Date: Wed, 12 Apr 2023 14:34:08 -0400 (EDT) [thread overview]
Message-ID: <1pno1qn2-518s-0n03-7799-52on321nns77@hzvpu.rqh> (raw)
In-Reply-To: <9E517741-28B2-4678-92E8-322B9C57B446@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Wed, 12 Apr 2023, Gavin via ntg-context wrote:
> Hi Hans, Alan, Mikael, and other Feynman fans,
>
> I do think Alan's node module could do a good job with this.
>
> > It would be nice to have a not too complicated syntax, but maybe just have some of the
> > "shapes" of paths available. So, which ones are actually needed?
>
> I think the needed shapes are:
> - dashed or dotted paths already built into MetaPost
> - paths that are wiggly, zig-zag or coiled
> - optional arrows on the paths
> - optional dots or blobs at the connecting points
>
> This is plenty for someone doing Standard Model physics. Model builders doing supersymmetric, walking-technicolor, bla-bla need more, of course, but I’d let them program their own shapes.
>
> The package feynMP already has all of these paths, as well as double-line variants, coded in MetaPost. If I could use feynMP with ConTeXt, that’s what I’d do. It produces very nice diagrams.
Have you tried using feynmp (the metapost macros) directly instead of the LaTeX wrapper? Can you create an example that works with metapost but fails in ConTeXt?
Aditya
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-04-12 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 3:45 Gavin via ntg-context
2023-04-12 11:41 ` [NTG-context] " Hans Hagen via ntg-context
2023-04-12 14:12 ` Mikael Sundqvist via ntg-context
2023-04-12 15:10 ` Gavin via ntg-context
2023-04-12 18:34 ` Aditya Mahajan via ntg-context [this message]
2023-04-12 20:33 ` Gavin via ntg-context
2023-04-12 22:12 ` Aditya Mahajan via ntg-context
2023-04-13 2:42 ` Gavin via ntg-context
2023-04-13 7:50 ` Hans Hagen via ntg-context
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=1pno1qn2-518s-0n03-7799-52on321nns77@hzvpu.rqh \
--to=ntg-context@ntg.nl \
--cc=adityam@umich.edu \
/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).