Hello Robert,
No problem at all, regarding the delay. Thank you for notifying on the build. I was able to test it out and the initial import seems to mostly work. I did notice that:
1) The logical values like IFFLOW are not being imported, i.e. if the value is True, the checkbox is not ticked. This seems to affect the OUTPUT field values too.
2) I enforce the Logical values and when I write out the new .rea file, I see values of 'yes' in place of 'T' for the Logical values. I haven't been able to run the example, but I think it would fail since Nek5000 may not interpret 'yes' properly?
3) This is more of a cosmetic issue. I create a Nek5000 Launcher and the Execution Path in the 'Hosts' section, already has a default path that seems to be an artifact. Would it be better to just leave it blank?
4) When I setup everything and click 'Go!', I get a runtime error that './nek5000' does not exist. From what I understand by going through the Nek5000 manual, we need to do a makenek first which generates the nek5000 executable. This is then used by the 'nek' script/executable.
5) Another cosmetic issue. Repeated instances of launching the job, causes more stderr and stdout files to accumulate in the 'Files' dialog box under 'Resources'.
I understand each set of them correspond to a particular job instance but currently, they are all listed flatly. Perhaps listing each set of files under an icelaunch id might help?
Hope this helps. Please let me know whenever you want this to be re-tested.