ASK+, ASK- P Flag

I'm trying to understand the behavior of the ASK+/- P flag. I've written a fairly lengthy procedure where repeat is a necessary function but in the Post Test dialog box, the repeat option is greyed out. I've tried enabling and disabling the P flag as well as inserting TARGET -p FSC but to no avail. Is there another flag that controls the feature?

Groups:

Comments

1488999028

Solved it. There was an ASK-

Solved it. There was an ASK- Z flag in the string. I yanked it and now it works. I can't find a reference for that flag in my manual. What does that one do?

1426003224

P controls how the Repeat or

P controls how the Repeat or Cancel buttons cause the Run Time to behave.

Z controls whether the Repeat option is available at all.

 

The reason some people disable the Repeat button is that using Repeat rather than Cancel stores the previous result in the database if you're re-running the same test due to a faulty connection or similar issue.

When you set +P, if you are clicking Repeat/Cancel on a line that is NOT a MEMC or MEMCX, the procedure restarts at that exact line. For MEMC or MEMCX lines, if you are in a version after 7.2, MET/CAL acts as if you are set to -P, unless you do a manual override in the ini file. With -P, it goes back to the first line in that test (so if the line is 15.023, it will restart at 15.001) unless there is a TARGET or TARGET -p after that in the test, resulting in it restarting there instead.

+Z enables the Repeat button. -Z disables it.

1426003224

Is repeat the best way to

Is repeat the best way to accomplish what you're doing, by the way? Would a loop of some kind be more efficient so you don't have to click repeat every time?

1488999028

Well, the repeat option isn't

Well, the repeat option isn't critical to the test itself. It's just very easy to connect a module incorrectly and since the entire procedure takes about 4 hours to run, not having the repeat option to redo a test that got physically connected incorrectly is rather troublesome. 

1426003224

Sounds like cancel is more

Sounds like cancel is more what you're looking for, then. Repeat will keep data from when it was connected incorrectly.

1488999028

Won't cancel terminate the

Won't cancel terminate the procedure?

1426003224

Oh, no, it's just like repeat

Oh, no, it's just like repeat but it overwrites a failure with new data instead of keeping both records.

1426003224

From the help file in version

From the help file in version 8.3.2:

Cancel

Selecting Cancel is the same as Repeat (see above) except that when the operator chooses Cancel, the result of the canceled test is not saved. As with Repeat, the procedure step on which execution resumes is controlled by the current setting of the ASK ‘P’ flag.

The Post Test Cancel button can be disabled (grayed out) by not setting the ASK ‘X’ flag in the procedure. A parameter ask_x_default in the [startup] section of the MET/CAL initialization file metcal.ini controls the default state of the ASK ‘X’ flag.

  • If ask_x_default = yes (or +), then the ASK ‘X’ flag will be set by default in a procedure that does not specify otherwise. This means that the Post Test Cancel button is enabled by default.
  • If ask_x_default = no (or –), then the ASK ‘X’ flag will not be set by default in a procedure that does not specify otherwise. This means that the Post Test Cancel button is disabled by default.

Default condition, as delivered: ask_x_default = yes.

1488999028

Wow! That is an amazingly

Wow! That is an amazingly unintuitive word to use to describe that feature. Thank you for that information. Even my more experienced colleague who can do Met/Cal scripting did not know that.

1426003224

Yeah, as I was typing my

Yeah, as I was typing my reply yesterday, it did seem curious to use that particular word. Would probably be more accurate to use "Retest" or something like that.