`fre run`: configure-ascii-files

[singhd789]

Write FMS ascii input files to run directory

• set ascii argFile name: line 1065 in runscript template
• write to ascii argFile: lines writing to ascii input file: 1080 - 1127 in runscript template
• run ascii argFile: line 1137 in runscript template
• find example of ascii file
• help?:
  • am5f8d0r1/c96L65_am5f8d0r1_amip/ncrc5.intel23-classic-prod-openmp/state/run/c96L65_am5f8d0r1_amip.o135222971.output.stager.19870101.A.args
  • /gpfs/f5/gfdl_f/scratch/Dana.Singh/volatile/am5/am5f8d0r1/c96L65_am5f8d0r1_amip/work/c96L65_am5f8d0r1_amip.o135222971/output.stager/gpfs/f5/gfdl_f/scratch/Dana.Singh/volatile/am5/am5f8d0r1/c96L65_am5f8d0r1_amip/ncrc5.intel23-classic-prod-openmp/ascii/19870101.ascii_out/19870101.diag_integral.out

[singhd789]

Note: this issue will probably be refactored or removed as these ascii argFile mainly just contains variables being set - so they can be options or information passed to the output stager

[singhd789]

Note: ascii argFiles mainly just container variable set up, which can be done in the cylc workflow itself. A specific tool to create these files is probably not needed