Software that makes placemats

[AHB]

You should delight that, at no effort to yourself, TPF’s finest minds are keeping me in check. Express joy.

This is true. I apologise for my earlier, churlish comment. My thanks and appreciation go to those able to contribute meaningfully to this thread and keep Julian challenged and in check.

I raise a glass of port to the good health of you all. Cheers!

[jdaw1]

In a sheet for displaying corks, what should be the default minimum space required per cork? Three inches across? And how much vertical space? (The algorithm will be efficient about space usage, but the minima are important.)

[jdaw1]

if it's ready in time, i can try next month for the GC-SW-QH tasting. But i appreciate this is non-essential!

Updated draft of the placemats.

• +Cork display sheets, as requested.

The manual has not yet been updated, but will be soon.

I hope that people appreciate that this functionality diminished my cellar by a very fine bottle of T77. The sacrifices one makes.

[jdaw1]

The manual has not yet been updated, but will be soon.

Some minor fixes to the new code, and manual updated. Please use the latest code.

[RAYC]

I hope that people appreciate that this functionality diminished my cellar by a very fine bottle of T77. The sacrifices one makes.

Probably not as much as you appreciated it!

[jdaw1]

I have an algorithm problem.

We need a known number of cork-display rectangles, this being computed using CorkDisplayNumCopies and CorkDisplaySpaceForNumExtras. We need to compute how many rows and columns go on each page, subject to CorkDisplayMinWidth and CorkDisplayMinHeight.

So the code loops over /Portrait and /Landscape, computing available space, and loop over numbers of rows and columns:
• Preferring possibilities that meet the CorkDisplayMinWidth and CorkDisplayMinHeight constraints.
• Within those, preferring those requiring as few pages as possible.
• Within those, preferring those for which each rectangle has maximal area.

It’s not bad, but the area preference is wrong, because it has no bias towards rectangles being of the ratio implied by the minima (tall and thin being unhelpful, for example). So, relabelling the minima as H and W, both positive, I want to maximise over positive h and w a function f[h,w,H,W] satisfying:
• f[h,w,H,W] = f[w,h,W,H];
• ∂f[h,w,H,W]/∂h > 0;
• ∂f[h,w,H,W]/∂w > 0;
• w/W > h/H ⇔ ∂f[h,w,H,W]/∂h > ∂f[h,w,H,W]/∂w, equality implying equality.
What should be f[…]? I’m stumped. Suggestions please.

[RAYC]

I have an algorithm problem.

We need a known number of cork-display rectangles, this being computed using CorkDisplayNumCopies and CorkDisplaySpaceForNumExtras. We need to compute how many rows and columns go on each page, subject to CorkDisplayMinWidth and CorkDisplayMinHeight.

So the code loops over /Portrait and /Landscape, computing available space, and loop over numbers of rows and columns:
• Preferring possibilities that meet the CorkDisplayMinWidth and CorkDisplayMinHeight constraints.
• Within those, preferring those requiring as few pages as possible.
• Within those, preferring those for which each rectangle has maximal area.

It’s not bad, but the area preference is wrong, because it has no bias towards rectangles being of the ratio implied by the minima (tall and thin being unhelpful, for example). So, relabelling the minima as H and W, both positive, I want to maximise over positive h and w a function f[h,w,H,W] satisfying:
• f[h,w,H,W] = f[w,h,W,H];
• ∂f[h,w,H,W]/∂h > 0;
• ∂f[h,w,H,W]/∂w > 0;
• w/W > h/H ⇔ ∂f[h,w,H,W]/∂h > ∂f[h,w,H,W]/∂w, equality implying equality.
What should be f[…]? I’m stumped. Suggestions please.

I suggest the formation of a working group chaired by AHB

[PhilW]

What should be f[…]? I’m stumped. Suggestions please.

Perhaps:
f(h,w)=wh/(ah+bw) for all h>=H,w>=W else 0 (invalid)
where a,b are positive constants essentially defining the ideal ratio; a>b, perhaps a=kb where k>1.0, likely ~2.

[AHB]

I suggest the formation of a working group chaired by AHB

I would be delighted to chair such a group, hereby known as the Taylor '77 Working Group.

[jdaw1]

An opening question for the Taylor 1977 Working Group (‘T77WG’?):

In a sheet for displaying corks, what should be the default minimum space required per cork? Three inches across? And how much vertical space? (The algorithm will be efficient about space usage, but the minima are important.)

We need the help of somebody who is expert in the handling of broken corks.

[AHB]

My suggestion would be to use a minimum length of 3 inches and a minimum width of 2 inches. These dimensions should allow all pieces of a fragmented cork to be reasonably contained in the rectangle.

[jdaw1]

So you prefer a portrait display to landscape? I am surprised.

[jdaw1]

f(h,w)=wh/(ah+bw)

An excellent form. It doesn’t quote solve the problem as asked, but if one is instead differentiating with respect to Ln[h] and Ln[w], so considering proportionate increases, it works well.

f[h,w,H,W] = h w /( W h + H w ), or –1 if the denominator is ≤0.

This is increasing in both h and w. It can be rearranged to be a constant times a function of (h/H) and (w/W), and is faster increasing in the smaller of these.

Thank you. To be implemented at the next opportunity.

[AHB]

So you prefer a portrait display to landscape? I am surprised.

I've mentally tried both layouts and while I don't feel very strongly one way or the other, I did find myself naturally holding a sheet of A4 in portrait form as the more natural form. However, i do accept that others may feel more strongly inclined to the landscape format.

[jdaw1]

