Eliminate Report entry for Subsequence path.

[Mikef]

I'm trying to clean up the Report Output but have one problem left. I have a "Library" sequence file that contains a number of functions, none of which enters anything into the report. (Run Options "Record Results" is unchecked.) There is a special "Parameters.sReportString" that is passed back to the calling step that generates any string (Failed or Passed) that is entered into the report from the Subsequence call step. I'm using "On-The-Fly" reporting.

My report looks like this:

Notify that Input Filter Time is Called: Skipped

Begin Sequence: ReadWriteParameter
(C:\TestStand\LIBRARY\Library Functions\lib_Functions.seq)


End Sequence: ReadWriteParameter

Read:tag_CLC_SET_POINT(1): Passed
Display
Locals.sParameterValue: Skipped

The Question is: How do I get rid of the "Begin Sequence:(...)" and "End Sequence" lines and extra CRLFs?

These lines are entered into the Report Body from the "reportgen_html.seq" or "reportgen_txt.seq" in the ProcessOTFStepResult sequence in the "Process Step Result" ActiveX call.

I want the lines to be entered Normally for ALL cases EXCEPT when the "lib_Function.seq" is called. I can't precondition the step to NOT run because I do want the other results for the subsequence call step to be entered in the report.

Any ideas?

Mike

[Anand_Jain]

Hi Mike
If I understand your problem correctly you would not like to record results from the call to lib_Functions.seq. The can be done by unChecking the "Record results" checkbox for that sequence call under the "Run Options" in the properties dialog.

I hope this helps
Regards
Anand Jain
National Instruments.

[Mikef]

No, that is not correct.

I DO want the Pass/Fail results of the subsequence call to be recorded, just NOT the Begin/End Sequence path lines. (Clutters up the report and makes it harder to read.)

If I uncheck the "Record Results" then I don't get ANY results.

Mike

[Anand_Jain]

Hi Mike
It looks like you would like to remove the following 2 strings from the the report.
1. Begin Sequence: ReadWriteParameter (C:\TestStand\LIBRARY\Library Functions\lib_Functions.seq)
2. End Sequence: ReadWriteParameter

There lines are added when a call is made to "AddSequenceResultToReport" in ReportGen_Html.seq or ReportGen_Txt.seq.
you can remove the above lines from the report by adding a precondition to "AddSequenceResultToReport", "Add Sequence File Path" and "Add Sequence End Marker" to check to see if the name of the sequence is NOT "ReadWriteParameter".

something like

Parameters.Result.TS.SequenceCall.Sequence != "ReadWriteParameters" and that will not add it to the result just for "ReadWriteParameter" sequence.


If you are using the DLL version to generate reports then you will need to modify "AddSequenceCallResultToReport_Html" and "AddSequenceCallResultToReport_Txt" in c_report.c file under \Components\NI\Models\TestStand Model\ to check for the "sequenceName" (Variable in the function which stores the sequence name) != "ReadWriteParameter"
You will then need to rebuild the ModelSupport2.dll in CVI.

I hope this helps.

Regards
Anand Jain
National Instruments.

[Mikef]

Thanks Anand, makes sense I guess. I think that I can struggle through making the necessary changes. (I'm not a seasoned CVI - or C programmer, but I can get help here locally.

One more quick question on this, If I build ModelSupport2.dll, if I put it in the [NI]User\Models\TestStandModels directory, will it be used instead of the file in the "NI" directory? I am using a custom Process Model in the "User" directory.

Mike

[Anand_Jain]

Hi Mike

TestStand uses search directories to find out which file to load and use. The search directories can be configured by configure -> search directories.
In that make sure that "User Coponents directory" is before "NI components directory" and both of them are checked.
Then if you rebuild ModelSupport2.dll and put it in your \Components\User\Models\TestSandModels folder it will use it instead of using the NI directory.

I hope this helps.
Regards
Anand Jain
National Instruments.

[Mikef]

Anand,

Thanks for the suggestion. I did install CVI and tried to debug the function that you pointed out, but found that I couldn't remove the lines. They seemed to be entered in the "Process Step Result" ActiveX call in the "ProcessOTFStepResult" sequence in the "reportgen_html.seq" file.

So my attempt at a solution was to add a step AFTER the "Process Step Results" step (where the Locals.ReportBody is generated) and REMOVE the unwanted lines from the Locals.ReportBody. The Precondition does a "Find(Locals.ReportBody, "\lib_Functions.seq") - the lib_Functions.seq is the file that I DON'T want in the report output. But for some reason, even though I've shortened the Locals.ReportBody string, the original lines are still
entered into the report, I can't figure out why contents of the Locals.ReportBody are being bypassed in the "Set Report" step farther down the sequence.

Mike

[Anand_Jain]

Mike
Are is "conserve memory" option in report options dialog checked ?

Anand Jain
National Instruments.

[Mikef]

Yes it is. I'm creating tests that will run a long time, 12 to 24 hours would not be unheard of, and running through LOTS of steps. I don't see any reason to maintain the steps for a long period of time.

How much of an effect will that have?

Mike

[Anand_Jain]

Mike
If you are using conserve memory option then the results are save during a call to TSOTFRG.dll server. The source of this server is shipped with TestStand under \Components\NI\Models\TestStandModels\TSOTFRG

If you have VC then you will be able to build a new version of the server.

In the file TSOTFRepGen.cpp you can modify "SetSequenceHeaderAndFooter" function to not add the the header and footer info to object for the given sequence. This object is used to generate the report.

Couple of issues.
1. You will need VC 6 with Service Pack 5
2. Make a copy of the TSOTFRG folder in the \user folder under the same path before you make changes to copy in the use
r folder.

If you do not have VC 6 please contact support and they should be able to help you .

Regards
Anand Jain
National Instruments.