Changes between Initial Version and Version 1 of Ticket #274


Ignore:
Timestamp:
Jun 16, 2020, 2:13:34 PM (16 months ago)
Author:
pesei
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #274

    • Property Owner set to pesei
    • Property Status changed from new to accepted
    • Property Milestone changed from to FLEXTRA 6
  • Ticket #274 – Description

    initial v1  
    1 A problem that occurs with FLEXTRA is that the output file can contain non-ascii characters. This happens because the variable datestring(1:24) is written out, but the non-standard call which would have filled it with today's date is commented out, meaning that the variable is never initialised. The simplest fix is to edit opencetoutput.f, openflightoutput.f and openoutput.f . In each case, find the comment
     1A problem that occurs with FLEXTRA is that the output file can contain non-ascii characters. This happens because the variable `datestring(1:24)` is written out, but the non-standard call which would have filled it with today's date is commented out, meaning that the variable is never initialised. The simplest fix is to edit `opencetoutput.f`, `openflightoutput.f` and `openoutput.f` . In each case, find the comment
    22
     3{{{
    34C      call fdate(datestring)
     5}}}
     6
    47
    58and immediately after it insert the line
    69
     10{{{
    711      datestring="----- Not Available ----"
     12}}}
    813
    9 One could just remove the print statements that print out datestring(1:24) but the above suggestion keeps the layout of the output file identical to how it was before, while ensuring that it is pure ascii.
     14
     15One could just remove the print statements that print out `datestring(1:24)` but the above suggestion keeps the layout of the output file identical to how it was before, while ensuring that it is pure ascii.
    1016
    1117The non-ascii characters are benign to some users, but can cause trouble for anyone trying to read the FLEXTRA output into python 3.
hosted by ZAMG