|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
[fitsbits] Start of the CONTINUE keyword Public Comment Period
The CONTINUE convention, however, is different in providing a more
general capability that could be used, for instance, within any other convention. I don't think I emphasized this point enough. A continuation convention, whether the one on the table or any other, changes the meaning of other conventions. One could, for instance, recast a CHECKSUM keyword: CHECKSUM= 'nADTnADQnADQnADQ' / ASCII 1's complement checksum as: CHECKSUM= 'nADTnADQ& ' / ASCII 1's complement checksum CONTINUE 'nADQnADQ' This would apply to your favorite string valued keyword as well. The example above would be a legal continuation but an illegal checksum value. (More than illegal for this example since the byte ordering needs to be preserved for the zeroing feature of the checksum to work.) Perhaps we need a broader discussion of the boundaries of usage for conventions. I suspect the issue of long values for string keywords remains an issue for the trusty old standards process, not the avant garde registry. Continuation is only one possible way to handle long strings. Rob |
#2
|
|||
|
|||
[fitsbits] Start of the CONTINUE keyword Public Comment Period
Rob Seaman writes: The CONTINUE convention, however, is different in providing a more general capability that could be used, for instance, within any other convention. I don't think I emphasized this point enough. A continuation convention, whether the one on the table or any other, changes the meaning of other conventions. One could, for instance, recast a CHECKSUM keyword: CHECKSUM= 'nADTnADQnADQnADQ' / ASCII 1's complement checksum as: CHECKSUM= 'nADTnADQ& ' / ASCII 1's complement checksum CONTINUE 'nADQnADQ' This would apply to your favorite string valued keyword as well. The example above would be a legal continuation but an illegal checksum value. (More than illegal for this example since the byte ordering needs to be preserved for the zeroing feature of the checksum to work.) Bill, could the convention be clarified to indicate that CONTINUE should not be used for keyword values that could fit in a single FITS card? And/or, that CONTINUE should be avoided for standard FITS keywords? Craig |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[fitsbits] Start of the CONTINUE keyword Public Comment Period | William Pence | FITS | 2 | July 16th 07 05:42 AM |
[fitsbits] Start of the CONTINUE keyword Public Comment Period | Rob Seaman | FITS | 0 | July 12th 07 05:21 PM |
[fitsbits] Start of the CONTINUE keyword Public Comment Period | Walter Jaffe | FITS | 0 | July 12th 07 10:15 AM |
[fitsbits] Start of the CONTINUE keyword Public Comment Period | Peter Teuben | FITS | 0 | July 11th 07 10:37 PM |
[fitsbits] Start of the CONTINUE keyword Public Comment Period | Thomas McGlynn[_2_] | FITS | 0 | July 11th 07 09:57 PM |