Community
Participate
Working Groups
Right now the ManagedFile object can either point to the path of a pre-existent file, or it can have a string contents. These contents are either resolved against the environment or not, and when not, it is assumed that it will be a reference to an attribute or property. It would make more sense to change the content possibilities to the following: 1. reference to the value of another property or attribute 2. list of <line> types containing <arg> types, as in the <script> type. This makes the script type a subtype of managed file (which it implicitly is), and allows more control over the resolution of the contents.
Created attachment 198055 [details] XML Definition for use case example Demonstration of feature
Created attachment 198056 [details] Screenshot of Launch Tab (1)
Created attachment 198057 [details] Screenshot of Launch Tab (2)
the input file is staged to "input" in home directory in this example. Inspection after run submission: [arossi@honest1 ~]$ cd input [arossi@honest1 ~/input]$ ls namelist.input [arossi@honest1 ~/input]$ cat namelist.input &run runname = 'cloud2d', runlabel = 'cloud2d', simtime = 7200., dt = 10., nsmall = 12., nx = 181., nz = 36., xdomain = 180000., zdomain = 17500., ugrid = 14., &end c &dump tprint = 100., tplot = 300., tsave = 600., &end c &init_params tbble = -15., xcntr = 18000., zcntr = 3000., xrad = 4000., zrad = 2000., sndtype = 0, inittype = 0, &end