Think not of the paper, but of the rectangle to hold the cork or cork pieces. That rectangle could be landscape, even on a portrait page (e.g., two columns and four rows). Should the rectangle be portrait or landscape?

[PhilW]

f(h,w)=wh/(ah+bw)

An excellent form. It doesn’t quote solve the problem as asked, but if one is instead differentiating with respect to Ln[h] and Ln[w], so considering proportionate increases, it works well.

f[h,w,H,W] = h w /( W h + H w ), or –1 if the denominator is ≤0.

This is increasing in both h and w. It can be rearranged to be a constant times a function of (h/H) and (w/W), and is faster increasing in the smaller of these.

Thank you. To be implemented at the next opportunity.

Minor note
f[h,w,H,W] = h w /( W h + aH w )
where a>0 (or scaled by rearrangement) would allow for the optimum proportion being potentially different from the ratio of the minimum values.

Think not of the paper, but of the rectangle to hold the cork or cork pieces. That rectangle could be landscape, even on a portrait page (e.g., two columns and four rows). Should the rectangle be portrait or landscape?

I'd suggest landscape rectangles for preference, whether page is landscape or portrait.

[jdaw1]

To be implemented at the next opportunity.

Done.

Code: Select all

/CDSizeScore  % http://www.ThePortForum.com/viewtopic.php?t=175&start=205
   CDHeightOneCork CDWidthOneCork mul
   CorkDisplayMinWidth 0 gt  CorkDisplayMinHeight 0 gt  and
   {
      CorkDisplayMinWidth CDHeightOneCork mul  CorkDisplayMinHeight CDWidthOneCork mul  add  dup 0 gt {div} {pop pop -1} ifelse
   } if  % positive minima
def  % /CDSizeScore

[PhilW]

@Julian - ty for making the placemat postscript freely available online; used to great effect last night for non-TPF session.

Also discovered another possible bug, as follows:
- first define all the /Belowtitles as ( ) (i.e. a brackets with two spaces between; defining one member of the array this way and all others as () is also sufficient)
- then set /DecanterLabelsNumCopies to 1
- then convert to pdf (using ps2pdf.com)
- this causes the distiller to crash due to overflow (probably something to do with assessing font size based on only space characters?).

The reason this occurred was that I previously had values in all the /Belowtitles fields, all with start and end spaces, such as "( Magnum )" and simply removed all the words, but not the additional start/end spaces.

You might perfectly validly say "don't set values in the /Belowtitles aarray to a pair brackets with two spaces between"; Alternatively, setting a minimum value for BelowtitleFontSizes or similar might be worthwhile to prevent the crash.

[jdaw1]

You might perfectly validly say "don't set values …"

I would not say any such thing. It should work.

It was a minor problem. In outputting to the log, a number was being cvsed into a string that was one character too small. Fixed.

Thank you for the clear bug report. Please re-test.

[PhilW]

Thank you for the clear bug report. Please re-test.

Fix verified.

[jdaw1]

New version. The code did some checks for errors. Over time this had grown into a disorganised and incomplete part of the code. Now improved.

[jdaw1]

I acknowledge the bug apparent on page 139 (pre-pour, CáF80 aus Portugal) of the draft of the placemats for the 1980 Horizontal in Leverkusen. Page 142 (pre-pour, SW) has a similar problem.

Expect repair within a few weeks.

[jdaw1]

The joy of a post-whisky shower: the problem was a factor of two, and I realised just where. Fixed.

[jdaw1]

After the GC + SW + QH triple vertical on Thu 17 Nov 2011, DRT asked that there be extra paper between tasters’ sets. He then suggested that this could be my placename page. So JDAW placename, JDAW glasses, JDAW TNs, then the next person’s same.

My thinking is as follows.

• I could add an extra page, marked with my name, with no other function. The wastage rankles.

• Or it could be the placename, as DRT suggested. But RAYC prints the placenames to card, so having them non-consecutive would complicate his printing.

• Or alternate sets (alternate people, so to speak) could be rotated by 180°. But would that be sufficiently different for the task at hand?

What do others think?

[jdaw1]

For the GC + SW + QH triple vertical on Thu 17 Nov 2011, RAYC made several similar versions of the placemats, and then overlapped the printouts to simulate the following A3 arrangement.

Of course this overlapping of multiple copies is unacceptable.

Currently the array parameter PermittedPackingStyles may contain any of (and must contain at least one of) /PseudoHexagonal, /SquareGrid, /RectangularDislocation, /RectangularDislocationV, /TwoRowsOrTwoColumns, /GaiaElegant, /Gaia, or /Irregular or one of its variants. None of these do quite what RAYC required.

The proposal is to allow PermittedPackingStyles to contain an array, at least as long as the number of glasses on the page. That array would contain sub-arrays of locations, [ x y ]. My code would then choose the radius and separately scale the x and y directions such that things fit as snugly as possible, obviously subject to the other upper bounds on the radius. That gives the technical user a lot of control over the rare complicated cases, whilst the usual name parameters still cope with the vast majority of arrangements that could be wanted.

In the particular case of the GC+SW+QH tasting, the element of PermittedPackingStyles could have been [ [0 2] [2 2] [4 2] [6 2] [0 1] [3 1] [6 1] [0 0] [3 0] [6 0] ]. Observe that this example assumes that positive y points north. This echoes the usual PostScript convention; but conflicts with the usual page arrangements in which glasses with a small WithinPage are at the top.

Thoughts? Comments? Views on which direction positive y should be? Bottle of Taylor 1977?

(This post the last on this page. Please could the first to reply to it quote it, except this line.)