Discard ProcessModelPostStep from result

[caviars]

Hi

I'm creating a process model with ProcessModelPostStep to update the sequence progess in my OI (using PostUIMsg). However the ProcessModelPostStep is recored into the test record. I tried to disable by checking the "Disable Result recoding" option from properties but I still store the ProcessModelPostStep into the test record.

The reason i don't want it to be stored is because it make the records files bigger (by almost 50%). I'm also parsing the record file to server and it make the process time longer.

I'm using TS3.1

[icastillejos]

I understand that you disabled results recording for the step,

how about disabling results recording for thw whole ProcessModelPostStep sequence?

[caviars]

Thanks for the reply.

I disabled the record option for all the steps inside the ProcessModelPostStep callback and the callback itself. It did reduce the size of the XML report.

Another problem is that the structure of the XML record changed (at lower level). This prevents my result parsing software (mostly hard coded) to work properly. Is there any way to add ProcessModelPostStep callback without changing the original XML record structure (NI SequentialModel XML record). Currently i'm using a standard NI sequentialModel and i'm adding the ProcessModelPostStep callback as an extra callback.

I'm also experiencing cases (a few) where the the result window failed to display XMl result. It only occured when i'm using the horizontal stylesheet.      

[AndrewMc]

Hey caviars,

When adding ProcessModelPostStep callback to your process model, this should not be added to the results list (and thus should not show up in the report).  Please post the process model that you have modified.

[caviars]

Actually what i mean ProcessModelPostStep is recorded into test record is that it that the callback changes the structure of the XML. The steps inside the callback are not recorded. It will looks the same if you open in in IE but the structure changed at low level (open with notepad). Is this normal because if it does i need to modify my parsing SW. 

I'm not really good at explaining so I'm attaching some simple text document to highlight the differences. 

Please forgive me for my poor explaination.

[AndrewMc]

caviars,

Again, will you please post the process model that has the ProcessModelPostStep callback overriden?  If you do not want to post the process model you have been working with, make the modification to a process model such as SequentialModel.seq and post that.  Overriding the ProcessModelPostStep callback in your process model should not affect your report.

[caviars]

Hi Andy

Thanks for your feedback but for some reason I cannot give you the process model. However I created another process model for your reference. Basically it is a standard NI sequential Model. I only added the ProcessModel PostStep Callback and disable the callback result recoding by checking the "Disable result recoding for all step. There is no step inside the PMPostStep Callback

If I run any sequence file with this PM the XML result structure (for the steps) will be different from the normal NI PM (.without PMPostStep).That is why I need to know whether this is expected since my parsing software needs to read the steps and parse them into another format.

Please note that the changes only occured at low level. Try open the XML report generated using text editor and you can see (at least i did) that the way each steps are recorded is different (not the whole XML structure). The difference is more obvious if the step is a multiple numeric limit test

Details related to ProceeModelPostStep will be added to each step.

The XML result  with PMPostStep something like this
     PostStepDetails (Status)---> Step Details(Time, Name, Type, Status) ---> Step Measurements details (All the measurements)
     WIthout PM postStep
     StepDetails(Status)  ---> Step Measurements Details(All the measurements)  --> Step Details (Time, Name, Type)
   
For your information, if I open the XML using IE the result XML will looks the same.

Thanks 

[AndrewMc]

Hey caviars,

I understand your dilemma.  The additional tag does show up in the xml for the report.  While this does not affect the report appearance, it seems to have an effect on your parsing tool. 

There are two options possible to achieve the removal of this additional tag - although it is not an easy feat. 

1) Notice that an additional variable is added to the ResultList for the client sequence - ResultList[i].TS.ProcessModelPostStep property.  The first option is to programmatically remove this property.  The caveat to this method is that each subsequence has its own ResultList that would need to be modified in this regard.  Thus, you would have to essentially iterate through all of the elements in the ResultList, removing each instance of that property, and check if that result has another ResultList within it (in order to remove each instance of the ProcessModelPostStep property).

2) Programmatically remove the instances of that header after the report has been generated.  There exists a CVI project that contains a function for removing certain XML tags.  I do not believe the code would help you significantly, but you might be able to build upon what's there.

Of course, your parsing utility could be modified to account for the structure or be more modular to account for any deviations (except that you're also concerned about size).