Wrapper for run_glm to override nml settings without writing a new nml

[jsta]

I could see some utility in being able to override nml settings without manually writing a new nml file. Then you wouldn't have so many nml files cluttering up the working directory. One way this could work is to:

• copy the existing nml file to a tempfile
• overwrite the specified portion of the nml file with write_nml
• redirecting run_glm to the modified file

run_glm(sim_folder = ".", ...)

where the ... is a pass-through to set_nml

Is this a bad work-flow idea?

[lawinslow]

Hmm, interesting idea. To keep the dependencies simple, it might be better to create a function in glmtools that takes an NML object, writes it, and then runs GLM against it. Maybe run_nml. That function would live in glmtools and wrap write_nml, set_nml, and run_glm. That would prevent us from having a dependency point GLMr -> glmtools.

run_nml(nml, run_dir=',', ...)

Maybe with ... pass-through to set_nml.

[jordansread]

Yeah, I've always wanted something like that too...