hacking the field boundaries


Hacking the field boundaries to force pattern continuity

Back to the list of tips



Did you ever wish for a little overlap at field boundaries, because you just want the bloody pattern to be continuous and you don't feel like recalibrating the system? Sure, sometimes we are lazy and have no shame.

Beamer lets you overlap fields, but it will not double-expose at the boundaries, so we whipped up a glorious hack just for this.

The program "fieldfudge" (on both ebeam servers) will shift fields by a given amount, so that all the blocks overlap a little. If that sounds like cheating, then yes, it definitely is.

The syntax is

fieldfudge infile.gpf outfile.gpf overlap(nm)


The input pattern should be generated with a fixed grid of fields, using beamer or freebeam. Do not use "floating" fields in beamer, since that would create all sorts of crazy unpredictable overlaps. Also, do not use any of beamer's other multi-pass functions. That would get very confusing.


If you need multi-pass writing to smooth out the bumps at field boundaries, then that's an entirely different story, covered in a different ebeam tip. For our friends outside of Yale, fieldfudge can be found in the ebpb funpak.



Back to the list of tips