<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
It has just been pointed out to me that we use a TDOCn header with the documentation for the column (which I think is a local extension maybe?) and the comment being long was an alternative source of information for the user. We will drop the long comment for
TTYPEn and continue to use TDOCn.
<div><br>
</div>
<div>— </div>
<div>Tim Jenness<br id="lineBreakAtBeginningOfMessage">
<div><br>
<blockquote type="cite">
<div>On Feb 25, 2025, at 08:02, Tim Jenness <TJenness@lsst.org> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<br id="lineBreakAtBeginningOfMessage">
<div><br>
<blockquote type="cite">
<div>On Feb 25, 2025, at 07:16, Seaman, Robert Lewis - (rseaman) <rseaman@arizona.edu> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">Hi Gregory,<o:p></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">As folks can infer from my ancient comments, I’m leery of relying on such fiddly features, and I also had nothing to do with whatever wording of either CONTINUE or “type long-string”
in the FITS standard.<o:p></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">What I’m wondering is whether Rubin or SPHEREx are really using CONTINUE – specifically, that is, with mandatory or reserved keywords. What is the use case?<o:p></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div>
</div>
</div>
</blockquote>
<br>
</div>
<div>The use case is people being verbose in the COMMENT attached to the column name.</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>TTYPE15 = 'deblend_peakId&' / ID of the peak in the parent footprint. This is</div>
<div>CONTINUE '&' / not unique, but the combination of 'parent'and</div>
<div>CONTINUE '&' / 'peakId' should be for all child sources. Top</div>
<div>CONTINUE '' / level blends with no parents have 'peakId=0'</div>
</div>
<div><br>
</div>
<div>Astropy almost manages to read that back okay but somehow puts the last line of the comment at the start of the comment.</div>
<div>This is an attempt to make the table definition a bit easier to understand if someone is looking at the header. Not sure what our alternative options are though.</div>
<div>All we can think of is adding a `HIERARCH TTYPE15 COMMENT` card explicitly with that comment text in as a long string.</div>
<div><br>
</div>
<div>—</div>
<div>Tim Jenness</div>
<div>Vera C. Rubin Observatory</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>