iraf.net

When running the standard task in command mode (I use the kpnoslit one), if "interact=yes" and the output is rather ugly because it's missing newlines in key spots.For instance, with an image with two apertures,[code:1:7ab90b5beb]standard ("file.ms", "output", "l2415", 1., 1., 12.210, "V", "G0", "YES", samestar=yes, beam_switch=no, apertures="", bandwidth=INDEF, bandsep=INDEF, fnuzero=3.6800000000000E-20, extinction="extinction.dat", caldir="onedstds$ctiocal/", observatory="esovlt", interact=yes, graphics="stdgraph", cursor="")[/code:1:7ab90b5beb]the output is[code:1:7ab90b5beb]file.ms[*,1,1](1): flux_standard
file.ms[1]: Edit bandpasses? kpnoslit>[/code:1:7ab90b5beb]This is slightly better or worse depending on the the combination of "interact" and "answer" used. Now interact is yes and answer is "no" for the same two aperture image:[code:1:7ab90b5beb]file.ms[*,1,1](1): flux_standard
file.ms[1]: Edit bandpasses? file.ms[*,2,1](2): flux_standard
file.ms[2]: Edit bandpasses? kpnoslit>
[/code:1:7ab90b5beb]The behavior is somewhat better if the task is run using an "epar".Basically, it would be good if the output looked nice regardless of the choices of "interact" and "answer" and for differing types of inputs.Also, if interact is "yes" and answer is "no", the task never prompts the user even though ostensibly they've only answered "no" to the first bandpass.Jason

The problem here is that you are putting the answer parameter on the command line. If you did not include it then there would be a query to the terminal and you would type an answer.I guess you are wanting to force the answer to always be yes and not have a prompt at all. This is reasonable. However, the task is sufficiently old that it was not design correctly for this behavior. So I'm afraid there isn't anything you can do and this task is unlikely to be updated anytime soon.Frank Valdes